locked
Somehow lost Genuine Windows status RRS feed

  • Question

  • My computer mysteriously crashed while downloading a video card update. When I finally got it back up and running, I was given a message that my copy of windows was not valid. I also had a BIOS checksum error, if the two things are related. This is a brand new system purchased 4 months ago. It came with windows 7. I haven't had any problems until today. I tried a system restore to the only restore point, which was 2 days before. No change in status. Could something like this be caused by a hardware BIOS problem?

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


    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-W8CT3-WJTWT-4DQ99
    Windows Product Key Hash: c46Yv4GMB11+0qwmF0nO9tcexFQ=
    Windows Product ID: 00359-OEM-8992687-00267
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {1E2FD1F7-7C08-4820-8FA0-6128F0E048A9}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110622-1506
    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 Home and Student 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


    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\Josh\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>{1E2FD1F7-7C08-4820-8FA0-6128F0E048A9}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-4DQ99</PKey><PID>00359-OEM-8992687-00267</PID><PIDType>2</PIDType><SID>S-1-5-21-394819182-2540183177-3230163857</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>Z68XP-UD3-iSSD</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F2</Version><SMBIOSVersion major="2" minor="4"/><Date>20110530000000.000000+000</Date></BIOS><HWID>11233007018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>61A77013E3AF728</Val><Hash>bPhN1mvdmdztKnryyTyD7pcCOS4=</Hash><Pid>81602-916-3264922-68303</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  


    Spsys.log Content: 0x80070002


    Licensing Data-->
    Software licensing service version: 6.1.7601.17514


    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00178-926-800267-02-1033-7601.0000-3062011
    Installation ID: 022160363143620036191604554075687034494833629315522971
    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: 4DQ99
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 2
    Trusted time: 2/21/2012 9:01:10 PM


    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 2:21:2012 19:26
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:




    HWID Data-->
    HWID Hash Current: NgAAAAIAAgABAAIAAgACAAAAAQABAAEAln0OnxU/mA5c2e4WsBsQKRgs0Bx39lia+VbA4S5z


    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 GBT   GBTUACPI
      FACP GBT   GBTUACPI
      HPET GBT   GBTUACPI
      MCFG GBT   GBTUACPI
      MSDM GBT   GBTUACPI
      ASPT GBT   PerfTune
      SSPT GBT   SsptHead
      EUDS GBT  
      MATS GBT  
      TAMG GBT   GBT   B0
      SSDT INTEL PPM RCM 
      MATS GBT  



    Wednesday, February 22, 2012 3:10 AM

Answers

  • After more research, I tried re-entering the product key from the Windows label on my system. That cleared the problem. However, I really want to know if this was caused by Malware or some other problem I should be worried about that will crop up again. If anyone who can interpret the above can let me know if there's any insight, I appreciate it.
    • Marked as answer by josh22 Wednesday, February 22, 2012 12:33 PM
    Wednesday, February 22, 2012 3:31 AM

All replies

  • What is the specific make and model number of your PC?

    Carey Frisch

    Wednesday, February 22, 2012 3:29 AM
    Moderator
  • After more research, I tried re-entering the product key from the Windows label on my system. That cleared the problem. However, I really want to know if this was caused by Malware or some other problem I should be worried about that will crop up again. If anyone who can interpret the above can let me know if there's any insight, I appreciate it.
    • Marked as answer by josh22 Wednesday, February 22, 2012 12:33 PM
    Wednesday, February 22, 2012 3:31 AM
  • It's a Maingear Vybe. It has a Gigabyte Z68XP-UD3-iSSD motherboard. 
    Wednesday, February 22, 2012 3:35 AM
  • "josh22" wrote in message news:58f80ce6-87de-4c6e-8879-9783ee3ef6cd...

    My computer mysteriously crashed while downloading a video card update. When I finally got it back up and running, I was given a message that my copy of windows was not valid. I also had a BIOS checksum error, if the two things are related. This is a brand new system purchased 4 months ago. It came with windows 7. I haven't had any problems until today. I tried a system restore to the only restore point, which was 2 days before. No change in status. Could something like this be caused by a hardware BIOS problem?

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


    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-W8CT3-WJTWT-4DQ99
    Windows Product Key Hash: c46Yv4GMB11+0qwmF0nO9tcexFQ=
    Windows Product ID: 00359-OEM-8992687-00267
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003



    Other data-->
    SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>Z68XP-UD3-iSSD</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F2</Version><SMBIOSVersion major="2" minor="4"/><Date>20110530000000.000000+000</Date></BIOS



    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Partial Product Key: 4DQ99
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 2
    Trusted time: 2/21/2012 9:01:10 PM


    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
     
    You have an OEM_SLP Key for an indeterminate manufacturer installed onto what appears to be a retail motherboard. This is quite possibly one generated by a hacker’s KeyGen tool rather than by MS.
     
    What EXACTLY does your COA sticker say? – do NOT post the Key!
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 10:02 AM
    Moderator
  • The manufacturer is Maingear, a custom boutique gaming PC maker. As I said, re-entering the code from the COA cleared the problem. I figured out how to locate the error number (it was in the lower left-hand corner of the error message that appears when I first logon). I googled that and found someone who had tried simply re-entering the key from the COA. That worked for me.

    The PC has an overclocked processor and all the usual custom gaming PC bells and whistles. I seriously doubt a custom maker like Maingear is selling clients hacked windows. Seems pretty bad for business and pointless (you can just up the price another $100 to cover the OEM windows, drop of water in the ocean compared to the rest of the cost). My thinking is that the system overclocking created an instability and that caused the motherboard to reset itself, or something along those lines. I don't have a lot of experience with this sort of problem, which is why I was hoping to get insight here to make sure the PC wasn't suffering from some kind of malicious software attack.

    The label says Windows 7 home premium and some other codes.

    Wednesday, February 22, 2012 12:32 PM
  • Apparently, the WGA program detected incorrect activation binary files or modified activation binary files, or the activation process determined to have been tampered with or worked around, or other tampering of license files was detected.

    Carey Frisch

    Wednesday, February 22, 2012 1:31 PM
    Moderator
  • "josh22" wrote in message news:51ca24c9-400f-4346-ade4-da175b67db6a...

    The manufacturer is Maingear, a custom boutique gaming PC maker. As I said, re-entering the code from the COA cleared the problem. I figured out how to locate the error number (it was in the lower left-hand corner of the error message that appears when I first logon). I googled that and found someone who had tried simply re-entering the key from the COA. That worked for me.

    The label says Windows 7 home premium and some other codes.

    OEM_SLP Keys are only issued to DirectOEM partners – who have to guarantee sales in the thousands per month. They ‘belong’ to manufacturers, rather than end-users, and are only valid on machines pre-installed by the particular manufacturer issued that Key, or installed using that manufacturer's Recovery disks, on their own machines.
     
    DirectOEMs also are required to modify the BIOS SLIC table on the motherboards they use to install Windows on – your motherboard appears to be a simple retail board, and has no visible signs of a SLIC table. Without this modification, the OEM_SLP Key cannot self-activate, and will demand re-activation – which is not possible, because the Key is blocked at the MS activation servers. The cure (as you found out) is to change the Key to the one on the COA sticker (which is your personal Key). It’s possible that this change should have been made prior to leaving the factory, and was simply forgotten – or it’s possible that the supplier (or someone else is breaking the rules deliberately.
     
    Darin may be able to comment further.
     
    Please post a new MGADiag report, so that we can check that all is OK.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 2:29 PM
    Moderator
  • Well, the problem hasn't remanifested itself. My motherboard and processor were replaced as a unit after initial installation (i.e., in my home) in the first month due to shipping damage. If there's any mismatch, perhaps that's the underlying cause. The processor is a 2600k, an unlocked processor, which was set to overclocked speeds in the BIOS. Once I got a hold of the manufacturer (or builder, or whatever you want to call them), they seemed to think it could have been a power drop in my system that caused the motherboard to reset (hence, I lost my overclocking) which caused windows to see new hardware even though nothing had changed. I know this forum probably sees a lot of pirated software, but I don't think that's the problem here. I can't see a company trying to compete with major manufacturers taking such a risk.
    • Edited by josh22 Wednesday, February 22, 2012 6:00 PM
    Wednesday, February 22, 2012 5:59 PM
  • "josh22" wrote in message news:916901bc-5ec3-4361-97d5-8c330ffa66ae...
    Well, the problem hasn't remanifested itself. My motherboard and processor were replaced as a unit after initial installation (i.e., in my home) in the first month due to shipping damage. If there's any mismatch, perhaps that's the underlying cause. The processor is a 2600k, an unlocked processor, which was set to overclocked speeds in the BIOS. Once I got a hold of the manufacturer (or builder, or whatever you want to call them), they seemed to think it could have been a power drop in my system that caused the motherboard to reset (hence, I lost my overclocking) which caused windows to see new hardware even though nothing had changed. I know this forum probably sees a lot of pirated software, but I don't think that's the problem here. I can't see a company trying to compete with major manufacturers taking such a risk.
     
     
    The processor is irrelevant in this context. The only thing of relevance is the BIOS, and consequently the motherboard.
    A power fluctuation doesn’t cause changes in the BIOS – or such things would happen every time you switched the machine off at the wall. Likewise overclocking doesn’t alter the SLIC table, unless you deliberately overwrite the BIOS in such a way as to do so.
    Please post  anew MGADiag report

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 6:10 PM
    Moderator
  • If the hard drive and motherboard weren't originally paired when Windows was installed, would that cause the problem? Why the sudden manifestation after three months?

    I don't really know all the hardware lingo. Will this cause me future problems? Is this something I can fix at home, or do I need to send it back to them? Can it be repaired without losing all my data, assuming a fix is required? The system is still under warranty. I don't have the OEM Windows disk, just the windows-made recovery disks. If this is something they need to repair, I can take it up with them.

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


    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-9642D-CTT4D-R9DJ7
    Windows Product Key Hash: rZ43saByb4qB6+N2Yf/c4u0nU70=
    Windows Product ID: 00359-OEM-8802064-96994
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {7D3786B4-A08F-4516-8B2C-B9F3AB3B7B02}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110622-1506
    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 Home and Student 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


    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\Josh\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>{F8F01838-EA60-4BA9-B720-00714BA1EC93}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-R9DJ7</PKey><PID>00359-OEM-8802064-96994</PID><PIDType>3</PIDType><SID>S-1-5-21-394819182-2540183177-3230163857</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>Z68XP-UD3-iSSD</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F2</Version><SMBIOSVersion major="2" minor="4"/><Date>20110530000000.000000+000</Date></BIOS><HWID>11233007018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>61A77013E3AF728</Val><Hash>bPhN1mvdmdztKnryyTyD7pcCOS4=</Hash><Pid>81602-916-3264922-68303</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  


    Spsys.log Content: 0x80070002


    Licensing Data-->
    Software licensing service version: 6.1.7601.17514


    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: 9f83d90f-a151-4665-ae69-30b3f63ec659
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00176-020-696994-02-1033-7601.0000-0522012
    Installation ID: 011900424363177596567831398541989962167732991332609814
    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: R9DJ7
    License Status: Licensed
    Remaining Windows rearm count: 2
    Trusted time: 2/22/2012 12:12:37 PM


    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 2:21:2012 19:26
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:




    HWID Data-->
    HWID Hash Current: NgAAAAIAAgABAAIAAgACAAAAAQABAAEAln0OnxU/mA5c2e4WsBsQKRgs0Bx39lia+VbA4S5z


    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 GBT   GBTUACPI
      FACP GBT   GBTUACPI
      HPET GBT   GBTUACPI
      MCFG GBT   GBTUACPI
      MSDM GBT   GBTUACPI
      ASPT GBT   PerfTune
      SSPT GBT   SsptHead
      EUDS GBT  
      MATS GBT  
      TAMG GBT   GBT   B0
      SSDT INTEL PPM RCM 
      MATS GBT  



    Wednesday, February 22, 2012 6:26 PM
  • Apparently, the WGA program detected an "out-of-tolerance" Windows licensing condition as a result of the system crash.  Your system is activated now and the problem has been resolved.

    Carey Frisch

    Wednesday, February 22, 2012 6:38 PM
    Moderator
  • Microsoft(r) Windows 7 Home Prem

    Below that: Seneca

    Below that a bar code, of the right of that: GFC-01051

    Below that the product key, followed by another barcode with this to the right: X16-96112

    Below that: a string of 14 digits.

    Microsoft branding, circles throughout.

    Note that there was also damage to the case in the original shipping. It's possible that the only original item from the initial ship is the hard drive. In other words, they might have just put the hard drive into a new system. In fact I'm pretty sure that's what happened, because of the initial damage. I'd had it long enough to put some stuff on it before deciding that the shipping damage might be a problem. Could that be the root cause? 

    Wednesday, February 22, 2012 6:42 PM
  • Basically you're saying somehow the system crashed and that caused the problem. There's no further action required then, correct?
    Wednesday, February 22, 2012 6:45 PM
  • Yes, if the hard drive with Windows 7 was reinstalled in a different computer, some of the hardward IDs likely changed resulting in a temporary Windows 7 licensing "out-of-tolerance" issue.

    Carey Frisch

    Wednesday, February 22, 2012 6:47 PM
    Moderator
  • Thank you for your help.
    Wednesday, February 22, 2012 6:53 PM
  • "josh22" wrote in message news:3765d50c-4698-448e-84b4-3ed8a870f73e...

    Microsoft(r) Windows 7 Home Prem

    Below that: Seneca

    Below that a bar code, of the right of that: GFC-01051

    Below that the product key, followed by another barcode with this to the right: X16-96112

    Below that: a string of 14 digits.

    Microsoft branding, circles throughout.

    Note that there was also damage to the case in the original shipping. It's possible that the only original item from the initial ship is the hard drive. In other words, they might have just put the hard drive into a new system. In fact I'm pretty sure that's what happened, because of the initial damage. I'd had it long enough to put some stuff on it before deciding that the shipping damage might be a problem. Could that be the root cause?

    It’s possible – but it’s still shoddy work by the manufacturer.
    The sticker sounds fine,
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 6:54 PM
    Moderator
  • "josh22" wrote in message news:23b276b3-7dfb-466f-801b-7364359399a8...

    If the hard drive and motherboard weren't originally paired when Windows was installed, would that cause the problem? Why the sudden manifestation after three months?

    I don't really know all the hardware lingo. Will this cause me future problems? Is this something I can fix at home, or do I need to send it back to them? Can it be repaired without losing all my data, assuming a fix is required? The system is still under warranty. I don't have the OEM Windows disk, just the windows-made recovery disks. If this is something they need to repair, I can take it up with them.

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


    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-9642D-CTT4D-R9DJ7
    Windows Product Key Hash: rZ43saByb4qB6+N2Yf/c4u0nU70=
    Windows Product ID: 00359-OEM-8802064-96994
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003


    Other data-->
    SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>Z68XP-UD3-iSSD</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F2</Version><SMBIOSVersion major="2" minor="4"/><Date>20110530000000.000000+000</Date></BIOS




    Licensing Data-->
    Software licensing service version: 6.1.7601.17514


    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Partial Product Key: R9DJ7
    License Status: Licensed
    Remaining Windows rearm count: 2
    Trusted time: 2/22/2012 12:12:37 PM


    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 2:21:2012 19:26
     



     
    That’s the proper Key :)
    The Key here is one from a ‘small’ manufacturer (OEM System Builder)  such as it’s likely that your supplier is, rather than a COA_SLP Key, which is what would be in effect if the sticker had been from one of the DirectOEMs.
     
    You need to clear the remaining minor error message, by validating Windows at www.microsoft.com/genuine/validate
    When it passes, you’ll be offered IE9 and MSE – you don’t need to take them if you don’t want to!
     
    Good luck
     
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 7:00 PM
    Moderator
  • Probably right. Sometimes it's hard to know until you've already dropped the money. I just hope this issue is resolved. 
    Wednesday, February 22, 2012 7:04 PM
  • "josh22" wrote in message news:6d798825-e8f3-4b52-8e4f-4204a8032a44...
    Probably right. Sometimes it's hard to know until you've already dropped the money. I just hope this issue is resolved.
     
    It certainly looks like it to me :)
     
    Good luck!

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 22, 2012 7:31 PM
    Moderator