Updates are downloaded but fail to install

When I try to download and install updates with Windows Update (or Microsoft
Update) all updates are downloaded but fail to install.

The following error is shown:

"Failed Updates

Problem: A problem on your computer is preventing updates from being
downloaded or installed"

This happens when I try to install any or all updates available.

The WindowsUpdate.log file shows:

"[CallerId = WindowsUpdate]
2005-12-15 16:57:28 1036 70c Agent *********
2005-12-15 16:57:28 1036 70c Agent * Updates to install = 1
2005-12-15 16:57:28 1036 70c Agent * Title = <NULL>
2005-12-15 16:57:28 1036 70c Agent * UpdateId =
{C88C7BCC-2E77-4D95-A27F-1E04330B4BD7}.100
2005-12-15 16:57:29 1036 70c Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800704dd
2005-12-15 16:57:29 1036 70c Agent * WARNING: Exit code = 0x80240020
2005-12-15 16:57:29 1036 70c Agent *********
2005-12-15 16:57:29 1036 70c Agent ** END ** Agent: Installing updates
[CallerId = WindowsUpdate]
2005-12-15 16:57:29 1036 70c Agent *************
2005-12-15 16:57:29 1036 70c Agent WARNING: WU client failed installing
updates with error 0x80240020
2005-12-15 16:57:29 2712 594 COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = WindowsUpdate]
2005-12-15 16:57:29 2712 594 COMAPI - Install call failed
2005-12-15 16:57:29 2712 594 COMAPI - Reboot required = No
2005-12-15 16:57:29 2712 594 COMAPI - WARNING: Exit code = 0x80240FFF;
Call error code = 0x80240020
2005-12-15 16:57:29 2712 594 COMAPI ---------
2005-12-15 16:57:29 2712 594 COMAPI -- END -- COMAPI: Install [ClientId =
WindowsUpdate]
2005-12-15 16:57:29 2712 594 COMAPI -------------
2005-12-15 16:57:30 2712 aa0 COMAPI WARNING: Operation failed due to earlier
error, hr=80240020"

Any help would be appreciated.

Gordon

The 80240020 error is oftentimes caused by a missing SensLogn key in the
registry. Copy/paste the following, between the two sets of asterisks, into
Notepad and then Save as a file named SensLogn.reg
NOTE: the [HKEY_LOCAL_MACHINE\SOFTWARE\......\Notify\SensLogn] line in this
post will wrap to two lines...it needs to be on one line in Notepad. Also,
ensure that you have the blank line at the end.

Copy/paste the appropriate one for the operating system that you are using.

For WIN2K

********************
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\WinLogon\Notify\SensLogn]

"Asynchronous"=dword:00000001
"DLLName"="WlNotify.dll"
"Impersonate"=dword:00000001
"Lock"="SensLockEvent"
"Logoff"="SensLogoffEvent"
"Logon"="SensLogonEvent"
"MaxWait"=dword:00000258
"Safe"=dword:00000001
"Shutdown"="SensShutdownEvent"
"StartScreenSaver"="SensStartScreenSaverEvent"
"StartShell"="SensStartShellEvent"
"Startup"="SensStartupEvent"
"StopScreenSaver"="SensStopScreenSaverEvent"
"Unlock"="SensUnlockEvent"

********************

For WINXP

********************
REGEDIT4

[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

********************

Once you have created and saved the SensLogn.reg file, double-click on it,
then click on Yes when asked if you want to merge the information into the
registry.

I've had the same or similar problem as Gordon for months, and have tried
countless solutions suggested here and elsewhere. Unfortunately, manually
installing the latest critical updates did not improve matters either. I
also tried the registry update suggested by Patti. If it accomplished
anything, I'm not sure what. Here's the last portion of of my update log; if
anyone has any new ideas, I'd appreciate knowing about them.

2005-12-15 20:20:04 872 52c Report REPORT EVENT:
{5E2C2EE9-BF5B-44A4-BA8D-E2F0B6392F6D}
2005-12-15
20:19:59-0800 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
2005-12-15 20:20:09 2524 9e0 COMAPI -------------
2005-12-15 20:20:09 2524 9e0 COMAPI -- START -- COMAPI: Install [ClientId =
WindowsUpdate]
2005-12-15 20:20:09 2524 9e0 COMAPI ---------
2005-12-15 20:20:09 2524 9e0 COMAPI - Allow source prompts: Yes; Forced:
No; Force quiet: No
2005-12-15 20:20:09 2524 9e0 COMAPI - Updates in request: 1
2005-12-15 20:20:09 2524 9e0 COMAPI - ServiceID =
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2005-12-15 20:20:09 2524 9e0 COMAPI - Updates to install = 1
2005-12-15 20:20:09 2524 9e0 COMAPI <<-- SUBMITTED -- COMAPI: Install
[ClientId = WindowsUpdate]
2005-12-15 20:20:09 872 52c Agent *************
2005-12-15 20:20:09 872 52c Agent ** START ** Agent: Installing updates
[CallerId = WindowsUpdate]
2005-12-15 20:20:09 872 52c Agent *********
2005-12-15 20:20:09 872 52c Agent * Updates to install = 1
2005-12-15 20:20:09 872 52c Agent * Title = <NULL>
2005-12-15 20:20:09 872 52c Agent * UpdateId =
{2A3FF495-C150-442B-811A-D78782B76411}.100
2005-12-15 20:20:09 872 52c Agent * Bundles 1 updates:
2005-12-15 20:20:09 872 52c Agent *
{740E9157-2D8B-4AC7-8231-438A54283B2C}.100
2005-12-15 20:20:09 872 52c Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800704dd
2005-12-15 20:20:09 872 52c Agent * WARNING: Exit code = 0x80240020
2005-12-15 20:20:09 872 52c Agent *********
2005-12-15 20:20:09 872 52c Agent ** END ** Agent: Installing updates
[CallerId = WindowsUpdate]
2005-12-15 20:20:09 872 52c Agent *************

I've been busy the past few days so I didn't get a chance to check back to
this thread until now.

When you ran the registry edit that I provided, did you then immediately
try, unsuccessfully, to install needed updates from the Microsoft Update
site? If so, perhaps a restart is required after running the registry edit
in order to successfully install the updates.

In the past year, I have run into the same, "download, but not installing
Windows Updates problem" on a few computers that I have worked on....The
following fix sent to me by an MSTech is the first solution that has ever
worked. I hope it works for you like it did for me, as immediately after
applying the registry fix, even before rebooting, the Windows Update Icon
appeared in the tray for the first time in months:

From your description, I understand that, Windows Update could be
downloaded but could not be installed, if I have misunderstood you, please
feel free to let me know.

This issue most likely occurs when the following registry key or its sub key
is missing or corrupt.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify
At this time, let's refer to the following steps to restore this key.

1. Click Start, Run, type: notepad C:\fix.reg and press Enter. Choose Yes
when you are prompted.
2. Copy the following commands and then paste them into the opened Notepad
window.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\crypt32chain]
"Asynchronous"=dword:00000000
"Impersonate"=dword:00000000
"DllName"=hex(2):63,00,72,00,79,00,70,00,74,00,33, 00,32,00,2e,00,64,00,6c,00,\
6c,00,00,00
"Logoff"="ChainWlxLogoffEvent"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\cryptnet]
"Asynchronous"=dword:00000000
"Impersonate"=dword:00000000
"DllName"=hex(2):63,00,72,00,79,00,70,00,74,00,6e, 00,65,00,74,00,2e,00,64,00,\
6c,00,6c,00,00,00
"Logoff"="CryptnetWlxLogoffEvent"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\cscdll]
"DLLName"="cscdll.dll"
"Logon"="WinlogonLogonEvent"
"Logoff"="WinlogonLogoffEvent"
"ScreenSaver"="WinlogonScreenSaverEvent"
"Startup"="WinlogonStartupEvent"
"Shutdown"="WinlogonShutdownEvent"
"StartShell"="WinlogonStartShellEvent"
"Impersonate"=dword:00000000
"Asynchronous"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\igfxcui]
@=""
"DLLName"="igfxsrvc.dll"
"Asynchronous"=dword:00000001
"Impersonate"=dword:00000001
"Unlock"="WinlogonUnlockEvent"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\ScCertProp]
"DLLName"="wlnotify.dll"
"Logon"="SCardStartCertProp"
"Logoff"="SCardStopCertProp"
"Lock"="SCardSuspendCertProp"
"Unlock"="SCardResumeCertProp"
"Enabled"=dword:00000001
"Impersonate"=dword:00000001
"Asynchronous"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\Schedule]
"Asynchronous"=dword:00000000
"DllName"=hex(2):77,00,6c,00,6e,00,6f,00,74,00,69, 00,66,00,79,00,2e,00,64,00,\
6c,00,6c,00,00,00
"Impersonate"=dword:00000000
"StartShell"="SchedStartShell"
"Logoff"="SchedEventLogOff"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\sclgntfy]
"Logoff"="WLEventLogoff"
"Impersonate"=dword:00000000
"Asynchronous"=dword:00000001
"DllName"=hex(2):73,00,63,00,6c,00,67,00,6e,00,74, 00,66,00,79,00,2e,00,64,00,\
6c,00,6c,00,00,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
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\SSOExec]
"Asynchronous"=dword:00000001
"Impersonate"=dword:00000001
"DLLName"="%windir%\\temp\\sso\\ssoexec.dll"
"Unlock"="SSOExec"
"Lock"="SSOReset"
"Logoff"="SSOReset"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\termsrv]
"Asynchronous"=dword:00000000
"DllName"=hex(2):77,00,6c,00,6e,00,6f,00,74,00,69, 00,66,00,79,00,2e,00,64,00,\
6c,00,6c,00,00,00
"Impersonate"=dword:00000000
"Logoff"="TSEventLogoff"
"Logon"="TSEventLogon"
"PostShell"="TSEventPostShell"
"Shutdown"="TSEventShutdown"
"StartShell"="TSEventStartShell"
"Startup"="TSEventStartup"
"MaxWait"=dword:00000258
"Reconnect"="TSEventReconnect"
"Disconnect"="TSEventDisconnect"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\Notify\wlballoon]
"DLLName"="wlnotify.dll"
"Logon"="RegisterTicketExpiredNotificationEven t"
"Logoff"="UnregisterTicketExpiredNotificationEvent "
"Impersonate"=dword:00000001
"Asynchronous"=dword:00000001
3. After you paste the above commands, please close the Notepad window.
Choose Yes when you are prompted to save the file.

4. Click Start, Run, type: C:\fix.reg and press Enter to run the commands we
have pasted.
5. A dialog box will pop-up saying "Are you sure you want to add the
information in C:\fix.reg to the registry?". Click Yes on this dialog box

6. Reboot the machine.
7. After the machine reboots use Windows Update and see if the problem has
gone away.

I want to thank you for the post, Ron, and to very much thank Steve too, for
the registry fix. The last updates (and I've now done something like 140 of
them according to the MS Updates website log) I had been able to install
from the MS Updates website were on Thursday January 5, 2006. Since then I
had been downloading the KB numbers for the updates and manually applying
them, but this time on last Wednesday March 8, 2006 I could not even
download them at all because the MS Update website thought that I didn't
have Genuine Windows anymore! So I applied the fix for that
and was then able to do manual updates using downloaded files. I left one
optional update uninstalled for testing to see if I could now also update
using the MS Update website. I could not! So I set a system restore point
and then applied the below quoted registry fix. Went back to the MS Update
website and tried again. It still failed, but I noticed it had not tried to
dl the update that failed (apparently because the failure before the fix had
dl'd it) but when I again tried to install the update from the MS Update
website this time it did dl it and it did install. Yippee! A problem I've
been fighting ever since applying the update to fix the WMF exploit problem
back in January seems to now be fixed. I wonder just how planned this event
was... and I will remember.

I applied both registry patches and another one found in this NG
(search for user "barrowhill" , "psexec")
the situation is still the same, but at least I got over the "genuinie"
tool problem

windows update shows me 8 patches , downloads them and then dont
install them , still the same
but when shutting down, the updates show up in the shut down dialog box
and get installed, finally

So that is Ok so far, but the interactive windowsupdate still dont
work.
Any idea what other screw to turn .. I guess my registry already is a
cemetery :((

Adding some lines of update.log, hth
w.b.


2006-03-16 18:19:09 1176 640 Agent *************
2006-03-16 18:19:09 1176 640 Agent ** START ** Agent: Installing
updates [CallerId = WindowsUpdate]
2006-03-16 18:19:09 1176 640 Agent *********
2006-03-16 18:19:09 1176 640 Agent * Updates to install = 1
2006-03-16 18:19:09 1176 640 Agent * Title = <NULL>
2006-03-16 18:19:09 1176 640 Agent * UpdateId =
{A1521C73-0F6C-4532-801D-8B5146FC9D11}.100
2006-03-16 18:19:09 1176 640 Agent * Bundles 1 updates:
2006-03-16 18:19:09 1176 640 Agent *
{636FF899-C65D-4644-B743-246C0EBB9A87}.100
2006-03-16 18:19:09 1176 640 Agent * WARNING: Exit code = 0x80240020
2006-03-16 18:19:09 1176 640 Agent *********
2006-03-16 18:19:09 1176 640 Agent ** END ** Agent: Installing
updates [CallerId = WindowsUpdate]
2006-03-16 18:19:09 1176 640 Agent *************
2006-03-16 18:19:09 1176 640 Agent WARNING: WU client failed installing
updates with error 0x80240020
2006-03-16 18:19:09 1340 614 COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = WindowsUpdate]
2006-03-16 18:19:09 1340 614 COMAPI - Install call failed
2006-03-16 18:19:09 1340 614 COMAPI - Reboot required = No
2006-03-16 18:19:09 1340 614 COMAPI - WARNING: Exit code =
0x80240FFF; Call error code = 0x80240020
2006-03-16 18:19:09 1340 614 COMAPI ---------
2006-03-16 18:19:09 1340 614 COMAPI -- END -- COMAPI: Install
[ClientId = WindowsUpdate]
2006-03-16 18:19:09 1340 614 COMAPI -------------
2006-03-16 18:19:10 1340 554 COMAPI WARNING: Operation failed due to
earlier error, hr=80240020
2006-03-16 18:19:13 1176 640 Report REPORT EVENT:
{D09C0E4E-33B9-491A-BF8E-2309BDE5E4C1} 2006-03-16
18:19:08+0100 1 162 101 {A1521C73-0F6C-4532-801D-8B5146FC9D11} 100 0 WindowsUpdate Success Content
Download Download succeeded.
2006-03-16 18:19:28 1176 d34 AU AU found 0 updates for install at

Thanks Stephon, Thanks a lot. Your registry fix solved my problem. And the
Windows Update Icon also appears in the tray for the first time in months!!!

I have tried all of these suggestions, and, unfortunatel, none have worked.
I still cannot install service pack 2 or any other updates. Blah!!

Windows XP Service Pack 2 Problem Solver

How to troubleshoot Windows Update, Microsoft Update, and Windows Server
Update Services installation issues
http://support.microsoft.com/default...b;en-us;906602

How to troubleshoot problems connecting to Windows Update or to Microsoft
Update
http://support.microsoft.com/kb/818018/

No matter what I do, I still get these errors: Service WARNING:
GetUserTokenFromSessionId failed with hr 0x800704dd
Exit code = 0x80240020

The troubleshooters do not help with these errors (I am the administrator on
this system, and I used the above posts to try and correct my registry.)
Sadly, my computer is rather old and I have misplaced my Compaq XP recovery
CD, so I have no original to make a slipstream CD with. I have an XP pro
upgrade CD that includes SP2 from an old laptop I don't use anymore; I wasn't
sure if it was okay to use that, or if it was even safe to use with problems
in my registry.

I just took a look at my registry, and I still do not have a SensLogn; I have
WgaLogon and Reinstall. Why didn't the posts above work to fix this?

Nevermind!!!
I went to castlecops.com and got some help.
Turns out I had a lot of malware my programs weren't finding and viruses,
including VX2, that were rewriting my registry and preventing updates. Go to
the forums at castlecops and register for free; they can really help.
My computer is now pristine, and updated!

This worked great after I added a space between the Windows and the NT, the
file separates at this point in the post. It is 'Windows NT' not
'WindowsNT'. Thanks so much for the help.

\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\SensLogn

Again thanks to everyone here. I couldnt get it to work until DT added this
last note. Also just to say that it wont work until you have rebooted the
machine after adding the space.

This fix worked on Windows XP SP2 when Microsoft Update (Windows Update
replacement) died with error 0x8DDD0009

What fix ? Did you write with invisible ink ? <eg>
Please post with the original post included as posting like this is
useless for others who are seeking a solution.

Looks like it's a comment about Stephon's posting
about a fix sent "by an MSTech" (over a year ago). ; }

http://www.microsoft.com/communities...d58&sloc=en-us

(web interface search of this newsgroup for
morley

been searching for days for a fix to this issue i was having, added the reg
fix as per Stephen and viola....i had did a repair from my orginal cd, logged
onto win updates, was told to d/l and install the windows installer, which i
did, i returned to update soght and was offered some 90 updates, when i
selected review and install would get a message similar to 0kb downloaded
ready to install, and then the d/led but failed to install message, i d/led
manually and installed sp3 beta and returned to update sight, i was then
presented with 5 updates after doing a custom...again the 0kb downloaded and
failed to install message...again the posted by stephen fix worked great
thank you thank you thank you