locked
Unauthorized change made, limited use, no start button, had a virus, Thanks for looking RRS feed

  • Question

  • I had a virus that caused some problems. I used an antivirus to find and remove the virus. Upon rebooting my computer, I have limited use. It came up with "windows software protection" window. It says "an unauthorized change was made to windows." and "Windows has discovered a change that will result in limited Windows functionality. Use the link below to find out how to fix Windows." I tried the validation at the microsoft validation website. I also tried using the net start slsvc command as administrator before the validation. But the validation always fails. I have had this comuter for 2+ years now with no problems. Important: I have no start button and no acces to the control panel that I can find. I tried a system restore to as far as I could, which is 2 weeks. It still has the same unauthorized change error message which started 2 days ago after clearing the virus. My only acces to any file is through internet explorer. One further complication is that I am using logmein  (similar to GOTOmyPC) from the US. and the computer and my 15 year old daughter is in Honduras. Even with this limited access, Logmein works fine once the computer fully boots. But anything that needs to be done before boot has to be coordinated with her. Also, automatic updates has been off for some time, maybe years? but all of a sudden it keeps trying to install updates as I shut down. Then upon booting it finds a problem and removes all the updates. Please help me restore windows Vista. Thank you so much for taking the time to review this information.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-GD2PK-BD3R2-44MV3
    Windows Product Key Hash: f7FPE6g/CLFmnJ4E6GbEU9Xn1sA=
    Windows Product ID: 89572-OEM-7332166-00021
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.002
    ID: {243217C0-6634-4804-AF3B-7C348B92A88A}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Basic
    Architecture: 0x00000000
    Build lab: 6000.vista_ldr.100218-0019
    TTS Error: M:20101127125602344-
    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: 114 Blocked VLK 2
    Microsoft Office Professional Edition               2003 - 114         2003 - 114 Blocked VLK 2
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_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 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-->
    File Mismatch: C:\Windows\system32\dnsapi.dll[6.0.6000.20740], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{243217C0-6634-4804-AF3B-7C348B92A88A}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6000.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-44MV3</PKey><PID>89572-OEM-7332166-00021</PID><PIDType>2</PIDType><SID>S-1-5-21-3624432063-2329503558-1459896849</SID><SYSTEM><Manufacturer>Compaq-Presario</Manufacturer><Model>GC662AAR-ABA SR5113WM</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version> 5.09</Version><SMBIOSVersion major="2" minor="4"/><Date>20070515000000.000000+000</Date></BIOS><HWID>B1323507018400E8</HWID><UserLCID>480A</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central America 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-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57001</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: U1BMRwEAAAAAAQAABAAAAE4MAAAAAAAAYWECADAgAAAjfWGibsfIAdArSr9MLECc5R83cvYPeMznAXYVeDsBZq1KY2CXHwQlKKWrDSX+TUnPcknHNFs3/fmA2FF124VnPMn56Nv0G9GSHcVVv83wdsn3Del+lcWOGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMLiwVVAoMyU94f4OJRDtahjIHJxql0xja2QHEOfkX2gL5gNhRdduFZzzJ+ejb9BvRLix0jhgxoZh9KIqIeiT4KBg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJ/LDbD7YAFCrt0CwU8rCLBb5J3qRftJP7lt0UnK2qL1eifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zGTTqXj8Zp7wBRfkK/v58Np7ZKBOP3AlXNjRrbegJYlo+YDYUXXbhWc8yfno2/Qb0cSPuH2XLwTJ6hHrdDfylMIYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYifyw2w+2ABQq7dAsFPKwiwW+Sd6kX7ST+5bdFJytqi9Xon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMz7XHvoomTAtX2vg3tfKMspr6Bus4asAsuQNeOjXniq2/mA2FF124VnPMn56Nv0G9H6ytgGyE/eExTUlRVKoux/GD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMpUG0Rsv9gDYREKgJMNkrymp0rKXPcP95dM9853efKQT5gNhRdduFZzzJ+ejb9BvR+srYBshP3hMU1JUVSqLsfxg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJ/LDbD7YAFCrt0CwU8rCLBb5J3qRftJP7lt0UnK2qL1eifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zKGqYcRIJnL37yRcjRvLH0J/0+mn5NDn6IcBvhhsGDvt+YDYUXXbhWc8yfno2/Qb0frK2AbIT94TFNSVFUqi7H8YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYifyw2w+2ABQq7dAsFPKwiwW+Sd6kX7ST+5bdFJytqi9Xon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMzaQTx0FVDUVYnau79KazsfL1aWovCjKPFwzQW4pZSJbPmA2FF124VnPMn56Nv0G9H6ytgGyE/eExTUlRVKoux/GD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMz/s5e5eTEFiBay8iDQVDybmlHxYfr5ckAzOOSFBhVYv5gNhRdduFZzzJ+ejb9BvRJOlpCe+XJsqgdANqY5cUsBg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJ/LDbD7YAFCrt0CwU8rCLBb5J3qRftJP7lt0UnK2qL1eifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zK/CMjHJ6wX8LH5kNQRbPQipYydS/sgAgL/s63kXcd53+YDYUXXbhWc8yfno2/Qb0caWqwq5NVLMsBILKRuWRP4YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYifyw2w+2ABQq7dAsFPKwiwW+Sd6kX7ST+5bdFJytqi9Xon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMw6iP7fubgMmZytUYKBOxoBWaKG0vTiLcTJhW3e7gCo1vmA2FF124VnPMn56Nv0G9EMxVTZfacBn7pfP46pwhlRGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMa5+Y56NSKLGKFnjTuEaab6jYP0/EsWFrGkqzZqCbd2n5gNhRdduFZzzJ+ejb9BvRDMVU2X2nAZ+6Xz+OqcIZURg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJ/LDbD7YAFCrt0CwU8rCLBb5J3qRftJP7lt0UnK2qL1eifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zEuPxy/0OZExxDCE2bIOBKRgCljJuoHwH6H/gcHorQt9+YDYUXXbhWc8yfno2/Qb0bjpGFMzc47ad/A/xGnQXGkYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYifyw2w+2ABQq7dAsFPKwiwW+Sd6kX7ST+5bdFJytqi9Xon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMzUXtxBid70LDYhoEFQoVCxkTr/Eb3Xbg4HXQESX5Lid/mA2FF124VnPMn56Nv0G9G46RhTM3OO2nfwP8Rp0FxpGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMELzQB7LC8jgd21CmVVlS+foOU7OIkn2tUD4zovnBYPX5gNhRdduFZzzJ+ejb9BvRuOkYUzNzjtp38D/EadBcaRg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJ/LDbD7YAFCrt0CwU8rCLBb5J3qRftJP7lt0UnK2qL1eifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zOSjL5FdvBK3E8bWgABr/MQKEMDumDoeYd8seGom05Fd+YDYUXXbhWc8yfno2/Qb0bjpGFMzc47ad/A/xGnQXGkYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYifyw2w+2ABQq7dAsFPKwiwW+Sd6kX7ST+5bdFJytqi9Xon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMy0uP/GWcreGatb0r2wXYZI4wjCkgEe+e0z7s1MutHKC/mA2FF124VnPMn56Nv0G9FVWOwp3LXieLpkoR8TFDSRGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2In8sNsPtgAUKu3QLBTysIsFvknepF+0k/uW3RScraovV6J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Licensing Data-->
    Software Licensing service is not running.

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OgAAAAIAAwABAAIAAgACAAAAAgABAAEAnJ+mXIV4DXXWkRC2kgAAq0yOznCN7/L0ZuOJ2F4YrFbI9A==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   HPQOEM  SLIC-CPC
      FACP   HPQOEM  SLIC-CPC
      HPET   HPQOEM  SLIC-CPC
      MCFG   HPQOEM  SLIC-CPC
      SLIC   HPQOEM  SLIC-CPC
      SSDT   HPQOEM  SLIC-CPC

     

    Saturday, November 27, 2010 9:16 PM

Answers

  • It should be possible to repair the system without recourse to a reformat/reinstall.

    Vista is in, what we call 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 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 caused by a running program that is incompatible with Vista.

     

      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an 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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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 Mod-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 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:20101127125602344-
     This is the Tamper Time Stamp and it breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010        11          27            1256                      02344-
     -

     


    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 Nov 27 

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for Nov 27 2010 "

    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 Nov 25, 26.,27 (or around the date the issue first occurred)

      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 at some time in the past, but didn’t run it till now, 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. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Friday, December 3, 2010 10:27 PM
    Sunday, November 28, 2010 6:04 PM
    Moderator

All replies

  • Saturday, November 27, 2010 9:22 PM
    Moderator
  • If I perform the system recovery without a backup, will I lose my other data on my drive, such as pictures?

     

    Thanks,

    Jeff

    Saturday, November 27, 2010 9:47 PM
  • Yep, an HP recovery procedure will wipe the drive clean (reformat it) and then reinstall the Windows Vista operating system.  However, as I recall, the initial recovery process will prompt you to create a backup of your files.  Please see: Backing up files during recovery section in the link I previously posted.


    Carey Frisch

    Saturday, November 27, 2010 9:56 PM
    Moderator
  • It should be possible to repair the system without recourse to a reformat/reinstall.

    Vista is in, what we call 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 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 caused by a running program that is incompatible with Vista.

     

      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an 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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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 Mod-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 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:20101127125602344-
     This is the Tamper Time Stamp and it breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010        11          27            1256                      02344-
     -

     


    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 Nov 27 

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for Nov 27 2010 "

    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 Nov 25, 26.,27 (or around the date the issue first occurred)

      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 at some time in the past, but didn’t run it till now, 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. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Friday, December 3, 2010 10:27 PM
    Sunday, November 28, 2010 6:04 PM
    Moderator