Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Vista Unauthorised Change after Windows Update RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I ran windows update 30 mins ago and it said 2 updates installed ( they were pretty big and I think one of them was a new version of Explorer (8).  On reboot (as requested) I got the following when I tried to log on to my ID.

    Windows Activation
    An unauthorised change was made to windows.
    Windows has discovered a change that will result in limited Windows Functionality.  Use link below to find out how to fix windows.

    Following the link took me to a page that said Windows could be sure my Vista was genuine and offered a link to the Genuine Validation page.

    As my system is 100% genuine and I've run this many times before for Vista and for Office I had no concern about running it again.  It downloaded ( a new version? ) of the activation control and then told me my system was not Genuine!

    I followed some of the links - ran the tool that said it would check I was OK to run the advantage tool and all the checks passed but the validation tool still said it's not a valid system.

    The further help gave some guidance on restarting the windows validation service which was completely useless since I have no way to get to the start button and follow the recommended steps. The ONLY thing that works is this browser session. Closing the browser window - or just dismissing the dialog box logged me off - stopping me from attempting to fix the problem.

    This system has been running for well over a year since I last installed it.  There have been no new programs installed and I run a fully loaded up to date AntiVirus and Firewall ( Kaspersky ).  I don't visit dodgy web sites.

    I will try to find this forum from my laptop which hopefully is still running.

    I note that some of the posts in the forum talk about running some sort of diagnostic - but I don't know how to do this, especially without being able to be logged on.

    Your help would be much appreciated as I really don't want to have to reinstall.

    Thanks
    Sunday, May 3, 2009 2:57 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Paul,


      In your Diagnostic Report is a line that says: "TTS Error: M:20090503151340877".  TTS stands for Tamper Time Stamp. The time stamp tells me that am "M" (meaning Mod-Auth) type issue occured at 20090503151340877 which translates to "May 3rd 2009 15:13 (3:13PM) and 40877 milliseconds" (in local computer time).

      

      A Mod-Auth Tamper occures when a program modifies (tampers) Vista System Files. Your Diagnostic Report continues to tell me that the the system files being modified, in your case, were running in system memory (i.e. RAM) this is called an In Memory Mod-Auth Tamper.   The only things that can cause this type of issue are Programs that are incompatible with Vista or Malware.  The mechanism that Vista uses to detect a Tamper doesn't run all the time (it, in fact, runs randomly) so it makes sense that you wouldn't see the issue all the time. 

      If the issue continues, please follow the below guidelines for assistance in identifing the incompatible program or malware infection.


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

        (year)  (month) (day) (time in 24format) (millisecond)
    M:    2009       05        03            1513                  40877-


    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 05/03 

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/03/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 05/02/2009, 05/01/2009 and 04/30/2009  (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

    Thank you,
    Darin MS
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 9:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello paulmg,

      To generate a Diagnostic Report,

    1) Click the "Use link below to find out how to fix windows" option.
    2) An Internet Browser will open, 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 (after a few sec.) click the “Copy” button.
    5)  Return to this thread http://social.microsoft.com/Forums/en-US/genuinevista/thread/7f9bdd96-1568-43d4-a5d6-1948358f58c4 .In a reply post, paste the Diagnostic Report.

    Thank you,
    Darin MS


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Something strange happened.  I tried a few more times and got nowhere.
    Eventually after several more tries the error message went away and Vista started normally.
    Have no idea why - since I was unable to change the system in any way.

    Ran your MGA Tools and got this (below)  - though it now (of course) shows all OK.

    Maybe there is some timing issue or inconsistency in the checking software. 

    Anyhow .. thanks for trying .. Paul

    Diagnostic Report (1.9.0006.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0
    Online Validation Code: 0x0
    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-GJM8G-YWHT8-JPJ9G
    Windows Product Key Hash: tU3/GkaFIpnf8yWnOyJPZkxkmXg=
    Windows Product ID: 89578-483-2250813-71880
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {86962FE8-1642-4922-A09D-3FE0217AE8BF}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.090302-1506
    TTS Error: M:20090503151340877-
    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: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: Registered, 1.7.111.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    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: 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>{86962FE8-1642-4922-A09D-3FE0217AE8BF}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-JPJ9G</PKey><PID>89578-483-2250813-71880</PID><PIDType>5</PIDType><SID>S-1-5-21-3789313466-3545908908-2760892996</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS A8N-SLI Premium ACPI BIOS Revision 1303</Version><SMBIOSVersion major="2" minor="3"/><Date>20060810000000.000000+000</Date></BIOS><HWID>B7333507018400F6</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>2F8CD4918D86F1A</Val><Hash>YZMLqIz1ygyrbXi/h2iWJ5kwNcw=</Hash><Pid>81602-909-5504851-68459</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAALoTAAAAAAAAWmICAOjgbZeu7c+8I6LJAVMWKYGB4wMcsbz+lAen7Wcb//w+2FDwzHrgCv96Ia7pmGe2v8SlKTycnojfTvBwWO97BuxrKcj+9gzTrUJt+r2dmomSaJBUQwqxuI3aY6YYnKfOZv/AmB9uvmxWADGc/Om8chOEErmG/Notf8znFtOTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o3ahIBpTbeopSs8i4ZePvEQhLRUSI+U3SBDxSocUJDOz74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nG7/kKvFyrZB/hYEI+VbH5OPtX2VxPPxhEAijr+U4dxHvewbsaynI/vYM061Cbfq9394MfT+3z/yidsgv5iE2M5ynzmb/wJgfbr5sVgAxnPzpvHIThBK5hvzaLX/M5xbTkzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6N2oSAaU23qKUrPIuGXj7xEIS0VEiPlN0gQ8UqHFCQzs++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZwFUHjTAgCfFMkM31Y0FGdFIWrbpNDjyBMJb257fOO4i73sG7GspyP72DNOtQm36vVSyUXQMAt0r04D3FFrdCFCcp85m/8CYH26+bFYAMZz86bxyE4QSuYb82i1/zOcW05M3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXujdqEgGlNt6ilKzyLhl4+8RCEtFRIj5TdIEPFKhxQkM7PvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

    Licensing Data-->
    Software licensing service version: 6.0.6001.18000
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, RETAIL channel
    Activation ID: 9e042223-03bf-49ae-808f-ff37f128d40d
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89578-00142-483-225081-01-2057-6001.0000-2022008
    Installation ID: 011820421932826325379935006101629330889571130423613726
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: JPJ9G
    License Status: Licensed

    HWID Data-->
    HWID Hash Current: PgAAAAEABgABAAEAAgABAAAABAABAAEAJJSWsnZc3pN+COrUAId06j6O6iZ84cYO8vS2DjCXoqUitqxWYKk=

    OEM Activation 1.0 Data-->
    N/A

    OEM 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   Nvidia  AWRDACPI
      FACP   Nvidia  AWRDACPI
      MCFG   Nvidia  AWRDACPI

     

    Monday, May 4, 2009 8:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Paul,


      In your Diagnostic Report is a line that says: "TTS Error: M:20090503151340877".  TTS stands for Tamper Time Stamp. The time stamp tells me that am "M" (meaning Mod-Auth) type issue occured at 20090503151340877 which translates to "May 3rd 2009 15:13 (3:13PM) and 40877 milliseconds" (in local computer time).

      

      A Mod-Auth Tamper occures when a program modifies (tampers) Vista System Files. Your Diagnostic Report continues to tell me that the the system files being modified, in your case, were running in system memory (i.e. RAM) this is called an In Memory Mod-Auth Tamper.   The only things that can cause this type of issue are Programs that are incompatible with Vista or Malware.  The mechanism that Vista uses to detect a Tamper doesn't run all the time (it, in fact, runs randomly) so it makes sense that you wouldn't see the issue all the time. 

      If the issue continues, please follow the below guidelines for assistance in identifing the incompatible program or malware infection.


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

        (year)  (month) (day) (time in 24format) (millisecond)
    M:    2009       05        03            1513                  40877-


    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 05/03 

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/03/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 05/02/2009, 05/01/2009 and 04/30/2009  (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

    Thank you,
    Darin MS
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 9:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Can someone help me. Since a couple a days ago the validation error was happening to me. I can't even go into Control Panel, or search for updates.
    This is my report.
    Diagnostic Report (1.9.0006.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    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: {9E4D42C8-41EA-451A-B59C-648B783ADF92}(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: 6001.vistasp1_gdr.090302-1506
    TTS Error:
    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: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 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 8.0; Win32)
    Default Browser: C:\Program Files\Opera\opera.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>{9E4D42C8-41EA-451A-B59C-648B783ADF92}</UGUID><Version>1.9.0006.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-292908123-1370728468-2763552064</SID><SYSTEM><Manufacturer>Gateway</Manufacturer><Model>GT5620</Model></SYSTEM><BIOS><Manufacturer>945GCT-M3</Manufacturer><Version>V1.07</Version><SMBIOSVersion major="2" minor="4"/><Date>20070626000000.000000+000</Date></BIOS><HWID>45323507018400FA</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>GATEWA</OEMID><OEMTableID>SYSTEM  </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>7B346FE747BB70E</Val><Hash>PxJQkgQsrWdg+R2ep+lnGj0uQSQ=</Hash><Pid>81602-903-6966942-68855</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

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

    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAQABAAAAAgABAAEAJJSsKwxXIiZk9ap2SOQS9Zb78vSKBzpJrFYqhQ==

    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            GATEWA        SYSTEM  
      FACP            GATEWA        SYSTEM  
      HPET            GATEWA        SYSTEM  
      MCFG            GATEWA        SYSTEM  
      SLIC            GATEWA        SYSTEM  
      SSDT            PmRef        Cpu0Ist
      SSDT            PmRef        Cpu0Ist


    Tuesday, May 5, 2009 9:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Darin,
    Thanks for your help - unfortunately I wasn't able to follow up on the investigation.  I was thinking about rebuilding my system anyway to reconfigure the hard disks and so did a clean re-install rather than waiting for the problem to re-occur and spending time shooting it.
    Thanks again ... Paul
    Thursday, May 7, 2009 9:12 AM