System with DW was acting a bit funny so I rebooted it. After doing an update or two, it ended up here.
It’s been 25 minutes right there at 100%. The dots continue to circle, but no other screen activity. Occasional disk light activity.
How long is the longest time anyone has ever seen a PC like this actually finish on its own?
Two hours. I stopped paying attention to it because I was annoyed and a couple hours later from across the room saw it reboot out of the corner of my eye. But that was literally the only time ever that one finished once it hits that level.
Is it one of the big feature updates? Those things are notorious for taking forever and making you think they've failed.
Just finished. About 85 out of 90 minutes at 100%.
I think I would have been (slightly) more patient if it had been stuck on 0%. But 100% makes you think “ok it’s done at least, what am I waiting for?”
I wait very little time, but I am also a rebel. I never right click to safely remove a USB drive, and never actually read the terms of service. Yeah, I am that rebellious....
I usually try to wait until it is time to sleep before agreeing or scheduling an update.
I know it isn't always avoidable, but starting at that stupid twirly circle for hours is the worst.
I often let it kick off an update when I leave it for the day, and it always seems to be situated the next morning.
I usually try to wait until it is time to sleep before agreeing or scheduling an update.
Me too. In this case I didn’t agree to anything, just one of those “quick reboots” you might do when troubleshooting.
To be fair to Microsoft, I did nod off once or twice after being hypnotized by the blue screen of dots, which is what they intended to have happen to those who stare too long...
I am looking at a Windows XP machine that has been updating for 2,910 days.
At a certain point it is better to just hard reboot and suffer the consequences, particularly if you have to, ya know... get work done at some point. My threshold for stuck at 100% is about 30 minutes.
I almost always wait - coming from an IT background I've seen my fair share of PCs that haven't booted after botched updates.
I have noticed recently with some of the big updates that have come out your PC will often get stuck trying to update certain parts and is waiting on a reboot. I had one the other day that was like this. After several forced shutdowns all was good. On the Windows 10 machines we put into the field we go into the "Local Group Policy Editor and tell the system to "download updates and notify to install." Otherwise you can't stop Win 10 from rebooting after an update and a production machine will always reboot and the most inappropriate time.
Ask questions and get answers to your physical security questions from IPVM team members and fellow subscribers.
