locked
Counterfit WIndows after 5 months, why so long? RRS feed

  • Question

  • Hi,

     

    I have just been noptified that my 6 month old copy of Windows 7 is counterfit.  Now my question is simple, why does it take so long to be notified that it is a copy?  The problem is simply that any consumer protection that you have with PayPal for example is only 45 days, so this long period of time is actually takling away any proteciton, other than credit card purchases that we as consumers have. We all buy in good faith. So why so long to be notifed?

     

    Cheers,

     

    Gareth

    Saturday, April 23, 2011 10:24 AM

Answers

  • "Garethhj1969" wrote in message news:4697cb62-3620-40a2-a642-ca906b1fcbba...
    Here is my report:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-PQ324-9QMJM-GF949
    Windows Product Key Hash: ePlbvencxsIveGpZZ0kwNob+wvg=
    Windows Product ID: 00371-221-3135574-86118
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
     
    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
     

    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
    Saturday, April 23, 2011 2:12 PM
    Moderator

All replies

  • "Garethhj1969" wrote in message news:8b41610a-7369-44d2-b619-52bffe7b0e36...

    Hi,

     

    I have just been noptified that my 6 month old copy of Windows 7 is counterfit.  Now my question is simple, why does it take so long to be notified that it is a copy?  The problem is simply that any consumer protection that you have with PayPal for example is only 45 days, so this long period of time is actually takling away any proteciton, other than credit card purchases that we as consumers have. We all buy in good faith. So why so long to be notifed?

     

    Cheers,

     

    Gareth


    There are many reasons why an installation could be showing as potentially non-genuine...
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, April 23, 2011 11:21 AM
    Moderator
  • I have the same problem with a copy I bought on Ebay.

    I called microsoft and they explained that I have an MDN copy for developers which has a 6 month license.

    Tried getting satisfaction from Ebay, but the purchase is too long ago.

    Just have to buy another copy or key according to microsoft.

    Steve

    Saturday, April 23, 2011 12:48 PM
  • @calsteve347

    Please observe both announcements above.


      Most Non-Genuine issues look the same regardless of the true underlying cause. So to help minimize the confusion caused by troubleshooting multiple different issues, we ask that all users creat their own thread for thier own specific issue.

    In other words, please do not post "Me Too" messages in other people's threads.

      In order to receive the best support, we request all users initially download and run the Genuine Diagnostics tool (MGADiag.exe) at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue", click the "Copy" button then “Paste” the report into a reply message in this thread.

     


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Saturday, April 23, 2011 1:24 PM
    Answerer
  • Here is my report:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-PQ324-9QMJM-GF949
    Windows Product Key Hash: ePlbvencxsIveGpZZ0kwNob+wvg=
    Windows Product ID: 00371-221-3135574-86118
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {C3273CD5-C6FE-4301-8B81-0E11B3D53315}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    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 Ultimate 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:\Users\Gareth\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-->
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{C3273CD5-C6FE-4301-8B81-0E11B3D53315}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-GF949</PKey><PID>00371-221-3135574-86118</PID><PIDType>5</PIDType><SID>S-1-5-21-2696049978-1362781956-1267977470</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0303   </Version><SMBIOSVersion major="2" minor="5"/><Date>20100525000000.000000+000</Date></BIOS><HWID>F7B83607018400FE</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="{91120000-002E-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Ultimate 2007</Name><Ver>12</Ver><Val>2D3483888E6EF7A</Val><Hash>RwNjclKBNuSj9MYCSmmfgseheKg=</Hash><Pid>81608-957-4378904-65634</Pid><PidType>1</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"/><App Id="A1" Version="12" Result="100"/><App Id="BA" 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-313557-00-2057-7600.0000-1112011
    Installation ID: 012796832243053364295223726543182374999216128550340865
    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: GF949
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 3
    Trusted time: 23/04/2011 15:08:41
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 4:21:2011 17:35
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAgABAAAAAQABAAEAonYYUiSlRryENIwmaGV24qLx7ngwB6ZO1LHqgg==
    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 052510 APIC1439
      FACP 052510 FACP1439
      HPET 052510 OEMHPET 
      MCFG 052510 OEMMCFG 
      OEMB 052510 OEMB1439
      ASPT 052510 PerfTune
      OSFR 052510 OEMOSFR 
      SSDT DpgPmm CpuPm
    Saturday, April 23, 2011 2:09 PM
  • "Garethhj1969" wrote in message news:4697cb62-3620-40a2-a642-ca906b1fcbba...
    Here is my report:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-PQ324-9QMJM-GF949
    Windows Product Key Hash: ePlbvencxsIveGpZZ0kwNob+wvg=
    Windows Product ID: 00371-221-3135574-86118
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
     
    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
     

    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
    Saturday, April 23, 2011 2:12 PM
    Moderator