Answered by:
An unauthorized change was made to your license
Question
-
Hi everyone. I rebooted my PC yesterday but before login the message "An unauthorized change was made to your license" appeared. I did not install software nor any hardware. I would like to know what's going on. To resolve the issue we tried replacing parts but none of it resolved the issue. I would like to mention that Windows boots fast but is extremely slow to use (even in Safe mode). Please explain.
Diagnostic Report (1.9.0006.0):
-----------------------------------------
WGA Data-->
Validation Status: Genuine
Validation Code: 0
Online Validation Code: 0x80070426
Cached Validation Code: N/A, hr = 0x80070426
Windows Product Key: *****-*****-QKH2C-XD77K-GC9QC
Windows Product Key Hash: AMa7Hmg+xXZNQjNSx8bStvdeahg=
Windows Product ID: 89576-OEM-7303915-72166
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.0.6001.2.00010100.1.0.006
ID: {C66326A0-36B4-4D60-8057-1B32865536C4}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.9.9.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Business
Architecture: 0x00000000
Build lab: 6001.vistasp1_gdr.080917-1612
TTS Error: M:20090128121327330-
Validation Diagnostic:
Resolution Status: N/AWgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: 6.0.6001.18000WGA 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 = 0x80070002OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGATray.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Enterprise 2007 - 103 Blocked VLK
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_025D1FF3-365-80041010_025D1FF3-230-80041010_025D1FF3-231-1_025D1FF3-518-80040154_025D1FF3-238-80040154_025D1FF3-239-2_025D1FF3-245-80070002_025D1FF3-259-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
Default Browser: C:\Program Files\Mozilla Firefox\firefox.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: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{C66326A0-36B4-4D60-8057-1B32865536C4}</UGUID><Version>1.9.0006.0</Version><OS>6.0.6001.2.00010100.1.0.006</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-GC9QC</PKey><PID>89576-OEM-7303915-72166</PID><PIDType>3</PIDType><SID>S-1-5-21-2367132135-2391422277-2372459215</SID><SYSTEM><Manufacturer>INTEL_</Manufacturer><Model>DQ3510J_</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>JOQ3510J.86A.0942.2008.0807.1958</Version><SMBIOSVersion major="2" minor="4"/><Date>20080807000000.000000+000</Date></BIOS><HWID>85033007018400FA</HWID><UserLCID>0413</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65242</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="103"/><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="19" Version="12" Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/><App Id="44" Version="12" Result="103"/><App Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults>Spsys.log Content: U1BMRwEAAAAAAQAABAAAABARAAAAAAAAWmICAATQEohA8t92ioDJAVMWKYGB4wMcsbz+lAen7Wd89sHsMTzqJQLhV3YD6HT3ACi7N1TRoRkvo5G4827F/MShSbpyt8EDSHUE4bJvJRmSncBnUvQnN6atMmK3K2jU7vtvjzPGHXAcEQG310OzYS2aWEuplwkBLaZUi/QBCaawQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nfPbB7DE86iUC4Vd2A+h097WMsH++rcqYv5tvRY1torxoS3Qo7jK0QbHFVhf6eeyYfYgYKJXWpO2RZzdJBeploT8o2HvNCtHZpV+OvviAWcjggiufFak8OFGoTKS6hXFLqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23Fszgift7ojEtbVSJvAMAEwNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERY39ozctTRTx9hja2DsDoBJG82LW3l3uXNQAZk6Ery6RDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ3z2wewxPOolAuFXdgPodPcAKLs3VNGhGS+jkbjzbsX8xKFJunK3wQNIdQThsm8lGXRcKb1KT4Fp17BEBfDmxQru+2+PM8YdcBwRAbfXQ7NhLZpYS6mXCQEtplSL9AEJprBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7Wcu/25jdcdO8iTNWt7GSH5TRLr0j4cxU+0Z1jDsAR4bL2hLdCjuMrRBscVWF/p57JhEM+NsxmY7bK5gwIEKUoenPyjYe80K0dmlX46++IBZyOCCK58VqTw4UahMpLqFcUuqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nLv9uY3XHTvIkzVrexkh+U0S69I+HMVPtGdYw7AEeGy9oS3Qo7jK0QbHFVhf6eeyYmO5MVMdYCD7y3uTm40Fufj8o2HvNCtHZpV+OvviAWcjggiufFak8OFGoTKS6hXFLqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23Fszgift7ojEtbVSJvAMAEwNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERY39ozctTRTx9hja2DsDoBJG82LW3l3uXNQAZk6Ery6RDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ8Ahqk76o1jgc0CUekcYVDPg685xdf8nXjs6fAJIu1kPxKFJunK3wQNIdQThsm8lGbL26kYranl/VwCMS+c1DpDu+2+PM8YdcBwRAbfXQ7NhLZpYS6mXCQEtplSL9AEJprBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WfAIapO+qNY4HNAlHpHGFQz4OvOcXX/J147OnwCSLtZD8ShSbpyt8EDSHUE4bJvJRlJUjLroaFlzPGRhtTQrs6w7vtvjzPGHXAcEQG310OzYS2aWEuplwkBLaZUi/QBCaawQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nKy0aF2/3q/6vxnu7tKiMaX9FgdAfXsMYhmsr2VOM0EpoS3Qo7jK0QbHFVhf6eeyYhsUoPTNogPQuY3eSDUCG1z8o2HvNCtHZpV+OvviAWcjggiufFak8OFGoTKS6hXFLqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23Fszgift7ojEtbVSJvAMAEwNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERY39ozctTRTx9hja2DsDoBJG82LW3l3uXNQAZk6Ery6RDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ5ojsDwTImWJX5M+5AUFacTNtBuRaegIeuY9u7LyyzUCaEt0KO4ytEGxxVYX+nnsmE5qDIcSbOPre+C/mGbkTag/KNh7zQrR2aVfjr74gFnI4IIrnxWpPDhRqEykuoVxS6ostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txbM4In7e6IxLW1UibwDABMDSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWN/aM3LU0U8fYY2tg7A6ASRvNi1t5d7lzUAGZOhK8ukQzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WdZMc5ecc1zL1OA0p9c7Ycx2O/L8azGRba2QXZi3o0PG8ShSbpyt8EDSHUE4bJvJRnfU8oubgVGrCVTEV4JnBTW7vtvjzPGHXAcEQG310OzYS2aWEuplwkBLaZUi/QBCaawQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nWTHOXnHNcy9TgNKfXO2HMbjm2Xw0Cs87sawVvJGfA55oS3Qo7jK0QbHFVhf6eeyYH48wA2jo118Psid4Su7szT8o2HvNCtHZpV+OvviAWcjggiufFak8OFGoTKS6hXFLqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23Fszgift7ojEtbVSJvAMAEwNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERY39ozctTRTx9hja2DsDoBJG82LW3l3uXNQAZk6Ery6RDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZzZLq22pGkyghYlr2vWUHSNS6KD6uZ1HAp9NtCzAYnbGxKFJunK3wQNIdQThsm8lGQ13dyjzbGrkHUjY+VYDnVju+2+PM8YdcBwRAbfXQ7NhLZpYS6mXCQEtplSL9AEJprBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7Wc2S6ttqRpMoIWJa9r1lB0jUuig+rmdRwKfTbQswGJ2xsShSbpyt8EDSHUE4bJvJRmwpWvjupyV/nNp8Fn+A9vh7vtvjzPGHXAcEQG310OzYS2aWEuplwkBLaZUi/QBCaawQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nNkurbakaTKCFiWva9ZQdI1LooPq5nUcCn020LMBidsbEoUm6crfBA0h1BOGybyUZcu1MMmebtEHZs+R0wnAlp+77b48zxh1wHBEBt9dDs2EtmlhLqZcJAS2mVIv0AQmmsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ1tIu304ytAQQ8YRUGFz3f22dXHmeJ6FA8pJPfFI7xFzaEt0KO4ytEGxxVYX+nnsmILQyAZBGi+KZD5Zk2PZgLM/KNh7zQrR2aVfjr74gFnI4IIrnxWpPDhRqEykuoVxS6ostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txbM4In7e6IxLW1UibwDABMDSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWN/aM3LU0U8fYY2tg7A6ASRvNi1t5d7lzUAGZOhK8ukQzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WeaI7A8EyJliV+TPuQFBWnEEQo1nh/7Y5GBX7hVRnmCuWhLdCjuMrRBscVWF/p57JjMEmLDiPynjpPIb7NfK1jdPyjYe80K0dmlX46++IBZyOCCK58VqTw4UahMpLqFcUuqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=
Licensing Data-->
Software Licensing service is not running.HWID Data-->
HWID Hash Current: MAAAAAIAAgABAAEAAwAAAAAAAAABAAEA6GGCvZrtDWLe1MaYoipAl3tDQMHy9MwxOEM Activation 1.0 Data-->
N/AOEM 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 INTEL DQ3510J
FACP INTEL DQ3510J
MCFG INTEL DQ3510J
WDDT INTEL DQ3510J
ASF! INTEL DQ3510J
ASPT INTEL DQ3510J
WDTT INTEL DQ3510J
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
SSDT INTEL CpuPm
TCPA INTEL TIANO
Wednesday, January 28, 2009 11:57 AM
Answers
-
Hello Lance359,
It looks like there maybe more then one issue going on here.
1) The error code 0x80070426 tells me that Vista's Software Licensing Service has stopped
2) The error message "An unauthorized change was made to your license" and the Tamper Time stamp (TTS) Error: M:20090128121327330- in your diagnostic report suggests a In Memory type Mod-Auth tamper. Meaning an incompatible program is attempting to do something that Vista does not allow (note: it does not matter that you did not install anything recently. Viruses, Trojans and other malware can be incompatible with Vista too)
First you will want to restart Vista's Software Licensing Service. Vista uses this Service to check itself for Mod-Auth tampers and such (basiclly it monitors Vista to confirm it is Genuine) but if the Service is somehow stopped or disabled, Vista automaticly defaults to Non-Genuine.
Please try the first set of steps and if it does not resolve the issue, move on to the next set.
Note: There are a number of Services that run under Windows and while the Software Licensing Service, itself, is supported by Windows Genuine Advantage, the process for starting and stopping services is a Windows Core sub-system and is outside the focus (and knowledge) of this support. If the below steps do not result in the Software Licensing Service running, there may be a larger issue with Vista's Services sub-system and we suggest contacting Vista support at http://support.microsoft.com
The first set of steps are how to set the Software Licensing Service to start at each Vista Start-up.
1. Click on the Start button and in the Start Search box type in: services.msc
2. Press the Enter key on your keyboard.
3. The Services window should now open.
4. Scroll down to Software Licensing, then right-click on it and select Properties.
5. Under the General tab, click on the Stop button.
6. Set the Startup Type to Automatic, then click Apply.
7. Next, under Service Status, click on the Start button.
8. Last, restart your computer.
The second set of steps are the Manual steps to Force Start the Software Licensing Service.
If you have access to the Start button:
1) Click the Start button
2) Type: cmd in the Start Search field
3) At the top the Start window, you will see cmd.exe
4) Right Click cmd.exe and select Run as Administrator
5) Type: net start slsvc
If you do not have access to the Start button:
1) Click the option that launches an Internet Browser
2) A Browser will open, type: %windir%\system32 into the address field
3) Find the file cmd.exe
4) Right Click on the cmd.exe and select Run as Administrator
5) Type: net start slsvc
Once you have restarted the Software Licensing service, go down to my next post where I provide assistance in fixing the In Memory Mod-Auth Tamper issue.
Thank you,
Darin MS
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Edited by Darin Smith MS Thursday, January 29, 2009 12:20 AM
- Proposed as answer by Darin Smith MS Thursday, January 29, 2009 12:21 AM
- Marked as answer by Darin Smith MS Tuesday, February 3, 2009 9:29 PM
Thursday, January 29, 2009 12:05 AM -
Hello Again Lance359,
If you are following this post then you have Successfully restarted Vista's Software Licensing Service. If you have not, then please see the "Note" section in my above post. There is no point in attempting to resolve the In Memory Mod-Auth since without first restarting Vista's Software Licensing service. Without the Service, you will not be able to figure out which incompatible program is causing the problem, let alone if the issue is fixed or not.
-----------
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 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 occur.
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 there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a TMod-Auth State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
Below I have provided a number of steps to help you identify the program that is causing the In Memory Mod Auth Tamper:
First, go to http://support.microsoft.com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:(year) (month) (day) (time in 24format) (millisecond)
M:2009 01 28 1213 27330-
Now that you know the time of the tamper, you can now try to connect that time with a program.1) Login to Vista and select the option that launches an Internet Browser
2) Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
3) When asked if you want to Open or Save this file, select Open
4) In the left hand panel, click Reliability Monitor
5) Click on the “System Stability Chart” above the date 01/28
6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/28/2009"
7) Look for any program that shows "Application Install" in the 'Activity' column.
8) Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 01/27/2009, 01/26/2009 and 01/25/2009
This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue . Unfortunately, if you installed the program some time in the past and just now ran it for the frst time, this process may not be helpful. The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
Also Note : it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In memory Mod-Auth. I have seen a recent increase of In Memory Mod-Auths and a number of them I have receive confirmation that a Malware infection was the cause. If you follow the above steps and can not find a program that is causing the Mod-Auth, you may want to investigate if a Virus or Trojan may be the cause. You can contact PC Safety, which is a Microsoft group, that provides free help with Malware infections.
PC Safety:
1-866-PCSafety or 1-866-727-2338
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Proposed as answer by Darin Smith MS Thursday, January 29, 2009 12:21 AM
- Marked as answer by Darin Smith MS Tuesday, February 3, 2009 9:29 PM
Thursday, January 29, 2009 12:19 AM
All replies
-
Hello Lance359,
It looks like there maybe more then one issue going on here.
1) The error code 0x80070426 tells me that Vista's Software Licensing Service has stopped
2) The error message "An unauthorized change was made to your license" and the Tamper Time stamp (TTS) Error: M:20090128121327330- in your diagnostic report suggests a In Memory type Mod-Auth tamper. Meaning an incompatible program is attempting to do something that Vista does not allow (note: it does not matter that you did not install anything recently. Viruses, Trojans and other malware can be incompatible with Vista too)
First you will want to restart Vista's Software Licensing Service. Vista uses this Service to check itself for Mod-Auth tampers and such (basiclly it monitors Vista to confirm it is Genuine) but if the Service is somehow stopped or disabled, Vista automaticly defaults to Non-Genuine.
Please try the first set of steps and if it does not resolve the issue, move on to the next set.
Note: There are a number of Services that run under Windows and while the Software Licensing Service, itself, is supported by Windows Genuine Advantage, the process for starting and stopping services is a Windows Core sub-system and is outside the focus (and knowledge) of this support. If the below steps do not result in the Software Licensing Service running, there may be a larger issue with Vista's Services sub-system and we suggest contacting Vista support at http://support.microsoft.com
The first set of steps are how to set the Software Licensing Service to start at each Vista Start-up.
1. Click on the Start button and in the Start Search box type in: services.msc
2. Press the Enter key on your keyboard.
3. The Services window should now open.
4. Scroll down to Software Licensing, then right-click on it and select Properties.
5. Under the General tab, click on the Stop button.
6. Set the Startup Type to Automatic, then click Apply.
7. Next, under Service Status, click on the Start button.
8. Last, restart your computer.
The second set of steps are the Manual steps to Force Start the Software Licensing Service.
If you have access to the Start button:
1) Click the Start button
2) Type: cmd in the Start Search field
3) At the top the Start window, you will see cmd.exe
4) Right Click cmd.exe and select Run as Administrator
5) Type: net start slsvc
If you do not have access to the Start button:
1) Click the option that launches an Internet Browser
2) A Browser will open, type: %windir%\system32 into the address field
3) Find the file cmd.exe
4) Right Click on the cmd.exe and select Run as Administrator
5) Type: net start slsvc
Once you have restarted the Software Licensing service, go down to my next post where I provide assistance in fixing the In Memory Mod-Auth Tamper issue.
Thank you,
Darin MS
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Edited by Darin Smith MS Thursday, January 29, 2009 12:20 AM
- Proposed as answer by Darin Smith MS Thursday, January 29, 2009 12:21 AM
- Marked as answer by Darin Smith MS Tuesday, February 3, 2009 9:29 PM
Thursday, January 29, 2009 12:05 AM -
Hello Again Lance359,
If you are following this post then you have Successfully restarted Vista's Software Licensing Service. If you have not, then please see the "Note" section in my above post. There is no point in attempting to resolve the In Memory Mod-Auth since without first restarting Vista's Software Licensing service. Without the Service, you will not be able to figure out which incompatible program is causing the problem, let alone if the issue is fixed or not.
-----------
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 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 occur.
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 there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a TMod-Auth State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
Below I have provided a number of steps to help you identify the program that is causing the In Memory Mod Auth Tamper:
First, go to http://support.microsoft.com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:(year) (month) (day) (time in 24format) (millisecond)
M:2009 01 28 1213 27330-
Now that you know the time of the tamper, you can now try to connect that time with a program.1) Login to Vista and select the option that launches an Internet Browser
2) Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
3) When asked if you want to Open or Save this file, select Open
4) In the left hand panel, click Reliability Monitor
5) Click on the “System Stability Chart” above the date 01/28
6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/28/2009"
7) Look for any program that shows "Application Install" in the 'Activity' column.
8) Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 01/27/2009, 01/26/2009 and 01/25/2009
This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue . Unfortunately, if you installed the program some time in the past and just now ran it for the frst time, this process may not be helpful. The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
Also Note : it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In memory Mod-Auth. I have seen a recent increase of In Memory Mod-Auths and a number of them I have receive confirmation that a Malware infection was the cause. If you follow the above steps and can not find a program that is causing the Mod-Auth, you may want to investigate if a Virus or Trojan may be the cause. You can contact PC Safety, which is a Microsoft group, that provides free help with Malware infections.
PC Safety:
1-866-PCSafety or 1-866-727-2338
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Proposed as answer by Darin Smith MS Thursday, January 29, 2009 12:21 AM
- Marked as answer by Darin Smith MS Tuesday, February 3, 2009 9:29 PM
Thursday, January 29, 2009 12:19 AM
