Re: Updates are downloaded but fail to install

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 (see
http://groups.google.com/group/microsoft.public.windowsupdate/browse_thread/thread/20398c7c4fe95a6a/d7c4c5ec958838f8?lnk=st&q=psexec.exe&rnum=4&hl=en#d7c4c5ec958838f8)
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.


"Ron Sherman" <RonSherman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:907234B7-A7B4-423C-A658-84192357F8EE@xxxxxxxxxxxxxxxx
Thanks everyone for the suggestions. I just now received and applied the
same fix from MS Tech Support that worked for Stephon. (I know nothing,
but
it seems to be a more elaborate version of Patti's fix.) Adding the first
registry fix in the MS solution (without the optional subsequent steps)
took
care of the problem for me, it seems. I had presented the same problem to
Microsoft about 5 times without success, and if I hadn't been moved to do
it
yet again, Stephon's response is all that would have saved me. Thanks
Stephon, and thanks Microsoft for finally getting it, hopefully.

"Stephon" wrote:

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"="RegisterTicketExpiredNotificationEvent"
"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.




"Ron Sherman" wrote:

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 *************
2005-12-15 20:20:09 872 52c Agent WARNING: WU client failed installing
updates with error 0x80240020
2005-12-15 20:20:09 2524 cac COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = WindowsUpdate]
2005-12-15 20:20:09 2524 cac COMAPI - Install call failed
2005-12-15 20:20:09 2524 cac COMAPI - Reboot required = No
2005-12-15 20:20:09 2524 cac COMAPI - WARNING: Exit code =
0x80240FFF;
Call error code = 0x80240020
2005-12-15 20:20:09 2524 cac COMAPI ---------
2005-12-15 20:20:09 2524 cac COMAPI -- END -- COMAPI: Install
[ClientId =
WindowsUpdate]
2005-12-15 20:20:09 2524 cac COMAPI -------------
2005-12-15 20:20:10 2524 9e0 COMAPI WARNING: Operation failed due to
earlier
error, hr=80240020


"Patti MacLeod" wrote:

Hi 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.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User

"Gordon" <Gordon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A90738F9-AF9C-46DB-9598-0A719D97794A@xxxxxxxxxxxxxxxx
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 =


.

Relevant Pages

  • Re: Windows XP home login/off
    ... How to Perform an In-Place Upgrade of Windows XP ... Click on How To Run a Repair Install ... registry has worked the 5 or 6 times I have seen this problem. ... The script will stop and ask you to hit enter to continue to load SCSI ...
    (microsoft.public.windowsxp.wmi)
  • Re: update fails with 0x800703E3 error
    ... Delete *ALL of the contents* of SoftwareDistribution, not the folder itself ... Close Windows Explorer ... Double click WindowsUpdateAgent20-x86.exe to install the required files. ... My earlier reference to the registry was that other solutions to similar ...
    (microsoft.public.windowsupdate)
  • Re: MM wont work after system recovery.
    ... the registry entry, that I had deleted is back in place. ... "Dick" wrote: ... Open Windows Explorer. ... users install from the net but this ...
    (microsoft.public.windowsxp.moviemaker)
  • Re: Error 8000FFFF when WU search for updates
    ... transaction due to file in use or Component reboot required, package changes ... pending xml and registry identifiers ... This is because another update within the same install transaction ... The "Windows Features" dialog box is empty in Windows Vista, ...
    (microsoft.public.windowsupdate)
  • Re: recurring Windows Configuration box appears since installing Publisher 2007
    ... apply since I am on Windows XP Media Edition. ... got tired of doing this and spent several hours searching for a fix. ... How to install and to repair 2007 Office features ... Ever since I installed Publisher 2007, I have been having trouble with ...
    (microsoft.public.publisher)