Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows 7 no longer genuine after reconfiguring dual boot. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been using a dual boot, dual HDD box with Win7 / XP for many months, defaulting to Win 7 Ulttimate. I use EasyBCD for the dual boot. I went into the bios to dump the opening logo screen and  loaded all the defaults by accident. One of those "not thinking it through" moments.  It booted into XP and I had lost all my dual boot settings. So I reconfigured them. Booted fine into Win 7 but I now get the message "Windows Computer Build 7600, This copy of Windows is not genuine". Very frustrating. Here is my diag. report:

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 50

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2

    Windows Product Key Hash: W5/6nm6F2UPXrCkY5xUhXb/+21g=

    Windows Product ID: 00426-OEM-8992662-00006

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7600.2.00010100.0.0.001

    ID: {ACF3C02E-80D2-47CE-AD2F-3C6BB0920975}(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: 7600.win7_gdr.100618-1621

    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:\Users\Ty\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>{ACF3C02E-80D2-47CE-AD2F-3C6BB0920975}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HYRR2</PKey><PID>00426-OEM-8992662-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-3325024052-503416123-2930752354</SID><SYSTEM><Manufacturer>NVIDIA</Manufacturer><Model>122-CK-NF68</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="4"/><Date>20070928000000.000000+000</Date></BIOS><HWID>13B83607018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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.7600.16385

     

    Name: Windows(R) 7, Ultimate edition

    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel

    Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00426-00178-926-600006-02-1033-7600.0000-0332011

    Installation ID: 019865453623463202129653328701027880653603984173143764

    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: HYRR2

    License Status: Notification

    Notification Reason: 0xC004F063.

    Remaining Windows rearm count: 2

    Trusted time: 2/2/2011 10:48:30 AM

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: 0xC004C533

    HealthStatus: 0x0000000000000000

    Event Time Stamp: 2:2:2011 09:21

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

     

     

    HWID Data-->

    HWID Hash Current: NAAAAAIAAgABAAEAAQACAAAAAgABAAEAln2iWSQPEDmSAEwfdmRKK45mCtaY6WTu3AqA1w==

     

    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 NVDAACPI

      FACP Nvidia NVDAACPI

      HPET Nvidia NVDAACPI

      MCFG Nvidia NVDAACPI

      WDRT Nvidia NVDAACPI

     

     

    Wednesday, February 2, 2011 4:31 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2

    ><PID>00426-OEM-8992662-00006</PID>

    Manufacturer>NVIDIA</Manufacturer><Model>122-CK-NF68</Model></SYSTEM>

    <BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="4"/><Date>20070928000000.000000+000</Date></BIOS><HWID>13B83607018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern BIOS valid for OA 2.0: yes, but no SLIC table

     

     

     


    As this is a pirated version of Win 7 OEM for an Acer computer and it was never shipped with your computer (bios too old for Win 7 OEM) you need to purchase a full Win 7 Ultimate and change the product key to make it legal.  That is your only option to make legal with Win 7 Ultimate you have installed.

    If you purchased this and thought it was a legal purchase then you need to contact the seller for an immediate full refund of purchase price.

    • Marked as answer by Darin Smith MS Wednesday, February 2, 2011 10:44 PM
    Wednesday, February 2, 2011 6:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Even though he didn't fully explained the issue in any detail, LVTravel is correct.

     The information that tells us this is a non-genuine copy of Windows 7 is that 1) your Windows is using a Windows 7 OEM SLP key and 2) (as LVTravel has highlighted) the Bios in your PC is dated back to 2007 which is well before Windows 7 was released.

    Why is that an issue? To explain that, I first have to explain how an OEM SLP  key works.


     OEM SLP: This key ONLY comes pre-installed in a PC built by a Large Manufacturer. This key is geared to work with the OEM Bios Flag that is only found on that Manufacturer's computer hardware. So when Windows is installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates.


       Your Windows is using an OEM SLP key, but cannot see the OEM Bios Flag in the computer’s Bios and, as such, is unable to Self-Activate. This is because the Bios was created before Windows 7 was released so couldn't have a Bios Flag for a version of Windows that hadn't even been created yet. This suggests that this Windows 7 did not originally come pre-installed in that PC and if that is the case, then that Windows 7 is not licensed to be used on that PC because (as I mentioned above) an OEM SLP key is Only used in Windows that originally come pre-installed in a PC from a Large Manufacturer and OEM software is not licensed to be transferable to any other PCs.

    Thank you,

     

     

    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, February 2, 2011 10:45 PM
    Wednesday, February 2, 2011 10:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2

    ><PID>00426-OEM-8992662-00006</PID>

    Manufacturer>NVIDIA</Manufacturer><Model>122-CK-NF68</Model></SYSTEM>

    <BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="4"/><Date>20070928000000.000000+000</Date></BIOS><HWID>13B83607018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern BIOS valid for OA 2.0: yes, but no SLIC table

     

     

     


    As this is a pirated version of Win 7 OEM for an Acer computer and it was never shipped with your computer (bios too old for Win 7 OEM) you need to purchase a full Win 7 Ultimate and change the product key to make it legal.  That is your only option to make legal with Win 7 Ultimate you have installed.

    If you purchased this and thought it was a legal purchase then you need to contact the seller for an immediate full refund of purchase price.

    • Marked as answer by Darin Smith MS Wednesday, February 2, 2011 10:44 PM
    Wednesday, February 2, 2011 6:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Even though he didn't fully explained the issue in any detail, LVTravel is correct.

     The information that tells us this is a non-genuine copy of Windows 7 is that 1) your Windows is using a Windows 7 OEM SLP key and 2) (as LVTravel has highlighted) the Bios in your PC is dated back to 2007 which is well before Windows 7 was released.

    Why is that an issue? To explain that, I first have to explain how an OEM SLP  key works.


     OEM SLP: This key ONLY comes pre-installed in a PC built by a Large Manufacturer. This key is geared to work with the OEM Bios Flag that is only found on that Manufacturer's computer hardware. So when Windows is installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates.


       Your Windows is using an OEM SLP key, but cannot see the OEM Bios Flag in the computer’s Bios and, as such, is unable to Self-Activate. This is because the Bios was created before Windows 7 was released so couldn't have a Bios Flag for a version of Windows that hadn't even been created yet. This suggests that this Windows 7 did not originally come pre-installed in that PC and if that is the case, then that Windows 7 is not licensed to be used on that PC because (as I mentioned above) an OEM SLP key is Only used in Windows that originally come pre-installed in a PC from a Large Manufacturer and OEM software is not licensed to be transferable to any other PCs.

    Thank you,

     

     

    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, February 2, 2011 10:45 PM
    Wednesday, February 2, 2011 10:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you. These are very informative. While I don't doubt what you are saying I am VERY curious as to how it ever worked in the first place. I got this new machine (custom...grrrr) back in late summer and has been fine until this week. Strange.
    Wednesday, February 2, 2011 11:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "boxturt" wrote in message news:1ac09aa5-a40b-4476-a8d9-0d6ac921e6bf...
    Thank you. These are very informative. While I don't doubt what you are saying I am VERY curious as to how it ever worked in the first place. I got this new machine (custom...grrrr) back in late summer and has been fine until this week. Strange.

     
    Here's one of my spiels about the time-lag
     
    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
    Thursday, February 3, 2011 12:13 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
     The "For products sold using a loader" part of Noel's post is most likely the right explanation for this particular case.
    Darin MS
    Thursday, February 3, 2011 8:40 PM