locked
Windows 7 Build 7601 This copy of Windows is not genuine RRS feed

  • Question

  • I have been running Windows 7 Ultimate for many months.  Suddenly, I'm getting the not genuine message.

    Here are the results from the diagnostics:

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-B933G-WG9KM-3B37F
    Windows Product Key Hash: BXbJQ7q5TqSLbIQlhFBCRtlNi0k=
    Windows Product ID: 00426-068-3059821-86795
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {76C5EF85-4B47-45F8-99C8-5687E2FCC8CD}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110408-1631
    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 (x86)\Mozilla Firefox 4.0 Beta 12\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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{76C5EF85-4B47-45F8-99C8-5687E2FCC8CD}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3B37F</PKey><PID>00426-068-3059821-86795</PID><PIDType>5</PIDType><SID>S-1-5-21-1929369317-3293861376-3313198689</SID><SYSTEM><Manufacturer>LENOVO</Manufacturer><Model>6459CTO</Model></SYSTEM><BIOS><Manufacturer>LENOVO</Manufacturer><Version>7LETB7WW (2.17 )</Version><SMBIOSVersion major="2" minor="4"/><Date>20080425000000.000000+000</Date></BIOS><HWID>EBDC3507018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>LENOVO</OEMID><OEMTableID>TP-7L   </OEMTableID></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>B0FD2112440BEBA</Val><Hash>QCGYmzJq1rY9hekck1+2JQghKq4=</Hash><Pid>89409-861-6128792-65755</Pid><PidType>8</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.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-068-305982-00-1033-7601.0000-1712011
    Installation ID: 019993864623739745200590352370154621122343850490552485
    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: 3B37F
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 4
    Trusted time: 6/20/2011 10:23:38 AM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 6:20:2011 09:59
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: OAAAAAEABQABAAEAAAACAAAAAwABAAEA6GEKn8G1LghGgwYMAC0an6KfWNBGBv/4i60C/mYmRso=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x0
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            LENOVO        TP-7L  
      FACP            LENOVO        TP-7L  
      HPET            LENOVO        TP-7L  
      BOOT            LENOVO        TP-7L  
      MCFG            LENOVO        TP-7L  
      SSDT            LENOVO        TP-7L  
      ECDT            LENOVO        TP-7L  
      TCPA            LENOVO        TP-7L  
      SLIC            LENOVO        TP-7L  
      ASF!            LENOVO        TP-7L  
      SSDT            LENOVO        TP-7L  
      SSDT            LENOVO        TP-7L  
      SSDT            LENOVO        TP-7L  
      SSDT            LENOVO        TP-7L  


    My product code is not 221; so, I don't think this is the msdn problem.

    Thanks for any help/

    Monday, June 20, 2011 5:49 PM

Answers

All replies


  • "

    Windows Product ID: 00426-068-6851602-86240

     

    The product ID -068- Indicates a not for resale MSDN account. If you are not the account holder and you purchased this in a retail box, the box and it's contents are counterfeit.

    For more information see this:

     http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/a2444f34-0aff-4f29-a8ac-67e28b0c0285

    To see how good these counterfeits are becoming, see:

    http://www.youtube.com/watch?v=hzqNNiOM0cs

    You will have to purchase a legitimate windows from a legitimate retailer."

     

    Thats the answer I got in my thread.looks like you have 068 as part of you product ID too.I'm no expert though.

    Monday, June 20, 2011 5:57 PM
  • "kafrey-bfordhsl" wrote in message news:b47d30c5-34c9-46bb-a25d-81e794ba0d6f...

    I have been running Windows 7 Ultimate for many months.  Suddenly, I'm getting the not genuine message.

    Here are the results from the diagnostics:

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-B933G-WG9KM-3B37F
    Windows Product Key Hash: BXbJQ7q5TqSLbIQlhFBCRtlNi0k=
    Windows Product ID: 00426-068-3059821-86795
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001


    My product code is not 221; so, I don't think this is the msdn problem.

    Thanks for any help/

    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....
     
     
    http://www.youtube.com/watch?v=hzqNNiOM0cs
     

     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, June 20, 2011 6:34 PM
    Moderator
  • "Kless58" wrote in message news:e28d75a5-bdc8-4480-b9f8-cf7ff2fb6a7f...

    "

    Windows Product ID: 00426-068-6851602-86240

     

    The product ID -068- Indicates a not for resale MSDN account. If you are not the account holder and you purchased this in a retail box, the box and it's contents are counterfeit.

    For more information see this:

     http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/a2444f34-0aff-4f29-a8ac-67e28b0c0285

    To see how good these counterfeits are becoming, see:

    http://www.youtube.com/watch?v=hzqNNiOM0cs

    You will have to purchase a legitimate windows from a legitimate retailer."

     

    Thats the answer I got in my thread.looks like you have 068 as part of you product ID too.I'm no expert though.


    Ah  - the power of " Been there - got the T-Shirt!" :)
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, June 20, 2011 6:35 PM
    Moderator
  • The 45 day from eBay would be great IF Microsoft had notified me of the problem with the software in a timely manner.

    I installed the software back in early December and it' taken Microsoft more than six months to find that it's bogus.

    Oh, well.  Live and learn I guess

    Monday, June 20, 2011 6:45 PM
  • "kafrey-bfordhsl" wrote in message news:b6a847b6-b129-4257-95b1-c9612075eb82...

    The 45 day from eBay would be great IF Microsoft had notified me of the problem with the software in a timely manner.

    I installed the software back in early December and it' taken Microsoft more than six months to find that it's bogus.

    Oh, well.  Live and learn I guess


    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
    Monday, June 20, 2011 7:30 PM
    Moderator
  • It seems to me that Microsoft could do a bit more to help the average consumer avoid this problem.

    I would suspect that the population of Microsoft users can easily be totally bifurcated: either a user understands what an MSDN product is or he does not.  In either case, the Windows installer could tell the user when he installs an MSDN product.  The installer could then warn the user about the effects of using such a product.  If the user falls into the first category, he can easily deal with the notification.  If the user falls into the second category, he will have sufficient time to deal with the seller without having to wait for many months to pass before he is abruptly notified that he is not running a "genuine" product.

    Tuesday, June 21, 2011 2:02 AM
  • "kafrey-bfordhsl" wrote in message news:1d125e98-4dd9-4d96-886f-a37eb73b5d97...

    It seems to me that Microsoft could do a bit more to help the average consumer avoid this problem.

    I would suspect that the population of Microsoft users can easily be totally bifurcated: either a user understands what an MSDN product is or he does not.  In either case, the Windows installer could tell the user when he installs an MSDN product.  The installer could then warn the user about the effects of using such a product.  If the user falls into the first category, he can easily deal with the notification.  If the user falls into the second category, he will have sufficient time to deal with the seller without having to wait for many months to pass before he is abruptly notified that he is not running a "genuine" product.


    This (or variants of it) has been suggested a number of times - hopefully MS is taking it on board.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, June 21, 2011 5:29 AM
    Moderator