Windows 7 SP1 x64 Install Error 0x80070490

[Dzomlija]

Whenever I try to install Windows 7 Service Pack 1 for x64, either via Windows Update or the standalone installer (windows6.1-KB976932-X64.exe - 947,070,088 bytes), I get the following error message:

Installation was not successful
Element Not Found
Error: ERROR_NOT_FOUND(0x80070490)

This happens also if I try from safe mode

​

So I followed the link provided by karlsnooks in the Steps to follow before installing Win7 SP1 from download center thread. The Microsoft information said that for steps 1 and 2 and need to backup my data, and update my drivers. I do this regularly, so this is a non-issue for me.

Step 3 said to install update KB2454826 if it is not already on my system. I don't need to install this update, because it's already there:

​

I've had a look at the CBS.LOG file (View attachment 140143), and have seen numerous errors. If someone with a bit more smarts than me can help me decode the problem so that I can install SP1?

I've also tried installing the System Update Readiness Tool (KB947821), to no avail.

As an absolute 100% no-other-choice-last-resort-effort, I am willing to format and reinstall Windows, but I'd prefer to figure out how to fix this problem without having to do so. That way, I'll be able to install SP1 onto customers computers where I do not have the option of performing a format.

I guess it's just my (good?) luck that this has happened to me first, before I need to deal with customers. Untill the problem is resolved, I'll not be installing SP1 for customers.

EDIT: For the record, my Windows 7 Ultimate x64 is legal, and has been validated:

​

 

[zigzag3143]

There is an after the fact Microsoft Kb article on this. Your error reports a registry setting (cbs.manifest) that is corrupt.

They dont suggest a solution there but since cbs.log manifest is genereated by

sfc /scannow I wonder if running it would repair that. It would at least tell you if there are errors there.

Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

 

[Night Hawk]

Have you made any full system images and restored any to the drive? When wondering why neither the beta or RC would finish on the 64bit while a fast temp install of the 32bit would see them go on the one difference was having created and restored images where the SP installer is unable to access the primary.

When seeing the eror screen click on the link shown for the MS page since the solution information has been updated for the rtm release on different options. All the updates and readiness tool were on here but each attempt fiailed until the rtm stalled instead where new info was then seen. "mountvol /E" entered at the elevated command prompt followed by a full restart took care of that fast!

 

[Bill2]

If sfc scan doesnt help, repair install would be the way to go.

 

[Dzomlija]

SFC /SCANOW found no problems:


EDIT:
Downloading now:
http://www.microsoft.com/downloads/...87-66b0-4e9c-9c3b-1fc9ea40f69f&displaylang=en

 

[Dzomlija]

There is an after the fact Microsoft Kb article on this. Your error reports a registry setting (cbs.manifest) that is corrupt.

They dont suggest a solution there but since cbs.log manifest is genereated by

sfc /scannow I wonder if running it would repair that. It would at least tell you if there are errors there.

Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

It tells me "This update is not applicable to your computer":


and SP1 installation still fails:


I'm going to try to remove the update, and then re-install it to see if that makes a difference.

 

[Bill2]

Peter, you've got the 32 bit version of the file. Your system's 64 bit, isnt it?

 

[Dzomlija]

Peter, you've got the 32 bit version of the file. Your system's 64 bit, isnt it?

:drool:

Thats what I get for trying to install SP1, fix my room fan, watch the VS02E07, and fix the cabinet doors in the kitchen at the same time.

Prometheus is the multitasker at Quad Core, not me...

Downloading Now:
http://www.microsoft.com/downloads/...17-580f-410c-b6a9-1069d772a835&displaylang=en

 

[Night Hawk]

That will do it! Hope iit goes well next time anyways!

(Gee how does it feel being a multitasker by the way? I typically see 10-20 things piled on at once. Every time I turn around... )

 

[Dzomlija]

Feeling like a prat after Bill2 corrected me, I downloaded the correct System Update Readiness Tool for Windows Server 2008 x64 Edition (KB947821) [February 2011] .

Not that it helped much, because I still get the "This update is not applicable to your computer" error, and SP1 still won't install:


You don't think that maybe Internet Explorer 9 BETA could be causing the problem? Which I can't uninstall, because it does not show in the Install Updates list, or Add/Remove programs...

 

[Dzomlija]

Let me try again with System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2011]

Will report back...

 

[Dzomlija]

This time the System Update Readiness Tool for Windows 7 installed properly. But SP1 STILL will not install!

 

[wysiwyg]

Welcome to the club, my 64bit I had no problem, but 32bit refuses to install, well no, it installs but won't configure it fails at 10%.

 

[Night Hawk]

When going to uninstall IE9 RC review the guide. http://www.sevenforums.com/tutorials/112121-internet-explorer-9-uninstall.html

In the Show Installed Updates it's listed as Windows Internet Explorer not simply Internet Explorer explaining how you missed it.

The RC has no effect on the SP install however. When the fail error screen appears click on the MS link since they have updated the information on what steps to take for getting the SP to take.

Here the beta and RC both failed at 99% "reverting changes" being the message then seen due to having initially restored a system image. I then simply clicked on the link seen for this final release to see the "mountvol /E" command to resolve that immediately. The 2/22 release at first glance simply stalled on the spot in the first minute or so until looking that up.

Likewise you need to pay attention to the specific error seen and remedy found on the MS page the link brings up to see which resolve will work there. You most likely will see 3 or 4 options to look at.

 

[Fayla]

It didn't work me either. I ended up reinstalling Window's, soon as it logged in for the first time I applied SP1 and it went successfully. It didn't ask for the readiness patch, like it had pre-format, weird, since I had 0 updates installed.

This time the System Update Readiness Tool for Windows 7 installed properly. But SP1 STILL will not install!

 

[Night Hawk]

There's one update required for SP1 that apparently has been giving numerous problems for people. That would be the KB2454826 update you need to see installed.

At first that one did refuse to install for a few tries until being less stubborn and finally going on. Ironically that's Step #3 in the recommends MS provided before you download from the MS Download Center. Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Step 3: Install Windows Update KB2454826



Install Windows Update KB2454826 from Windows Update (http://www.update.microsoft.com/) if it is not already installed. If you install the service pack from the Microsoft Download Center and do not install Windows Update KB245862, you could encounter a Stop error in Windows in rare cases.

Windows Update KB2454826 will automatically be installed when you install the service pack by using Windows Update. However, Windows Update KB2454826 is not automatically installed when you install the service pack from the Microsoft Download Center.

To check whether Windows Update KB2454826 is installed, click Start, type View installed updates in the Search programs and files box, and then press Enter. Notice whether Update for Microsoft Windows (KB2454826) is listed. If the update is not listed, you will have to install it from Windows Update (http://www.update.microsoft.com/) .

For anyone else still having problems seeing the SP go on I would recommend clicking on the link found on the error screen that usually appears when the install hangs right away or before the restart and looking over the MS page. The specific error will now be seeing a few options to solve the different types of installation problems.

 

[Dzomlija]

How is update KB2454826 supposed to help with the Windows SP1 installation, when it clearly has nothing to do with Windows Update and/or software installation?

(Quoted from A performance and functionality update is available for Windows 7 and for Windows Server 2008 R2, the to which was provided in Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center)

This article describes an update for Windows 7 and for Windows Server 2008 R2. This update contains the following new functionality, performance improvements, and solutions to issues:

• This update provides new functionality and performance improvement for the graphics platform.
• This update provides performance improvements when you print from XPS-based applications to GDI-based print drivers.
• This update resolves some streaming issues that are related to Media Foundation.

With or without said update, my SP1 installation fails using either Windows Update or the standalone installer...

 

[Night Hawk]

Have you restored any system images to the drive at all? Even if you haven't the same solution found here for seeing the SP installed might just work for you if you are not running into any specific error messages.

Try running the "mountvol /e" command in an elevated command prompt just the same followed by a full restart to see if the service pack suddenly takes off and finishes for you. It seems that the SP installer at times is unable to fully access the OS primary resulting in a failed attempt.

Here having restored an image on a previous occasion the first attempt saw the "cannot install" message on the first install screen and went nowhere until giving that a quick try to see results. It won't hurt anything giving that a try.

As for the KB2454826 update that's not included in with the others like the KB245862 update. Without it however it's been found the SP installation will stall at times. Unfortunately that same update has been causing a number of issues for other things like Live Mail. You'll find that one mentioned enough on a Bing search.

Another non MS source provides a list of things to do as well which brings up one thing I already was looking at regarding any antivirus, firewall, or other system protections you have inplace getting in the way. What you should know before you install Windows 7 SP1 | The Windows Club

Have enough free disk space available? The 64bit stand alone as you know is 903mb for a file size when downloaded.

 

[wysiwyg]

Tried 6 times to install SP1, doing different things, turn of defender,firewall, AV, tried in Safe mode with Networking, all no good.

Finally did a full backup and re-installed OS, installed 60+ updates, had to Activate OS to get SP1.

Bingo it floated through.

I've come to the conclusion that its a corrupted file in the system of those that can't install it.

Like mine, the 64 bit no problem, but the 32 bit would'nt work, the re-install corrected the error.

That my idea anyway. Any one with a better idea, be my guest.

In case you're wondering I rarely use the 64 bit so its had less chance of getting corrupted.

 

[Night Hawk]

I have to wonder if the main problem isn't seen in the installer itself having a bug and not fully able to access the OS primary not so much what present state Windows is in. Initially I set up a fast install of the 32bit along with the 64bit host when the beta was first out and saw the beta go right on the 32bit install without a glitch.

The miain drive here however had already seen an image restored when a mishap occurred while trying something else out just prior to that and simply failed at the 99% mark. Now with the final SP out the link to the MS page seen on the error had 3 or 4 options to work with depending on things like having restored an image.

I suggested to someone to try the same "mountvol /e" command in an elevated command prompt followed by a full restart regardless if it was still the original 7 install or reimage of the drive to see if that would help in other circumstances as well.

Note that seems to follow the idea of fresh clean installs of 7 are also generally seen on freshly formatted or reformatted primaries not ones that have been rather busy for some time.

Another last thought that comes to mind now was simply right clicking on the stand alone version to "run as admin" to see if elevaring permissions somewhat could help. In other words you take ownership somewhat to get past the built-in admin account's security levels.

It won't hurt to try anyways/ Whenever an SP or other update refuses to go on often it turns out to be something small and unthought of. Yet it still gums up the works!