Service Pack 1 fails to install (error_file_not_found_0x80070002)

Page 1 of 3 123 LastLast

  1. Posts : 27
    Windows 7 Home Premium 64 bit
       #1

    Service Pack 1 fails to install (error_file_not_found_0x80070002)


    I've never been offered SP1 through windows update for some reason so i decided to download the standalone installer and i went through the following steps:

    1. Ran the system update readiness tool - no errors found.
    2. Went through following steps before installing - Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center - though in the third step listed the updates suggested failed to install saying they were not applicable to my computer even though i got the x64 versions.
    3. Ran a full virus scan - found one infected script file so deleted.
    4. Went ahead and tried installing SP1 but after going through the preparing computer process it came up unsuccessful with the message 'ERROR_FILE_NOT_FOUND_0x80070002'.

    Here is where i got the service pack from - http://www.microsoft.com/en-us/downl...ang=en&id=5842 -the x64 version which i believe is 'windows6.1-KB976932-X64.exe'.

    So after this i ran through the following steps:

    1. Ran the Fix It tool which again found no errors to repair.
    2. Stopped the windows update service, renamed the SoftwareDistribution folder and restarted windows update service so as to re-download updates.
    3. I also followed one solution whereby you boot into safe mode and allow permissions for [SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] because a section of the CBS file says this registry root could not be opened. Rebooting again into safe mode and running the SP1 installer.

    None of this worked so now i am completely stumped, i might just have to do a full restore when i can be bothered. Though i've attached the CBS file if anyone can shed some light on the problem. Thanks.
      My Computer


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

    Your CBS.log file appeared to contain no data from an SFC - this may be because the log was archived on a reboot.
    Please post the latest persist log, or run another SFC and post the new CBS.log file
      My Computer


  3. Posts : 2,913
    Windows 7 Ultimate x64 SP1
       #3

    Instead of renaming the folder, I'd follow all of the steps outline in the MS article.

    http://windows.microsoft.com/en-US/w...error-80070002
      My Computer


  4. Posts : 27
    Windows 7 Home Premium 64 bit
    Thread Starter
       #4

    NoelDP said:
    Your CBS.log file appeared to contain no data from an SFC - this may be because the log was archived on a reboot.
    Please post the latest persist log, or run another SFC and post the new CBS.log file
    Is that where you run 'sfc /scannow' from a command prompt? I tried that and it returns the message 'windows resource protection could not start the repair service' despite running cmd as administrator. Where do i find the persist log?

    kegobeer said:
    Instead of renaming the folder, I'd follow all of the steps outline in the MS article.

    Windows Update error 80070002
    Won't that just re-download updates once the service is restarted? I did that yesterday and got a bunch of updates i've had before. But i will try it. Though no updates have ever been listed under 'installed updates' only under 'view update history'. Which makes me believe i've had a borked windows installation from the very beginning.
      My Computer


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

    If SFC is failing that badly, it means that there are some fairly fundamental things wrong with the OS.
    The persist files are in the same folder as the CBS.log file

    I wonder..... Please post an MGADiag report - I have a supicion I may know what's happening.

    download and save the MGADiag tool to your desktop - http://go.microsoft.com/fwlink/?linkid=52012
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
    - **in your own thread**, please
    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!
    How to Tell
      My Computer


  6. Posts : 27
    Windows 7 Home Premium 64 bit
    Thread Starter
       #6

    Yeah, it does seem like there is something fundamentally wrong even though i have had no problems with it until just recently started getting a BSOD occasionally, which might be resolved now. Here are the persist files, which i doubt can tell you much. I'll run that MGADiag report shortly.
    Service Pack 1 fails to install (error_file_not_found_0x80070002) Attached Files
      My Computer


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

    Odd - there's no CBS persist log, only the CheckSUR files.
    Since the current CBS log only holds data from today, please run another SFC /SCANNOW, and post the new CBS.log file immediately afterwards (after a reboot)- and check to see if a CBS persist log has been created.
      My Computer


  8. Posts : 27
    Windows 7 Home Premium 64 bit
    Thread Starter
       #8

    But it won't let me run an sfc scan. I only got that CBS file from trying to install SP1.

    Lots of instances of that error message in the MGADiag test though, i can see this being a full restore but then if it's been broken since installation would that even resolve any issues.

    The COA sticker says:

    Windows 7 Home Prem
    OEM Software

    Seems like a genuine sticker to me, it has a holographic strip running through the centre lengthwise.


    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-W874H-4HYVM-KVKXT
    Windows Product Key Hash: DgCAhHPpvlQr7Cp2mDJGfa4A4Tg=
    Windows Product ID: 00359-OEM-8702972-85523
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {455C5BD8-CD16-46CF-9CDB-EF58FF81E6C7}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100226-1909
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{455C5BD8-CD16-46CF-9CDB-EF58FF81E6C7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-KVKXT</PKey><PID>00359-OEM-8702972-85523</PID><PIDType>3</PIDType><SID>S-1-5-21-1713040681-1314412740-1622756178</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P55M-UD2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20100211000000.000000+000</Date></BIOS><HWID>FEBA3607018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00174-029-785523-02-2057-7600.0000-0982010
    Installation ID: 003981792652014032789763381721731813168690594375186323
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: KVKXT
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 29/04/2012 22:22:10

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NgAAAAEABgABAAEAAAACAAAAAQABAAEA6GFGCKgYdo2AlihgQsYIhcKP5KIQBmI99Jh0OnZW

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC GBT GBTUACPI
    FACP GBT GBTUACPI
    HPET GBT GBTUACPI
    MCFG GBT GBTUACPI
    EUDS GBT
    TAMG GBT GBT B0
    SSDT INTEL PPM RCM

      My Computer


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

    Don't worry about the errror codes in the MGADiag report - most of them are perfectly normal.
    The only two 'unusual problems' are related -
    1) You haven't installed the WAT Update - (which causes the File Mismatches we see here)
    2) You appear never to have validated the install.

    Neither of them are related to your current problem, and can be ignored.

    I was expecting to see a long list of file mismatches - but since there are none, my earlier thoughts will have to be discarded.

    Please attempt the SFC /SCANNOW anyhow - it will place data into the CBS.log file which may allow us to troubleshoot it.
      My Computer


  10. Posts : 27
    Windows 7 Home Premium 64 bit
    Thread Starter
       #10

    Ahh yes, the WAT update, is that KB971033? I remember at the time i purposely rejected that update because i didn't like the idea of windows 'calling home'. Is this what would be needed to validate the install because it says it's activated in system properties.

    I've rebooted but i simply cannot run sfc, it's still saying 'windows resource protection could not start the repair service'. I opened the command prompt as administrator unless there's another way to do it.
      My Computer


 
Page 1 of 3 123 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 20:22.
Find Us