locked
Invalid Key? RRS feed

  • Question

  • Having a hard time with this box. After it worked for a year or more now reports I have to activate windows. After booting in safe mode here's the diagnostics:

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Not Activated
    Validation Code: 1
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-RMDCP-V37KX-9FD6W
    Windows Product Key Hash: Wl/Ia0ekQAMmCBHwFIcsqxdBs2k=
    Windows Product ID: 76487-OEM-2211906-00119
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {2D060815-C2AA-43B4-A559-0E2CD27F28E0}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.8.31.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    Windows XP Notifications Data-->
    Cached Result: 1
    File Exists: Yes
    Version: 1.8.31.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    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: B4D0AA8B-604-645_025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.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>{2D060815-C2AA-43B4-A559-0E2CD27F28E0}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-9FD6W</PKey><PID>76487-OEM-2211906-00119</PID><PIDType>2</PIDType><SID>S-1-5-21-581382497-975626583-1620657947</SID><SYSTEM><Manufacturer>MICRO-STAR INTERNATIONAL CO.,LTD</Manufacturer><Model>MS-7529</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.4B9</Version><SMBIOSVersion major="2" minor="5"/><Date>20090721000000.000000+000</Date><SLPBIOS>Viglen,Viglen,Viglen</SLPBIOS></BIOS><HWID>A50030F70184E078</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>2</stat><msppid></msppid><name>Viglen Support Information.</name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.8.31.0"/><File Name="WgaLogon.dll" Version="1.8.31.0"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Licensing Data-->
    N/A

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 13C66:GENUINE C&C INC
    Marker string from OEMBIOS.DAT: Viglen,Viglen,Viglen

    OEM Activation 2.0 Data-->
    N/A

    The winxp came as OEM on the box along with other 30. The rest are ok. Verified and they use the same OEM key.

    Here's the diagnostic from a good working box using same key and xp (comparing them it may help you?):

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-RMDCP-V37KX-9FD6W
    Windows Product Key Hash: Wl/Ia0ekQAMmCBHwFIcsqxdBs2k=
    Windows Product ID: 76487-OEM-2211906-00119
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {E0F32AD7-2440-4055-9815-4D2B873797B0}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.8.31.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    Windows XP Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.8.31.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    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: B4D0AA8B-604-645_025D1FF3-230-1

    Browser Data-->
    Proxy settings: proxy1.equinoxsolutions.com:80
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Prompt
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Prompt
    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>{E0F32AD7-2440-4055-9815-4D2B873797B0}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-9FD6W</PKey><PID>76487-OEM-2211906-00119</PID><PIDType>2</PIDType><SID>S-1-5-21-509514838-1318319754-2324716332</SID><SYSTEM><Manufacturer>Viglen</Manufacturer><Model>MS-7529</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.4B9</Version><SMBIOSVersion major="2" minor="5"/><Date>20090721000000.000000+000</Date><SLPBIOS>Viglen,Viglen,Viglen</SLPBIOS></BIOS><HWID>A5D031F70184E078</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>2</stat><msppid></msppid><name>Viglen Support Information.</name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.8.31.0"/><File Name="WgaLogon.dll" Version="1.8.31.0"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Licensing Data-->
    N/A

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 13C66:GENUINE C&C INC|1C7EF:Viglen Ltd
    Marker string from OEMBIOS.DAT: Viglen,Viglen,Viglen

    OEM Activation 2.0 Data-->
    N/A

     

    Thanks for your help.

    Wednesday, December 1, 2010 11:27 AM

Answers

  • Hello CeasP,

    As Noel noted, the only way this particular combination of Viglen SLP OEM XP license and computer are going to stay activated is the operating system has to see the special data in the computer's BIOS when it goes looking for it periodically.  When the OS does not find the data, it thinks it was moved to a non-Viglen computer, which would violate the EULA for this license, so it deactivates and becomes nongenuine.

    The normal solution is to use the PK on the CoA for a telephonic activation thereby bypassing the now-defective OEM SLP activation, but that only works when the installed OS is the same as the OS on the CoA, which in this case is not the case because the computers were deployed using a downgrade from Vista Business or Ultimate to XP Pro (which is in compliance with the OEM EULA for Vista Business and Ultimate licenses).

    So for this to keep working, XP needs to see the BIOS data.  Solution: replace the motherboard with identical fully functional item from Viglen, being sure to tell them you need their OEM SLP branded mobo that will work with both Vista and XP.

    Other solution, change this computer to Vista.  If you use the (presumably) supplied Viglen installation disc for Vista Business or Ultimate, it may or may not see that data in the BIOS---if not, you have the PK on the CoA to activate with.

    • Marked as answer by Darin Smith MS Wednesday, December 1, 2010 10:06 PM
    Wednesday, December 1, 2010 4:34 PM
  • "Noel D Paton" wrote in message news:d43449f0-bdf5-4a49-9b85-1f3cf953c531...
     
    Unfortunately, Viglen went to the wall many years ago (unless they've been resurrected), and there is no way that they can provide support any more.
     

    --


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

    Ah - it appears that they do still exist, in a new form. Unfortunately, the information in the report is insufficient to identify the model of the PC concerned, or even the specific motherboard involved, so it's going to mean a call to their support people to see if they have the appropriate BIOS update for the machine involved, or an alternative means of solving the problem.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, December 7, 2010 12:26 AM
    Thursday, December 2, 2010 7:40 AM
    Moderator
  • Well, I can confirm this method works (at least for me) after I have used it on another of the Viglen PC's that was having same issue. After BIOS update winxp loaded without a sign of not being activated before. Im not very knowledgeable about these matters but I can guess that even a BIOS 'update' to same version would be able to unlock it. Probably something got corrupted in bios or somewhere. I will leave you advanced guys to speculate. If you want more info I'll be available for a couple more days during weekdays.

     

    Thanks Noel.

    • Marked as answer by Darin Smith MS Tuesday, December 7, 2010 12:25 AM
    Friday, December 3, 2010 3:38 PM

All replies

  • Having a hard time with this box. After it worked for a year or more now reports I have to activate windows. After booting in safe mode here's the diagnostics:

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Not Activated
    Validation Code: 1
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-RMDCP-V37KX-9FD6W
    Windows Product Key Hash: Wl/Ia0ekQAMmCBHwFIcsqxdBs2k=
    Windows Product ID: 76487-OEM-2211906-00119
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    .


    It's likely that for some reason the OS is unable to read the parts of the BIOS that control self-activation - use the Product Key Update tool to change the key to the one on the COA sticker
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 1, 2010 11:32 AM
    Moderator
  • Product Key Update tool doesn't change the key as it is says the key I'm trying to use is the same with the one on the box.

    Trying to activate it tells me "Unauthorized key". The key is good and I have just rechecked it. Its same on other 30 pc's all fine. Is it possible someone check the key if it was blacklisted or something?

     

    Thanks again.

    Wednesday, December 1, 2010 12:08 PM
  • Product Key Update tool doesn't change the key as it is says the key I'm trying to use is the same with the one on the box.

    Trying to activate it tells me "Unauthorized key". The key is good and I have just rechecked it. Its same on other 30 pc's all fine. Is it possible someone check the key if it was blacklisted or something?

     

    Thanks again.


    Which Key are you using in the Update Tool? - You cannot use the OEM_SLP key, as it is not possible to activate that key either by phone or over the internet. You MUST use the key on the COA sticker on that machine, which is different to the currently-installed key.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 1, 2010 12:25 PM
    Moderator
  • Hmm. Let me elaborate.

    This computers were supposed to come with windows vista. So the sticker on them is for windows vista. We asked the supplier a downgrade to windows xp. He installed xp but sticker remained for vista. Checking the key on them with a xp key reader I could see its the same as above Windows Product Key: *****-*****-RMDCP-V37KX-9FD6W.

     

    Now, what key should I use with that tool? I don't think the Vista one on the sticker. What now?

     

    Thanks.

    Wednesday, December 1, 2010 12:37 PM
  • Hello CeasP,

    As Noel noted, the only way this particular combination of Viglen SLP OEM XP license and computer are going to stay activated is the operating system has to see the special data in the computer's BIOS when it goes looking for it periodically.  When the OS does not find the data, it thinks it was moved to a non-Viglen computer, which would violate the EULA for this license, so it deactivates and becomes nongenuine.

    The normal solution is to use the PK on the CoA for a telephonic activation thereby bypassing the now-defective OEM SLP activation, but that only works when the installed OS is the same as the OS on the CoA, which in this case is not the case because the computers were deployed using a downgrade from Vista Business or Ultimate to XP Pro (which is in compliance with the OEM EULA for Vista Business and Ultimate licenses).

    So for this to keep working, XP needs to see the BIOS data.  Solution: replace the motherboard with identical fully functional item from Viglen, being sure to tell them you need their OEM SLP branded mobo that will work with both Vista and XP.

    Other solution, change this computer to Vista.  If you use the (presumably) supplied Viglen installation disc for Vista Business or Ultimate, it may or may not see that data in the BIOS---if not, you have the PK on the CoA to activate with.

    • Marked as answer by Darin Smith MS Wednesday, December 1, 2010 10:06 PM
    Wednesday, December 1, 2010 4:34 PM
  • "Dan at IT Associates" wrote in message news:ead7503f-d395-4c22-9699-4ae424c1d8ad...

    Hello CeasP,

    As Noel noted, the only way this particular combination of Viglen SLP OEM XP license and computer are going to stay activated is the operating system has to see the special data in the computer's BIOS when it goes looking for it periodically.  When the OS does not find the data, it thinks it was moved to a non-Viglen computer, which would violate the EULA for this license, so it deactivates and becomes nongenuine.

    The normal solution is to use the PK on the CoA for a telephonic activation thereby bypassing the now-defective OEM SLP activation, but that only works when the installed OS is the same as the OS on the CoA, which in this case is not the case because the computers were deployed using a downgrade from Vista Business or Ultimate to XP Pro (which is in compliance with the OEM EULA for Vista Business and Ultimate licenses).

    So for this to keep working, XP needs to see the BIOS data.  Solution: replace the motherboard with identical fully functional item from Viglen, being sure to tell them you need their OEM SLP branded mobo that will work with both Vista and XP.

    Other solution, change this computer to Vista.  If you use the (presumably) supplied Viglen installation disc for Vista Business or Ultimate, it may or may not see that data in the BIOS---if not, you have the PK on the CoA to activate with.


    @Dan
    Unfortunately, Viglen went to the wall many years ago (unless they've been resurrected), and there is no way that they can provide support any more.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 1, 2010 8:54 PM
    Moderator
  • "Noel D Paton" wrote in message news:d43449f0-bdf5-4a49-9b85-1f3cf953c531...
     
    Unfortunately, Viglen went to the wall many years ago (unless they've been resurrected), and there is no way that they can provide support any more.
     

    --


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

    Ah - it appears that they do still exist, in a new form. Unfortunately, the information in the report is insufficient to identify the model of the PC concerned, or even the specific motherboard involved, so it's going to mean a call to their support people to see if they have the appropriate BIOS update for the machine involved, or an alternative means of solving the problem.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, December 7, 2010 12:26 AM
    Thursday, December 2, 2010 7:40 AM
    Moderator
  • Guys your advise was helpful.

    After updating BIOS (motherboard is Viglen Vig610M) using same key is before the XP is activated and reported as genuine. I din't even needed to go through the steps of activating. The tray nag just disappeared. I got the latest version of BIOS from their website.

     

    Hopefully its all done now and it will stay activated for good. :)

     

    Thanks to all responders.

    Thursday, December 2, 2010 11:53 AM
  • Hello CeasP,

    I did not suggest reflashing/updating the BIOS in my original response because at least IME BIOS updates (at least for the big guys) don't generally write/refresh the SLP data and certificate information.  Good call on your part giving the BIOS update a shot, luckily their BIOS update seems to rewrite/refresh everything, so it looks like you solved the problem (fingers crossed!). :-)

    Just curious, if you run the mgadiag again and look at the bottom of the report at the BIOS section, do you see any changes from the first report?

    Thursday, December 2, 2010 3:39 PM
  • "Dan at IT Associates" wrote in message news:9c3a3104-a4ed-400a-9ba2-cf05d93a8c52...

    Hello CeasP,

    I did not suggest reflashing/updating the BIOS in my original response because at least IME BIOS updates (at least for the big guys) don't generally write/refresh the SLP data and certificate information.  Good call on your part giving the BIOS update a shot, luckily their BIOS update seems to rewrite/refresh everything, so it looks like you solved the problem (fingers crossed!). :-)

    Just curious, if you run the mgadiag again and look at the bottom of the report at the BIOS section, do you see any changes from the first report?


    If you look at the two reports first posted, there is a difference, although both appear to be the same version - the BIOS in the working one includes an OEM statement for Viglen - the 'borked' one does not.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 2, 2010 4:29 PM
    Moderator
  • Well, I can confirm this method works (at least for me) after I have used it on another of the Viglen PC's that was having same issue. After BIOS update winxp loaded without a sign of not being activated before. Im not very knowledgeable about these matters but I can guess that even a BIOS 'update' to same version would be able to unlock it. Probably something got corrupted in bios or somewhere. I will leave you advanced guys to speculate. If you want more info I'll be available for a couple more days during weekdays.

     

    Thanks Noel.

    • Marked as answer by Darin Smith MS Tuesday, December 7, 2010 12:25 AM
    Friday, December 3, 2010 3:38 PM