none
Vista activation Error: 0xC004D401 RRS feed

  • Question

  • I recently (<30 days) got a gateway laptop running Vista Home Premium. 

    I have not activated Vista yet and for the last 2-3 days am getting the error : "An unauthorized change was made to Windows."
    I ran the 'genuine windows test' on http://www.microsoft.com/genuine/validate/default.aspx?displaylang=en&sguid=3ac35640-2cfa-4e56-8fee-1eef204a0332&control=install

    and it said
    "
    This copy of Windows did not pass genuine validation.

    A software program installed on this computer may be incompatible with Windows Vista.
    "

    I tried to activate by going to Control Panel > System > Windows activation

    but on clicking "Click here to activate Windows now" again gives the "An unauthorized change was .. " error. A dead end.

    Any ideas ?

    Thanks
    Wednesday, January 21, 2009 6:36 PM

Answers

  • Hi

    I had to take the extreme step of restoring the laptop to factory settings using restore discs :(

    Entered the product id again and it now says that 'windows is activated'

    Hopefully this will settle the issue.

    Rgds

    • Marked as answer by Darin Smith MS Wednesday, January 28, 2009 12:41 AM
    Tuesday, January 27, 2009 2:13 AM

All replies

  • Hello vistaOnGateway,

      

    In order to recieve the best support, we request all users initially download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue" click the Windows tab, click the "Copy" button, then paste the report into a response message in this thread.


    If you do not have access to the Start Button:

    1) Login to Vista and Click the option that brings up Internet Explorer.

    2) Type: http://go.microsoft.com/fwlink/?linkid=52012 into the browser address bar.

    3) A window will come up asking if you want to Run or Save, Select Run

    4) When the program runs, Click the Continue button, then click the Copy button.

    5) Return to this thread by Typing: http://forums.community.microsoft.com/en-US/genuinevista/thread/8a57a012-8f38-4430-a632-fffcdffcaf75 into the browser address bar.

    6) In a reply post, Paste the Diagnostic Report.



    Thank you,
    Darin


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Wednesday, January 21, 2009 9:02 PM
  •  

    Diagnostic Report (1.7.0110.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-3RBY2-BGQ2R-DR9M6
    Windows Product Key Hash: EYIpz/47G03lWRAOmk3kg+lR7Rc=
    Windows Product ID: 89578-OEM-7332157-00141
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {5BF66BE1-4CDA-4DAE-8242-6E515807716C}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error: K:20090121160309775-M:20090121131814144-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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
    WGATray.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-709-645_025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3_FA827CE6-153-8007007e_FA827CE6-180-8007007e



    Wednesday, January 21, 2009 9:15 PM
  •  

    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 usually caused by a running program that is incompatible with Vista.

     Note: you did not provide the whole Diagnostic Report, so it is missing the "File Scan Data--->" section. I use that section to be able to tell if the issue is a In Memory or On Disk type mod-auth. Basically, if there is any file(s) listed under the "File Scan Data--->" section, then it would be an On Disk Mod-Auth, but if there is no file listed, then it's an In Memory Mod-Auth.
     
      Below I have provided information for dealing with a In Memory Mode-Auth, since it is the most common type.

    -----------------------------------------------------

     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 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        21             1318                    14144-

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well[C2] .


    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/21 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/21/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/20/2009, 01/19/2009 and 01/18/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 ago, but you didn't run it till now (and, hence, prompted the tamper state), 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

    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 Wednesday, January 21, 2009 10:44 PM formatting
    • Proposed as answer by Darin Smith MS Wednesday, January 21, 2009 10:46 PM
    Wednesday, January 21, 2009 10:43 PM
  • Hi Darin

    I followed the instructions to find any program installed recently which could cause " In Memory Mode-Auth " state. I checked reports for last 3 days and found one new installation which I then removed but it did not help. In the reliability monitor, there were several "Driver Install" and "Application Uninstall" (eg, Windows Live Messenger, Microsoft Works).

    I ran the diagnostic tool again. Below is the full copy. By the way, running the diagnostic tool also give the "An unauthorized change was made to Windows." error and I still cant change product key in System.

    ----------------

    Diagnostic Report (1.7.0110.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-3RBY2-BGQ2R-DR9M6
    Windows Product Key Hash: EYIpz/47G03lWRAOmk3kg+lR7Rc=
    Windows Product ID: 89578-OEM-7332157-00141
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {5BF66BE1-4CDA-4DAE-8242-6E515807716C}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error: K:20090121160309775-M:20090121180922929-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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
    WGATray.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-709-645_025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3_FA827CE6-153-8007007e_FA827CE6-180-8007007e

    Browser 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: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{5BF66BE1-4CDA-4DAE-8242-6E515807716C}</UGUID><Version>1.7.0110.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-DR9M6</PKey><PID>89578-OEM-7332157-00141</PID><PIDType>2</PIDType><SID>S-1-5-21-1993426301-2012136589-3533103626</SID><SYSTEM><Manufacturer>Gateway</Manufacturer><Model>T-6330u</Model></SYSTEM><BIOS><Manufacturer>Gateway</Manufacturer><Version>89.25</Version><SMBIOSVersion major="2" minor="4"/><Date>20080721000000.000000+000</Date></BIOS><HWID>4B303507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>GATEWA</OEMID><OEMTableID>SYSTEM  </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAHAIAAAAAAAAYWECAAQwSojKMDUsP3rJAW4aG1/FHasdtBRBPRnxqCLx/3TaYtqDnlgtTYt2/6JXzC3ZwlSJxSTtv6MCNTw8q7hyF0mQSAB5ba/1Omiqgsr2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi8f902mLag55YLU2Ldv+iV8wt2cJUicUk7b+jAjU8PKu4chdJkEgAeW2v9TpoqoLK9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIsTx6ktc4+yjoO9uQby4HsWW89F9Q4QQPlHIYB56uUQ1WDEt+xCUHnMQMEoqnh3Rm/ZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCLE8epLXOPso6DvbkG8uB7FlvPRfUOEED5RyGAeerlENVgxLfsQlB5zEDBKKp4d0Zv2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi8f902mLag55YLU2Ldv+iV+O84oYDL6lsSe8u94ETeOwdpw5gY5jEhBqDUK2RmFGd9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIktdzbaGF+P2v2DzON99O9wSmA+DeOZVmCsq3d1rzd/eX3iEEbbGuCouWtoMXt9CRfZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCLfe1qWwpdBgvkncJfDCFGgcXLG17XgJD7twOM6ENpWnNts49Paoo93aHHA2fDvsFL2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi2W/n4e4Y5FPtHLnL81USZfw+eVXQcESwVt4u8iUmjo7aF6zXtiF+TCoE6u4pO3sP9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIsKegdl3lvB5x2L9grhWxsZIkUgUItZwRBL1ZoXiQj1Ske1zbXZ5MxMQ4eXxSk0E3/ZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJOcFNUfVuQ9aaZkgB5+vHMRrlnwvvwMLiInQUjTZb4TyTyNQZ361vFlxHFbCE+uKX2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiw9sdxChPU07lNo2QW9UEaO9kgPnNw/o6XFqFLLepBKEG2AVd/aEPPjY5DDIkTlqz9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401

    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAIAAQABAAAAAwABAAEAeqj0aRaRKq3ywgYMRoNqvlL+7Njy9LyqJl58RaxWKoU=

    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   INTEL   CRESTLNE
      FACP   INTEL   CRESTLNE
      HPET   INTEL   CRESTLNE
      BOOT   PTLTD   $SBFTBL$
      MCFG   INTEL   CRESTLNE
      TCPA   Intel    CRESTLN
      TMOR   PTLTD          
      SLIC   GATEWA  SYSTEM 
      APIC   INTEL   CRESTLNE
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci


     

    Wednesday, January 21, 2009 11:32 PM
  • The full Diagnostic confirms it's a In Memory type.  It could be a Driver, but that is unlikely (incompatible drivers usually cause a different error).

      One of the best (but most inconvenient) ways to figure out what program is causing the issue (if you were unable to do it using my above steps) is, that once you see the error come up, you know that the incompatible program is currently running. See what programs you have open right then (including any programs that launch at startup, such as anti-virus and such) and then uninstall the most recently installed program. Then reboot and see if the error happens again. Keep that up till you no longer get the error.

      If, by the unlikely chance, that the issue is being caused by a Driver, you may want to take that "Driver Install" list, find the most up-to-date version of each of those drivers and install them. This should overwrite the older drivers and since up-to-date drivers are more likely to be compatible with Vista, if the issue is being caused by a bad driver, this should fix it.

      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

    Hope this helps,
    Darin

    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Thursday, January 22, 2009 12:53 AM
  • Hi Darin

    As per your suggestion, I was monitoring the occurence of "An unauthorized change was made to Windows."

    The error seems to be coming up periodically precisely every 30 min in a 2hr+ period. The only program running all this while was IE.

    Does this give any clue ?

    Regards

    Friday, January 23, 2009 5:27 PM
  •  

     Since IE is not incompatible with Vista, the program that is causing the problem is, most likely, running (in the background) at the time Vista is starting up. 

    Examples of programs that run in the background (that start at Vista Startup) include Anti-Virus, Firewall and so on.

    In addition, Malware, such as Viruses and Trojans, just like any other program, can be incompatible with Vista. They also usually run in the background and at Vista start up. (I just recently got confermation that a Trojan named twex.exe caused this same type of Mod-Auth issue, for another customer, and once it was removed the Mod-Auth ceased).

    In your case, since you haven't (knowingly) installed anything new and the offending program appears to run in the background and starts at Windows Startup, my gut feeling is that the cause is either a bad driver or malware.

     

    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

     

    If you believe your issue is caused by some sort of malware, you may want to call PC Safety. They are a Microsoft dept that provides free support for Malware related infections:

    Call <removed by Moderator: Phone number no longer in use>

     

    Darin


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    • Edited by Darin Smith MS Tuesday, April 10, 2012 6:57 PM removed phone number no longer in use
    Friday, January 23, 2009 7:00 PM
  • Hi

    I had to take the extreme step of restoring the laptop to factory settings using restore discs :(

    Entered the product id again and it now says that 'windows is activated'

    Hopefully this will settle the issue.

    Rgds

    • Marked as answer by Darin Smith MS Wednesday, January 28, 2009 12:41 AM
    Tuesday, January 27, 2009 2:13 AM