Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
My MSDN license generates a not genuine after 2 years - advanced tool says it is? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    I am a software developer, MSDN subscriber and previous 9 year MVP.  This particular install of Windows dates from 7/23/2010, I've had no need to reinstall since I keep it pretty clean.  Just today I got a notification that my Windows install was not genuine, so I updated the tool and re-ran it and got the same result.  Reboot and re-run, same result.  I found the advanced tool as mentioned in the sticky and posted the results below, as you will note this tool reports that Windows IS genuine, which is as it should be since I don't share my keys with anyone.

    The last real Windows update was on 1/10/13 which was a handful of current security updates, no apparent issues after that.  The only update today was the definition update for Microsoft Security Essentials ver 1.141.3816.0.

    A little curious as to the inconsistent results between the two tools.  The validation tool that fails is here:

    http://www.microsoft.com/genuine/validate/

    It whirs for a while and that shows the result of "Files that Windows needs to work properly have been modified, removed, or disabled. To resolve, you need to install genuine Windows. "

    Diagnostic Report (1.9.0019.0):
-----------------------------------------
WGA Data-->
Validation Status: Genuine
Validation Code: 0

Cached Validation Code: 0x0
Windows Product Key: *****-*****-WHJ46-TFF4G-49PWV
Windows Product Key Hash: IFl7i7eUzhJ1OuLXaZf0z9He/bc=
Windows Product ID: 00426-065-1394121-86760
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {18DB7B27-D13B-4753-988F-5FAE49632933}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

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

WGA 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:\Users\Chris\AppData\Local\Google\Chrome\Application\chrome.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\sppobjs.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514]
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514]

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{18DB7B27-D13B-4753-988F-5FAE49632933}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-49PWV</PKey><PID>00426-065-1394121-86760</PID><PIDType>5</PIDType><SID>S-1-5-21-3124375037-947514836-3420421309</SID><SYSTEM><Manufacturer>MICRO-STAR INTERNATIONAL CO.,LTD</Manufacturer><Model>MS-7345</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.8</Version><SMBIOSVersion major="2" minor="5"/><Date>20080124000000.000000+000</Date></BIOS><HWID>5FF63307018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: a0cde89c-3304-4157-b61c-c8ad785d1fad
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00172-065-139412-00-1033-7600.0000-2342010
Installation ID: 008541003506932532583394349492345440348844050601973881
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: 49PWV
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 1/13/2013 3:11:41 PM

Windows Activation Technologies-->
HrOffline: 0x8004FE21
HrOnline: 0x00000000
HealthStatus: 0x000000000000A8B0
Event Time Stamp: 1:13:2013 15:05
WAT Activex: Registered
WAT Admin Service: Registered

HWID Data-->
HWID Hash Current: PgAAAAIABgABAAIAAQACAAAAAgABAAEA6GFYKrDwP1Jk/gae5KneISq/iP0Q31DJbAzPsGI94DPEvpLOTFg=

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			012408		APIC1719
  FACP			012408		FACP1719
  HPET			012408		OEMHPET 
  MCFG			012408		OEMMCFG 
  OEMB			012408		OEMB1719
  GSCI			012408		GMCHSCI

    www.chrisnet.net

    Sunday, January 13, 2013 8:34 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    There are 1900 instances of the following error type in the CBS report 

    2013-01-13 15:04:04, Info                  CBS    Session: 30273993_586234426 initialized by client WindowsUpdateAgent.
2013-01-13 15:04:04, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    This suggests to me that there are problems with the registry, more than the file system. -
    your best option for a repair is likely to be a repair install, I suspect.

    Luckily, such installs are relatively painless in Win7, and generally work pretty well. You'll need disk with SP1 embedded.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Wednesday, January 16, 2013 10:12 AM
    Moderator

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi, Chris (5-year MVP this end<g>)

    That's a rare set of file mismatches you have there.

    It's them which are causing your problems.

    Please run CHKDSK /R and SFC /SCANNOW and post the results to your SkyDrive

    A CheckSUR run and log may also be a good idea.

    It's VERY rare to get file mismatch results without an error code - and one or two of the involved files usually result in a failure within the Licensing Data section

    This makes me think that you have a problem in the registry, rather than in the file system - but we do need to check both (hence the blanket test request)

    Have you installed/updated any software lately? Changed your AV?

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Sunday, January 13, 2013 10:41 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks so much Noel!

    Well it looks like I've got some drive issues going on.  The primary drive is a SSD and although the SFC scan was fine, the chkdsk did show some problems.  The question now i guess is what is the best way to repair? 

    Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  193536 file records processed.                                          File verification completed.
  743 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  254074 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  193536 file SDs/SIDs processed.                                         Cleaning up 212 unused index entries from index $SII of file 0x9.
Cleaning up 212 unused index entries from index $SDH of file 0x9.
Cleaning up 212 unused security descriptors.
Security descriptor verification completed.
  30270 data files processed.                                            CHKDSK is verifying Usn Journal...
  36582456 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x3c1343000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3c1351000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3c1352000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3c1352000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3c1353000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3c1353000 for 0x1000 bytes.
Windows replaced bad clusters in file 15633
of name \Users\Chris\AppData\Local\MICROS~1\WINDOW~1\Backup\old\WINDOW~1.MSM.
Read failure with status 0xc000009c at offset 0x3ae8f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3ae91000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3ae92000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3ae92000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3ae93000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3ae93000 for 0x1000 bytes.
Windows replaced bad clusters in file 24817
of name \Windows\winsxs\AM971D~1.163\Query.dll.
Read failure with status 0xc000009c at offset 0x3b008000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3b011000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3b012000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3b012000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3b013000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3b013000 for 0x1000 bytes.
Windows replaced bad clusters in file 112249
of name \Windows\SysWOW64\D3DCSX~1.DLL.
Read failure with status 0xc000009c at offset 0x3c11d0000 for 0x9000 bytes.
Read failure with status 0xc000009c at offset 0x3c11d1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3c11d2000 for 0x7000 bytes.
Read failure with status 0xc000009c at offset 0x3c11d2000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3c11d3000 for 0x6000 bytes.
Read failure with status 0xc000009c at offset 0x3c11d3000 for 0x1000 bytes.
Windows replaced bad clusters in file 128550
of name \Windows\winsxs\AMEAA2~1.211\CRYPT3~1.MUI.
Read failure with status 0xc000009c at offset 0x8892cc000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8892d1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8892d2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8892d2000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8892d3000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8892d3000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x889444000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x889451000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x889452000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x889452000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x889453000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x889453000 for 0x1000 bytes.
Windows replaced bad clusters in file 137757
of name \Windows\System32\catroot\{F750E~1\MID8CB~1.CAT.
  193520 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  7404030 free clusters processed.                                         Free space verification is complete.
Adding 18 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 124930047 KB total disk space.
  94928580 KB in 132149 files.
     84312 KB in 30271 indexes.
        72 KB in bad sectors.
    300959 KB in use by the system.
     65536 KB occupied by the log file.
  29616124 KB available on disk.

      4096 bytes in each allocation unit.
  31232511 total allocation units on disk.
   7404031 allocation units available on disk.

Internal Info:
00 f4 02 00 7f 7a 02 00 47 a9 04 00 00 00 00 00  .....z..G.......
50 05 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  P...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.


    www.chrisnet.net

    Tuesday, January 15, 2013 2:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The only repair worth doing is replacing the drive :(

    It looks to me as if it may be about to fail badly - 18 bad sectors on an SSD is not good.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Tuesday, January 15, 2013 9:04 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well that part is a given, the good news is that SSD prices have been dropping recently.

    What I meant was if I get the install transferred to a clean drive can I replace those files by copying from another installation or will file protection balk me?

    www.chrisnet.net

    Tuesday, January 15, 2013 12:53 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    To be honest, I have no idea! - certainly a direct copy will be blocked.

    You could try SFC /SCANNOW again - unless you already ran it after the CHKDSK.

    CheckSUR would be a good idea - it may point up both file and registry problems.

    http://support.microsoft.com/kb/947821

    Please post both the CBS.log file and the CheckSUR.log file, and I'll take a look.

    The CBS log contains a lot more detail than is seen in just the sfcdetails.txt file that the KB tells you to extract - not a lot of which I understand, but which may give me some idea where to start looking.

    The CheckSUR log may contain data which again points up an area for investigation, if not repair (I can deal with a lot of the errors that the report could throw up, but I may have to call the cavalry if it starts getting exotic!)

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Tuesday, January 15, 2013 1:25 PM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Neal,

    Yes I ran SFC /SCANNOW again and it reported no integrity violations.

    I ran CheckSUR again and it also said that there were no errors (according to CheckSUR.log).

    CheckSUR.log

    CBS.log

    Thanks,
    Chris

    www.chrisnet.net

    Wednesday, January 16, 2013 2:41 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Here's where the plot thickens a little.

    The MGADiag tool originally reported the following:

    File Scan Data-->
File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514]
File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514]
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514]

    So I decided to compare these files to a known good Windows 7 x64 system and the files are binary idential!  Just for giggles I tried replacing a couple of the files by taking ownership with "takeown" and "cacls" and was able to rename the old and replace, but it made no difference in MGADiag.

    So it would seem the files are good but somehow the stored signature values are what is actually corrupt, and I suspect there is no easy way to fix that short of a service pack install that happens to replace the files.

    www.chrisnet.net

    Wednesday, January 16, 2013 3:07 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    There are 1900 instances of the following error type in the CBS report 

    2013-01-13 15:04:04, Info                  CBS    Session: 30273993_586234426 initialized by client WindowsUpdateAgent.
2013-01-13 15:04:04, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    This suggests to me that there are problems with the registry, more than the file system. -
    your best option for a repair is likely to be a repair install, I suspect.

    Luckily, such installs are relatively painless in Win7, and generally work pretty well. You'll need disk with SP1 embedded.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Wednesday, January 16, 2013 10:12 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Neil,

    I'm hoping the repair will take care of it.  I will download the integrated SP1 version from MSDN and try it out this weekend.

    Thanks,
    Chris

    www.chrisnet.net

    Wednesday, January 16, 2013 8:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Good luck! - let us know how it comes out.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Wednesday, January 16, 2013 8:55 PM
    Moderator