New
#11
Sorry about that - real life got in the way (too many computers to fix!).
Back in a bit :)
Still no change - which means that the only known solution is a repair install
There is a vague chance that the SFC scan that Golden suggested may work (it has, on occasion) - so it's worth a try.
OK, sorry for the delay and thanks for not closing this thread.
I've been reading a lot of dead end threads on this topic so I enlisted the assistance of an old co-worker and (I even had a few good cognitive days where the old thinker was on the mark...lol) this is what we came up with.....
According to Microsoft, this seems to be a problem with a corrupt "Language Pack", aka .mui files.
They say,
"This issue may occur for several reasons. The most likely reason is that language packs (MUI) have been installed on computers that are running Windows editions that are not licensed for additional language packs. (Note This is not necessarily an indication of tampering. Some applications can install multi-lingual support even when that edition of Windows is not licensed for those language packs.) This issue may also occur if Windows has been modified by malware to allow additional features to be installed. This issue may also occur if certain system files are corrupted."
Regarding Error Code 0x8004FE21 - This computer is not running genuine Windows.
How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista
I've attached the "MGADiags" results as well as the "sfc /scannow" results from "safe mode" and neither one come up with any "file mismatch" or "tampered file" messages.
Now I may be having a "senior moment" here however, considering that the problem goes away in "safe mode" (been doing most of my work there because of it...lol) this obviously means there is something loading in "normal mode" that is causing the problem. (possibly the language packs or the corrupt files that have replaced the language pack files.)Code:MGADiag Safe Mode.txt Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: N/A, hr = 0x8007043c Windows Product Key: *****-*****-PFBD2-88J3C-7HT7Y Windows Product Key Hash: bY4ggYHJxC6zN9FFEChDKOAuGZk= Windows Product ID: 00426-067-9546972-86618 Windows Product ID Type: 5 Windows License Type: Retail Windows OS version: 6.1.7601.2.00010100.1.0.001 ID: {2FEA2CE8-4388-4C33-8566-B8D1B31394D2}(3) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Ultimate Architecture: 0x00000009 Build lab: 7601.win7sp1_gdr.120830-0333 TTS Error: 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: 109 N/A 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 (x86)\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>{2FEA2CE8-4388-4C33-8566-B8D1B31394D2}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7HT7Y</PKey><PID>00426-067-9546972-86618</PID><PIDType>5</PIDType><SID>S-1-5-21-1545054437-1505894867-219525375</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio 1737</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A04</Version><SMBIOSVersion major="2" minor="5"/><Date>20081126000000.000000+000</Date></BIOS><HWID>E1AD3B07018400F8</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>DELL </OEMID><OEMTableID>M09 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x8007043C' to display the error text. Error: 0x8007043C Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0x00000000 HealthStatus: 0x0000000000000000 Event Time Stamp: 10:24:2012 07:55 ActiveX: Registered, Version: 7.1.7600.16395 Admin Service: Not Registered - 0x8007043c HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: LgAAAAEABQABAAEAAAAAAAAAAAABAAEA6GHouzajOCt6f45saEF42uSWcsdGyg== OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x0 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC PTLTD APIC FACP INTEL CRESTLNE HPET INTEL CRESTLNE BOOT PTLTD $SBFTBL$ MCFG INTEL CRESTLNE SLIC DELL M09 OSFR DELL DELL SSDT PmRef CpuPm SSDT PmRef CpuPm SSDT PmRef CpuPm Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Ken>cd\ C:\>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\>
So, how do we...
1. replace or repair the corrupted files? Replace them from the Install Disk?
2. remove/uninstall all language packs or at least keep them from loading (I typically don't use any kind of language features)
I also did a search to see where most of the "Tampered Files" reside and it looks like there are various copies and versions of these files throughout the C:\windows directory, see below:
Now this may be a wild guess, but I'm thinking the original files may still be intact and somehow the system is loading the Tampered Files. However, how we determine that is not within my comprehension at the moment...lolCode:Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Ken>cd\ C:\>dir spsys.log /s Volume in drive C has no label. Volume Serial Number is 2633-0EC2 File Not Found C:\>dir spsys.* /s Volume in drive C has no label. Volume Serial Number is 2633-0EC2 Directory of C:\Windows\System32\drivers 06/10/2009 03:48 PM 426,496 spsys.sys 1 File(s) 426,496 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..ive-blackbox-driver_31bf3856ad364e35_6.1.7600.16385_none_656773dac187bca2 06/10/2009 03:48 PM 426,496 spsys.sys 1 File(s) 426,496 bytes Total Files Listed: 2 File(s) 852,992 bytes 0 Dir(s) 79,935,868,928 bytes free C:\>dir spp*.dl* /s Volume in drive C has no label. Volume Serial Number is 2633-0EC2 Directory of C:\Windows\System32 11/20/2010 08:27 AM 244,224 spp.dll 11/20/2010 08:27 AM 145,920 sppc.dll 07/13/2009 08:41 PM 413,696 sppcc.dll 07/13/2009 08:41 PM 1,203,712 sppcext.dll 11/20/2010 08:27 AM 232,448 sppcomapi.dll 07/13/2009 08:41 PM 381,952 sppcommdlg.dll 07/13/2009 08:41 PM 113,152 sppinst.dll 11/20/2010 08:27 AM 102,400 sppnp.dll 11/20/2010 08:27 AM 1,082,880 sppobjs.dll 07/13/2009 08:41 PM 65,536 sppuinotify.dll 11/20/2010 08:27 AM 418,816 sppwinob.dll 07/13/2009 08:41 PM 142,336 sppwmi.dll 12 File(s) 4,547,072 bytes Directory of C:\Windows\System32\en-US 07/13/2009 09:26 PM 4,608 spp.dll.mui 07/13/2009 09:26 PM 54,784 sppc.dll.mui 07/13/2009 09:27 PM 16,384 sppcc.dll.mui 07/13/2009 09:30 PM 17,408 sppcext.dll.mui 07/13/2009 09:29 PM 6,656 sppcomapi.dll.mui 07/13/2009 09:24 PM 52,224 sppcommdlg.dll.mui 07/13/2009 09:29 PM 2,560 sppnp.dll.mui 07/13/2009 09:29 PM 3,072 sppuinotify.dll.mui 8 File(s) 157,696 bytes Directory of C:\Windows\System32\oobe 11/20/2010 08:27 AM 57,856 spprgrss.dll 1 File(s) 57,856 bytes Directory of C:\Windows\SysWOW64 11/20/2010 07:21 AM 172,544 spp.dll 11/20/2010 07:20 AM 121,344 sppc.dll 07/13/2009 08:16 PM 389,632 sppcc.dll 07/13/2009 08:16 PM 1,111,552 sppcext.dll 11/20/2010 07:21 AM 193,536 sppcomapi.dll 07/13/2009 08:16 PM 345,088 sppcommdlg.dll 11/20/2010 07:21 AM 100,864 sppinst.dll 07/13/2009 08:16 PM 118,784 sppwmi.dll 8 File(s) 2,553,344 bytes Directory of C:\Windows\SysWOW64\en-US 07/13/2009 09:09 PM 4,608 spp.dll.mui 07/13/2009 09:05 PM 54,784 sppc.dll.mui 07/13/2009 09:04 PM 16,384 sppcc.dll.mui 07/13/2009 09:04 PM 17,408 sppcext.dll.mui 07/13/2009 09:03 PM 6,656 sppcomapi.dll.mui 07/13/2009 09:09 PM 52,224 sppcommdlg.dll.mui 6 File(s) 152,064 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-pnpsysprep.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2d12ac454fb6f8f6 07/13/2009 09:29 PM 2,560 sppnp.dll.mui 1 File(s) 2,560 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-pnpsysprep_31bf3856ad364e35_6.1.7601.17514_none_9fe380ebcdb1e969 11/20/2010 08:27 AM 102,400 sppnp.dll 1 File(s) 102,400 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..-spp-plugin-windows_31bf3856ad364e35_6.1.7601.17514_none_6fe02fb8134de429 11/20/2010 08:27 AM 418,816 sppwinob.dll 1 File(s) 418,816 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..-ux-sppcc.resources_31bf3856ad364e35_6.1.7600.16385_en-us_dc4609a958e3234e 07/13/2009 09:27 PM 16,384 sppcc.dll.mui 1 File(s) 16,384 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..clientext.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c2382769078e1059 07/13/2009 09:30 PM 17,408 sppcext.dll.mui 1 File(s) 17,408 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..pp-client.resources_31bf3856ad364e35_6.1.7600.16385_en-us_953f0977fbbe9530 07/13/2009 09:26 PM 54,784 sppc.dll.mui 1 File(s) 54,784 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..ty-spp-ux.resources_31bf3856ad364e35_6.1.7600.16385_en-us_54dae2e5153375ce 07/13/2009 09:29 PM 6,656 sppcomapi.dll.mui 07/13/2009 09:24 PM 52,224 sppcommdlg.dll.mui 07/13/2009 09:29 PM 3,072 sppuinotify.dll.mui 3 File(s) 61,952 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..y-spp-plugin-common_31bf3856ad364e35_6.1.7601.17514_none_2136d8ac9cfcea8b 11/20/2010 08:27 AM 1,082,880 sppobjs.dll 1 File(s) 1,082,880 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_6.1.7600.16385_none_28bbe77bcacffbe4 07/13/2009 08:41 PM 1,203,712 sppcext.dll 1 File(s) 1,203,712 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-client_31bf3856ad364e35_6.1.7601.17514_none_f4c2f729c23f3c2b 11/20/2010 08:27 AM 145,920 sppc.dll 1 File(s) 145,920 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-installer_31bf3856ad364e35_6.1.7600.16385_none_12cbc2d3c1ed26ee 07/13/2009 08:41 PM 113,152 sppinst.dll 1 File(s) 113,152 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux-sppcc_31bf3856ad364e35_6.1.7600.16385_none_ee126e948f0f7b95 07/13/2009 08:41 PM 413,696 sppcc.dll 1 File(s) 413,696 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7601.17514_none_b9e7a42ab571bbb9 11/20/2010 08:27 AM 232,448 sppcomapi.dll 07/13/2009 08:41 PM 381,952 sppcommdlg.dll 07/13/2009 08:41 PM 65,536 sppuinotify.dll 3 File(s) 679,936 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-wmi_31bf3856ad364e35_6.1.7600.16385_none_5d99275dbb91746d 07/13/2009 08:41 PM 142,336 sppwmi.dll 1 File(s) 142,336 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.1.7601.17514_none_905283bdc3e1d2d8 11/20/2010 08:27 AM 57,856 spprgrss.dll 1 File(s) 57,856 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-spp-main.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1caa2c287378295b 07/13/2009 09:26 PM 4,608 spp.dll.mui 1 File(s) 4,608 bytes Directory of C:\Windows\winsxs\amd64_microsoft-windows-spp-main_31bf3856ad364e35_6.1.7601.17514_none_426cfc30c37c5a4e 11/20/2010 08:27 AM 244,224 spp.dll 1 File(s) 244,224 bytes Directory of C:\Windows\winsxs\wow64_microsoft-windows-s..ty-spp-ux.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5f2f8d37499437c9 07/13/2009 09:03 PM 6,656 sppcomapi.dll.mui 07/13/2009 09:09 PM 52,224 sppcommdlg.dll.mui 2 File(s) 58,880 bytes Directory of C:\Windows\winsxs\wow64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7601.17514_none_c43c4e7ce9d27db4 11/20/2010 07:21 AM 193,536 sppcomapi.dll 07/13/2009 08:16 PM 345,088 sppcommdlg.dll 2 File(s) 538,624 bytes Directory of C:\Windows\winsxs\wow64_microsoft-windows-security-spp-wmi_31bf3856ad364e35_6.1.7600.16385_none_67edd1afeff23668 07/13/2009 08:16 PM 118,784 sppwmi.dll 1 File(s) 118,784 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-s..-ux-sppcc.resources_31bf3856ad364e35_6.1.7600.16385_en-us_80276e25a085b218 07/13/2009 09:04 PM 16,384 sppcc.dll.mui 1 File(s) 16,384 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-s..clientext.resources_31bf3856ad364e35_6.1.7600.16385_en-us_66198be54f309f23 07/13/2009 09:04 PM 17,408 sppcext.dll.mui 1 File(s) 17,408 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-s..pp-client.resources_31bf3856ad364e35_6.1.7600.16385_en-us_39206df4436123fa 07/13/2009 09:05 PM 54,784 sppc.dll.mui 1 File(s) 54,784 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-security-spp-clientext_31bf3856ad364e35_6.1.7600.16385_none_cc9d4bf812728aae 07/13/2009 08:16 PM 1,111,552 sppcext.dll 1 File(s) 1,111,552 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-security-spp-client_31bf3856ad364e35_6.1.7601.17514_none_98a45ba609e1caf5 11/20/2010 07:20 AM 121,344 sppc.dll 1 File(s) 121,344 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-security-spp-installer_31bf3856ad364e35_6.1.7601.17514_none_b8de3b18067e3952 11/20/2010 07:21 AM 100,864 sppinst.dll 1 File(s) 100,864 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-security-spp-ux-sppcc_31bf3856ad364e35_6.1.7600.16385_none_91f3d310d6b20a5f 07/13/2009 08:16 PM 389,632 sppcc.dll 1 File(s) 389,632 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-spp-main.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c08b90a4bb1ab825 07/13/2009 09:09 PM 4,608 spp.dll.mui 1 File(s) 4,608 bytes Directory of C:\Windows\winsxs\x86_microsoft-windows-spp-main_31bf3856ad364e35_6.1.7601.17514_none_e64e60ad0b1ee918 11/20/2010 07:21 AM 172,544 spp.dll 1 File(s) 172,544 bytes Total Files Listed: 70 File(s) 14,936,064 bytes 0 Dir(s) 79,993,409,536 bytes free C:\>
Sooooo, I'm hoping it is within yours...lol
Then again, this just may be another rabbit trail...
Any thoughts?
Stubbornly still here,
Ken
NO - this is NOT the 'Vistalizator' problem.
The reason that the problem 'goes away' in Safe Mode is that the TrustedInstaller service cannot run there, and so access is denied to the relevant parts of the OS for the program to do the checking - which is why you get the following error instead,,,,
Licensing Data-->
On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x8007043C' to display the error text.
Error: 0x8007043C
The problem lies not with the file system as such, but buried somewhere in the registry.
One thing you could try - I have no idea what the result is likely to be - would be a CheckSUR scan, which checks a part of the registry for errors, and may uncover something of note.
Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)
Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file
Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.
Well, You are just not going to believe this, but the issue is resolved and restored! Full functionality has returned to my system and there are no more MGA issues either, see for yourselves...
Code:MGADiag Report 2-28-2013.txt Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: 0x0 Windows Product Key: *****-*****-PFBD2-88J3C-7HT7Y Windows Product Key Hash: bY4ggYHJxC6zN9FFEChDKOAuGZk= Windows Product ID: 00426-067-9546972-86618 Windows Product ID Type: 5 Windows License Type: Retail Windows OS version: 6.1.7601.2.00010100.1.0.001 ID: {2FEA2CE8-4388-4C33-8566-B8D1B31394D2}(3) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Ultimate Architecture: 0x00000009 Build lab: 7601.win7sp1_gdr.130104-1431 TTS Error: 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: 109 N/A 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 (x86)\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>{2FEA2CE8-4388-4C33-8566-B8D1B31394D2}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7HT7Y</PKey><PID>00426-067-9546972-86618</PID><PIDType>5</PIDType><SID>S-1-5-21-1545054437-1505894867-219525375</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio 1737</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A04</Version><SMBIOSVersion major="2" minor="5"/><Date>20081126000000.000000+000</Date></BIOS><HWID>E1AD3B07018400F8</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>DELL </OEMID><OEMTableID>M09 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> Software licensing service version: 6.1.7601.17514 Name: Windows(R) 7, Ultimate edition Description: Windows Operating System - Windows(R) 7, RETAIL channel Activation ID: a0cde89c-3304-4157-b61c-c8ad785d1fad Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 00426-00172-067-954697-00-1033-7601.0000-0572013 Installation ID: 022076968370941373745893425674814846216842176653397412 Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339 Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341 Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340 Partial Product Key: 7HT7Y License Status: Licensed Remaining Windows rearm count: 4 Trusted time: 2/28/2013 5:59:00 PM Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0x00000000 HealthStatus: 0x0000000000000000 Event Time Stamp: 2:27:2013 18:31 ActiveX: Registered, Version: 7.1.7600.16395 Admin Service: Registered, Version: 7.1.7600.16395 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: NgAAAAEABQABAAEAAAACAAAAAgABAAEA6GHouzajOCt6f45saEF42uSWcsca7HJdTNXg2EbK OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x0 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC PTLTD APIC FACP INTEL CRESTLNE HPET INTEL CRESTLNE BOOT PTLTD $SBFTBL$ MCFG INTEL CRESTLNE SLIC DELL M09 OSFR DELL DELL SSDT PmRef CpuPm SSDT PmRef CpuPm SSDT PmRef CpuPm
The kicker of this is, it all came about rather accidentally and unexpectedly.
Let me just mention here, on Tuesday I spent 3 hours on the phone with Microsoft "Tech Support" as well as "MSDN Support" and "Activation Support" (typical MS...lol). I sent them the plethora of requested files, received my case #, and hung up. They had no clue and as yet I am still awaiting a reply.
Now I run ESET "Smart Security" on all my machines and I recently renewed my licenses for another 3 yrs. Just to note, this was well after all the problems started by at least 2 months. So, as my anti-virus was updating I noticed that it had a small "rc" (Release Candidate) after the version number displayed in the header. I thought to myself "Wow, I wonder if this version is full blown yet?", still not making any connection with the present situation. So I proceeded to update it and the update did typically what many updates do and performed an uninstall/re-install of the program. After about 3 freezes and re-attempts it finally installed successfully and lo and behold the first thing to pop up was MS updates and all functionality was returned.
At first, I couldn't believe it! It couldn't be that simple, could it? So I ran the MGADiags (see results above) as well as the "sfc /scannow" command and they both came up clean.
Problem Solved! WooHoo!
I sent an email to ESET and have yet to receive any response, but for my money, the proof is clearly in the pudding...lol
Thanks to one and all for your untiring efforts in helping to resolve this issue, I am grateful to you all.
God Bless!
So you have a Beta version of ESET installed? (rc usually means Release Candidate)
No wonder we couldn't find related data :)
Perhaps the new version introduced a block between the Software Protection Service and the registry, and it's that which raised the non-genuine flag.
Hopefully, this is now permanently resolved - good luck!