Slashdot Mirror


Vista SP1 Update Locks Out Some Users

Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable. The update loops forever on "Configuring updates: Stage 3 of 3 — 0% complete. Do not turn off your computer." "Shutting down"... restart and loop. Echostorm notes having found traces of what sounds like the same bug in early beta releases of SP1. It's unclear how many users are affected. So far there is no word on a fix from Microsoft.

4 of 410 comments (clear)

  1. It's not on windows update by Megor1 · · Score: 5, Informative

    You can't download SP1 yet from Microsoft, in fact its not due out for weeks...

    --
    Everyone that disagrees with me is a paid shill
  2. That's some keen fucking reporting by sharkey · · Score: 5, Informative

    Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable.

    A forum post from last month about issues with the Vista SP1 Release Candidate (prerelease code, just to let Echostorm know). SP1 does not go out via auto updates until next month, and is only officially available to select system builders and beta testers now.

    It's unclear how many users are affected.

    I counted 5, including the guy who yanked his power cable and trashed his filesystem.

    So far there is no word on a fix from Microsoft.

    It might possibly be fixed in the RTM version of SP1. Who knows? Certainly not Echostorm, who is having a poopie because he hosed his own PC and is trying to drum up a whine-fest about it. Definitely not kdawson either, who posted this because, well, it's kdawson.

    This is taking slashvertisments to the preschool tantrum level.

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  3. Vista SP1 isn't public yet, unless you pirate it. by Coopjust · · Score: 5, Informative

    Vista SP1 isn't available publicly yet, unless you hop on The Pirate Bay.

    Microsoft placed 6 weeks between code finalization and public release for 6 weeks of driver testing; some drivers were not properly written, and MS wanted to work with hardware manufacturers/OEMs to find hardware with problems. Everyone bitched about how technical users should get it early.

    Then these same people download SP1 from an unauthorized source, and bitch when it breaks their system. They downloaded an update without letting Microsoft work the kinks out, and they didn't get the update from MS. No automatic download was involved in this.

  4. ASUS P5N-E by nick_davison · · Score: 5, Informative

    It may well not be SP1.

    A very large number of owners of ASUS P5N-E motherboards are reporting the same issue simply with recent updates. It's quite likely the SP1 update is simply triggering the same issue.

    Here's a google search on the issue. You'll notice a common thread is that P5N-E owners have the issue, users of other motherboards don't see it.

    It's been happening since mid January, from what I can gather, and I'm not finding any solutions to it yet.