New
#380
That's good to hear! With a cpu activity indicator here I hardly see it move except when placing a good load for resources like opening a VM or other larger app. No problems to report since the 2/23 install went well here.
That's good to hear! With a cpu activity indicator here I hardly see it move except when placing a good load for resources like opening a VM or other larger app. No problems to report since the 2/23 install went well here.
My PC has been off the road for about a month and I just got it back working yesterday (with much help from this forum's members)
Anyway, as you can imagine there are a lot of updates I've missed including SP1.
I am running Windows 7x64 and have a custom theme installed. I removed that by reverting to the standard W7 theme in Personalization.
When I tried to install SP1 it failed.
Any ideas anyone?
Cheers, John
Based on the feedback from others who were having the same issue and the fact that it was simply not going work otherwise, I did a clean install of win7, prevented it from downloading any other updates except sp1, loaded other updates and am back to running like it was supposed to.
jd
Make sure you disable any/all antivirus software, and try again. If it fails you can just download it, although the download size go's up quite a bit then. One of my machines worked through windows update, the other I did manually, and both went smooth and had no issues.
If you haven't installed the new IE9, I'd recommend installing it 'After' SP1, make sure SP1 go's nice and smooth for ya.
That's a good manner as i did go through some troubleshots install with SP1 wave1 leaked & SP1 RTM (both returned me the exact same Error Code 80004005), but did a stand-alone SP1.exe install, instead the Windows Update one. Running just fine since my march 2nd clean install....IE9 installed some days afterward.
I had a problem in that I installed SP1 and removed it using system restore because of an incompatibility issue with my Plantronics headset. I then could not reinstall it despite doing a clean boot and everything else that was recommended. I selected an earlier system image to take my computer back to an earlier time. SP1 then installed without problems.
I think I have posted this elsewhere but cannot find it.
I had two issues one my friends machine wouldn't download SP1 because of an error that showed up as FFFFFFFFFF something or other - turned out to be a virus Kaspersky TDSS Killer found a rootkit - got rid of it and SP1 no problem.
My own machine wouldn't do without downloading the System Update Readiness Tool http://support.microsoft.com/kb/947821 did it and no problems with SP1.
Install Windows Update KB2454826 from Windows Update before trying the stand alone exe package.
That one update has been a cause for concern but is required to see a good install of SP1. If you restored a system image at some point prior to SP1's release one solution mentioned before is to open an elevated command prompt and type in the "mountvol /e" command, press enter, exit the command prompt, and restart the system first before the next attempt.
After trying to find out why the beta then RC refused to go on the 64bit host here the error prompt with the RTM release lead to an MS page then seeing 3 or 4 options depending on situation. Having restored an image just before the beta release that information wasn't available at the time.
As for the update that one is a definite however with or without the readiness tool. The other advise to minimize all startup processes including any protections like antivirus, antispyware, any firewall will be a help as well. You disable those temporarily until SP1 is on.
Have posted this elsewhere - can't find where but...
Just done a clean up for a friend and yep SP1 wouldn't download found an error with FFFFFFF in it - virus. Did a Kaspersky TDDS Killer and it found a rootkit got rid ofit and SP1 doenoadedwithout a hitch.
My own machine wouldn't download it until I put in the M$ System Readiness Update Tool.
http://support.microsoft.com/kb/947821
Hey look I knew I'd posted it somewhere - I'll have to shut a couple of my machines off - apologies to all!