locked
Windows 7 Build 7600 not genuine RRS feed

  • Question

  • Yesterday, my screen turned black and at the bottom right-hand corner of the screen appeared

    "Windows 7

    Build 7600

    This copy of windows is not genuine" 

    I have been using Windows 7 Ultimate for about 3 months and now this problem appears. I searched the forum and tried a lot of things but still couldn't solve it. Can anyone please help me ? 

    I tried removing the Windows Activation Technologies update (KB971033) but still no result. So I installed it again. 

    Here is my diagnosis from mgadiag.exe: 

     

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 50

    Cached Online Validation Code: 0xc004c4ab

    Windows Product Key: *****-*****-X92GV-V7DCV-P4K27

    Windows Product Key Hash: aU2z1/fnhnLHmhBm699qYZT2E6s=

    Windows Product ID: 00426-OEM-8992662-00400

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7600.2.00010100.0.0.001

    ID: {4BEDE005-CAB0-40AE-BC51-1BE51A48B782}(3)

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

    OGAExec.exe Signed By: Microsoft

    OGAAddin.dll Signed By: Microsoft

     

    OGA Data-->

    Office Status: 109 N/A

    OGA Version: Registered, 2.0.48.0

    Signed By: N/A, hr = 0x800b0100

    Office Diagnostics: B4D0AA8B-604-645_B4D0AA8B-604-645_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\Tin\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>{4BEDE005-CAB0-40AE-BC51-1BE51A48B782}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-P4K27</PKey><PID>00426-OEM-8992662-00400</PID><PIDType>2</PIDType><SID>S-1-5-21-1644359058-2851021561-2071053192</SID><SYSTEM><Manufacturer>Acer</Manufacturer><Model>Aspire E380</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>R01-B3</Version><SMBIOSVersion major="2" minor="3"/><Date>20070207000000.000000+000</Date></BIOS><HWID>61BA3607018400F8</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><OEMID>DELL  </OEMID><OEMTableID>QA09   </OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></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-600400-02-1033-7600.0000-3642010

    Installation ID: 019810513426922322719030591543277921647146311444143480

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

    License Status: Notification

    Notification Reason: 0xC004F200 (non-genuine).

    Remaining Windows rearm count: 3

    Trusted time: 12/30/2010 5:48:22 PM

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: 0xC004C4AB

    HealthStatus: 0x0000000000000000

    Event Time Stamp: 12:29:2010 15:25

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

     

     

    HWID Data-->

    HWID Hash Current: OAAAAAIAAwABAAEAAQACAAAAAwABAAEAeqh4eV48TjRqKl5GkgAKpC523oiAtBe6KiBqdBdYjrY=

     

    OEM Activation 1.0 Data-->

    N/A

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes

    Windows marker version: 0x20001

    OEMID and OEMTableID Consistent: yes

    BIOS Information: 

      ACPI Table Name OEMID Value OEMTableID Value

      APIC ACRSYS ACRPRDCT

      FACP ACRSYS ACRPRDCT

      HPET ACRSYS ACRPRDCT

      MCFG ACRSYS ACRPRDCT

      SSDT PTLTD POWERNOW

      SLIC DELL   QA09   

     

    I just want to know if there is a way to solve this. If there isn't then I'll just reinstalled Vista which I previously used. It comes with Acer Aspire E380 desktop. Hope this information would help.

    Thank you for your help :)

     

    Thursday, December 30, 2010 10:48 PM

Answers

  • Unfortunately, someone installed a  pirated copy of Windows 7 Ultimate edition that was designed for installation on a Dell computer  and not an Acer computer.  The only way to solve this issue is to reformat your hard drive and reinstall your genuine Windows Vista operating system.

    From your MGA Report:

    BIOS Information: 

      ACPI Table Name OEMID ValueOEMTableID Value

      APIC ACRSYSACRPRDCT

      FACP ACRSYSACRPRDCT

      HPET ACRSYSACRPRDCT

      MCFG ACRSYSACRPRDCT

      SSDT PTLTD POWERNOW

      SLIC DELL  QA09   


    Carey Frisch
    Friday, December 31, 2010 3:48 AM
    Moderator
  • "JaeTran" wrote in message news:5d8d82dc-4811-455e-bf79-4aa045de6290...

    Thank you very much. I just wanted to know if a reinstall is necessary:)

    One question, though, it was ungenuine but how did I use it for 3 months. Does MS not check it frequently ? 

    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 certain 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 installs and start work, and within 3 days, a loader-installed machine will get a notification. However, the WAT update is a voluntary one (a fact which is NOT well-published, and ignored by the more paranoid).
    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.
     
    Sorry if that sounds a little long-winded, but it's the first time I've actually tried to put my understanding of both time-delays down on the same piece of 'paper'.
     
    If you need anything more, just ask, and I'll try to explain - but I am not an insider, just someone with a little more knowledge than you, and a lot of the above is based on the way I would do it, combined with what little I know of the way that MS works.
     
    HTH?
     
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by JaeTran Monday, January 10, 2011 8:03 PM
    Monday, January 10, 2011 2:20 AM
    Moderator

All replies

  • Unfortunately, someone installed a  pirated copy of Windows 7 Ultimate edition that was designed for installation on a Dell computer  and not an Acer computer.  The only way to solve this issue is to reformat your hard drive and reinstall your genuine Windows Vista operating system.

    From your MGA Report:

    BIOS Information: 

      ACPI Table Name OEMID ValueOEMTableID Value

      APIC ACRSYSACRPRDCT

      FACP ACRSYSACRPRDCT

      HPET ACRSYSACRPRDCT

      MCFG ACRSYSACRPRDCT

      SSDT PTLTD POWERNOW

      SLIC DELL  QA09   


    Carey Frisch
    Friday, December 31, 2010 3:48 AM
    Moderator
  • Thank you very much. I just wanted to know if a reinstall is necessary:)

    One question, though, it was ungenuine but how did I use it for 3 months. Does MS not check it frequently ? 

    Sunday, January 9, 2011 11:10 PM
  • "JaeTran" wrote in message news:5d8d82dc-4811-455e-bf79-4aa045de6290...

    Thank you very much. I just wanted to know if a reinstall is necessary:)

    One question, though, it was ungenuine but how did I use it for 3 months. Does MS not check it frequently ? 

    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 certain 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 installs and start work, and within 3 days, a loader-installed machine will get a notification. However, the WAT update is a voluntary one (a fact which is NOT well-published, and ignored by the more paranoid).
    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.
     
    Sorry if that sounds a little long-winded, but it's the first time I've actually tried to put my understanding of both time-delays down on the same piece of 'paper'.
     
    If you need anything more, just ask, and I'll try to explain - but I am not an insider, just someone with a little more knowledge than you, and a lot of the above is based on the way I would do it, combined with what little I know of the way that MS works.
     
    HTH?
     
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by JaeTran Monday, January 10, 2011 8:03 PM
    Monday, January 10, 2011 2:20 AM
    Moderator
  • Thank you for taking your time to answer my question. 

    As a newbie, this information is new for me. And it helps me a lot. Thanks for your help :)

    Monday, January 10, 2011 8:06 PM