Slashdot Mirror

← Back to Stories (view on slashdot.org)

Broken Windows 10 Update Causes Reboot Loops For Some Users

Posted by Soulskill on from the clippy's-revenge dept.

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."

4 of 203 comments (clear)

  1. No problems here by Anonymous Coward · · Score: 5, Funny

    What reboo..........

  2. Forced Updates-- What could POSSIBLY go wrong? by Falconnan · · Score: 5, Insightful

    No update cycle is perfect. Problems happen. But being unable to refuse an update, or roll it back, etc., is a recipe for problems galore. The wise thing for Microsoft would be to establish four basic categories of update: Security, Important, Optional, and Driver. Security updates being mandatory makes sense given the general user's overall lack of understanding. Important could be major bug fixes, feature repair, that kind of thing. Drivers should be given a warning label and made completely optional and non-automatic. Optional is optional. "We want a unified support environment" does not help the end user who cannot do his/her homework.

    1. Re:Forced Updates-- What could POSSIBLY go wrong? by drinkypoo · · Score: 5, Informative

      No update cycle is perfect. Problems happen. But being unable to refuse an update, or roll it back, etc., is a recipe for problems galore.

      You can do all of those things, although the means are extremely non-obvious.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Forced Updates-- What could POSSIBLY go wrong? by gstoddart · · Score: 5, Interesting

      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.