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.
They actually DO beta test their software, right??????????
I know that they're said to have copied the concept of a GUI from apple (who, yes, stole it from PARC) but I didn't think Microsoft would follow the iBrick update also.
In Xanadu did Kubla Khan
A stately pleasure dome decree
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!
So in other words, it IS an improvement!
"Ask not what your country can do for you." --John F. Kennedy
Q: Vista SP1 gets locks up the machines after update.
A: [x] Fiction (wins a T-Shirt)
[ ] Fact (truth but no T-Shirt to you bad boy.)
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Incorrect. If you paid attention, it was rolled out via the automatic update.
This is clearly a botch by Microsoft, not something "illegally downloaded".
In Xanadu did Kubla Khan
A stately pleasure dome decree
They're lucky! When it finishes booting, it kicks your dog and sends kiddie porn to all the contacts in your address book!
this time, it's with "One Infinite Loop"
bah! -1 retard for me. I didn't RTFA before I posted. I didn't see the part that it was rolling out via Automatic Update.
I suck.
Eventually the loop will stop, and the installation will complete. But only if you BELIEVE!
SJW: Someone who has run out of real oppression, and has to fake it.
Seriously, sounds like a version issue. An SCM (Software Configuration Management). Seriously, I worked for smaller companies that were serious about versioning and regression testing. Is it my imagination or does MS seem more and more like a software organization that is out of control?
putting the 'B' in LGBTQ+
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
Microsoft will be releasing a worm to fix this problem early next week!
Somewhere in a dark place you will find:
www.m1
I'm sorry. I can't believe I read a summary about a computer problem without it being called "bricking". What the hell is wrong with the world?!?
That's a dillution of the term "brick", and it's also not true. Except in the case of a really destructive update (as in, corrupts the FS or similar), if an update ever renders my Linux unbootable, I'll just pop in the install CD and use it to roll back the changes.
Certainly not what I'd call an "easy" process -- easy for me, maybe -- but it's by no means a brick.
Don't thank God, thank a doctor!
Well. If you read the first forum post that person states that he used the Refresh RC... And my windows update doesn't tell me anything about any updates. If it's one of those preSP updates I can understand, but why doesn't you say so then...
It hasn't begun rolling out via Automatic Update and the linked article is a forum post that refers to SP1 RC Refresh. RC Refresh is technically the same patch as SP1 but Microsoft has since releases pre-patches for SP1 which are rolling out via Automatic Updates - presumably to fix many of these issues.
So yeah - this story seems like bullshit and those parroting its claims need to remember that this is Slashdot - where facts are less important than a story tagged "haha".
Something similar happened with the 10.4.11 update as well.
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.
you can download a disk image, boot from the disk, and start being productive. It's a proven fix that worked for me.
Vista Repair Disk
I used it as soon as I started having problems with Vista on a new work computer and it's been smooth sailing ever since.
"The Most Fun Possible on 4 wheels" is at SunBuggy in Las Vegas
of the situation years ago when a patch went that killed ones network connection. The solution from Microsoft? Download a new patch to correct the situation.
Um, yeah.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
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.
Since Vista SP1 isn't even being deployed via Windows Update until next month, this whole story reeks of BS...
a machine that looked exactly the same but now made poping noises.
Sanctus, Sanctus, Sanctus, Dominus Deus Sabaoth Pleni sunt caeli et terra gloria tua...
Stop-Prism.org: Opt Out of Surveillance
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.
I say that because we have been Beta testing SP1 on 350 machines here at my university for some months now. Machines with different graphic cards, processors , extra hardware like scanners, different printers, graphic input tablets, and so on. That problem in our 350 machines was never detected.
So, sure, that proble may exists, but it must be some special combination that non of the testers was available to reproduce. Let it be only a 0,5 percent of Vista users who have that problem. You will read about it anywhere and think "oh, that sucks, they do not test, blah blah". Sure, only the press doesn't write about the 99,5% who didn't have any problems with it. It's a problem with proportion: do you want to see the glass half-full or half-empty. And here in /. you sure want it to be half empty.
It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
Apparently in their native tongue, "Windows Update" and "uTorrent" come out the same. This is NOT available from Microsoft to the general public, or even their TechNet & MSDN subscribers (just double-checked mine to be sure). There are currently two methods I am aware of: Installing a fresh copy from the ISO that has been leaked, or doing some registry magic on RC2 update package to make it not expire, which has been rumored to be the RTM but I haven't seen any confirmation anywhere.
As our way of thanking you for your positive contributions to Slashdot, you are eligible to disable Slashdot 2.0.
I got Vista Home Premium with a new Dell Inspiron 530 I bought the other day, and I found that I liked it a lot (and I've been an MS basher around here too-I'm astounded myself). I have not had any problems with Vista running any of my old Windows software and it has worked with all of my hardware. So, I'm keeping it on here rather than dicking with Kubuntu and getting that up and running. I'll just keep that on my old machine.
I got a work email from Microsoft saying that Vista SP1 was available now on MSDN. So, I downloaded it last night. Just to be sure before I took the plunge, I chatted with Dell customer support who told me not to install SP1 yet and to wait until it comes out over Windows Update. I couldn't quite get it out of them, but it sounds like Dell is still working with Microsoft on some things. More than once I was told to not install SP1 on my machine. So, I'm waiting it out.
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.
Maybe it was the reference to "Mak" and "MakOz"? The only thing missing was "Mak f@nboiz SUXRZ!".
"Somebody has to do something. It's just incredibly pathetic it has to be us."
--- Jerry Garcia
Those registry edits force the release candidates, which are more stable than betas but are still not intended for widespread public consumption. That's meant to let hobbyists run on non production machines.
I'll buy Vista SP1 blowing up some poor bastard's computer and killing his dog, but sleeping with his wife? With or without the suggestively named "Service Pack", Vista is much too lame to bone a guy's wife.
It would be so busy phoning home to make sure sex with a real, live woman wasn't forbidden by Sony or some other DRM-Monster, wifey would be off banging XXXP Pro while Vista was still issuing safe download warnings.
I've calculated my velocity with such exquisite precision that I have no idea where I am.
This installed on my production machine Wednesday:
KB937287
Description from Microsoft's Support Site: This article describes the prerequisite software updates that apply to versions of Windows Vista that are mentioned in the "Applies to" section. These software updates are a prerequisite for Windows Vista Service Pack 1 (SP1). Additionally, these updates help improve reliability when you install or remove Windows Vista SP1.
Two or three additional software updates are required before you install Windows Vista SP1. The software updates that are required depend on the version of Windows Vista that you want to upgrade. Prerequisite update 935509 that is listed in this article only applies to Windows Vista Enterprise and to Windows Vista Ultimate. The other prerequisite updates that are listed in this article apply to all versions of Windows Vista.
Such duplicates is, or can be, good management. It allows decoupling of development, so important bug fixes in one part of the tool chain can be released without waiting for another part of the tool chain which might be under a major rewrite.
Major free software packages like gcc does the same, include their own copy of various utilities and libraries. Doing so provides the best of two worlds, it allows code sharing at the development plane, while avoiding the coupling usually associated with using some other projects code.
There is a tiny price in disk usage for the end user, but a price worth paying for not having to wait an additional year for new features, because release schedules have to get synchronized.
To get the full benefit it is necessary to have established clear ownership of the various components, and have a strong ethics with regard to making sure changes are propagated back "upstream". Such an ethics is evolving in the free software world.
I have no idea if the situation is similar inside Microsoft, but the basic mechanisms favoring decoupling certainly exists within a large company as well.
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.
Oh slashdot, how you have become the Fox News of the IT world. Fact: SP1 has not been on automatic update yet, and won't be for a couple of weeks yet.
To echo what others have said, let's not let simple things like facts get in the way of good journalism.
throw new NoSignatureException();