I have Vista Business x64. It took about 5 tries before I could get SP1 to even show up on windows update, but once it did, it downloaded without a problem, did it's initial install in windows without a problem and then shutdown to do its 3 phases.

• Chrome Stopped Working Windows 10

Chrome Stopped Working Windows 10

It got to 100% of stage 3 of 3 (the end), hung there for about 10 minutes and then said 'service pack did not install. Reverting changes.' And it did, and it works just fine still. I dont have any of those problem drivers or programs for SP1, so why did it fail?

HA, here's to answering my own quesiton. I realized that I had Windows Modules Installer (trustedinstaller.exe) set to manual in services and stopped. Turn it on, set to automatic and made sure it was set to start up in system configuration and holy.it worked.Somebody give MS a medal for this one. You would think that this should one of the many things it checks BEFORE it starts.and I don't know.maybe TELL me its a problem instead of flipping me off and undoing an hour's worth of work./sigh.

All i can say on this one is a 'me too'. Except in my case it's a Vista Business 32bit.First time around the windows portion failed. Rechecked updates and it offered an Office 2007 Suite SP1 (or something similar. Though i don't have office installed). I let it install that update and after that the Windows portion of SP1 install completed without problems. Only to get the exact same Stage 3: 100%.

'Service Pack did not install. Reverting Changes' message.I tried a recheck on Windows Update to see if it would offer another 'update' like it did with the Office 2007 Suite SP1 update before. But so far only SP1. And honestly. I am not going to bother right now to simply retry only to get the same result 1-2 hours later.With kind regards,-Pascal Hofstee. We have experienced the same on Vista Ultimate x64. After churning for 1.5 hours, and two reboots, the update had quit and rolled back.On identically configured Vista Enterprise x64 systems, Vista SP1 installed without incident.Amusingly, the update took on systems with active anti-virus, but not on the same type of systems without active antivurus software (but just checked for viruses before attempting SP1 update).-To Microsoft's lacking developers:What we want to know is why your stupid Vista service pack update waits until after it's work is all but complete to give up and roll back.

Why on earth are the impediments to finishing the installation of SP1 not detectable BEFORE it starts the lengthy process. Stupid (a million times stupid) developers to take this approach. It's also great not to get any specific error messages or even the slightest hint about WHY the SP1 update decides to quit in the end.If the update consisted only of replacing operating system files, as it should, the process would take less than 15 minutes. Since the process takes more like 90-150minutes on even the newest systems (2GB RAM and 10k RPM HDD's), this leads back to the heaving disaster that is the Windows registry.

This 1970's hierarchical database, a catch-all mess with the worst indexing on earth, has got to go. After two failed attemps, I went to the logs or I should say I tried to go to the error log and could not find it.I ran SFC /Scannow and it created a log that shows some of the TFF fonts are missing. Surely MS doesn't abort an update because of Fonts. You know it is completely unreasonable that they do not create a reason log and put it on the desktop, is that beyond reason? I don't think so,It is hard to beleive that my HP Pavillion is not updateable on a full purchased windows home premium kit. HA, here's to answering my own quesiton.

I realized that I had Windows Modules Installer (trustedinstaller.exe) set to manual in services and stopped. Nero burning rom full version free download. Turn it on, set to automatic and made sure it was set to start up in system configuration and holy.it worked.Somebody give MS a medal for this one.

You would think that this should one of the many things it checks BEFORE it starts.and I don't know.maybe TELL me its a problem instead of flipping me off and undoing an hour's worth of work./sigh. Spudman,Thanks for discoveing a secret for exactly the same problem I encountered yesterday three times. I wa most aggravated by the lack of any feedback as to why it failed at all. I note that before going through the process there was some warning information about how long it might take and that the computer may shutdown and turn on again as part of the procedure. My rhetorical question is why didn't MS include suggestions for initial conditions like the very important 'key' that you uncovered? Also, if there are any special instructions needed concerning anti-virus or firewalls (like leave on, turn off etc) why aren't they included?

Why don't the wizards there think like customers who will, in all liklihood, be doing this themselves? Why wouldn't they do a what-if scenario to anticipate somevery basic problems? In short, this is a poorly thought-out rollout of an important upgrade. Again my thanks.

If it doesn't work for me, then it is something else that I will scour various forums to try an solve. You know it is hard to have any respect for Microsoft. They tell me that the upgrade was done on over 4 million computers and maybe I believe them and maybe I don't.