none
Validation phonenumber needed for in USA bought Notebook (Sager) RRS feed

  • Question

  • During the install of Vista SP2 I accidently choose the 32bits version. This resulted in a "stand off"", the pack couldn't finish and the system thought I had not a genuine Vista version. Reinstalling or removing the pack was impossible so I needed to do a cleandisk and a reinstall of my Vista home CD from Sager. This solved the SP problem but now I keep on getting Windows validation problems. I requested the online windows vaildation several times but it probably doesn't work. I live in the Netherlands and it seems that I need a validation from the USA support but the validation wizard doesn't show a number for me to call. 

    I have only 2 days left for validation. Please help.

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-YFJJ9-QVCM2-HBV28
    Windows Product Key Hash: qkR8K5WopCkJV40MPISEJUyD/bE=
    Windows Product ID: 89583-OEM-7332157-00028
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {C5C2E762-B4CE-44B6-B581-0DA50C9FA797}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6002.vistasp2_gdr.101014-0432
    TTS Error: K:20110926225400196-M:20110927090336384-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    WGA 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: 114 Blocked VLK 2
    Microsoft Office Professional Editie 2003 - 114 Blocked VLK 2
    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)\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>{C5C2E762-B4CE-44B6-B581-0DA50C9FA797}</UGUID><Version>1.9.0019.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HBV28</PKey><PID>89583-OEM-7332157-00028</PID><PIDType>2</PIDType><SID>S-1-5-21-3400879858-487774606-2878448786</SID><SYSTEM><Manufacturer>SAGER</Manufacturer><Model>M570RU</Model></SYSTEM><BIOS><Manufacturer>Phoenix</Manufacturer><Version>SROSA001.86C.</Version><SMBIOSVersion major="2" minor="4"/><Date>20090727000000.000000+000</Date></BIOS><HWID>10323507018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MIDERN</OEMID><OEMTableID>MIDERN  </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110413-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Editie 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73967-640-0000106-57258</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="114"/><App Id="16" Version="11" Result="114"/><App Id="18" Version="11" Result="114"/><App Id="19" Version="11" Result="114"/><App Id="1A" Version="11" Result="114"/><App Id="1B" Version="11" Result="114"/><App Id="44" Version="11" Result="114"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAKwHAAAAAAAAYWECAAAAAACrllP133PMARhy9171jCizkdIEkQaJZ65r2nfa24+KsZ+Kle9bna2oIpwa6vz2G/zjbO3QCeLdnyd7IPmIgITKmLNv1wD2WLYHADKKZNk7VqY64vHjbn9BqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuJojzM131iWCF/SdMhud1cDDi9ZiRboHNLGUDCRcTazQneyD5iICEypizb9cA9li2KsRfx0H5RYgBUJlehypBoqmjnBHePB2LDp7apxATyFCKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrh6l6gI7qIqTnBnfzlOCPEVVORLpzLoQHRH0/4dapftPJ3sg+YiAhMqYs2/XAPZYtni8s/Fx/dYrN3xF/ufFy8qpo5wR3jwdiw6e2qcQE8hQipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ64kVU48tEN5bv8drJ7VzlMDNDBVUC3OMYUXXpoqCSxNDyd7IPmIgITKmLNv1wD2WLZtwgElwMh/tT50FmgBOqMGqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu/F+3bgby1cqjXWoMYySvyHkc/x2dqTTJBqC0IXB2UrwneyD5iICEypizb9cA9li2/m9V//msH5u76uaWZUMS94pdiFr6+odM8fY+MESkf6eKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrl7Fhpue/zBg9LTV6J5MDRbTgx4/OvUtOK5d3upzYlm1J3sg+YiAhMqYs2/XAPZYtlRcaXVYYfOXVFw0jb8yYziKXYha+vqHTPH2PjBEpH+nipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, OEM_SLP channel
    Activation ID: bffdc375-bbd5-499d-8ef1-4f37b61c895f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89583-00146-321-500028-02-1033-6001.0000-2502011
    Installation ID: 101874811453482905181672087462949491532962996545696035
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: HBV28
    License Status: Initial grace period
    Time remaining: 20280 minute(s) (14 day(s))

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAIABAABAAEAAwABAAAAAwABAAEA6GHWDXcWLLZknypfRoMGDHSjpicQhgir8vRGxJCsfi+sVkbK

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   INTEL   CRESTLNE
      FACP   INTEL   CRESTLNE
      HPET   INTEL   CRESTLNE
      BOOT   PTLTD   $SBFTBL$
      MCFG   INTEL   CRESTLNE
      TCPA   Intel    CRESTLN
      TMOR   PTLTD          
      APIC   INTEL   CRESTLNE
      SLIC   MIDERN  MIDERN 
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci


     






    • Edited by SJHope Tuesday, September 27, 2011 8:25 PM
    Tuesday, September 27, 2011 7:40 PM

Answers

  • Hi SJHope,

     

      " I managed to get my key using the Jelly Bean Keyfinder tool and the validation was succesful."

     

      That would be great if your issue is resolved, However, the problem is that the key you got out of Windows is the OEM SLP key and that key only works in conjunction with the proper OEM Bios Flag (known as a 'Windows Marker') in the computer's motherboard.  And since your Diagnostic Report shows "BIOS valid for OA 2.0: no, invalid Windows marker", the OEM SLP key can't work.

      Would you rerun a Diagnostic Report so we can confirm the issue is resolved (I suspect Windows is just in it's Initial Grace Period and after that expires Windows will go into a Non-Genuine state)

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, October 5, 2011 10:07 PM
    Wednesday, September 28, 2011 8:36 PM

All replies

  • Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is designed to only work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was 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.

     

    B)    COA SLP: This is the Product key that you see on the sticker on the side, bottom or (for some laptops) in the battery compartment of your computer. It is a valid product key, but should only be used in limited situations (such as in this instance where the OEM SLP key has stopped self-activating).

     

       Your Windows is using an OEM SLP key, but (for whatever reason) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate.

      To fix the issue, you will need to change out the OEM SLP key with the COA SLP key.  The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard.

     

      After completing the Change Product Key process, if Windows has not already automatically Activated you will need to Activate by Phone. To do this click the Start button and type: slui 4  This will launch the Activate by Phone window.  Select your location and follow the directions (Note: a phone number for the closest Activation Call Center will be provided based on the location you select).

     

    Thank you,


    Darin MS
    Tuesday, September 27, 2011 9:42 PM
  • Dear Mr. Smith,

    Thanks for you quick response.

    The sticker under my notebook was unreadable so I passed your reply to Sager support to ask for my COA SPL key. This is what they answerred.

    "Hi Hope, we do not record the Windows prooductkey. You need to use the Midern Computer recovery disc to install Windows Vista from scratch. The fresh installed Windows does not require activation."

    I did use their recovery disc to re-install Vista after the cleandisk, so the answer wasn't very helpful. I managed to get my

    key using the Jelly Bean Keyfinder tool and the validation was succesful.

    Thans again.

    S. Hope

     

     

     

     

     

     


    • Edited by SJHope Wednesday, September 28, 2011 8:09 PM
    Wednesday, September 28, 2011 7:49 PM
  • Hi SJHope,

     

      " I managed to get my key using the Jelly Bean Keyfinder tool and the validation was succesful."

     

      That would be great if your issue is resolved, However, the problem is that the key you got out of Windows is the OEM SLP key and that key only works in conjunction with the proper OEM Bios Flag (known as a 'Windows Marker') in the computer's motherboard.  And since your Diagnostic Report shows "BIOS valid for OA 2.0: no, invalid Windows marker", the OEM SLP key can't work.

      Would you rerun a Diagnostic Report so we can confirm the issue is resolved (I suspect Windows is just in it's Initial Grace Period and after that expires Windows will go into a Non-Genuine state)

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, October 5, 2011 10:07 PM
    Wednesday, September 28, 2011 8:36 PM
  • No reply from the Original Poster.

    Issue is assumed to be resolved.


    Darin MS
    Wednesday, October 5, 2011 10:07 PM