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.
About 10 minutes before this popped up, I got my first client call with this symptom.
Ahhh, Microsoft. Thank you for all the work you throw my way!
The only thing I can confirm so far is yep, Safe Mode don't work.
Linux, you magnificent bastard, I read the fucking manual!
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
Reading a little more of the forum confirms my theory about it mostly being the Refresh RC 2 ("Which should be the same as the RTM").
I havn't found a single thread about someone saying anything about windows update.
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.
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.
You sound like you'd be happier with Technocrat.net. Decidedly fewer trolls and 12 year old fanboiz there. I lurk, but don't really post much.Give it a shot.
I believe MS said they would not roll it to fully automated updates till they fixes some driver installation problem that was displayed in the RC.
They however failed to tell what drivers were affected, and how you can manually fix it. Yanking the power cord certainly is not the method MS would recommend. It htink you need the install disk and run some kind of recovery mode. (that is how it worked under XP.
The linked forum post is referring to a RC, not to the RTM.
http://windowsvistablog.com/blogs/windowsvista/archive/2008/02/11/windows-vista-sp1-availability-for-technical-customers.aspx
"For broad availability, we are still planning to release in mid-March, since we want to be sure that everyone has the smoothest experience possible.". You can have it earlier if you are want to touch buttons....
windows update is only pushing
the final two of three prerequisite updates needed to install Windows Vista SP1
basically it says you still need 2 more reboots before you can have sp1 automatically.
Thanks for confirming how rabidly anti-Microsoft this site is.
Not only was the original article allowed to make it even though it was clearly incorrect. Since SP1 will not be available on Windows Update for at least a month. Most of the responders automatically piled on the typical anti-MS/Vista nonsens and even disagreed with posters trying to correct the article pointing to the article as proof.
What are you smoking? S3 is still around. Matrox as well. Then there's Intel, ATi, nVidia, then there's 3DLabs. I think Trident might be around, but only in a pure 2D platform. Cirrus Logic is also still in business, though whether or not they still manufacture GPUs is unknown to myself.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
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.