Windows 10: KB4100347 causes Windows boot up problem

Yesterday, I had problems with Windows Update KB4100347. The update seems to be installed succesfully, but after the Windows login screen, I get a white screen with a scroll box and some strange text. Definitely not the expected desktop background with the icons and the taskbar. You are stuck at this point. This is the second time I get this kind of error after a major Windows update. The last time was with Windows 10 April 2018 update. I then managed to undo the installation, and block the update right after. It seems that this update was succesfully installed later on. This time I did the same (revert the update and block it). Except that this is annoying, I wonder if this is something to be concerned about. Is it a problem with my computer, or is it a problem with the update? As I said, this is only the second time a Windows update fails. You would expect from Microsoft that they don't offer unreliable updates.

:)

 

Windows 10 Boot times issue


The two are linked as you've observed and as I mentioned.

What puzzles me is the change after the power outage, which would suggest some form of corruption, which does not seem the case.

The other thing that can cause slow boot times are certain updates. For example this update:
KB4100347 Intel microcode updates for Windows 10 v1803 - September 13 - Page 9 - Windows 10 Forums

So I'm now wondering if the change in boot time is actually unrelated to your power outage. Using WPR as @zinou suggests is then the next step.

 

Windows 10 1709 System Restore problems...


That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

ughhh! BSOD on boot

I guess my computer BSOD on boot right before getting to windows. not sure what the problem is though, everything is stable.

It gave me a list of two files in windows that could have caused the problems