Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows 7 Ultimate, Error 7601. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Installed Windows 7 Ultimate in 2011 but install was marked not genuine on 01/01/13.  I purchased sealed retail copy of Win 7 Ultimate and no problems until yesterday.  There was a issue where Babylon invaded my P.C. and turned off my Norton Security (which is now solved), But there is now a message in bottom right hand corner of the screen, (Windows 7 Build 7601 This copy of Windows is not genuine) and the screen is black.

    Diagnostics Tool Information:-

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-F2YXM-G9K7P-62PTM
    Windows Product Key Hash: 3wfGxvPwKgyWfBLUzJwYXRvUmwQ=
    Windows Product ID: 00426-068-2813383-86541
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {D67F563C-973E-4F50-B0F1-30D7219FB1FC}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000000
    Build lab: 7601.win7sp1_gdr.120830-0333
    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: 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\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>{D67F563C-973E-4F50-B0F1-30D7219FB1FC}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-62PTM</PKey><PID>00426-068-2813383-86541</PID><PIDType>5</PIDType><SID>S-1-5-21-2722605212-46756544-3448253712</SID><SYSTEM><Manufacturer>Dell Inc.                </Manufacturer><Model>Precision WorkStation 690    </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.                </Manufacturer><Version>A06</Version><SMBIOSVersion major="2" minor="3"/><Date>20070820000000.000000+000</Date></BIOS><HWID>E7113D07018400FA</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><OEMID>DELL  </OEMID><OEMTableID>B8K    </OEMTableID></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-068-281338-00-2057-7601.0000-0022013
    Installation ID: 013523656504586225397412054332878896366445551841254484
    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: 62PTM
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 5
    Trusted time: 02/01/2013 19:50:50

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 1:2:2013 18:55
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAEAAQACAAAAAwABAAEA6GFifbbPckMckFKy7mIkiwoVbJJiPbynk4/AdypjKoU=

    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 DELL   B8K    
      FACP DELL   B8K    
      HPET DELL   B8K    
      BOOT DELL   B8K    
      MCFG DELL   B8K    
      SSDT DELL st_ex
      ASF! DELL   B8K    
      TCPA DELL   B8K    
      SLIC DELL   B8K    

    Wednesday, January 2, 2013 8:07 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The Key in use is an MSDN Key from a not-for-resale MSDN account.

    Unless you are an MSDN subscriber, you are not entitled to use the Key – and whoever sold it to you was not entitled to do so. 

    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 posts.... .................................

     

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

     

    and

     

    http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/309bb621-92d5-43d6-98c1-2bb51b35607f

     

    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 months. 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, January 2, 2013 8:49 PM
    Moderator