Download succesfully, Fail Installation, Succeed on "Shutdown Inst

I have had this problem twice on two different computers in the last week:

-- Customer comes in with spyware/virus problems
-- clean computer using virus program, spybot, adaware, hijack this until no
more traces come up
-- both computers had watools and ibis toolbar removed (May be irrelevant)
-- When I go to update computer using windows updates website, updates show
up, I download them, they fail to install.
-- I used manual updates to get computer ready for SP2.
-- Install SP2.
-- Updates for SP2 download, fail to install
-- Now however, updates install option shows up when I go to shut down the
computer. I use this option and updates install successfully.

I tried reinstalling windows updates by deleting: directories in
Windows/SoftwareDistribution, ProgramFiles/WindowsUpdates, WUTemp, temporary
IE files

Here is the relevant parts of the log (to the best of my knowledge)
containing the last windows update failure to install (after succesfull
download) and then success when installing with the shutdown option.

......
2005-06-08 17:24:22-0400 1100 460 WU client calls back to download call
{EDDE97E2-C24A-4F52-A7E6-51F2FD358F36} with code Call progress and error 0
2005-06-08 17:24:39-0400 1100 b00 Download job for update
{B63A8B34-6E30-491A-B2C0-8A83093E45CA}, revision 101 completed successfully.
2005-06-08 17:24:39-0400 1100 b00 Successfully downloaded file from
http://www.download.windowsupdate.co...4102d4a95c.psf
to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\8872348e610454dc87bf93345cf855d1\download\Windo wsXP-KB885250-x86-ENU.psf.blob.
2005-06-08 17:24:40-0400 1100 a18 WU client calls back to download call
{EDDE97E2-C24A-4F52-A7E6-51F2FD358F36} with code Call progress and error 0
2005-06-08 17:24:40-0400 1100 a18 WU client calls back to download call
{9DDD2DBA-27F7-4694-975B-12213CC52838} with code Call progress and error 0
2005-06-08 17:24:41-0400 1100 b00 WU client persisted 2 download calls
2005-06-08 17:24:41-0400 1100 b00 WU client persisted 2 download calls
2005-06-08 17:24:41-0400 1100 b00 WU client persisted 2 download calls
2005-06-08 17:24:42-0400 1100 b00 WU client persisted 2 download calls
2005-06-08 17:24:42-0400 1100 b00 WU client persisted 2 download calls
2005-06-08 17:24:42-0400 1100 a18 Download complete for all calls
2005-06-08 17:24:42-0400 1100 a18 Setting AU scheduled install time to
2005-06-09 07:00:00
2005-06-08 17:24:42-0400 1100 a18 WU client calls back to download call
{EDDE97E2-C24A-4F52-A7E6-51F2FD358F36} with code Call complete and error 0
2005-06-08 17:24:42-0400 1100 a18 WU client completed and deleted call
{EDDE97E2-C24A-4F52-A7E6-51F2FD358F36}
2005-06-08 17:24:42-0400 1100 a18 WU client persisted 1 download calls
2005-06-08 17:24:42-0400 1100 a18 WU client calls back to download call
{9DDD2DBA-27F7-4694-975B-12213CC52838} with code Call complete and error 0
2005-06-08 17:24:42-0400 1100 a18 WU client completed and deleted call
{9DDD2DBA-27F7-4694-975B-12213CC52838}
2005-06-08 17:24:42-0400 1100 a18 WU client persisted 0 download calls
2005-06-08 17:24:42-0400 1100 128 ISusInternal API failed
CClientCallRecorder:isconnectCall with error 0x8024000c
2005-06-08 17:24:42-0400 1992 130 ISusInternal:isconnectCall failed,
hr=8024000C
2005-06-08 17:24:42-0400 1100 128 WU client succeeds
CClientCallRecorder::BeginInstallUpdates from WindowsUpdate with call id
{9C47CA6D-D34A-4676-BDCA-0BE6C4EEAA0F}
2005-06-08 17:24:42-0400 1100 a18 WU client executing call
{9C47CA6D-D34A-4676-BDCA-0BE6C4EEAA0F} of type Install call
2005-06-08 17:24:42-0400 1100 a18 validate updates before Install
2005-06-08 17:24:44-0400 1100 a18 prune update list before Install
2005-06-08 17:24:44-0400 1100 a18 GetUserTokenFromSessionId failed with hr
0x800704dd
2005-06-08 17:24:44-0400 1100 a18 WU client failed installing updates with
error 0x80240020
2005-06-08 17:24:44-0400 1100 a18 WU client calls back to install call
{9C47CA6D-D34A-4676-BDCA-0BE6C4EEAA0F} with code Call failed and error
0x80240020
2005-06-08 17:24:44-0400 1100 a18 WU client completed and deleted call
{9C47CA6D-D34A-4676-BDCA-0BE6C4EEAA0F}
2005-06-08 17:24:45-0400 1992 130 Operation completed due to earlier error.
(hr=80240020)
2005-06-08 17:24:45-0400 1100 df8 ISusInternal API failed
CClientCallRecorder:isconnectCall with error 0x8024000c
2005-06-08 17:24:45-0400 1992 130 ISusInternal:isconnectCall failed,
hr=8024000C
2005-06-08 17:24:47-0400 1100 a18 REPORT EVENT:
{367D3328-CA7A-4C54-89E4-67233465FAC4} 180 2005-06-08
17:24:42-0400 1 162 101 {BB642BE1-0DEA-4782-8C40-BFDBAA3DA376} 101 0 AutomaticUpdates Success Content Download Download succeeded.
2005-06-08 17:24:47-0400 1100 a18 REPORT EVENT:
{5AECD14C-4B4D-4A16-87F8-479F40DAFF59} 181 2005-06-08
17:24:42-0400 1 162 101 {B63A8B34-6E30-491A-B2C0-8A83093E45CA} 101 0 AutomaticUpdates Success Content Download Download succeeded.
2005-06-08 17:24:47-0400 1100 a18 REPORT EVENT:
{73D43684-5037-4738-8817-E5135ED0C937} 182 2005-06-08
17:24:42-0400 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, June 09, 2005 at 3:00 AM: - Security Update for Windows
XP (KB890859) - Windows Malicious Software Removal Tool - May 2005 (KB890830)
- Critical Update for Office XP on Windows XP Service Pack 2 (KB885884) -
Cumulative Security Update for Internet Explorer for Windows XP Service Pack
2 (KB890923) - Critical Update for Windows XP (KB886185) - Security Update
for Windows Messenger (KB887472) - Update for Windows XP (KB887742) -
Security Update for Windows XP (KB885250)
2005-06-08 17:24:57-0400 3000 d1c 8 updates are ready to be installed at
shutdown.
2005-06-08 17:25:03-0400 1100 450 Service received logoff notification
2005-06-08 17:25:03-0400 1100 4dc AU received event of 3
2005-06-08 17:25:10-0400 1100 128 WU client succeeds
CClientCallRecorder::BeginInstallUpdates from AutomaticUpdates with call id
{D4B0A773-6A6E-49D6-A486-7E37A7AEFFB8}
2005-06-08 17:25:10-0400 1100 128 Successfully initiated install for 8 updates
2005-06-08 17:25:10-0400 696 e08 AU will install 8 updates.
2005-06-08 17:25:10-0400 1100 738 WU client executing call
{D4B0A773-6A6E-49D6-A486-7E37A7AEFFB8} of type Install call
2005-06-08 17:25:10-0400 1100 738 validate updates before Install
2005-06-08 17:25:11-0400 1100 738 prune update list before Install
2005-06-08 17:25:11-0400 1100 738 setting system restore point
2005-06-08 17:25:11-0400 1100 738 SRSetRestorePoint failed with
ERROR_SERVICE_DISABLED (expected behavior on client SKUs with SR turned off)
2005-06-08 17:25:11-0400 1100 738 WU client starts install in local system
context
2005-06-08 17:25:11-0400 1100 738 WU client is installing update
{B1FF52C3-7D37-46A9-B813-8BBDDC74A3D5}.100
2005-06-08 17:25:31-0400 1100 738 WU client finishes installing update
{B1FF52C3-7D37-46A9-B813-8BBDDC74A3D5}.100 with result 0
2005-06-08 17:25:31-0400 1100 738 REPORT EVENT:
{911540D0-FA4F-40CD-A2ED-A1D0AFEE4888} 183 2005-06-08
17:25:31-0400 1 199 101 {FAA4E626-ED18-4ACA-B2B3-D9711543C05F} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB890859)
.....

Thanks for your help

I know this is an old message, but I believe I've found the solution and am
trying to spread the word.
If you are still having this problem, can you check the following key in
your registry - and see if it exists?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\SensLogn

My guess is that it doesn't. Let me know, and we'll follow up from there.

To: "davidrrm"

After visiting most of the sites about windows update I,ve been trying all
kinds of fix to this same problem with no success. Reading through your post
with some new idea I decide to check my machine's registry, went all the way
up to ...\notify\ but that "\Senslogn" is not there. Will you help me?
My OS is Windows XP Media Center 2002 sp2.

Follows transcription of my last log:

2005-07-29 22:58:41 1136 484 Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800704dd
2005-07-29 22:58:41 1136 484 Agent * WARNING: Exit code = 0x80240020
2005-07-29 22:58:41 1136 484 Agent *********
2005-07-29 22:58:41 1136 484 Agent ** END ** Agent: Installing updates
[CallerId = MicrosoftUpdate]
2005-07-29 22:58:41 1136 484 Agent *************
2005-07-29 22:58:41 1136 484 Agent WARNING: WU client failed installing
updates with error 0x80240020
2005-07-29 22:58:41 3356 d5c COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = MicrosoftUpdate]
2005-07-29 22:58:41 3356 d5c COMAPI - Install call failed
2005-07-29 22:58:41 3356 d5c COMAPI - Reboot required = No
2005-07-29 22:58:41 3356 d5c COMAPI - WARNING: Exit code = 0x80240FFF;
Call error code = 0x80240020
2005-07-29 22:58:41 3356 d5c COMAPI ---------
2005-07-29 22:58:41 3356 d5c COMAPI -- END -- COMAPI: Install [ClientId =
MicrosoftUpdate]
2005-07-29 22:58:41 3356 d5c COMAPI -------------
2005-07-29 22:58:42 3356 d20 COMAPI WARNING: Operation failed due to earlier
error, hr=80240020


Bellows show log for the 1st time I got the code 0x800704dd reported:

2005-06-06 21:08:40-0400 1156 1a4 Successfully refreshed Redirector cab.
2005-06-06 21:08:41-0400 1156 70c AU received event of 1
2005-06-06 21:08:41-0400 1156 70c GetUserTokenFromSessionId failed with hr
0x800704dd



First time a "warning" shows up on the log:

2005-06-23 18:33:45 1156 f98 Setup Agent skipping selfupdate check following
a successful selfupdate
2005-06-23 18:33:56 1156 1b8 Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800704dd
2005-06-23 18:33:56 1156 1b8 AU WARNING: AU found no suitable session to
launch client in
2005-06-23 18:34:36 1156 f98 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-06-23 18:34:36 1156 f98 PT + ServiceId =
{9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2005-06-23 18:37:08 1156 f98 PT WARNING: SyncUpdates failure, error =
0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
200
2005-06-23 18:37:08 1156 f98 PT WARNING: SOAP Fault: 0x00012c
2005-06-23 18:37:08 1156 f98 PT WARNING: faultstring:Fault occurred
2005-06-23 18:37:08 1156 f98 PT WARNING: ErrorCode:InvalidCookie(1)
2005-06-23 18:37:08 1156 f98 PT WARNING: Message:

2005-06-23 18:37:08 1156 f98 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2005-06-23 18:37:08 1156 f98 PT WARNING:
ID:e883d451-6996-4af4-807a-18917e57f800
2005-06-23 18:37:08 1156 f98 PT WARNING: Sync of Updates: 0x80244015
2005-06-23 18:37:20 1156 f98 Agent * WARNING: Failed to synchronize, error
= 0x80244015


And the 1st time I got code 0x80240020:

2005-07-16 12:04:10 1124 744 Agent * Bundles 1 updates:
2005-07-16 12:04:10 1124 744 Agent *
{6CA7379C-4705-490E-805B-72CB213CA621}.102
2005-07-16 12:04:10 1124 744 Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800704dd
2005-07-16 12:04:10 1124 744 Agent * WARNING: Exit code = 0x80240020
2005-07-16 12:04:10 1124 744 Agent *********
2005-07-16 12:04:10 1124 744 Agent ** END ** Agent: Installing updates
[CallerId = WindowsUpdate]
2005-07-16 12:04:10 1124 744 Agent *************
2005-07-16 12:04:10 1124 744 Agent WARNING: WU client failed installing
updates with error 0x80240020
2005-07-16 12:04:10 1676 c34 COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = WindowsUpdate]
2005-07-16 12:04:10 1676 c34 COMAPI - Install call failed

Well as I said I read and try most of the suggestions about both codes, and
I hope you can have that final answer.

Thanks in advance,
SPACEJUMPER
__________________________________________________ ______________


"davidrrm" wrote:

> I know this is an old message, but I believe I've found the solution and am
> trying to spread the word.
> If you are still having this problem, can you check the following key in
> your registry - and see if it exists?
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon\Notify\SensLogn
>
> My guess is that it doesn't. Let me know, and we'll follow up from there.

Since you are running SP2 of XP, I think you should have this in your
registry, but I only have a sample of two machines. So, please, backup your
critical files before trying this. Also, make sure that you are virus and
spyware free.

Save the text below in senslogon.reg. Run RegEdt32 and select File/import...
and select senslogon.reg. Reboot your machine, and hopefully it will all work
nicely. WARNING - Changing the registry can always cause trouble, so do this
at your own risk.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\SensLogn]
"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

Hi,

I came across your suggestion. I have XP SP2 and noticed that I don't have
the senslogin key in my registry. I guess you're suggesting that I import
this key into my registry and reboot.

After that I should be able to perform a Windows Update and have the
downloaded files installed successfully?

Please confirm. Thanks.

"davidrrm" wrote:

>
> Since you are running SP2 of XP, I think you should have this in your
> registry, but I only have a sample of two machines. So, please, backup your
> critical files before trying this. Also, make sure that you are virus and
> spyware free.
>
> Save the text below in senslogon.reg. Run RegEdt32 and select File/import...
> and select senslogon.reg. Reboot your machine, and hopefully it will all work
> nicely. WARNING - Changing the registry can always cause trouble, so do this
> at your own risk.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon\Notify\SensLogn]
> "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
>
>
>
>

That's what I've found to work on one machine that failed in this way. Your
mileage may vary. :-)

"SCLNY" wrote:

> Hi,
>
> I came across your suggestion. I have XP SP2 and noticed that I don't have
> the senslogin key in my registry. I guess you're suggesting that I import
> this key into my registry and reboot.
>
> After that I should be able to perform a Windows Update and have the
> downloaded files installed successfully?
>
> Please confirm. Thanks.
>
> "davidrrm" wrote:
>
> >
> > Since you are running SP2 of XP, I think you should have this in your
> > registry, but I only have a sample of two machines. So, please, backup your
> > critical files before trying this. Also, make sure that you are virus and
> > spyware free.
> >
> > Save the text below in senslogon.reg. Run RegEdt32 and select File/import...
> > and select senslogon.reg. Reboot your machine, and hopefully it will all work
> > nicely. WARNING - Changing the registry can always cause trouble, so do this
> > at your own risk.
> >
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> > NT\CurrentVersion\Winlogon\Notify\SensLogn]
> > "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
> >
> >
> >
> >

Adding this key to the registry FIXED this problem. Thanks all!

"davidrrm" wrote:

>
> That's what I've found to work on one machine that failed in this way. Your
> mileage may vary. :-)
>
> "SCLNY" wrote:
>
> > Hi,
> >
> > I came across your suggestion. I have XP SP2 and noticed that I don't have
> > the senslogin key in my registry. I guess you're suggesting that I import
> > this key into my registry and reboot.
> >
> > After that I should be able to perform a Windows Update and have the
> > downloaded files installed successfully?
> >
> > Please confirm. Thanks.
> >
> > "davidrrm" wrote:
> >
> > >
> > > Since you are running SP2 of XP, I think you should have this in your
> > > registry, but I only have a sample of two machines. So, please, backup your
> > > critical files before trying this. Also, make sure that you are virus and
> > > spyware free.
> > >
> > > Save the text below in senslogon.reg. Run RegEdt32 and select File/import...
> > > and select senslogon.reg. Reboot your machine, and hopefully it will all work
> > > nicely. WARNING - Changing the registry can always cause trouble, so do this
> > > at your own risk.
> > >
> > > Windows Registry Editor Version 5.00
> > >
> > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> > > NT\CurrentVersion\Winlogon\Notify\SensLogn]
> > > "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
> > >
> > >
> > >
> > >

I had the same problem since 2003 and finally your SenLogn key worked.
One thing I would like to know though. I've always had to manually get every
update and install it locally. Since it downloaded of them all fine before
and failed to install them, it would seem that ther are tons of temporary
files somewhere collected on my drive that were never used to install as i
would still try windows upadte first to see if it would start working again.
where are all these downloaded files that were never used and can they be
cleaned off the hard drive?

Thanks again "davidrmm".

"davidrrm" wrote:

>
> Since you are running SP2 of XP, I think you should have this in your
> registry, but I only have a sample of two machines. So, please, backup your
> critical files before trying this. Also, make sure that you are virus and
> spyware free.
>
> Save the text below in senslogon.reg. Run RegEdt32 and select File/import...
> and select senslogon.reg. Reboot your machine, and hopefully it will all work
> nicely. WARNING - Changing the registry can always cause trouble, so do this
> at your own risk.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon\Notify\SensLogn]
> "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
>
>
>
>