Broken Windows 10 Update Causes Reboot Loops For Some Users
An anonymous reader writes: The Guardian reports that some early adopters of Windows 10 are finding their computers stuck in a reboot loop after installing a particular update. KB3081424 is a cumulative update, packaging together a group of smaller ones for ease of installation. For some users, the update continually fails to finish installing before issuing a reboot command to the PC. "It downloads, reboot to install. Gets to 30% and reboots. Gets to 59% and reboots. Gets to 59% again and then states something went wrong so uninstalling the update. Wait a few minutes and reboot. Back to login screen," said Microsoft forum user BrettDM. "This happens without fail, every single time."
Microsoft's saga on desktops went like this:
1. We will not make hardware, we only write operating system software, so applications can run.
2. Our OS runs on many hardware configs., so many many applications run on our desktops
3. We own the desktop. We are on a billion devices, but we still don't make h/w, yet we still get to decide how h/w should be built for Windows. We can break h/w, h/w drivers, updates if we choose to. We don't care the OS is insecure, 'cos we are on a billion boxes, and that's all that matters.
4. Oh! So you turn off updates, so we can't force patch our buggy OS? You gave us a bad rep. in the market? Here... Take this 'free' upgrade, and you can't stop my forced updates. We get to a billion devices again.
5. Oh, the forced updates eat your bandwidth, infinite loops crashes??? Your bad... thanks for being our valuable beta tester.
6. What? You're running away to Ubuntu or Fedora to get stuff done? Boo...hooo, why does no one think of me, the great Microsoft? I'm giving you the OS for free, you still don't want it... boo..hooo!!
If you keep throwing chairs, one day you'll break windows....
Idiot. The problem occurs when there are orphaned SIDs in the registry and no real users corresponding. Happens every time in a domain attached PC with Active Directory in every single corporate network. So about let's say 30% of the cases.
Roughly 10 million machines with the problem. Very good I say!
If you keep throwing chairs, one day you'll break windows....