locked
Windows 7 Pro validation failure RRS feed

  • Question

  • My pc won't download automatic updates anymore since September 13, 2010.  also, I noticed I can't get my windows validated on following website:http://www.microsoft.com/genuine/validate/?displaylang=nl&sGuid=2a77af43-5a81-4d9c-82e1-b79d54d8f238.

    When I look at the properties of my computer, I can see windows 7 is activated correctly.

    Below you can find the MGADiag report.  When trying to copy the report i got an error: 0x80070002.  Maybe this has something to do with my problem?
    The windows licence I'm using normally is valid, the licence isn't installed on another pc, so I can't figure out the problem...

    thanks in advance.
    Jef Elst

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-YT2YY-WPG76-3HVXC
    Windows Product Key Hash: Tm4vYcJEetV4/hZ386t3Wxcq/Sk=
    Windows Product ID: 00371-OEM-9044254-28268
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {7D983695-2E53-4CAB-AD2D-8FFF5A1BB5D3}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    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: 100 Genuine
    Microsoft Office XP Standard Voor leerlingen, studenten en docenten - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    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[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{7D983695-2E53-4CAB-AD2D-8FFF5A1BB5D3}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3HVXC</PKey><PID>00371-OEM-9044254-28268</PID><PIDType>3</PIDType><SID>S-1-5-21-530657935-2935168737-2738010588</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>2DBA3607018400FE</HWID><UserLCID>0813</UserLCID><SystemLCID>0413</SystemLCID><TimeZone>Romance (standaardtijd)(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{913D0413-6000-11D3-8CFE-0050048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office XP Standard Voor leerlingen, studenten en docenten</Name><Ver>10</Ver><Val>880F2B255C8CF12</Val><Hash>sB7audyt0AXo8b2SSCXUgPhXMx0=</Hash><Pid>55932-719-6117857-17516</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="10" Result="100"/><App Id="18" Version="10" Result="100"/><App Id="1A" Version="10" Result="100"/><App Id="1B" Version="10" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Versie van Software Licensing-service: 6.1.7600.16385

    Naam: Windows(R) 7, Professional edition
    Beschrijving: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activerings-id: e120e868-3df2-464a-95a0-b52fa5ada4bf
    Toepassings-id55c92734-d682-4d71-983e-d6ec3f16059f
    Uitgebreide PID: 00371-00180-442-528268-02-2067-7600.0000-3452010
    Installatie-id016771516936643853238436534140686044188314520371310053
    URL van processorcertificaat: http://go.microsoft.com/fwlink/?LinkID=88338
    URL van computercertificaat: http://go.microsoft.com/fwlink/?LinkID=88339
    URL van gebruikte licentie: http://go.microsoft.com/fwlink/?LinkID=88341
    URL van productcodecertificaat: http://go.microsoft.com/fwlink/?LinkID=88340
    Gedeeltelijke productcode: 3HVXC
    Licentiestatus: licentie
    Resterend aantal nieuwe Windows-activeringen: 3
    Vertrouwde tijd: 15/12/2010 19:49:02

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 12:15:2010 19:03
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppobjs.dll
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\sppwinob.dll
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui
    Tampered File: %systemroot%\system32\drivers\spsys.sys


    HWID Data-->
    HWID Hash Current: LgAAAAEAAQABAAIAAQABAAAAAQABAAEAln2IdTAPJFuYFzZfznDCj/SY8IJ2Vg==

    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

     

    Wednesday, December 15, 2010 6:59 PM

Answers

  •   Each region decides how it wants to handle support.  Most support WGA for free but there are some regions that doesn't separate WGA from general Windows pay support. 

      At this point, you have a few options for possibly resolving the issue.

     

    a) Try doing a System Restore to a point before the issue first occured.

    b) Replace the damaged files by coping them from a good copy of Windows (Unfortunatly this is outside my area of support, but one of the Community Members may be able to walk you thru the process).

    or

    c) Reinstall Windows

     

    Sorry I couldn't be more help,


    Darin MS
    • Proposed as answer by Darin Smith MS Thursday, December 16, 2010 10:18 PM
    • Marked as answer by Darin Smith MS Tuesday, December 28, 2010 12:54 AM
    Thursday, December 16, 2010 10:17 PM

All replies

  • I also noticed that when I try to install Windows Activation Technologies, I get an error code: 0xC8000426.  For that error, I cannot find a solution either.  Perhaps both problems are related?

    Thanks in advance.
    Jef Elst

    Wednesday, December 15, 2010 8:10 PM
  • Note the file mismatch and tamper sections, the files found by WAT do not match the expected files, something has changed or corrupted them, try the following options. It is highly likely as you suspected, that the error code is related to the non-genuine status.

    SFC/system restore

    type cmd in the search box of the start menu, right click on the icon that appears and type sfc /scannow without the qoutes and press enter, allow SFC to run, reboot when directed. If you get any error messages write them down exactly as they appear. After rebooting go to www.microsoft.com/genuine and attempt to validate.

     

    If that does not work then type system restore in the search box, click on the resulting program and follow the wizards prompts to restore to a previous point prior to the non-genuine status.

     

    If that does not work then start a no cost wga tech support incident at the following link http://support.microsoft.com/gp/contactwga

    Wednesday, December 15, 2010 8:49 PM
  • Carl

    Do I have to execute the sfc /scannow command in safe mode or is that not necessary?  Right now I am at work so I won't be able to execute the command until this evening.

    Thanks in advance

    Jef Elst

    Thursday, December 16, 2010 7:42 AM
  • Carl

    Do I have to execute the sfc /scannow command in safe mode or is that not necessary?  Right now I am at work so I won't be able to execute the command until this evening.

    Thanks in advance

    Jef Elst


    Normal Mode is fine - but you have to issue the command from an Elevated Command Prompt window

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 16, 2010 8:35 AM
    Moderator
  • I executed the SFC /scannow command and got following results:

    Systeemcontrole wordt gestart. Dit proces kan enkele minuten duren.

    Verificatiefase van systeemscan wordt gestart.
    Verificatie is 100% voltooid.
    Er zijn beschadigde bestanden gevonden, maar deze kunnen niet allemaal worden he
    rsteld.
    De details zijn opgenomen in CBS.Log windir\Logs\CBS\CBS.log. Bijvoorbeeld
    C:\Windows\Logs\CBS\CBS.log

    Translated: There were damaged files found, but they can't all be repaired. details can be found in CBS.log.

    Since I couldn't post the logfile here (my post won't commit), I uploaded the logfile to following location: http://jefelst.be/cbs_log.txt
    When this isn't accepted, can you please give me details on how i can put the logifle in a comment...

    Thanks in advance

    Jef Elst

     

    Thursday, December 16, 2010 9:12 AM
  • I executed the SFC /scannow command and got following results:

    Systeemcontrole wordt gestart. Dit proces kan enkele minuten duren.

    Verificatiefase van systeemscan wordt gestart.
    Verificatie is 100% voltooid.
    Er zijn beschadigde bestanden gevonden, maar deze kunnen niet allemaal worden he
    rsteld.
    De details zijn opgenomen in CBS.Log windir\Logs\CBS\CBS.log. Bijvoorbeeld
    C:\Windows\Logs\CBS\CBS.log

    Translated: There were damaged files found, but they can't all be repaired. details can be found in CBS.log.

    Since I couldn't post the logfile here (my post won't commit), I uploaded the logfile to following location: http://jefelst.be/cbs_log.txt
    When this isn't accepted, can you please give me details on how i can put the logifle in a comment...

    Thanks in advance

    Jef Elst

     


    There's a size-limit on posts in these forums - you did the right thing by posting a link.
     
    There appears to have been some major corruption present. It may well be worth running the scan again, to see whether it fixes any more. A lot of the involved files are .NET framework ones, which could indicate a botched update (but I honestly don't know). You could try posting to the Win 7 Repair Answers forum, with the link again, and asking if someone there can diagnose or assist.
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 16, 2010 1:44 PM
    Moderator
  • This was the third time I ran the scan so I guess the scan will not solve more problems.  I'll start a thread on the forum you specified, but all other idea's in this thread are welcome.  Since the pc still runs normally (except for the windows updates and the WGA errors), I'm hoping a reinstall won't be necessary.

    Thanks in advance.

    Jef Elst

    Thursday, December 16, 2010 1:58 PM
  • Sorry we could not help you fix it, start a no cost wga tech support incident at the following link http://support.microsoft.com/gp/contactwga

    Thursday, December 16, 2010 2:47 PM
  • I started the wga tech support call but they told me no support exists for oem licenses in Belgium.  I don't get that.  it's not like I bought a OEM system from a major manufacturer, I bought a oem license that is sold by microsoft itself.  Is it normal that I don't get support for this kind of problem?

    A couple of posts back, you mentionned that most of the problems that are in the cbl logfile are related to the dot net framework.  Can reinstalling the dot net framework solve the issue, or is there any other way to manually replace the files by correct ones?

    Currently, my pc is still running.  all he doesn't do anymore is receive updates and complain about the license.  There is some software on the pc that was pretty difficult to install, so when not necessary, i don't want to do the install again.  also, the situation that could have caused the problem would be interesting.  When I know how the situation was causes, I can avoid the situation in the future...

    Thanks in advance.  

    Jef Elst

    Thursday, December 16, 2010 4:47 PM
  • I was under the assumption that ALL WGA support was free. Wait for Darin's response if you want to pursue the WGA support, It was probably Noel who mentioned the .net framework issue and as I am not 100% sure what he saw or has experienced I will let him answer. If you feel that .net or any other application or patch caused the issue perform a system restore to a point prior to the installation of that program.

    Thanks

    Carl

    Thursday, December 16, 2010 6:28 PM
  • "Carl Stephens" wrote in message news:35e402f2-64d2-44f8-99c8-ac0538ae4072...

    I was under the assumption that ALL WGA support was free. Wait for Darin's response if you want to pursue the WGA support, It was probably Noel who mentioned the .net framework issue and as I am not 100% sure what he saw or has experienced I will let him answer. If you feel that .net or any other application or patch caused the issue perform a system restore to a point prior to the installation of that program.

    Thanks

    Carl


    Unfortunately, .NET is now an integral part of Windows, and cannot simply be uninstalled.
    My feeling is that the .NET issue is a peripheral one, and the WGA problem takes priority, and as such the OP should specify the WGA problems rather than anything else when attempting to create a support incident. (Let MS work out that it may be related to .NET, in other words <eg>). There's more than one way to skin the proverbial cat!
     
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 16, 2010 9:52 PM
    Moderator
  •   Each region decides how it wants to handle support.  Most support WGA for free but there are some regions that doesn't separate WGA from general Windows pay support. 

      At this point, you have a few options for possibly resolving the issue.

     

    a) Try doing a System Restore to a point before the issue first occured.

    b) Replace the damaged files by coping them from a good copy of Windows (Unfortunatly this is outside my area of support, but one of the Community Members may be able to walk you thru the process).

    or

    c) Reinstall Windows

     

    Sorry I couldn't be more help,


    Darin MS
    • Proposed as answer by Darin Smith MS Thursday, December 16, 2010 10:18 PM
    • Marked as answer by Darin Smith MS Tuesday, December 28, 2010 12:54 AM
    Thursday, December 16, 2010 10:17 PM
  • Darin

    Thank you for your replies.  Unfortunately, I don't have time until wednesday to try to replace the files.

    To prevent data loss, I'll take a mirror copy of the disk and try to replace the files that are mentionned in the logfile I pasted in a previous post.  When this works, I'll let you know.

    Noel

    I'll also try to log a call at microsoft Belgium, explaining I'm having WGA issues only.  When they come up with a proper solution, I can always take the original disk back.

    I'll let you know what advice solved the situation.

    Thanks.

    Jef Elst

    Friday, December 17, 2010 7:46 AM
  • Issue is assumed to be resolved.

    Darin MS
    Tuesday, December 28, 2010 12:55 AM