locked
genuine error code 0x8007007e specific module could not be found... RRS feed

  • Question

  • Hi guys, tryjng to validate W7, it also cannot get network access, we get this error

    "genuine error code 0x8007007e specific module could not be found"

     any ideas?

     

     running a virus scan but nothing has shown up

     

     thx!!

    Monday, June 13, 2011 3:09 PM

Answers

  • I do not believe the issue is related to Upgrade vs Full install.

     

    Cookiemonster23 states that he received the issue while attempting online validation. Online Validation will prompt the user to install the WAT Update before validation can occur. 

    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]

    However, if you look at the Diagnostic Report, it shows that the WAT update has not been installed or (more likely considering the other parts of the report) was removed at some point, possibly using the Remove WAT tool that is floating around the internet (that Remove WAT tool doesn't do anything good and will usually cause problems like this).

    I recommend installing the WAT update by going to http://support.microsoft.com/kb/971033 scroll down to "How to obtain the update package" and select the correct update based on if your Windows is 32bit or 64 bit.

     

    NOTE: If the WAT update was installed in the past and then removed by the Remove WAT "tool", Windows may still think the WAT update is still installed and may not let you reinstall in.  In this case, you will need to use whatever program was used to remove the WAT files to restore the WAT files.

     

    Thank you,


    Darin MS
    Tuesday, June 14, 2011 9:22 PM

All replies

  • Please observe announcement 1 above.  If you do not have internet access, save the download to your desktop and then transfer it to the subject computer.

      In order to receive the best support, we request all users initially download and run the Genuine Diagnostics tool (MGADiag.exe) at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue", click the "Copy" button then “Paste” the report into a reply message in this thread.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Monday, June 13, 2011 4:20 PM
    Answerer
  •  

    thx for the quick reply, here is the output:

     

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-YYXQ7-G9BMC-6JJTM
    Windows Product Key Hash: dhFfWkxaGvVtf0zdPkRtAR5q+xU=
    Windows Product ID: 00371-177-4389632-85114
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {4BE4FC20-8FC9-4A7B-8E14-B55F1C0E058D}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_rtm.090713-1255
    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>{4BE4FC20-8FC9-4A7B-8E14-B55F1C0E058D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-6JJTM</PKey><PID>00371-177-4389632-85114</PID><PIDType>5</PIDType><SID>S-1-5-21-3543109261-1652441743-1499091422</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0108   </Version><SMBIOSVersion major="2" minor="5"/><Date>20100323000000.000000+000</Date></BIOS><HWID>9AB93607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>1</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-->
    On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F012' to display the error text.
    Error: 0xC004F012

    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: NAAAAAEABgABAAEAAAABAAAAAQABAAEAonYePDAPaGXueGoDRryENIwm3kJep6ZO8CXqgg==

    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            032310        APIC1517
      FACP            032310        FACP1517
      HPET            032310        OEMHPET
      MCFG            032310        OEMMCFG
      OEMB            032310        OEMB1517
      ASPT            032310        PerfTune
      OSFR            032310        OEMOSFR
      SSDT            DpgPmm        CpuPm


    Monday, June 13, 2011 6:51 PM
  • "cookiemonster23" wrote in message news:b283c02d-f203-49e9-979a-e6dea983724f...

     

    thx for the quick reply, here is the output:

     

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-YYXQ7-G9BMC-6JJTM
    Windows Product Key Hash: dhFfWkxaGvVtf0zdPkRtAR5q+xU=
    Windows Product ID: 00371-177-4389632-85114
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048


    Spsys.log Content: 0x80070002

    Licensing Data-->
    On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F012' to display the error text.
    Error: 0xC004F012

    Looking at the output from this immediately makes me think that you purchased an Upgrade version - and then installed it 'clean'

    One your disk - does the word Upgrade appear?
     
    If so - what was your previous Windows installation? If it was a Full Retail version of Windows, then you must have upgraded having wiped the HD (which is NOT a good idea!)
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, June 13, 2011 7:45 PM
    Moderator
  •  

     

     hmm, interesting

     

    it s a full retail W7 pro, which shouldn't have any problems doing fresh installs?

     

     there was an initial mixup with our supplier, who sent us upgrade licenses instead of full versions, this user possibly had one of them

     

    however has been working fine for months before today

     

     thx for the clues! will investigate


    Monday, June 13, 2011 8:45 PM
  • I do not believe the issue is related to Upgrade vs Full install.

     

    Cookiemonster23 states that he received the issue while attempting online validation. Online Validation will prompt the user to install the WAT Update before validation can occur. 

    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]

    However, if you look at the Diagnostic Report, it shows that the WAT update has not been installed or (more likely considering the other parts of the report) was removed at some point, possibly using the Remove WAT tool that is floating around the internet (that Remove WAT tool doesn't do anything good and will usually cause problems like this).

    I recommend installing the WAT update by going to http://support.microsoft.com/kb/971033 scroll down to "How to obtain the update package" and select the correct update based on if your Windows is 32bit or 64 bit.

     

    NOTE: If the WAT update was installed in the past and then removed by the Remove WAT "tool", Windows may still think the WAT update is still installed and may not let you reinstall in.  In this case, you will need to use whatever program was used to remove the WAT files to restore the WAT files.

     

    Thank you,


    Darin MS
    Tuesday, June 14, 2011 9:22 PM
  • "Darin Smith MS" wrote in message news:ca992ddd-f3a6-4287-9a09-8cc63bba3c8e...

    I do not believe the issue is related to Upgrade vs Full install.

     

    Cookiemonster23 states that he received the issue while attempting online validation. Online Validation will prompt the user to install the WAT Update before validation can occur. 

    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]

    However, if you look at the Diagnostic Report, it shows that the WAT update has not been installed or (more likely considering the other parts of the report) was removed at some point, possibly using the Remove WAT tool that is floating around the internet (that Remove WAT tool doesn't do anything good and will usually cause problems like this).

    I recommend installing the WAT update by going to http://support.microsoft.com/kb/971033 scroll down to "How to obtain the update package" and select the correct update based on if your Windows is 32bit or 64 bit.

     

    NOTE: If the WAT update was installed in the past and then removed by the Remove WAT "tool", Windows may still think the WAT update is still installed and may not let you reinstall in.  In this case, you will need to use whatever program was used to remove the WAT files to restore the WAT files.

     

    Thank you,


    Darin MS

    If WAT has been blocked somehow, it wasn't RemoveWAT that did the job, because the usual file mismatches aren't present. :)

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, June 14, 2011 9:49 PM
    Moderator
  • What makes me think that WAT was installed at some point is:

    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000

     

    The way I understand it, if WAT was never installed, all three of those line should have a result of N/A


    Darin MS
    Wednesday, June 15, 2011 8:59 PM
  • "Darin Smith MS" wrote in message news:943fa5b5-4ee0-45bc-b985-5569ec7f248b...

    What makes me think that WAT was installed at some point is:

    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000

     

    The way I understand it, if WAT was never installed, all three of those line should have a result of N/A


    Darin MS

    WAT appears to be installed, because there are no file mismatches showing. OTOH, if the registry entries had been borked without actually removing the files, wouldn't they appear in the File Tampers list?
     
    It sounds more to me as if there's a firewall or like problem preventing full access to access to the servers, so WAT never gets any new definitions, and assumes it's offline so works on that basis.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, June 15, 2011 9:20 PM
    Moderator
  • This is what we would expect to see if a Windows had never install the WAT Update:

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

    Windows Activation Technologies-->
    HrOffline: N/A
    HrOnline: N/A
    HealthStatus: N/A
    Event Time Stamp: N/A
    WAT Activex: Not Registered - 0x80040154
    WAT Admin Service: Not Registered - 0x80040154

    --------------

     

    This is what we see in this user's diag  (I have underlined the differences):

    -------------

    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]

    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:

    ------------

     

    0x80070003 vs  0x80070002 = Not completely sure what this means, but suggests the WAT files are missing

    0x0000000000000000 vs N/A = Suggests WAT is/was installed at some point


    Darin MS
    Thursday, June 16, 2011 9:10 PM
  • "Darin Smith MS" wrote in message news:adc8e943-9d24-48d5-8c3c-efe4ae6d3186...

    This is what we would expect to see if a Windows had never install the WAT Update:

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

    Windows Activation Technologies-->
    HrOffline: N/A
    HrOnline: N/A
    HealthStatus: N/A
    Event Time Stamp: N/A
    WAT Activex: Not Registered - 0x80040154
    WAT Admin Service: Not Registered - 0x80040154

    --------------

     

    This is what we see in this user's diag  (I have underlined the differences):

    -------------

    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]

    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:

    ------------

     

    0x80070003 vs  0x80070002 = Not completely sure what this means, but suggests the WAT files are missing

    0x0000000000000000 vs N/A = Suggests WAT is/was installed at some point


    Darin MS

    Hmmm - sorry, must have had my threads confused!
    0x80070003 vs 0x80070002 one is a path  not found - the other a file not found
    Not sure, but... There is a subtle difference, I think, where one says the file doesn't exist (i.e. there's no entry in the MFT), while the other that it may exist but isn't readable (i.e. the file reference is present in the MFT, but access is disallowed somehow)
    It may be that someone has found a way of putting 'virtual' entries into the MFT as a way to prevent the installation of unwanted files? (in the same way that is done with real files in the case of some anti-malware protection schemes)
     
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, June 17, 2011 6:58 AM
    Moderator