locked
SP1 fails with ERROR_NOT_FOUND 0x80070490

    Question

  • This happens with the release version of SP1, on Windows 7 x64 Ultimate. Also installed KB 947821 (System Update Readiness Tool) as per "Go online to learn more about this issue" link in the error dialog, but it still fails. At some point during installation (after automatic logoff) it displays "Failure configuring Service Pack", then it rolls back, reboots, and after logon it provides the ERROR_NOT_FOUND 0x80070490 in the error dialog.

    The last installation attempt (following KB 947821) also briefly had a "Non Genuine" message pop up upon reboot, but then this condition disappeared.

    Anyone from Microsoft would like to give a look at the CBS.log, setupapi.app.log etc. files?

    Thursday, February 17, 2011 12:49 PM

All replies

  • upload the files, I look at them.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 12:54 PM
  • Thanks for your help. Did you get the files? I sent you a link via private mail.
    Thursday, February 17, 2011 2:01 PM
  • ok, my admin send me the link.

    2011-02-17 11:44:39, Info                  CBS    Doqe:   q-uninstall: Inf: sdbus.inf , Ranking: 2, Device-Install: 0, Key: 600, Identity: sdbus.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16438 , PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
    2011-02-17 11:44:39, Info                  CBS    Perf: Doqe: Uninstall started.
    2011-02-17 11:44:39, Info                  CBS    Doqe: [Forward] Uninstalling driver updates, Count 52
    2011-02-17 11:44:39, Info                  CBS    Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 11.
    2011-02-17 11:44:40, Info                  CBS    DriverUpdateUninstallUpdates failed [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    Some files of the Update KB976422 (The capacity of a Secure Digital (SD) card that is larger than 32 GB is reported incorrectly in Windows 7 and in Windows Server 2008 R2) are missing so that the uninstall fails.

    Please start the command prompt (cmd.exe) with admin rights [1] and run sfc [2]:

    sfc.exe /scannow

    Is it able to find and repair broken files (create the txt file shown under [2] and look if all files are restored)?

    best regards
    André

    [1] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token
    [2] http://support.microsoft.com/kb/929833


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 2:14 PM
  • Thank you so much for your analysis and suggestion.

    I numbered each of the following steps in the same archive as before (the original files you already saw now have a prefix "1").

    Step 2 of the new logs: I tried running sfc /scannow, and the first run it fixed things and required a reboot (it said "Windows Resource Protection found corrupt files but was unable to fix some of them... The system file repair changes will take effect after the next reboot.")

    Step 3 of the new logs: After the reboot I again run sfc /scannow and this time the result was "Windows Resource Protection found corrupt files and successfully repaired them."

    Step 4 of the new logs: Running SP1 fails with the same symptom as in my original post.

    Step 5 of the new logs: Running sfc /scannow one final time, the result was "Windows Resource Protection found corrupt files but was unable to fix some of them."

    Thanks again!

    Thursday, February 17, 2011 5:21 PM
  • have you created the sfcdefails.txt, shown in the KB article about sfc? Which files can't be repaired?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 7:53 PM
  • I checked all four log files (i.e. each time I run the tool). There are no entries that match the pattern mentioned in the KB article. I thought maybe some other entry sheds some light, with more knowledge of common issues (which I don't have).

    Thursday, February 17, 2011 7:56 PM
  • upload the latest CBS.log after running sfc. I check for you which files can't be repaired.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 8:50 PM
  • That's 5_scannow-3-after-sp1-attempt-2_CBS.log in the archive. It was run after rebooting after SP1 installation failed again.

     

    Thursday, February 17, 2011 8:51 PM
  • upload it (no email), my admin is not on the PC.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 9:04 PM
  • It is the exact same URL as before (I just added files to the same archive).

    Thank you!

    Thursday, February 17, 2011 9:09 PM
  • sfc was able to fix all files.

    !!!  sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7\sffdisk.inf' in Driver Store. Error = 0x00000490

    extract the update KB976422 with expand.exe [1] and copy the correct files into the folder C:\Windows\WinSxS\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7 and try again.

    André

    [1] http://technet.microsoft.com/en-us/library/dd744339(WS.10).aspx


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 17, 2011 9:31 PM
  • I have the same platform, same architecture, same scenario, and same error. But in my case, sfc runs totally clean. The latest CheckSUR has always, and continues to, run clean. This system has always been carefully maintained. I had no such issue either installing nor removing pre-release builds of SP1. I am, in short, at my wit's end with SP1 RTM.
    Friday, February 18, 2011 3:38 AM
  • Just ran into the same problem.  SFC scan brought back 0x80070490 errors 1298 times.  Saw some packages related to IE and realized I have IE9 release candidate installed.  Not sure if it is related or not yet as I don't have anymore time to play around with this.

    Still wonder why the SP1 installer "Details" button simply leaves us with this extremely cryptic error code and nothing more.  You know why you failed, why don't you show me a nice little log with all the failure points?  Is it really THAT hard to do?  I mean, you know, the install is ALREADY logging, how about aggregating the errors for us and showing them to us when we hit the "details" button.

    "(ERROR_NOT_FOUND 0x80070490)" ....  that's not details.

     

    • Edited by Jason Lynn Friday, February 18, 2011 1:28 PM spelling
    Friday, February 18, 2011 5:22 AM
  • Just ran into the same problem.  SFC scan brought back 0x80070490 errors 1298 times.  Saw some packages related to IE and realized I have IE9 release candidate installed.  Not sure if it is related or not yet as I don't have anymore time to play around with this.

    Better off removing IE9 RC anyways. Unsure about Win 7 SP1 but I think [from Vista SP2 or was it XP SP3?] that the current IE gets "baked in" - i.e. you can't remove it.

    That and IE9 will probably be out by April [or before?].

    Friday, February 18, 2011 6:59 AM
  • I seem to have isolated a failure noted in the setupapi.dev.log rooted in the inability to uninstall KB982018 ["An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available"]:

    [Boot Session: 2011/02/17 23:59:05.125]

    >>> [Uninstall Driver Updates]

     >>> Section start 2011/02/18 00:01:24.855

    cmd: C:\Windows\servicing\TrustedInstaller.exe

     sto: Driver Update Context:

    sto: Image State = Specialized

    sto: Image Architecture = amd64

    sto: Transaction = CbsDriversAndPrimitives

     sto: Driver Updates = 8

    inf: Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_neutral_a6afe6ee2ba8c9b9\usbstor.inf' ([strings])

     !!! sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_nvraid.inf_31bf3856ad364e35_6.1.7600.20712_none_96a205e1f19732b1\nvraid.inf' in Driver Store. Error = 0x00000490

    <<< Section end 2011/02/18 00:01:25.198

     <<< [Exit status: FAILURE(0x00000490)]

     Staying inside Win7-x64 RTM, and attempting to uninstal KB982018 by any means, via control panel or command-line, results in a Windows Update failure, rollback, and reboot to the original state. In other words, it's independent of SP1 itself. If this behavior is "by design", does Microsoft intend that I stay on Windows 7 RTM forever?

    Friday, February 18, 2011 8:46 AM
  • > extract the update KB976422 with expand.exe [1] and copy the correct files into the folder
    > C:\Windows\WinSxS\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438
    > _none_00698d0a036fb7e7 and try again.

    OK I tried that, but the files were already identical in the previous attempt. I also checked permissions: the Effective Permissions for System are Full Control on all 4 files. In any case SP1 installation fails in the same way (log # 9).

    I also tried uninstalling KB976422, but it keeps failing (both from Control Panel and via start /w pkgmgr...) Log series 7 documents this (both CBS and the actual pkgmgr log).

    So it seems that you identified one culprit of the whole problem in this KB76422. Problem is, how to uninstall or fix it in a way that SP1 will then work?

    What made you conclude that it is those files in ...00698d0a036fb7e7 that are bad, and not maybe the reference used to determine whether the files are bad? Could there be any other causes?

    I also note that the CBS file for the sfc /scannow always has an entry "Hashes for file member \??\C:\Windows\Help\mui\0409\diskmgt.CHM do not match actual file", which it manages to repair. Why does this happen each time I run it? I also checked this file, it is the same as on another computer.

    Also, like dj_palindrome noted, and to reinforce your feedback, I noted that setupapi.dev.log contains entries like:

    !!! sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7\sffdisk.inf' in Driver Store. Error = 0x00000490
    <<< Section end 2011/02/17 11:52:21.446
    <<< [Exit status: FAILURE(0x00000490)]

    Updated logs in the same archive.

    Thanks again for your time and help.

    Friday, February 18, 2011 11:51 AM
  • x490 = 1168 = Element not found. The files of the driverupdate are not in the WinSxS folder. take ownership of all files in the fodler and replace them with the files of the extracted
    amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7
    folder.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 18, 2011 1:07 PM
  • I had already done both steps (I also added permissions to Everyone, just in case). Could there be a problem with the data in DriverStore\FileRepository?

    For full reference, C:\Windows\winsxs contains:

    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16385_none_00307aaa039afa70
    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7
    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4
    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7601.17514_none_02618e7200897e0a
    (each of these contains sffdisk.inf, sffdisk.sys, sffp_mmc.sys, sffp_sd.sys)

    The KB .cab contains:

    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8
    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05
    (each of these contains sdbus.inf and sdbus.sys)

    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7
    - amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4
    (each of these contains sffdisk.inf, sffdisk.sys, sffp_mmc.sys, sffp_sd.sys)

    The last two folders are identical with the content of the corresponding files in C:\Windows\winsxs, one of which you asked me to check. The first two folders are not present in C:\Windows\winsxs.

    C:\Windows\System32\DriverStore\FileRepository only contains sffdisk.inf_amd64_neutral_4ef95a3b96c130d1, which has an extra .pnf file but is otherwise identical with C:\Windows\winsxs\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16385_none_00307aaa039afa70

    There are no other "ssfdisk..." folders in C:\Windows\System32\DriverStore\FileRepository.

    Does that help shed further light?

    Friday, February 18, 2011 3:50 PM
  • copy the files fro the cab extracted amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7 folder to the amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7 in WinSxS .

    Also copy the both

    amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8
    amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05

    folders to WinSxS .


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 18, 2011 4:22 PM
  • My mistake - everything was already as you said. C:\Windows\winsxs already contained five amd64_sdbus.inf... folders, two of which (*) are identical with the ones in the KB CAB:

    - amd64_sdbus.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_86b03fe7f8988681
    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16385_none_cdd7ae6ae4081881
    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8 *
    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05 *
    - amd64_sdbus.inf_31bf3856ad364e35_6.1.7601.17514_none_d008c232e0f69c1b

    The similar amd64_sffdisk.inf... folder series also had an accompanying amd64_sffdisk.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_ce490098e4623ca8 folder, so they are both sets of 5 folders.

     

    Friday, February 18, 2011 5:06 PM
  • replace all files/folders with the good files from the CAB.

    If you still can't install the Sp1, run an InPlace Upgrade [1][2] to repair your windows. Your programs are still usable after doing the InPlace upgrade. This should repair all missing/damaged files.

    André

    [1] http://support.microsoft.com/kb/2255099
    [2] http://www.sevenforums.com/tutorials/3413-repair-install.html


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 18, 2011 8:28 PM
  • Already done. All folders and files from the CAB are the same in winsxs. Also cross-checked with WinDiff, and checked permissions again.

    That is, there are other files in the KB976422 update CAB that are outside of those four folders. I wouldn't know what to do with them.

    Thanks for sticking to the issue. So you are sure the issue is in the content of winsxs, and not in the DriverStore?

    Friday, February 18, 2011 8:32 PM
  • Do you see the sffdisk.inf here C:\Windows\System32\DriverStore\FileRepository?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 18, 2011 8:51 PM
  • Yes as per my previous post:

    >>>
    C:\Windows\System32\DriverStore\FileRepository only contains sffdisk.inf_amd64_neutral_4ef95a3b96c130d1, which has an extra .pnf file but is otherwise identical with C:\Windows\winsxs\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16385_none_00307aaa039afa70

    There are no other "ssfdisk..." folders in C:\Windows\System32\DriverStore\FileRepository.
    <<<

    I confirm that sffdisk.inf inside there is identical with the same file inside C:\Windows\winsxs\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16385_none_00307aaa039afa70.

    It is NOT identical with the file inside C:\Windows\winsxs\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7

    The difference is only in this line:

    DriverVer=06/21/2006,6.1.7600.16385

    winsxs version:

    DriverVer=06/21/2006,6.1.7600.16438

    I have no idea how the DriverRepository data deals with the similar files in four different winsxs directories. I just note that the one that fails (hilighted in bold) has a different sffdisk.inf and a different sffp_sd.sys (the other two sys files are identical).

    Friday, February 18, 2011 9:28 PM
  • Better off removing IE9 RC anyways. Unsure about Win 7 SP1 but I think [from Vista SP2 or was it XP SP3?] that the current IE gets "baked in" - i.e. you can't remove it.

    That and IE9 will probably be out by April [or before?].


    Well, after a tumultuous time removing IE9 (repeated reboots and SFC scans), SP1 still fails with the same error.  I found that SFC seems to be rather confused and will say it repaird items on one scan, then the following will say corrupted items were not repairable.  Great.

    I did find the following error ion the setup.dev.log:

     !!!  sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo.inf' in Driver Store. Error = 0x00000490

    and

    !    dvi:                     Unable to update reflected section names for: netavpna.inf
    !    dvi:                     Error 1168: Element not found.

    The latter seeming to be closer to the error reported by the SP1 install.  As far as wehere to go from there, I am clueless.  Both of those INF files are from Microsoft, so I am unsure of what the problem is with them.  Research on Google on both of the issues turned up nothing of use.  The SFC scans reporting fixed/broken has me concerned as well.

    Friday, February 18, 2011 9:35 PM
  • The difference is only in this line:

    DriverVer=06/21/2006,6.1.7600.16385

    winsxs version:

    DriverVer=06/21/2006,6.1.7600.16438

    I have no idea how the DriverRepository data deals with the similar files in four different winsxs directories. I just note that the one that fails (hilighted in bold) has a different sffdisk.inf and a different sffp_sd.sys (the other two sys files are identical).

    I have no idea how the DriverRepository works and how the foldernames are created :(

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 18, 2011 9:39 PM
  • So are we giving up? :-( Is there no way to delete or reinstall KB976422, which in this case is blocking installation of SP1? Thank you!
    Monday, February 21, 2011 1:15 AM
  • I have no real idea.

    Wait of a rely from joscon .


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 21, 2011 2:52 PM
  • Just to kind of reset things here a little bit.  Can you give me the file version that is in \Windows\system32\drivers for sffdisk.sys.

    Based on what I am seeing it appears that there is either a simple driver not in use here (so we've staged the binaries in \Winsxs but they arent active) or we actually have a problem with the files in the drivers folder. 

    When you say you cant uninstall the fix, can you explain why exactly thats the case?  It doesnt appear as a removable update?  Fails with an error code?

    --Joseph

    Monday, February 21, 2011 3:08 PM
  • > Can you give me the file version that is in \Windows\system32\drivers for sffdisk.sys.

    6.1.7600.16385.

    > When you say you cant uninstall the fix,
    > can you explain why exactly thats the case?

    It appears as a removable update, yes, but it then fails and seems to undo the changes, so it remains available as a removable update. I tried to remove it both from the Control Panel and with pkgmgr. Full logs of these attempts are in steps 6 and 7 of the log archive (sent you the link via the blog contact form).

    Monday, February 21, 2011 3:18 PM
  • Can you manually replace the file in C:\Windows\WinSxS\amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7\sffdisk.inf with the proper INF from the expanded KB and re-try the installation?

    --Joseph

    Monday, February 21, 2011 6:52 PM
  • All four files (including the .inf) are already identical. It is the .inf in the DriverStore that is different (see previous posts).

    Thanks again for all your help.

     

    Monday, February 21, 2011 11:38 PM
  • The cause of my error 0x00000490 in the driver store seemed rather mysterious (the supposedly nonexistent files did exist and appeared to be the correct versions). But CBS is so cryptic that, if automated tools cannot fix some obvious problem, my prospects are dim. So I gave up and did a repair install back to RTM. It is also possible to use the unsupported method of expanding a full-product ISO with integrated SP1, then changing MinClient in /sources/cversion.ini from 7601 to 7600. Both methods will cost you a day and a half of fixing things that don't work quite right anymore.

    But I would like to point out one thing I *did* do wrong maintaining my system. I would typically expand the MSU files and install the LDF (QFE) hotfix branches from the command line, i.e. "pkgmgr /ip /m:update-bf.mum". But I inadvertently did not use an IPD-aware CAB-file expander to do this. I used 7-Zip because I thought its context-menu extensions made it easy to avoid the command line. The hotfixes *did* install but I may have timebombed my own system.

    So *do* use "expand -f:*.* <some CAB file> <some folder>" or make sure your CAB-file expander is IPD-aware. The link Andre gave us http://technet.microsoft.com/en-us/library/dd744339(WS.10).aspx shows you what to look out for.

     

    Tuesday, February 22, 2011 2:49 AM
  • Just in case joscon was waiting for my reply to dj_palindrome, yes, I had used expand -f to extract the CAB content.

    Furthermore, my system has not been modified in any way by me, because all folders and files were already as the kind people who posted so far said they should be. I just carefully used WinDiff and widened the access privileges - "just in case".

    So I find this puzzling: there is a standard Windows Update KB update that cannot be uninstalled or repaired, and there is no procedure to fix that, and this blocks SP1?

    Thank you again!

    Tuesday, February 22, 2011 4:04 PM
  • The only other thing I can think of here is that you're missing another file.  The fact that you cant install that update tells me that you probably have some sort of corruption in the stack that's causing this.  Unfortunately, there arent good ways around that once it happens.  You could check the setupapi.dev.log and see if its reporting any other files with the same problem.

    --Joseph

    Tuesday, February 22, 2011 4:42 PM
  • The update installed fine (when it was released). I cannot uninstall it.

    Did you perhaps see the logs?

    Tuesday, February 22, 2011 4:46 PM
  • Yes, I saw the logs.  Just because the update installed fine doesnt mean that there isnt corruption in the servicing stack on the machine.  That could come from another update installation or any number of other factors.  I didnt see anything else in your logs that pointed to another driver, but that's why I asked, to make sure.
    Tuesday, February 22, 2011 5:59 PM