Despite expectations for a March 18 release, reports all over the Internet have surfaced that Vista SP1 x64 RTM has been released via Windows Update. Not everyone seems to have access to it (yet, keep hitting that ‘Check for Updates’ button): it has only appeared for certain individuals at the moment. The update is of course optional; users need to manually choose to download it even if they have their Windows Update set to retrieve updates automatically.
Well waddya know, just checked and it’s turned up here on Vista64 in Windows update. Something is already moving my hand towards a button marked “Install” … I’m watching my finger click down on the mouse … voices in my head now … “I am the Borg. You will install …” urrgh, thud …
I installed it this morning. It did auto-download in the night, but it waited to ask if I wanted to install it.
Well it’s installed here now. Two reboots and half an hour – a lot easier, at least for me, than some earlier reports were suggesting.
Back to researching codes that dont exist in the wild yet, “service pack did not install, reverting changes” all the betas did that to me, if I had anything more than a fresh install sp1 wouldent install, good job to all at microsoft! I absolutely loath the fact that I must call them every time I reinstall now
You have to remove any betas you’ve installed before trying to install SP1.
Perhaps the install logs will give you a more detailed clue into why it’s failing?
This is a new install (well 3 weeks) and havent put any beta sp1’s on this one. it finally gave me a code a day later in windows update (said pending before even tho it wasent installing) so Im gonna look that up. but I dont think it matters anyways, windows update doesnt show it anymore, so I think they pulled it again.
its funny though, nearly everybody says “oh you didnt disable antivirus, you have things running in the background, you have (insert program here) conflicting”, and every time I have none of those even installed. I run a very minimal system for gaming only, and run Linux for everything else, so it kills me how things fail so easily with no good explaination (the error codes are usually used by 300 other microsoft programs as well, and havent been updated in thier kb system yet).
I also was thinking, maybe it is my hardware, nope… 3 different builds since ive been messing with it in november, same results, for every beta. it seems if my system has been installed for more than a week its doomed to not work.
For the sake of better safe than sorry, I’ll first try it on a virtual machine.
Still, more than a single reboot and not being able to do anything useful… To me it seems that they still have to look at the patching process on other platforms to find out how it can be done without this kind of time waste..
Wondering if the logs also are getting better now; older logs (for instance windows 2003) just suck. Unless you feel that knowing how many seconds MSSQL is up is interesting (don’t even try to look up the message. it doesn’t exist … their own “error codes”))
as a sidenote: I think they are over their top…
Looks like Microsoft didn’t fix the loopholes they claimed to have fixed, I know people who are running OEM hack versions with SP1 running fine.
It maybe a hit and miss affair but they failed to stop what they claimed they would, half job done again.