Okay, like many users I had downloaded the latest (RTM) version of the Windows 8.1 Update 1 and installed it as described in instructions (with all proper restarts after each update, I did not need first update of the four, as I had the March patch installed already). All was fine until I installed the last tiny update - Feature Pack for Windows (KB2937592). The update told me that it needed a reboot (though Wzor description was telling it did not need it). After reboot and logging into the account, my screen went completely blank, it stayed black for a while, until strange start button started appearing in some places on the screen, then all went dark, PC rebooted and then was all normal. Update is listed as successfully installed, so says the Event manager. sfc /scannow showed no corruption. dism also did not need to repair anything. About my Win 8.1 installation: it was Win 8.1 SL 64-bit RTM which later I upgraded to Win 8.1 ProWMC. Only default English language installed. I had all updates installed from Windows Update, including the March patch Tuesday. All GA Rollup updates were installed through WU. I had never used .msi packages on this system before, it was completely clean and nice install. Any guesses? If this is related to the fact that I had SL edition upgraded to ProWMC and this is a bug, then I guess microsoft did screw up with this last tiny feature pack update.
Those symptoms are usually related to some system files not loading correctly for some reason. It could be a driver or hardware issue, but is most likely related to either the updates not installing correctly, or some sort of security program or other custom software interfering with the update process.
I have only Windows Defender. And I am pretty sure no 3rd party software was interfering, unless it is Nvidia Geforce (latest driver)
Description said it did not require reboot at all. After the "normal" reboot, I logged into my account, and when desktop was supposed to appear it went dark and then the 2nd abnormal reboot happened.
Can't exactly remember for this update, but some need a second reboot, before the actual system starts up . EDIT: Equal what the procedure might suggest, this is at least decided by the Update Installer . Still no really normal behavior indeed.