W7 SP1 Failure

I have a problem with the installation of SP1, it won't install. I'm running W7 HP x64. It's on a new machine I got a couple of days ago, so I did a fresh install of windows, updated windows up to SP1. I realise that there probably isn't much to gain from installing the SP1, but I would like to get to the bottom of this issue, for myself, and for others also, if they are having the same issues.

When I try to install it through windows update it gives the error message 8000405. Looking up this code online doesn't really come up with much.

I've then downloaded SP1 standalone installer, and tried that, still won't work, giving the error message E_FAIL(0X8000405). It's then directed me to the Microsoft site to get help, so I've tried the Windows Update, troubleshooter, which seemed to correct some things on my system, but this didn't help. I've then downloaded the System Update Readiness tool, installed, and run SP1 again, still no help either through Windows update or the standalone.

I've the tried with my antivirus un-installed, guess what, no joy!!!!

I've read a couple of threads here regarding this, where people using things like ccleaner can affect the installation of SP1 but I have no programs like this running at the moment, so this won't be the issue.

So as it stands, I've run out of idea's, It's not an urgent need to get it installed, but would like to get to the bottom of it either way, so hopefully, for future reference for people with the same or similar issue, this could be a help.

Thanks in advance for any replies.

 

It could be a number of things. For one having your anti-virus uninstalled wont make a difference. You could be missing a fix that SP1 needs, do you have all of the C+ redistributes as well as necessary Net. Framework patches etc.? Really you aren't missing out on anything. Sp1 is just a bunch of updates you might have missed, really it's just a gambit to try and get people to install the update that checks for those who have a counterfeit windows. One that thousands deliberately miss. I would wait until they fix SP1 and there are tons, and I mean tons of programs that don't support SP1 at the moment and have multiple issues with it. My old anti-virus Kaspersky for one.

I wouldn't worry about it, as long as your installation isn't corrupt. Just check and recheck windows updates for things you might have missed. I hope your windows install is a legal copy, really you shouldn't have any problems installing windows updates unless it isn't...

Good luck though. I'm happy not having it and I've tried it before, just tons of issues like it was a new 'unsupported' OS.

 

Not to fussed about having it, but I hate being defeated by a machine lol, and the thread may serve a purpose for other people if I manage to resolve it.

I'll check the C+ and .NET stuff (I'll report back once checked), and my copy is legal, having a dodgy cracked OS is like getting a burglar to install an alarm system in your house, asking for trouble lol!!

 

Unfortunately, the very fact that you can't install SP1 means that your installation is corrupt. And, no, there are no legitimate programs that have any issues with Win7 SP1. If you have a program that does have such issues, then that's because that program is broken. The solution is simple: Get rid of the garbage.

 

Not meaning to spam but that is a hilarious example of an epic fail

EDIT: As for the guy above me, I disagree. There are confirmed instances of many, many programs that do not support SP1 as well as tons of retailers, companies, etc. that all state they are working on new drivers for Sp1.

 

The above, of course, is complete and utter nonsense. But you knew that already, didn't you?

 

Oh really? Feel free to explain exactly wherein that "epic fail" you are alluding to might lie. I'm on the edge of my seat here.

Again, the above is nonsense. It is not up to an application to "support SP1". It is the OS that runs applications, not the other way around. Windows 7 SP1 is the OS that the applications need to be compatible with. If the application had followed OS guidelines to begin with, then there would have been no issue. If, on the other hand, a developer's application is not compatible with the OS, then that's their problem, and nobody else's.

 

Chill out Pirx. It's midnight here. I was talking about this part of the OP's joke.

Look at the time my post is after yours, just barely 2 minutes. You were just a bit faster than me.

It's everyone's problem if people are already using the software and then Sp1 comes out and the software they need is no longer compatible. Don't be an arrogant fool and try and deny that. I understand your logic but that doesn't explain why companies are running in circles releasing new drivers for Sp1 and what-not and your logic doesn't explain how tons of people are having issues with programs due to upgrading to SP1. People are having problems with IE for crying out loud... You might want to embrace knowledge, and have a nice warm cup of tea.

 

O.k., sorry for the misattribution and corresponding reaction.

If the issue was caused by the software not having been compatible before, and only having worked because the developers were lucky, then what I said holds. Given the fact that tens of thousands of applications work just fine before and after SP1, chances are that this is the case.

I don't, and neither have hundreds of thousands of others. I also don't have any problems with any of my other applications.

The cup of tea is a good idea, however

 

Please document known companies who are running around in circles developing new versions of programs and drivers to 'support' SP1. Pointers to news releases or official support forum postings will be appreciated.

Please also explain how the earlier versions of programs and drivers do not 'support' SP1 or fail to work properly.

 

after sp1 failed a couple of times i found this and was good to go.

Download details: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2011]

 

I did try the tool above but with no success.

I did manage to install SP1, but basically I rolled the system back to pretty much when W7 was first installed. Seems a bit drastic, but I've only had the system a couple of days, and hadn't really done much to it, so it was quicker than uninstalling programs/updates until SP1 took.

 

You could have manually downloaded the SP1 package from the Microsoft website.

I used the SP1 RC, and I uninstalled it for the updates, which failed every time I tried to make it install.

I just manually downloaded the SP1 files from Microsoft, and it installed without a hitch.

 

I did this and still didn't install.

 

If the SP1 setup shows an error it is for the following reasons:

> Setup has detected a driver that won't work after the upgrade process
> Windows 7 is corrupted, and won't continue and risk in having your system not working anymore.

 

As it was a fresh install it was easier for me to rollback the install to when windows first installed.

If, on the other hand it was an older install I would have tried to eliminate the offending driver/program. Don't think it was a corrupt windows 7 installation as sp1 installed once i'd rolled it back.

 

W7 SP1 is merely a compilation of all of Microsoft's updates for Windows 7 to date; it doesn't introduce any new features or architectures that require companies to redevelop compatible applications.

 

Zep hasn't bothered to document companies who are being 'forced' to rework their software/drivers for SP1.

 

They are no changes. If a software/driver needs to be re-programed, it's because THEY decided to use a security flaw or bug in the advantage for their software instead of doing things properly. The team manager of the project KNOWS this, and he decided to take the chance that it will be closed up any day from now. It is HIS or HER fault. Not Microsoft.

Example: Let's say, for the sakes of example, I work on a web software, and I discovered, thanks to the internet, that with some undocumented PHP code or Flash plug-in or something or a mix, I can save a file on the users computer without even asking the user. I decide to store my program settings. New update on Firefox or Flash or PHP, now blocks this security flaw, so now my web program can no longer save its settings. What do I do? Tell my customers "Sorry don't update your server, and tell your users to use an old version of Flash or Java or Firefox". Or I admit my stupidity and acknowledge that I should have read documentation on the topic, and knew that I can't do this, and the only way to do this is store on the server the settings via accounts system (which probably I knew, but too lazy to make it, hence why I went with that hack rout), or save as cookies

This is the EXACT same story with Vista. When Vista came out, a bunch of software stop working as they assumed that their users are all running Administrator accounts. Well guess what.. because the developer team decided that reading Microsoft documentation, which is freely available on MSDN website for all, is complicated, and that might take 2-3 more days of work to implement proper ways to do things... they have a software that doesn't work with Vista anymore, as no one is real Administrator, instead of having a proud, solid, software that works perfectly under Vista, Windows 7, and possibly even later. Drivers is another story... but Vista was in Beta for a long time for companies, and they had no excuse to wait until Vista was official out to wake up and start working on drivers.