none
Windows 7 no longer genuine after 2 years RRS feed

  • Question

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-MJWX9-VTJ8X-69R3F
    Windows Product Key Hash: G+tktUPFOd/JjHY0MvviXAyYIeA=
    Windows Product ID: 00426-067-1771327-86732
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {2C2DE122-7C3D-4AAD-B519-BB69C218E38D}(3)
    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: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{2C2DE122-7C3D-4AAD-B519-BB69C218E38D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-69R3F</PKey><PID>00426-067-1771327-86732</PID><PIDType>5</PIDType><SID>S-1-5-21-1379921728-3881635146-3963567939</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7260</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.6</Version><SMBIOSVersion major="2" minor="5"/><Date>20070206000000.000000+000</Date></BIOS><HWID>B0FE3607018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>E. Australia Standard Time(GMT+10: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-067-177132-00-3081-7601.0000-1702011
    Installation ID: 016290490290900863612992468474310582281720430816103566
    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: 69R3F
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 4
    Trusted time: 6/19/2011 1:01:31 PM

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


    HWID Data-->
    HWID Hash Current: NgAAAAIAAgABAAEAAgADAAAAAQABAAEAeqiiNRU/blSSADDmbpbQTdaEd/ZiPXhm7404kibp

    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            A M I         OEMAPIC
      FACP            A M I         OEMFACP
      HPET            A M I         OEMHPET0
      MCFG            A M I         OEMMCFG
      OEMB            A M I         AMI_OEM


    I bought this copy on about 12th of April 2010 and installed it a week later. The non-genuine message came up about a month ago.
    Sunday, June 19, 2011 4:08 AM

Answers

All replies

  • "Ren128" wrote in message news:16b5a641-f87e-49b7-9bcd-d0a86aaed3f4...
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-MJWX9-VTJ8X-69R3F
    Windows Product Key Hash: G+tktUPFOd/JjHY0MvviXAyYIeA=
    Windows Product ID: 00426-067-1771327-86732
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001


    I bought this copy on about 12th of April 2010 and installed it a week later. The non-genuine message came up about a month ago.
    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
    Sunday, June 19, 2011 11:39 AM
    Moderator
  • "Ren128" wrote in message news:16b5a641-f87e-49b7-9bcd-d0a86aaed3f4...
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-MJWX9-VTJ8X-69R3F
    Windows Product Key Hash: G+tktUPFOd/JjHY0MvviXAyYIeA=
    Windows Product ID: 00426-067-1771327-86732
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001



    I bought this copy on about 12th of April 2010 and installed it a week later. The non-genuine message came up about a month ago.

    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
    Sunday, June 19, 2011 11:51 AM
    Moderator
  • Getting a refund might be a bit difficult, since I've purchased this copy of W7 over 2 years ago and the seller hasn't been active for at least over a year now.

    Anyways, what I really want to know is, how come it took Microsoft TWO YEARS to decide that my copy of windows is non-genuine? How come they couldn't do this straight away, or at least within 30 days, so I least I could have a chance of getting a refund?

     

     

    Monday, June 20, 2011 5:41 AM
  • "Ren128" wrote in message news:04f5f6d8-63f6-4b13-aef3-e6151152cfe3...

    Getting a refund might be a bit difficult, since I've purchased this copy of W7 over 2 years ago and the seller hasn't been active for at least over a year now.

    Anyways, what I really want to know is, how come it took Microsoft TWO YEARS to decide that my copy of windows is non-genuine? How come they couldn't do this straight away, or at least within 30 days, so I least I could have a chance of getting a refund?

     

     


    Obviously, this particular Key has not been sold that often - it takes a number of activations to trigger MS to block the account, and a clever counterfeiter will space out sales of all his available licenses so that they are all maxed out before he then either does a runner or floods the market and runs before the clients catch him.
     
    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 6:18 AM
    Moderator