Sp1 - error_not_found 0×80070490

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 x64 Professional OA
       #1

    Sp1 - error_not_found 0×80070490


    I know there is lots of issues about this error I think I tried them all and have got just just few errors now:

    The hardware: HP Compaq 7100 z Windows7 x64 Professional OA.

    My log CBS:
    SPI: (CheckForPendingFlag:90)Failed to open component hive at C:\Windows\System32\config\components er=0x0
    SPI: (SPIRegQueryDWORDValue:413)Failed to query registry value: ComponentsRemoved er=0x2
    SPI: (SPCVerifyTrust:1664)Failed to CryptCATAdminCalcHashFromFileHandle GLE=0x57
    SPI: (SPIRegQueryDWORDValue:413)Failed to query registry value: UploadDisableFlag er=0x2
    SPI: (SPIRegQueryDWORDValue:400)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryDWORDValue:400)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryDWORDValue:400)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryDWORDValue:400)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    CBS SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2

    I have been fighting with it over a week and drives me nuts.

    I am not interested in solution of recovery to factory defaults. Making a backup and later recovery will recover the faults again.

    In the worst scenario I can do in-place upgrade but is anyone who can tell me how to do it with a licence Windows 7 Professional OA ??? HP could deliver ma CDs with an image only where there is no upgrade. The other windows installation will require a serial number that doesn't match the one on the machine.

    To sum it up. I have got 2 questions:

    1. Is here anyone who knows how to fix log errors manually?
    2. Is here anyone who knows how to do an Upgrade In-Place with a OA Licence ?

    Thanx for any answers and suggestions.
      My Computer


  2. Posts : 2,663
    Windows 8.1 Pro x64
       #2

    Hello ITNewbie and welcome to the forums

    Download and install the System Update Readiness Tool:

    Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [September 2012] - Microsoft Download Center - Download Details

    Then copy and paste the contents of the CheckSUR log into your next post please. It can be found here:

    C:\Windows\Logs\CBS\CheckSUR.persist.log

    Please don't attach the file, I only want the contents :)

    Tom
      My Computer


  3. Posts : 5
    Windows 7 x64 Professional OA
    Thread Starter
       #3
      My Computer


  4. Posts : 2,663
    Windows 8.1 Pro x64
       #4

    ITNewbe said:
    To sum it up. I have got 2 questions:

    1. Is here anyone who knows how to fix log errors manually?
    2. Is here anyone who knows how to do an Upgrade In-Place with a OA Licence ?

    Thanx for any answers and suggestions.
    Thanks for the files :)

    I'm not experienced enough to be able to fix your CBS errors, but I'll keep looking into it for you.

    I will contact an activation expert with regard to your OA license question :)

    Tom
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    I think it's probably best if I ask for an MGADiag report - I'm a little confused :) (OK, situation: normal!)


    Please follow this tutorial and post an MGADiag report - then we can see what the problem is.

    https://www.sevenforums.com/windows-updates-activation/234159-windows-genuine-activation-issue-posting-instructions.html


    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine (or inside the battery compartment), but do NOT quote the Key on the sticker!
    http://www.microsoft.com/en-us/howtotell/Hardware.aspx
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    In all that data - 500MB of files - I can see no evidence that you've actually attempted an SFC scan.
    Please do so.



    Please run a full CHKDSK and SFC scan....
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

    At the Command prompt, type
    CHKDSK C: /R
    and hit the Enter key.

    You will be told that the drive is locked,
    and the CHKDSK will run at he next boot - hit the Y key, and then reboot.
    The CHKDSK will take a few hours depending on the size of the drive, so be patient!
    After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

    then run the SFC.

    SFC -System File Checker - Instructions
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
    At the Command prompt, type
    SFC /SCANNOW
    and hit the Enter key

    Wait for the scan to finish - make a note of any error messages - and then reboot.
    Copy the new CBS.log file created to your desktop (you can't manipulate it directly) and then compress and attach it to your response.
      My Computer


  7. Posts : 5
    Windows 7 x64 Professional OA
    Thread Starter
       #7

    sfc /scannow has been done couple of times with no errors.

    but finally my problem has been solved.

    Here is a brief explanation for others:

    1. Check your CBS log very carefully and not the last one. Check also the archived ones.

    In my case it was:Failed to resolve package 'Package_3_for_KB2506223~31bf3856ad364e35~amd64~~6.1.1.1'.

    in COMPONENTS there were more errors associated with this Package.

    I removed entries and Service Pack gone through.

    It is very individual problem and might not be relevant to anyone else.

    I have no clue why I had this entry amd64. The machine is Intel 64.

    Thank for your help.
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    All 64-bit machines with the exception of Itanium processors are described as 'amd64' - it has to do withthe architecture, not the manufacturer.

    I suspect that the SFC actually fixed the problem, rather than anything else - what do you mean by "I removed entries and...." ??
      My Computer


  9. Posts : 5
    Windows 7 x64 Professional OA
    Thread Starter
       #9

    no sfc - was obvious. I would not come here for sfc commmand ;-)

    I have created a fix.reg by openning a notepad and preparing it like this:

    Windows Registry Editor Version 5.00

    [-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\cfa685ec1fa7df8587ee0815de8902f96ebdab697a8ca7b 11c6c3cb415424ad6]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01be1844446..5c07dee85fa_31bf3856ad364e35_6. 1.7601.21673_91af9a2cf309496d]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a2215bb6a17..ac33bf83f45_31bf3856ad364e35_6. 1.7601.17570_d2f8c967508a5b16]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_01be184444675e8389d4a5c07dee85fa_31bf3856 ad364e35_6.1.7601.21673_none_91af9a2cf309496d]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_a2215bb6a173d20e629cfac33bf83f45_31bf3856 ad364e35_6.1.7601.17570_none_d2f8c967508a5b16]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.21673_none_17613c22ca75821a]

    [-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.17570_none_16d49e79b15a964b]

    It solved the problem.
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    What do you actually know about what you did, with those edits?
    It may have allowed you to install SP1, but what else did it do? (and here I admit total ignorance - so you can teach me something!)
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:50.
Find Us