locked
Windows 7 Build 7600 showing up as not genuine RRS feed

  • Question

  • Hi, as of today my Windows 7 Professional has started showing me the message stating that it is not a genuine copy - after 4 months without any problems.  It is a genuine copy, so why am I getting this message?  I've included the results of my MGADiag scan below:

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-HW8WR-CRFKT-T33KG
    Windows Product Key Hash: SVaC4Vgs+JoY7+cNKGHwrDYjHnI=
    Windows Product ID: 00371-221-4071493-86387
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {E2DFA746-D1FA-45AB-83CE-825EF308B715}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000000
    Build lab: 7600.win7_gdr.101026-1503
    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 Professional Plus 2007 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Opera\Opera.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>{E2DFA746-D1FA-45AB-83CE-825EF308B715}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-T33KG</PKey><PID>00371-221-4071493-86387</PID><PIDType>5</PIDType><SID>S-1-5-21-2427355501-4193732991-4193941989</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS P5N32-E SLI PLUS ACPI BIOS Revision 0805</Version><SMBIOSVersion major="2" minor="4"/><Date>20070822000000.000000+000</Date></BIOS><HWID>0EBB3607018400FA</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>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>83770C147C39586</Val><Hash>HujjXRyTgOYjf4RCWfGtC0B0HlY=</Hash><Pid>89409-707-1230233-65789</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: 770bc271-8dc1-467d-b574-73cbacbeccd1
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00172-221-407149-00-2057-7600.0000-0942011
    Installation ID: 014101716676748061700412402743416892211523246046328253
    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: T33KG
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 3
    Trusted time: 04/04/2011 23:29:02

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 4:4:2011 08:49
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NAAAAAEAAgABAAEAAQACAAAAAwABAAEA6GGyrVpirDuSAHYQ+jHczeJxB4NEmKDHYWDMMQ==

    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   Nvidia  ASUSACPI
      FACP   Nvidia  ASUSACPI
      HPET   Nvidia  ASUSACPI
      MCFG   Nvidia  ASUSACPI


    Thanks.

     

    Monday, April 4, 2011 10:39 PM

Answers

All replies

  • From your MGA Report:

    Windows Product ID: 00371-221-4071493-86387

    Unfortunately, the installed copy of Windows 7 Professional was found to be a "not-for-resale" MSDN Subscription license.  In order to fix this problem, you'll need to purchase a Genuine Windows 7 Professional – Full Version and change the product key.  Follow these steps to change your product key in Windows 7.

    More info: Blocked Product Keys


    Carey Frisch
    Monday, April 4, 2011 11:19 PM
    Moderator
  • The key is genuine but not valid for your use unless you are the MSDN subscriber to whom it was issued. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Monday, April 4, 2011 11:35 PM
    Answerer
  • "TheTJW" wrote in message news:0b498eb9-69ef-4479-8189-529088ac74c5...

    Hi, as of today my Windows 7 Professional has started showing me the message stating that it is not a genuine copy - after 4 months without any problems.  It is a genuine copy, so why am I getting this message?  I've included the results of my MGADiag scan below:

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-HW8WR-CRFKT-T33KG
    Windows Product Key Hash: SVaC4Vgs+JoY7+cNKGHwrDYjHnI=
    Windows Product ID: 00371-221-4071493-86387
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048


    Thanks.

     

    Your Key is from a not-for-resale MSDN account. You need to claim an immediate refund from the vendor - do NOT accept the offer of a new key.(all they are trying to do is to get past the 45-day claims window. or avoid you sending the evidence of their crimes to the authorities)
     
    Please read the following stickies.... ..
     
    http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/a2444f34-0aff-4f29-a8ac-67e28b0c0285
     
    and
     
    http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/06698c46-8668-4ccd-a544-a88969265a6b
     
    The pirates have got VERY good at this over the past few years, as the price of equipment for manufacturing the packages drops, and as factories open in less well-policed countries.
     
    see also this post....
     
    http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/46a58748-5a64-41ff-b7f4-f6d3b47beca9
     
     
    Also - have a look at this video....
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, April 5, 2011 5:47 AM
    Moderator
  • Ok, thanks for your help and advice.  Just wondering though, would it not make sense for you to be informed that the key belongs a not-for-resale MSDN account when you input the product key for the first time when installing the software?  As I purchased this copy of Windows 7 about 5 months ago, I'm not sure what come-back I'm going to have from the seller.
    Tuesday, April 5, 2011 10:20 AM
  • "TheTJW" wrote in message news:edbc4a7b-f9aa-4565-bb15-57fdde18687f...
    Ok, thanks for your help and advice.  Just wondering though, would it not make sense for you to be informed that the key belongs a not-for-resale MSDN account when you input the product key for the first time when installing the software?  As I purchased this copy of Windows 7 about 5 months ago, I'm not sure what come-back I'm going to have from the seller.

    I agree with you - hopefully MS will take this sort of suggestion onboard for the future.
    It shouldn't take too much to put a flag in the system on activation to point up the license-type.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, April 5, 2011 11:47 AM
    Moderator
  • So just to clarify, can I purchase a product ID for Windows 7 Professional only and enter that as a new ID for my current installation, or do I have to buy the complete product and use the Product ID from that to authenticate my current installation?

    Thanks.

    Tuesday, April 5, 2011 12:12 PM
  •  can I purchase a product ID for Windows 7 Professional

    Just to be clear, the Product Key is the 25 character string you get with your copy of Windows and input to activate.  It is a new Product Key that you need.  The Product ID is generated by Setup when you install Windows and is found at the bottom of the System Properties page.  It is the string that Microsoft Support techs ask for when you call with a problem. 

    You cannot purchase a legit product key by itself.  You purchase a copy of Windows to get the key.  In your case, if you purchase a full license copy of Windows 7 Professional you can clear the non genuine condition by entering the new product key at the Change Product Key link at the bottom of the System Properties page.  You do not have to reinstall Windows if you feel the present copy is otherwise safe from malware. 

    The System Properties page is reached by pressing WinKey + Pause.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, April 5, 2011 12:28 PM
    Answerer
  • Ok, thanks for your help and advice.  Just wondering though, would it not make sense for you to be informed that the key belongs a not-for-resale MSDN account when you input the product key for the first time when installing the software?  As I purchased this copy of Windows 7 about 5 months ago, I'm not sure what come-back I'm going to have from the seller.

           You can purchase a Genuine Windows 7 Professional – Full Version Product Key and then change the product key. Follow these steps to change the product key in Windows 7.
    Carey Frisch
    Tuesday, April 5, 2011 2:31 PM
    Moderator
  • Ok, thanks for your help and advice.  Just wondering though, would it not make sense for you to be informed that the key belongs a not-for-resale MSDN account when you input the product key for the first time when installing the software?  As I purchased this copy of Windows 7 about 5 months ago, I'm not sure what come-back I'm going to have from the seller.

    One problem with that is that MSDN (Microsoft Developer Network) was created to allow Developers to develop software that works with Microsoft products. Microsoft products available through the MSDN subscriptions are usually Retail versions so that when a developer tests thier software against MSDN software, they can be sure that the MSDN software is the same thing as what consumers will be using. Now, If we make changes to the MSDN software (even small changes like a new install screen that informs the user that it is MSDN Key being used) then MSDN software would no longer be the same as consumer software and developers couldn't be sure the software they are developing will work the same when used with Retail (non-msdn) software.

    "Instead of just changing the MSDN software, Why not change all Microsoft products so they inform the user that an MSDN key is being used?"

    Well, first off, that is a big job. But aside from that, major problem with that approach is that if we change all Microsoft software, now, what's to stop a pirate from using the old (unchanged) software instead? In other words, if Microsoft re-codes all it's software so that during install, it will inform the user if an MSDN key is being used, pirates will still use the old software that Doesn't inform the user if an MSDN key is being used.

     

    It's possible that Microsoft will do this for future products, but trying to retroactively change all past products would be unfeasible and still wouldn't actually resolve the issue.


    Darin MS
    Tuesday, April 5, 2011 9:19 PM
  • Just as an after thought, why exactly has this issue shown up suddenly, 4 months after I purchased Windows 7 Professional?
    Tuesday, April 5, 2011 10:47 PM
  • Because the product key is a genuine MSDN product key.  It took this long for Microsoft to detect that it was an abused key and invalidate it.  MSDN product keys are good for activation on ten installations at the same time.  By selling short of the threshhold that gets Microsoft's attention the crooks can stretch the time for detection while they sell more product on their websites.  When they are ready to cash out the crooks "dump" on the market and scoot.  This is when the product key gets flagged and shortly afterwards you see the notification.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, April 5, 2011 10:58 PM
    Answerer
  • "TheTJW" wrote in message news:fa3c315d-3ead-45c9-b2cf-d0167bd3f674...
    Just as an after thought, why exactly has this issue shown up suddenly, 4 months after I purchased Windows 7 Professional?
    Here's my standard spiel on the time-delays involved in tagging abused keys....
     
    For MSDN Keys:-
     
    MS can only act once a key hits a threshold (and they won't tell an outsider what that threshold is, understandably). They then have to put it through internal systems to ensure that all relevant parties are informed, just in case it's an oversight - then it enters the queue for the next update to the system. I have no idea how often the WAT checking system is updated, but I would suspect that it's no more than weekly because of admin and timing issues. The internal MS processes could therefore take easily a couple of weeks.
    It therefore depends on how close to the end of a vendors sales list you are, and how quickly he's selling them.
    The cannier ones will sell just enough to stay under the threshold for each product (MSDN subs include a huge number of products), until they've maximised the profits, then try and flood the market before disappearing into the sunset, laden with your cash. This could take anything up to a year or more.
     
    For products sold using a loader:-
    The loader gets around online activation by fooling the computer into thinking that the OS is installed onto the correct machine, by modifying certain files. Because of a number of factors, it's impossible to stop this, so MS came up with the WAT update - which has the ability to scan the relevant files, and detect the use of a loader tool. If the user fully updates the machine, including recommended updates and optional updates, then the WAT update is installed and starts work, and within 3 days, a loader-installed machine will get a notification. However, the WAT update is a voluntary one, at least at the first update run, and can be uninstalled, or refused
    The other time the WAT update is installed, is when you validate Windows for some reason - it is part of the validation process, rather than the activation process. this time, it does the scan immediately, and again this will show as non-genuine if a Loader is present.
    If a user never needs/wants to validate, then they need never install the WAT update, and may never see a non-genuine notification.

     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, April 6, 2011 5:45 AM
    Moderator
  • "Darin Smith MS" wrote in message news:e54058d2-9e1b-4d5b-a5b4-8a3fcdb8dd9c...
    Ok, thanks for your help and advice.  Just wondering though, would it not make sense for you to be informed that the key belongs a not-for-resale MSDN account when you input the product key for the first time when installing the software?  As I purchased this copy of Windows 7 about 5 months ago, I'm not sure what come-back I'm going to have from the seller.

    One problem with that is that MSDN (Microsoft Developer Network) was created to allow Developers to develop software that works with Microsoft products. Microsoft products available through the MSDN subscriptions are usually Retail versions so that when a developer tests thier software against MSDN software, they can be sure that the MSDN software is the same thing as what consumers will be using. Now, If we make changes to the MSDN software (even small changes like a new install screen that informs the user that it is MSDN Key being used) then MSDN software would no longer be the same as consumer software and developers couldn't be sure the software they are developing will work the same when used with Retail (non-msdn) software.

    "Instead of just changing the MSDN software, Why not change all Microsoft products so they inform the user that an MSDN key is being used?"

    Well, first off, that is a big job. But aside from that, major problem with that approach is that if we change all Microsoft software, now, what's to stop a pirate from using the old (unchanged) software instead? In other words, if Microsoft re-codes all it's software so that during install, it will inform the user if an MSDN key is being used, pirates will still use the old software that Doesn't inform the user if an MSDN key is being used.

     

    It's possible that Microsoft will do this for future products, but trying to retroactively change all past products would be unfeasible and still wouldn't actually resolve the issue.


    Darin MS

    It should actually be possible to make changes retrospective with a server-side update - at least for future products.
    If the activation return from the servers includes a tag that flags the key-type in use, then there need be no difference in the client-side bits between any of the activation clients or keytypes, except for the actual Key. Even the telephone activation scripts could be adjusted to cope with this relatively easily.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, April 6, 2011 6:13 AM
    Moderator