New
#1
getting Windows ready / Don't turn off your computer despite no update
I've had this happen a handful of times on both our machines before. In fact it happened on one just now. Basically I went into Windows update and saw it was checking for updates already. Presumably the scheduled auto process. It took ages to eventually come back and finish the check. There were no updates found. However when I restarted the PC it moved straight into 'getting Windows ready'. I left it half hour but it wasn't changing so I force turned off by holding power button down. I then switched back on and all was back to normal, I did another updates check which finished much quicker and restarted the machine and noted the problem didn't resurface. It seems to be a bug in Windows 10 that manifests itself on rare occasions. There are no updates to install but it seems to get stuck on getting Windows ready. I reckon it may of eventually rebooted if I'd left it long enough but I didn't have hours to spare.
it is rare but I know when it's likely to happen,if checking for updates takes an abnormally long time (several minutes) to complete its check then there is a good chance that upon next restart this 'getting Windows ready' issue will occur. It's as if the computer thinks there are updates and is waiting to install some when in fact none exist and it gets stuck in this phase. But why it happens is over my head. I think there is something in the automatic updates check that tries to happen silently in the background that can cause this. Maybe Windows update server is feeding machines duff information on these occasions. I have actually observed this in three different machines pre and post anniversary update so it was an issue in the previous public build and remains in the current public build. As you can imagine it's extremely irritating for this to happen, and no user wants to be force powering off a machine by holding the power button down to get out of it . That is always a risky solution which can cause corruption but it seems a user has no choice when this bug occurs. I've come to refer to this as the 'phantom updates bug', lol.
unfortunately i cannot remember on which forums but I have seen a fair few users report this happening from time to time. I wonder if anyone on here has observed this though and what they did, did you leave it and eventually rebooted, if so how long did that take? Does anyone have any idea what Windows is trying to do or why this happens?
cheers, Wayne