Slashdot Mirror
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."
Ideally not a true fix, but a workaround, at least.
At least it doesn't render the users' computers inoperable.
I got the update just fine... but the Start Menu Item limitation (512 menu items max) is still not fixed with this update.
Also, the Store and "Movies & TV" windows keep popping up randomly (I believe when I watch something with media player). Very annoying.
One more thing... why the heck is the titlebar/menu coloring a hot mess? All white? There is a theme out there called "colors" that kinda-sorta fixes the issue, but it won't stick the accent color I assigned. At least it makes the desktop less visually messy. It seems that every iteration of Windows has given users fewer and fewer options to change colors and details of the user interface... while making the supplied themes progressively worse. I should be able to make Windows 10 look like XP, if I want to (I don't want to, really).
For the most part, Windows 10 is fine... but annoying leftovers from Windows 8 and this interminable menu limitation is driving me nuts.
This is more about making life easier for Microsoft than it is about giving a damn about users.
When I forcibly uninstalled the update to Windows 8.1 which started pushing Windows 10 at me, one of the things it said it was doing was adding a piece to monitor and evaluate how well system updates are going. Basically gather metrics on how bad they're doing.
Microsoft has decided that it's their computer, that if they feel an update needs to be applied they will, and that if it breaks for some users that's an unfortunate side effect of having your customers doing your beta testing ... but thanks for doing our beta testing.
The trend with computers and electronic devices is for the license to say "you don't own this, and you don't get a say in what we do to it". And people are going to start pushing back when they suddenly find themselves with a broken computer because Microsoft forced an update on them.
Microsoft isn't going to pay to fix it, they're not going to pay for the loss of productivity. They're simply going to say "bummer", and keep doing it.
Which if you or I did that we'd be charged criminally under the computer fraud and abuse act or something similar.
But they have an EULA which says they're allowed to.
Lost at C:>. Found at C.
True, but that "non-obvious" part is the problem. It should be obvious, clearly labelled, and functional. The fact I can edit the registry and not nuke a computer is great. My father or uncle on the other hand... Just lots of "no". Though, really, I suppose I should thank Microsoft for the job security.
Is that it reboots all the time, and you can't stop it, only delay it (and if you're not on your computer 24/7, eventually you'll miss the delay prompt and it will just reboot). I'm obsessive with saving (if there's one thing Windows has taught me, it's to hit control+s after every sentence in a document or email) so I haven't lost work, but countless coworkers have. Yet, they still always have excuses when I offer to install Linux on their computers.
Reading the patch summaries would be nice if most of them weren't a minor variation of "Fixes an issue with Windows on some computers". That's a pretty useless summary.