none
Windows 7 is not genuine in Parallels Desktop OSX Virtual Machine but is genuine when natively booted.

    Question

  • Hi guys,

    I purchased a genuine copy of Windows 7 Professional through Microsoft's Student Advantage program and installed a full copy on my MacBook Pro using OSX's Boot Camp software such that I have two OS partitions: OSX and Win7.

    I also purchased a copy of Parallels Desktop for OSX so that I could boot my Win7 partition as a virtual machine from within OSX if I needed to use Windows on the fly in lieu of a full native boot.

    I validated successfully my copy of Win7 when I first installed it and booted natively (before I even had Parallels) but when I boot the operating system in a virtual machine, I am given errors that my copy is not genuine and it prevents me from performing certain tasks that require genuine validation.

    Obviously, I can work around this issue by just rebooting into Windows out of OSX but I don't feel I should have to do that considering I legitimately paid for it.

    Is there a work-around or fix that would allow my virtual machine to be rightfully considered genuine or am I stuck having to boot natively for this?

    Thanks guys!

     

    TECH SPECS:

    MacBook Pro 15" - Mid2010 variant

    Intel Core i5 2.53GHz

    4GB RAM

    NVIDIA GeForce GT320M

    Windows 7 Professional/OSX Snow Leopard Dual Boot

    Saturday, September 11, 2010 3:49 PM

Answers

  • The VM copy sees virtualized hardware, and therefore a different hardware configuration. Also, the license for windows allows one installation of windows. Technicly you are also not supposed to dual boot on the same machine using the same key even though the hardware is 100% identical.

    The VM is a separate machine requiring a separate license. It is allready activated on the existing hardware, if it is retail activating it on the VM would technicly make the actual hardware installation of it invalid, it would be reflected as having been activated on both hardware configurations in the data base that MS maintains on keys.

    To run a normal install AND a VM install you will need two product keys.

    • Proposed as answer by $Don Sunday, September 12, 2010 10:25 AM
    • Marked as answer by Darin Smith MSOwner Monday, September 13, 2010 8:46 PM
    Saturday, September 11, 2010 6:45 PM

All replies

  • We really need a report to help, can you post a diagnostic report according to the instructions located on the index of this forum

    http://social.microsoft.com/Forums/en/genuinewindows7/threads

    Just past the results in this thread.

    Saturday, September 11, 2010 4:13 PM
  • We really need a report to help, can you post a diagnostic report according to the instructions located on the index of this forum

    http://social.microsoft.com/Forums/en/genuinewindows7/threads

    Just past the results in this thread.


    Sorry, here is the report (this is from the virtual machine, not from a native boot):

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-VCR6F-P2JYH-QBVKR
    Windows Product Key Hash: ifUN9xDQ1KNvldlvkvZ3fgQ1RKk=
    Windows Product ID: 00371-862-6220495-85576
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {CDA1E6A8-831D-4951-BD4A-C73C462D55FA}(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.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:\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-->
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{CDA1E6A8-831D-4951-BD4A-C73C462D55FA}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-QBVKR</PKey><PID>00371-862-6220495-85576</PID><PIDType>5</PIDType><SID>S-1-5-21-3745461335-3857786891-2217074295</SID><SYSTEM><Manufacturer>Parallels Software International Inc.</Manufacturer><Model>Parallels Virtual Platform</Model></SYSTEM><BIOS><Manufacturer>Parallels Software International Inc.</Manufacturer><Version>5.0.9308.543312</Version><SMBIOSVersion major="2" minor="3"/><Date>20071026000000.000000+000</Date></BIOS><HWID>20B93607018400EC</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, Professional edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: e838d943-63ed-4a0b-9fb1-47152908acc9
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-862-622049-00-1033-7600.0000-2182010
    Installation ID: 003703490333817372892792045834965913520196575426732173
    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: QBVKR
    License Status: Notification
    Notification Reason: 0xC004F009 (grace time expired).
    Remaining Windows rearm count: 3
    Trusted time: 9/11/2010 12:57:59 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 8:8:2010 16:49
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MAAAAAIAAgABAAEAAQABAAAAAQABAAEAnJ8mYQwSS/uOqVj+9D0GhY3vpKmG/IR+

    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            PRLS          PRLS_OEM
      FACP            PRLS          PRLS_OEM


    Saturday, September 11, 2010 4:59 PM
  • "novaprospekt" wrote in message news:89cf661e-f66c-4bd0-91a7-09468c39294f...

    We really need a report to help, can you post a diagnostic report according to the instructions located on the index of this forum

    http://social.microsoft.com/Forums/en/genuinewindows7/threads

    Just past the results in this thread.


    Sorry, here is the report (this is from the virtual machine, not from a native boot):

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-VCR6F-P2JYH-QBVKR
    Windows Product Key Hash: ifUN9xDQ1KNvldlvkvZ3fgQ1RKk=
    Windows Product ID: 00371-862-6220495-85576
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048


    The problem here is that Parallels is seen by licensing as a different machine to the native install - and therefore requires a different license with its own Key.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, September 11, 2010 5:26 PM
    Moderator
  • "novaprospekt" wrote in message news:89cf661e-f66c-4bd0-91a7-09468c39294f ...

    We really need a report to help, can you post a diagnostic report according to the instructions located on the index of this forum

    http://social.microsoft.com/Forums/en/genuinewindows7/threads

    Just past the results in this thread.


    Sorry, here is the report (this is from the virtual machine, not from a native boot):

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-VCR6F-P2JYH-QBVKR
    Windows Product Key Hash: ifUN9xDQ1KNvldlvkvZ3fgQ1RKk=
    Windows Product ID: 00371-862-6220495-85576
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.048


    The problem here is that Parallels is seen by licensing as a different machine to the native install - and therefore requires a different license with its own Key.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth


    Thanks Noel, but is there no way that I can "convince" licensing that Parallels isn't a different machine? I mean, it is booting the same hard drive and for all intents and purposes the same operating system as if I was doing Win7 natively so my key should be valid. Is this a problem inherent in virtual machine technologies? 

    Saturday, September 11, 2010 6:14 PM
  • The VM copy sees virtualized hardware, and therefore a different hardware configuration. Also, the license for windows allows one installation of windows. Technicly you are also not supposed to dual boot on the same machine using the same key even though the hardware is 100% identical.

    The VM is a separate machine requiring a separate license. It is allready activated on the existing hardware, if it is retail activating it on the VM would technicly make the actual hardware installation of it invalid, it would be reflected as having been activated on both hardware configurations in the data base that MS maintains on keys.

    To run a normal install AND a VM install you will need two product keys.

    • Proposed as answer by $Don Sunday, September 12, 2010 10:25 AM
    • Marked as answer by Darin Smith MSOwner Monday, September 13, 2010 8:46 PM
    Saturday, September 11, 2010 6:45 PM
  • I proposed Carl_OH as an answer, because also I run Parallels Desktop For Mac and have had the same problem.  If you read the license carefully:

    License Model. The software is licensed on a per copy per computer basis. A computer is a physical hardware system with an internal storage device capable of running the software. A hardware partition or blade is considered to be a separate computer.

    2. INSTALLATION AND USE RIGHTS.
    a. One Copy per Computer. You may install one copy of the software on one computer. That computer is the "licensed computer."

    there is also this:

    d. Use with Virtualization Technologies.

     

    Our problem is we are NOT running the virtual "on the licensed computer".  We are effectively using our license right for the Bootcamp "partition" that runs (native) on Mac as the "physical hardware system with internal storage capable of running the software."

    Parallels For Mac Desktop runs on Mac OSX.  So, unfortunately, we do not "... use the software within only one virtual ... on the licensed computer."  Basically the license (and WGA) allows the use of the same copy of Win7 within a virtual running ON the same Win7.  If you were running Microsoft's VirtualPC in your Bootcamp partition, then you would probably pass WGA, as the Bootcamp hardware signature would be the same virtual hardware signature when the virtual is tested for WGA.

    So, as Carl_OH said, what happens is 2 different hardware signatures are presented to WGA when using the same copy of Win7 in a Bootcamp "native" hardware and a Mac OSX Parallels virtual machine configuration.

    While it would seem we should be able to run the same copy of Win7 in Bootcamp (hardware) and "within only one virtual" (Parallels), unfortunately the virtual has to be on the same "licensed computer".  While we may have a single computer that is a single "physical hardware system", a Bootcamp / Parallels configuration is NOT what is decribed by the license.

     

    Sunday, September 12, 2010 11:46 AM
  • Well I'm confused because I was doing some google searching and on Parallel's website/forums apparently there is a fix/workaround for this.

    I don't like the idea of this little technicality making it seem like it's a different machine because a VM is far from it.

    Monday, September 13, 2010 12:53 AM
  • There may be a work around, but it is still against the licensing agreement. One key, one install on one computer. Dual booting, or installs on hardware AND VM are a violation of the licensing agreement. How you proceed is up to you. I don't make moral judgements, just presenting the facts. If you choose to do something in violation of the agreement then that is something you have to deal with wether thier are real world consequences or not. I would also advise against robbing a bank but again, the choice is yours.

    When it is a law we agree with it is a law, when we don't agree with it it's a technicality.

    Monday, September 13, 2010 1:14 AM
  • There may be a work around, but it is still against the licensing agreement. One key, one install on one computer. Dual booting, or installs on hardware AND VM are a violation of the licensing agreement. How you proceed is up to you. I don't make moral judgements, just presenting the facts. If you choose to do something in violation of the agreement then that is something you have to deal with wether thier are real world consequences or not. I would also advise against robbing a bank but again, the choice is yours.

    When it is a law we agree with it is a law, when we don't agree with it it's a technicality.

    Well I appreciate your thoughts and help (as well everyone else's who replied here) regarding this matter. The issue has been resolved and I have successfully and legitimately activated my copy of Win7 in my virtual machine while still maintaining my boot camp partition activation.

    This isn't a place to rant on matters pertaining to digital rights management and file sharing but I will say that it is for reasons like this the paying customers of software feel shafted. When we try and do the right thing and pay for products, we're saddled with DRM and authentication technology technicalities that either constrain or hinder our fair use of the product. It's one thing if I'm putting a copy of Windows on multiple computers but a virtual machine that is merely booting a native installation partition does not in my opinion constitute something that should require two purchases of the operating system. Apparently, Microsoft's WGA department felt the same way as the operator I spoke to on the phone allowed me to authenticate both of my installations. 

    Thanks again guys.

    Tuesday, September 14, 2010 3:49 PM
  • May i ask how you did this because I am having the same problem.
    Tuesday, September 14, 2010 11:55 PM
  • Uh, like he said, he (called) talked to Microsoft's WGA department and told them why he thought he should be able to run his single copy of Win7 on Mac's Bootcamp Partition AND use that same copy in a Parallels For Mac Virtual Machine.

    While he may have posted what I consider a mini-rant, he certainly did do the right thing and went to those who bless the installation of their operating system.  As he expressed above, he felt he had a right to install (presumably based on his interpretation of the licensing specification) his copy of Win7 in the configuration he was trying to achieve.  The operator who took is called (fortunately) agreed and gave him the necessary pass key.  My guess is, if they had in fact denied his use of his copy of Win7 in the Bootcamp/Parallels configuration we would have seen a lot more than jmust a mini-rant. 8-)

    So really novaprospekt's last entry, September 14 @ 3:29 PM should probably be marked as the answer: call Microsoft's WGA department, say the magic words (like he did) and poof you too should be given the secret code.

     

     

    Tuesday, September 21, 2010 8:52 PM