Answered by:
WGA notifications stuck at "running processes after install"

Question
-
Hello, I've got an fresh install of OEM windows xp SP3 that can't get past the "finishing installation" "running processes after install" screen for windows genuine advantage notifications.
I've tried turning off MSE and confirming network connectivity, no luck.
any suggestions?
Friday, December 13, 2013 9:30 PM
Answers
-
So I also noticed that .net framework 1.1 sp1 was not installing properly, so I uninstalled 1.1, then reinstalled, and then successfully installed SP1
after that the WGA notification installation finished on it's own
hopefully this helps someone!
- Proposed as answer by Noel D PatonModerator Thursday, December 19, 2013 4:44 PM
- Marked as answer by csawatsky Thursday, December 19, 2013 4:57 PM
Monday, December 16, 2013 5:13 PM
All replies
-
Odd - perhaps it's a permissions issue.
Try this...
Open Windows Explorer (My Computer)
Navigate to the C:\ folder
Find the Windows sub-folder and right-click on it
select Properties
Clear the 'blob' from the 'Read-only (Only applies to files in folder)' box by clicking on it until it's plain white.
Click on Apply.
Make sure that the radio button for 'Apply changes to this folder, subfolders and files' is set, and click OK.
Accept the Administrator prompt. After a couple of seconds, you'll be told there is an error - click on the 'Ignore all' button.
Wait for it to finish - it could take a couple of minutes.
(the 'blob' will return - this is normal!)
OK out, and exit Windows Explorer.
Reboot twice
Then post an MGADiag report.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. Saturday, December 14, 2013 11:35 AMModerator -
ok done, still no luck
here is the mgadiag info
Diagnostic Report (1.9.0019.0):
-----------------------------------------
WGA Data-->
Validation Status: Genuine
Validation Code: 0Cached Validation Code: N/A
Windows Product Key: *****-*****-3QCQK-3G6CW-V9YKD
Windows Product Key Hash: WzRFWgoM5q6asgcNFqqn1ljUy6A=
Windows Product ID: 76487-OEM-2282052-04405
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 5.1.2600.2.00010100.3.0.pro
ID: {F3796A39-5421-4C43-961C-411518BE6805}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-230-1
Resolution Status: N/AWgaER Data-->
ThreatID(s): N/A
Version: N/AWGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->
Office Status: 109 N/A
OGA Version: Registered, 2.0.48.0
Signed By: Microsoft
Office Diagnostics: 025D1FF3-230-1Browser 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: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{F3796A39-5421-4C43-961C-411518BE6805}</UGUID><Version>1.9.0019.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-V9YKD</PKey><PID>76487-OEM-2282052-04405</PID><PIDType>3</PIDType><SID>S-1-5-21-1417001333-842925246-1801674531</SID><SYSTEM><Manufacturer>Acer</Manufacturer><Model>Aspire 5040</Model></SYSTEM><BIOS><Manufacturer>Phoenix </Manufacturer><Version>V1.05 </Version><SMBIOSVersion major="2" minor="3"/><Date>20060421000000.000000+000</Date><SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS><HWID>D86C3707018400EA</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/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Licensing Data-->
N/AWindows Activation Technologies-->
N/AHWID Data-->
N/AOEM Activation 1.0 Data-->
BIOS string matches: yes
Marker string from BIOS: 16BF0:Acer Incorporated
Marker string from OEMBIOS.DAT: Dell System,Dell Computer,Dell System,Dell SystemOEM Activation 2.0 Data-->
N/AMonday, December 16, 2013 3:20 PM -
So I also noticed that .net framework 1.1 sp1 was not installing properly, so I uninstalled 1.1, then reinstalled, and then successfully installed SP1
after that the WGA notification installation finished on it's own
hopefully this helps someone!
- Proposed as answer by Noel D PatonModerator Thursday, December 19, 2013 4:44 PM
- Marked as answer by csawatsky Thursday, December 19, 2013 4:57 PM
Monday, December 16, 2013 5:13 PM -
You're using an out-of-date copy of the MGADiag tool - please download the later version from here....
http://go.microsoft.com/fwlink/?linkid=52012
and run it - post the results from that, and we'll see what we can see.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. Monday, December 16, 2013 10:45 PMModerator -
Looking deeper at the existing data, it's obvious that there is some kind of hack installed in an attempt to circumvent Activation and Validation.
You really need to reformat and reinstall using genuine media and Key.
Unless the data from the updated MGADiag tool is significantly different, that will remain the conclusion.
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. Monday, December 16, 2013 11:13 PMModerator -
as mentioned above, my problem is resolved, but two things...
1) why does the so-called out-of-date copy of the mGADiag tool come up at the top of a google search, downloadable from microsoft?
2) if there was a hack installed, someone did it quickly when I wasn't looking. Full disclosure, the machine is an acer with a win xp oem sticker on it. I did not have an acer OS disk. I have a dell OS disk of the same version, I installed winxp, entered the acer key from the sticker, and activated it online. I was having some trouble with windows update (svchost pegging at 99% CPU) so googling indicated that a person could use a third party windows update tool to "catch up" on 5 years of updates, after which the build-in automatic updater would work fine.
Coles notes: The time I'd blow trying to get an activation hack to work is worth WAY more than a legit OS license, I'm only burning the midnight oil on this old beater laptop as a favor for my favorite uncle :)
Tuesday, December 17, 2013 3:25 AM -
1) Blame Google - MS doesn't control their rankings. What search term did you use? I get the proper version just searching on 'mgadiag'. I thought I'd got MS to expunge all the bad links that used to exist, but maybe Google is finding direct download links again.
2) That would explain the fact that the OS has a Dell OEMBIOS.DAT, but an Acer BIOS :) - it was that which rang alarm bells for me.
Interesting the .NET was somehow involved - since the WGA system in XP doesn't touch .NET so far as I know. It may simply have been blocking some functionality somehow. Thanks for the data - it may help someone else.
Good luck!
Noel Paton | Nil Carborundum Illegitemi CrashFixPC | The Three-toed Sloth No - I do not work for Microsoft, or any of its contractors. Tuesday, December 17, 2013 8:15 AMModerator