Yrag, Anyone....Assistance Needed With Windows Update.
it's now behaving at all well.
Tuesday, April 22, 2008 by starkers | Discussion: Personal Computing
Hadn't been into XP for a while on my Vista dual boot, so thought I'd go in and update everything, etc. All began well enough, Windows Upadates downloaded OK, but they just refuse to install no matter what I do. Even a repair install of XP (Pro SP2) did not resolve the issue.
Event Viewer shows these error reports:
Event ID: 1001... Fault Bucket 00733296.
Event ID: 1000... Fault Application drwtsn 32exe. version 5. 1.200.0 faulting module dgbhelp.dll version 2600.2180 fault address 0x0001295 d.
Event ID: 1001... Fault Bucket 01704331.
Event ID: 1000... Faulting Apllication Explorer.exe. version 60.2900.2180, faulting module user32 dll. version5.1 2600.2180, fault address 0x0000ee3c.
Also these warnings....
Event ID: 1015... Failed to connect to server. Error 0x8007043C.
Event ID: 1517... Windows saved user Home ***** registry while an application or sevice was using the registry during logoff. The memory used by the user's registry has not been freed. The memory will be unloaded when it is no longer in use.
These are the only error references I can find, so hope they help find & resolve the problem.
Thanks in advance, starkers. 
 |
|
Page 1 of 2 | |
|
|---|
wulfn1
Reply #2 Tuesday, April 22, 2008 8:32 AM
Reply #2 Tuesday, April 22, 2008 8:32 AM
I spent the week trying to install updates for .net and live writer , and it took me finally clicking on custom install and unclicking all but one and dling one at a time to get it to respond correctly
they're all installed now, but it took forever for some of them to dl and install,.
they're all installed now, but it took forever for some of them to dl and install,.
starkers
Reply #3 Friday, April 25, 2008 8:13 PM
I tried installing one at a time but still no go. The only way I've been able to get some updates to install is by going to MS home page and downloading/installing them manually via the exe files. However, it would be a very time consuming and tedious job to do that for all 112 updates required since the clean install of XP.
Hopefully, there is a better solution as all the updates are on my PC awaiting installation.
Reply #3 Friday, April 25, 2008 8:13 PM
I am no Yrag, but have you tried to untick some of the updates and download/install them in "tranches"?
I tried installing one at a time but still no go. The only way I've been able to get some updates to install is by going to MS home page and downloading/installing them manually via the exe files. However, it would be a very time consuming and tedious job to do that for all 112 updates required since the clean install of XP.
Hopefully, there is a better solution as all the updates are on my PC awaiting installation.
starkers
Reply #4 Friday, April 25, 2008 8:19 PM
Thanks for the advice, Wulfin1.... unfortunately no updates via Automatic Update will install... all fail no matter how I do it.
I'm sure there's a reason (I can't fathom) and an answer to this dilemma (I can't find), so hopefully yrag or someone more knowledgeable than I will have an explanation and a resolution.
Reply #4 Friday, April 25, 2008 8:19 PM
they're all installed now, but it took forever for some of them to dl and install,.
Thanks for the advice, Wulfin1.... unfortunately no updates via Automatic Update will install... all fail no matter how I do it.
I'm sure there's a reason (I can't fathom) and an answer to this dilemma (I can't find), so hopefully yrag or someone more knowledgeable than I will have an explanation and a resolution.
MasonM
Reply #6 Saturday, April 26, 2008 12:44 AM
Reply #6 Saturday, April 26, 2008 12:44 AM
Try holding your tongue to the left instead of to the right.
CommanderGizmo
Reply #7 Saturday, April 26, 2008 12:52 AM
Reply #7 Saturday, April 26, 2008 12:52 AM
Just out of curiosity, is your time set correctly with any applicable daylight savings updates installed? We shouldn't overlook the obvious, now should we?
CommanderGizmo
Reply #9 Saturday, April 26, 2008 1:03 AM
Reply #9 Saturday, April 26, 2008 1:03 AM
Just by way of mentioning: Windows Update issues are always free support issues with MS. They don't charge for them.
SIR NASTY OF TANG
Reply #10 Saturday, April 26, 2008 1:34 AM
yes check time and date and and run a full antivirus scan too.
Nasty
Reply #10 Saturday, April 26, 2008 1:34 AM
Just out of curiosity, is your time set correctly with any applicable daylight savings updates installed? We shouldn't overlook the obvious, now should we?
yes check time and date and and run a full antivirus scan too.
Nasty
SIR NASTY OF TANG
Reply #11 Saturday, April 26, 2008 1:38 AM
Reply #11 Saturday, April 26, 2008 1:38 AM
I just installed XP (on new gaming PC) today and updated 90+ hot fix from windows update but i alwas chose custom too.
Nasty
Nasty
starkers
Reply #12 Saturday, April 26, 2008 1:51 AM
Reply #12 Saturday, April 26, 2008 1:51 AM
yarg...tried one update but it failed to install again, the error report is as follows:
* Updates to install = 1
2008-04-26 15:30:07:765 1368 a04 Agent * Title = Root Certificates Update
2008-04-26 15:30:07:765 1368 a04 Agent * UpdateId = {D24FE7DE-266B-4260-BBF2-59824AF246CF}.101
2008-04-26 15:30:07:765 1368 a04 Agent * Bundles 1 updates:
2008-04-26 15:30:07:765 1368 a04 Agent * {C1292657-6E08-4BD7-A3E6-8725BB43B40C}.101
2008-04-26 15:30:12:000 1368 a04 Handler Attempting to create remote handler process as HOME-D923F24026\starkers in session 0
2008-04-26 15:30:12:171 3804 628 Misc =========== Logging initialized (build: 7.0.6000.381, tz: +1000) ===========
2008-04-26 15:30:12:171 3804 628 Misc = Process: C:\WINDOWS\system32\wuauclt.exe
2008-04-26 15:30:12:171 3804 628 AUClnt FATAL: Error: 0x80004002. wuauclt handler: failed to spawn COM server
2008-04-26 15:30:12:187 1368 a04 Handler FATAL: 0x80004002: ERROR: Remote update handler container process created (PID: 3804), but exited before signaling event
2008-04-26 15:30:12:187 1368 a04 Agent * WARNING: Exit code = 0x80004002
2008-04-26 15:30:12:187 1368 a04 Agent *********
2008-04-26 15:30:12:187 1368 a04 Agent ** END ** Agent: Installing updates [CallerId = MicrosoftUpdate]
2008-04-26 15:30:12:187 1368 a04 Agent *************
2008-04-26 15:30:12:187 1368 a04 Agent WARNING: WU client failed installing updates with error 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI - Install call failed
2008-04-26 15:30:12:187 2812 e5c COMAPI - Reboot required = No
2008-04-26 15:30:12:187 2812 e5c COMAPI - WARNING: Exit code = 0x80240FFF; Call error code = 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI ---------
2008-04-26 15:30:12:187 2812 e5c COMAPI -- END -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI -------------
2008-04-26 15:30:12:250 1368 460 Report REPORT EVENT: {5F68AF90-0CD7-424E-BF68-229CA10803F6} 2008-04-26 15:30:07:250+1000 1 162 101 {D24FE7DE-266B-4260-BBF2-59824AF246CF} 101 0 MicrosoftUpdate Success Content Download Download succeeded.
2008-04-26 15:30:12:937 2812 ecc COMAPI WARNING: Operation failed due to earlier error, hr=80004002
Hope that helps find a fix... cos it's all Greek to me.
* Updates to install = 1
2008-04-26 15:30:07:765 1368 a04 Agent * Title = Root Certificates Update
2008-04-26 15:30:07:765 1368 a04 Agent * UpdateId = {D24FE7DE-266B-4260-BBF2-59824AF246CF}.101
2008-04-26 15:30:07:765 1368 a04 Agent * Bundles 1 updates:
2008-04-26 15:30:07:765 1368 a04 Agent * {C1292657-6E08-4BD7-A3E6-8725BB43B40C}.101
2008-04-26 15:30:12:000 1368 a04 Handler Attempting to create remote handler process as HOME-D923F24026\starkers in session 0
2008-04-26 15:30:12:171 3804 628 Misc =========== Logging initialized (build: 7.0.6000.381, tz: +1000) ===========
2008-04-26 15:30:12:171 3804 628 Misc = Process: C:\WINDOWS\system32\wuauclt.exe
2008-04-26 15:30:12:171 3804 628 AUClnt FATAL: Error: 0x80004002. wuauclt handler: failed to spawn COM server
2008-04-26 15:30:12:187 1368 a04 Handler FATAL: 0x80004002: ERROR: Remote update handler container process created (PID: 3804), but exited before signaling event
2008-04-26 15:30:12:187 1368 a04 Agent * WARNING: Exit code = 0x80004002
2008-04-26 15:30:12:187 1368 a04 Agent *********
2008-04-26 15:30:12:187 1368 a04 Agent ** END ** Agent: Installing updates [CallerId = MicrosoftUpdate]
2008-04-26 15:30:12:187 1368 a04 Agent *************
2008-04-26 15:30:12:187 1368 a04 Agent WARNING: WU client failed installing updates with error 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI - Install call failed
2008-04-26 15:30:12:187 2812 e5c COMAPI - Reboot required = No
2008-04-26 15:30:12:187 2812 e5c COMAPI - WARNING: Exit code = 0x80240FFF; Call error code = 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI ---------
2008-04-26 15:30:12:187 2812 e5c COMAPI -- END -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI -------------
2008-04-26 15:30:12:250 1368 460 Report REPORT EVENT: {5F68AF90-0CD7-424E-BF68-229CA10803F6} 2008-04-26 15:30:07:250+1000 1 162 101 {D24FE7DE-266B-4260-BBF2-59824AF246CF} 101 0 MicrosoftUpdate Success Content Download Download succeeded.
2008-04-26 15:30:12:937 2812 ecc COMAPI WARNING: Operation failed due to earlier error, hr=80004002
Hope that helps find a fix... cos it's all Greek to me.
starkers
Reply #13 Saturday, April 26, 2008 1:55 AM
Reply #13 Saturday, April 26, 2008 1:55 AM
Also, farther up the page, where earlier auto updates failed to install, there's an error message/explanation: "update was culled out due to potential supersedence."
CommanderGizmo
Reply #14 Saturday, April 26, 2008 2:06 AM
Reply #14 Saturday, April 26, 2008 2:06 AM
May I humbly suggest that you perform a clean install of XP. Repair installs do not correct all problems, and can in fact cause them. I suggest this since it is honestly the fastest and simplest method of resolving your problem.
The problem very likely lies with some dll's and registry keys missing from your system or improperly created/registered. This likely was not fixed with the repair install since it overwrote only parts of the system.
That being said, if you still wish to attempt a repair otherwise, you should look into wether the appropriate services are running to enalbe windows update to perform the required tasks. Most often this can be an issue with the BITS service. You will have to force install the proper files/dll's and then register them with the system manually. This process will likely take more time than simply performing a clean install.
In my biz, time is money and the fastest solution that fully resolves the problem is often the best one.
The problem very likely lies with some dll's and registry keys missing from your system or improperly created/registered. This likely was not fixed with the repair install since it overwrote only parts of the system.
That being said, if you still wish to attempt a repair otherwise, you should look into wether the appropriate services are running to enalbe windows update to perform the required tasks. Most often this can be an issue with the BITS service. You will have to force install the proper files/dll's and then register them with the system manually. This process will likely take more time than simply performing a clean install.
In my biz, time is money and the fastest solution that fully resolves the problem is often the best one.
yrag
Reply #15 Saturday, April 26, 2008 2:31 AM
Reply #15 Saturday, April 26, 2008 2:31 AM
Open Registry and scroll to:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SensLogn]
Make sure all these keys show:
"DLLName"="WlNotify.dll"
"Lock"="SensLockEvent"
"Logon"="SensLogonEvent"
"Logoff"="SensLogoffEvent"
"Safe"=dword:00000001
"MaxWait"=dword:00000258
"StartScreenSaver"="SensStartScreenSaverEvent"
"StopScreenSaver"="SensStopScreenSaverEvent"
"Startup"="SensStartupEvent"
"Shutdown"="SensShutdownEvent"
"StartShell"="SensStartShellEvent"
"PostShell"="SensPostShellEvent"
"Disconnect"="SensDisconnectEvent"
"Reconnect"="SensReconnectEvent"
"Unlock"="SensUnlockEvent"
"Impersonate"=dword:00000001
"Asynchronous"=dword:00000001
If you change anything, export the key before changes. If anything goes wrong, just merge the saved key back. If you make any additions/changes, re-boot.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SensLogn]
Make sure all these keys show:
"DLLName"="WlNotify.dll"
"Lock"="SensLockEvent"
"Logon"="SensLogonEvent"
"Logoff"="SensLogoffEvent"
"Safe"=dword:00000001
"MaxWait"=dword:00000258
"StartScreenSaver"="SensStartScreenSaverEvent"
"StopScreenSaver"="SensStopScreenSaverEvent"
"Startup"="SensStartupEvent"
"Shutdown"="SensShutdownEvent"
"StartShell"="SensStartShellEvent"
"PostShell"="SensPostShellEvent"
"Disconnect"="SensDisconnectEvent"
"Reconnect"="SensReconnectEvent"
"Unlock"="SensUnlockEvent"
"Impersonate"=dword:00000001
"Asynchronous"=dword:00000001
If you change anything, export the key before changes. If anything goes wrong, just merge the saved key back. If you make any additions/changes, re-boot.
starkers
Reply #16 Saturday, April 26, 2008 5:56 AM
Reply #16 Saturday, April 26, 2008 5:56 AM
yrag... all the registry items are there but 4 are different:
"Asynchronous"=dword:0x0000001(1)
"Impersonate"=dword:0x0000001(1)
"Safe"=dword:0x0000001(1)
"MaxWait"=dword:00000258(600)
I did export them just in case, but the editor will not allow me to change the values to those you posted... can type them in OK but nothing happens when tying to apply.
Damned blasted puters....
You may humbly suggest if you like... cos if things don't improve real soon, I'll be doing just that, though not so humbly. Being it's not that long ago thatI did it, there's quite likely to be a few... er, a lot of curse words going on during the process.
"Asynchronous"=dword:0x0000001(1)
"Impersonate"=dword:0x0000001(1)
"Safe"=dword:0x0000001(1)
"MaxWait"=dword:00000258(600)
I did export them just in case, but the editor will not allow me to change the values to those you posted... can type them in OK but nothing happens when tying to apply.
Damned blasted puters....
May I humbly suggest that you perform a clean install of XP
You may humbly suggest if you like... cos if things don't improve real soon, I'll be doing just that, though not so humbly. Being it's not that long ago thatI did it, there's quite likely to be a few... er, a lot of curse words going on during the process.
Fuzzy Logic
Reply #17 Saturday, April 26, 2008 7:14 AM
Reply #17 Saturday, April 26, 2008 7:14 AM
Arrr, you scurvy sea dog, it be the rev'nue man, Sir William of Gates, seekin' 'is revenge, arrr
SIR NASTY OF TANG
Reply #18 Saturday, April 26, 2008 9:15 AM
Reply #18 Saturday, April 26, 2008 9:15 AM
At this point a clean install might be best as said already. you`ll do alot of work just to do it any ways
CommanderGizmo
Reply #19 Saturday, April 26, 2008 10:11 AM
Reply #19 Saturday, April 26, 2008 10:11 AM
If you would like to attempt a repair before you end up doing a clean install, you might find these links useful. Just a quick search for the info you seek:
WWW Link
WWW Link
WWW Link
That should get you going in the generally right direction, though seriously -- if this was a customer's machine I would just reinstall. Time is money.
WWW Link
WWW Link
WWW Link
That should get you going in the generally right direction, though seriously -- if this was a customer's machine I would just reinstall. Time is money.
yrag
Reply #20 Saturday, April 26, 2008 10:21 AM
Reply #20 Saturday, April 26, 2008 10:21 AM
You're either in a limited user account or it's a security app or both. List the apps installed.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 1 of 2 | |
|
|---|
Reply #1 Tuesday, April 22, 2008 5:36 AM