locked
An Unauthorized Change Was Made To Your License RRS feed

  • Question

  • Recently I booted up my HP laptop running windows Vista and it told me that there was an unauthorized change to my license and it will not let me log on or access my desktop or start menu in any way.  I read in another thread to download a diagnostic tool, and I have done so and will paste the results below:

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80004005
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {FAE578EC-04A5-46B0-89BB-A607ACD62E3A}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071009-1548
    TTS Error: M:20080318221205322-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2920-80070002_7E90FEE8-198-80004005_77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3_B4D0AA8B-784-80070057

    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: Disabled
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Disabled
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Disabled
    Script ActiveX controls marked as safe for scripting: Disabled

    File Scan Data-->
    File Mismatch: C:\Windows\system32\user32.dll[6.0.6000.16438]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{FAE578EC-04A5-46B0-89BB-A607ACD62E3A}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-176653743-4256975924-1453970037</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6000 (GA384UA#ABA)  </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.25     </Version><SMBIOSVersion major="2" minor="4"/><Date>20070512000000.000000+000</Date></BIOS><HWID>AB333507018400FE</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><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>90AF7A645CB3586</Val><Hash>eaU9ob3nAeOmxA0gIytrn7ViIbM=</Hash><Pid>89396-707-7999125-65971</Pid><PidType>14</PidType></Product><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><PidType>19</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: 0x800700EA

    I called into microsoft and the girl on the phone verified my product key was a genuine product key (as this is the software that came on the HP laptop) but said I would have to pay for technical support.  I don't want to have to restore my computer because I have lots of data on this laptop that I don't want to have to lose.  Can anyone please help?

    Thanks!
    Wednesday, March 19, 2008 3:43 AM

Answers

  • Hello mccalld,

     

      

    Hello,

     

    Vista is in, what is called a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.

     

    1) A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by random file corruption, a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occure.

     

    2) A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way. and is usually caused by a running program that is incompatible with Vista.

     

    Because of the Mismatched file listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an On Disk Mod-Auth. The Mismatched file (Slsvc.exe[6.0.6000.16509]) is the file that has been Modified or has become corrupted.

     

    Normally, I would look up the version number of this file and figure out which current Windows Update contained that file. I would then tell you to install (or re-install) the update. This would replace the bad file with an unmodified/corrupted copy. Unfortunatly, in the past, would not work for file Slsvc.exe because the update that contained that file could only be installed once and could not be uninstalled/reinstalled.

     

    But now that Service Pack 1 for Vista has been released, the issue has become allot easier to resolve. All you need to do is install SP1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). This should replace the bad Slsvc.exe file with a known good (and updated) copy.

     

     

    Please tell me if this has resolved your issue.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Wednesday, March 19, 2008 8:21 PM

All replies

  • Hello mccalld,

     

      

    Hello,

     

    Vista is in, what is called a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.

     

    1) A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by random file corruption, a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occure.

     

    2) A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way. and is usually caused by a running program that is incompatible with Vista.

     

    Because of the Mismatched file listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an On Disk Mod-Auth. The Mismatched file (Slsvc.exe[6.0.6000.16509]) is the file that has been Modified or has become corrupted.

     

    Normally, I would look up the version number of this file and figure out which current Windows Update contained that file. I would then tell you to install (or re-install) the update. This would replace the bad file with an unmodified/corrupted copy. Unfortunatly, in the past, would not work for file Slsvc.exe because the update that contained that file could only be installed once and could not be uninstalled/reinstalled.

     

    But now that Service Pack 1 for Vista has been released, the issue has become allot easier to resolve. All you need to do is install SP1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). This should replace the bad Slsvc.exe file with a known good (and updated) copy.

     

     

    Please tell me if this has resolved your issue.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Wednesday, March 19, 2008 8:21 PM
  • Thanks Darin.  I installed SP1 and the update worked like a charm.  It is working just fine now.  I still don't understand why this happened, and in reading the boards, it seems to be a fairly common problem that people have.  At any rate, I do appreciate your assistance and your prompt reply!

    Thanks again!

    Damon
    Thursday, March 20, 2008 4:36 PM
  • Hi mccalld,

     

     

      That is Excellent!

     

      I have to confess, you were the first person I suggested this fix to, so I am glad it worked and that you took the time to tell me!

     

      The On Disk type Mod-Auth (where a file is physically modified) is actually pretty uncommon. Unfortunately, my team and I have not yet found the common thread that would link the On Disk Mod-Auths, that I have seen, to a single cause (if there even is a single cause).

     

       The In Memory type Mod-Auth (caused by a incompatible program modifing a system file within system memory) is allot more common and will continue to be common untill most programs become Vista compatible or fall into disuse.

     

     

    Thanks again for your time in coming back and telling me the results of my suggested fix, this will greatly help other other users with similar issues.

     

    Darin Smith

    WGA Forum Manager

    Thursday, March 20, 2008 7:05 PM