Still?

Hi,
My PC (win 10 pro 64bit) never boots after any update. I just see a black screen with those little white dots rotating on the lower half of the screen and they do that for hours. That nonsense started with the anniversary update a month or so ago.
I have to turn the PC off and on and go through the BIOS setup until it finally finishes booting.
After that it boots every time until after the next update.
Can someone give me any advice?
Thanks,
Ed

I ran that sfc /scannow thingybut it did not yield any results.

As to the HD led, it flickers irregularly, sometimes it's bright for a second or two and then it goes back to flickering. Looks like it's doing something meaningful but heaven knows what.

Hi,
My PC (win 10 pro 64bit) never boots after any update. I just see a black screen with those little white dots rotating on the lower half of the screen and they do that for hours. That nonsense started with the anniversary update a month or so ago.
I have to turn the PC off and on and go through the BIOS setup until it finally finishes booting.
After that it boots every time until after the next update.
Can someone give me any advice?
Thanks,
Ed

It happened to me too. The solution for me was "disable fast Startup"

Fast Startup - Turn On or Off in Windows 10 - Windows 10 blog

Why You Might Want to Disable Fast Startup

Sounds awesome, right? Well, it is. But Fast Startup also has its problems, so you should take the following caveats into consideration before enabling it:

• When Fast Startup is enabled, your computer doesn’t perform a regular shut down. Since applying new system updates often requires a shutdown, you may not be able to apply updates and turn your computer off. Restart is unaffected, though, so it still performs a full cold shutdown and restart of your system. If a shutdown doesn’t apply your updates, a restart still will.
• Fast Startup can interfere slightly with encrypted disk images. Users of encryption programs like TrueCrypt have reported that encrypted drives they had mounted before shutting down their system were automatically remounted when starting back up. The solution for this is just to manually dismount your encrypted drives before shutting down, but it is something to be aware of. (This doesn’t affect the full disk encryption feature of TrueCrypt, just disk images. And BitLocker users shouldn’t be affected.)
• Systems that don’t support hibernation won’t support Fast Startup either. Some devices just don’t play well with hibernation. You’ll have to experiment with it to see whether your devices respond well or not.
• When you shut down a computer with Fast Startup enabled, Windows locks down the Windows hard disk. You won’t be able to access it from other operating systems if you have your computer configured to dual-boot. Even worse, if you boot into another OS and then access or change anything on the hard disk (or partition) that the hibernating Windows installation uses, it can cause corruption. If you’re dual booting, it’s best not to use Fast Startup or Hibernation at all.
• Depending on your system, you may not be able to access BIOS/UEFI settings when you shut down a computer with Fast Startup enabled. When a computer hibernates, it does not enter a fully powered down mode. Some versions of BIOS/UEFI work with a system in hibernation and some do not. If yours doesn’t, you can always restart the computer to access BIOS, since the restart cycle will still perform a full shutdown.

I have turned off fast startup.
Waiting to see what happens next time an update runs.
Thanks Guys.

Do you have another hard disk having an active partition connected since that can confuse and delay the boot process?

Well, yes indeed, I do have a back-up HD installed that still has the system installed.
But the regular everyday boot is fine, just not after an update.

That disk might well have another active partition. You can use MiniTool Partition Wizard to change it to inactive. Worth a try?

I'll do that, thanks a lot.
Ed

I'll do that, thanks a lot.
Ed

Were you able to get this resolved? I'm having the same issue.

I don't know yet. I may not have had an update in the meantime.