12-13 update install failure


Go Back   Computer Help Articles > Windows Update
12-13 update install failure 12-13 update install failure
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
Page 1 of 2 1 2 >
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default 12-13 update install failure
On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from "Microsoft
Update,
http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us." The
files were downloaded but would not install. The error message was: "A
problem on your computer is preventing updates from being downloaded or
installed." The comment was to try again. When I did, I got the message that
the updates were already downloaded and ready to install. When I tried, the
install failed with the same message. I did not get an error code. I tried
to use the troubleshooter, google, and this news group but did not find an
answer. However, a number of posters seem to have the same problem.

I went to the download center, individually downloaded & installed the two
updates without a problem. They do not show up on my update log but are in
the add/delete program list. I also ran the MSRT from the download center
without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis and
have not found a problem. The November updates and MSRT downloaded and
installed without a problem so I do not know what caused the December
update.microsoft.com install failure. I know that the logical answer is
that I installed some s/w that is causing the problem. I have looked and
the only s/w installations between the November update and the December
update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
version update. I have check BIT and Automatic Updates services. Both are
automatic and started.

Any suggestions?

Gateway GX1710; Winxpsp2 home; i.e.6

David


Reply With Quote
  #2  
Old 01-05-2006, 05:15 PM
Patti MacLeod
 
Posts: n/a
Default RE: 12-13 update install failure
Hi David,

Check the WindowsUpdate.log file for error codes that are related to the
failed install. The WindowsUpdate.log file can be found in the C:\Windows
folder (if there are 2 log files for Windows Update, open the one where
WindowsUpdate is displayed as one word in the filename). Copy the entries in
that file that match the date and time of the last failed install and then
paste these entries into a reply to this thread.

A fairly common error code, it seems, when updates download but fail to
install is 80240020
If this is the error code displayed in your WindowsUpdate.log file, here are
a couple of things for you to check.....

Open the registry editor and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
Check for the existence of a Notify_Disabled subkey under Winlogon. If that
subkey exists, delete it. Now, navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Notify
Check for the existence of a SensLogn subkey. If SensLogn does not exist,
you will need to add this missing key and its values.
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.

********************
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. Restart your computer for the changes to take effect.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User


"David" wrote:

> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from "Microsoft
> Update,
> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us." The
> files were downloaded but would not install. The error message was: "A
> problem on your computer is preventing updates from being downloaded or
> installed." The comment was to try again. When I did, I got the message that
> the updates were already downloaded and ready to install. When I tried, the
> install failed with the same message. I did not get an error code. I tried
> to use the troubleshooter, google, and this news group but did not find an
> answer. However, a number of posters seem to have the same problem.
>
> I went to the download center, individually downloaded & installed the two
> updates without a problem. They do not show up on my update log but are in
> the add/delete program list. I also ran the MSRT from the download center
> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis and
> have not found a problem. The November updates and MSRT downloaded and
> installed without a problem so I do not know what caused the December
> update.microsoft.com install failure. I know that the logical answer is
> that I installed some s/w that is causing the problem. I have looked and
> the only s/w installations between the November update and the December
> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
> version update. I have check BIT and Automatic Updates services. Both are
> automatic and started.
>
> Any suggestions?
>
> Gateway GX1710; Winxpsp2 home; i.e.6
>
> David
>
>
>
Reply With Quote
  #3  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
Hi Patti,
Thanks for your answer. Now that I know where to look I did find two error
codes. Neither one is 80240020. (I did a search for 80240020 from the
beginning of the log and could not find it.)


The first, hr=8024a000, happens often and most of the time in the following
sequence:
Shutdwn Install at shutdown: no updates to install
Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000
I guess this is not a problem.

The other error code is: hr=80240018. I did a search to find the first
occurance. It started happening on 12-7-05. On that day there are over 20
occurrences. The first one is:
2005-12-07 11:09:48 1208 4cc Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.

I have copied the portion of the 12-13-05 WindowsUpdate.log that identified
the three downloads and shows the first 80240018 error on that date.
2005-12-13 12:39:54 1196 560 DnldMgr *************
2005-12-13 12:39:54 1196 560 DnldMgr ** START ** DnldMgr: Downloading
updates [CallerId = MicrosoftUpdate]
2005-12-13 12:39:54 1196 560 DnldMgr *********
2005-12-13 12:39:54 1196 560 DnldMgr * Priority = 3, ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2005-12-13 12:39:54 1196 560 DnldMgr * Updates to download = 3
2005-12-13 12:39:54 1196 560 Agent * Title = Update for Windows XP
(KB910437)
2005-12-13 12:39:54 1196 560 Agent * UpdateId =
{88ECB294-6967-4250-BCB7-8C37B83915A8}.101
2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
2005-12-13 12:39:54 1196 560 Agent *
{C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
2005-12-13 12:39:54 1196 560 Agent * Title = Cumulative Security Update for
Internet Explorer for Windows XP (KB905915)
2005-12-13 12:39:54 1196 560 Agent * UpdateId =
{B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101
2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
2005-12-13 12:39:54 1196 560 Agent *
{C26A1380-04FA-4BD7-A394-22C8BE220403}.101
2005-12-13 12:39:54 1196 560 Agent * Title = Windows Malicious Software
Removal Tool - December 2005 (KB890830)
2005-12-13 12:39:54 1196 560 Agent * UpdateId =
{E9497F41-3D87-4237-AF23-A44A93B28D13}.100
2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
2005-12-13 12:39:54 1196 560 Agent *
{54FE0B51-6023-47A7-A9CB-F83C04EA625A}.100
2005-12-13 12:39:54 3648 4b4 DtaStor Update service properties: service
registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download job
[UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
2005-12-13 12:39:54 1196 560 DnldMgr * Queueing update for download handler
request generation.
2005-12-13 12:39:54 1196 560 DnldMgr Generating download request for update
{C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
2005-12-13 12:39:54 1196 560 Handler Windows Patch download for UpdateId =
{C729D82A-2CE3-497F-82C4-E0EA6149E5F3}: selected action is download
full-file.
2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download job
[UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
2005-12-13 12:39:54 1196 560 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.

I have looked at the registry and everything looks OK.


80240018?

David

"Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
news:4BD2DF5C-5D4E-4064-B0A3-B9FA7AF07765@microsoft.com...
> Hi David,
>
> Check the WindowsUpdate.log file for error codes that are related to the
> failed install. The WindowsUpdate.log file can be found in the C:\Windows
> folder (if there are 2 log files for Windows Update, open the one where
> WindowsUpdate is displayed as one word in the filename). Copy the entries
> in
> that file that match the date and time of the last failed install and then
> paste these entries into a reply to this thread.
>
> A fairly common error code, it seems, when updates download but fail to
> install is 80240020
> If this is the error code displayed in your WindowsUpdate.log file, here
> are
> a couple of things for you to check.....
>
> Open the registry editor and navigate to:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
> Check for the existence of a Notify_Disabled subkey under Winlogon. If
> that
> subkey exists, delete it. Now, navigate to:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Notify
> Check for the existence of a SensLogn subkey. If SensLogn does not exist,
> you will need to add this missing key and its values.
> 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.
>
> ********************
> 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. Restart your computer for the changes to take effect.
>
>
>
> Regards,
>
> --
> Patti MacLeod
> Microsoft MVP - Windows Shell/User
>
>
> "David" wrote:
>
>> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from
>> "Microsoft
>> Update,
>> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us."
>> The
>> files were downloaded but would not install. The error message was: "A
>> problem on your computer is preventing updates from being downloaded or
>> installed." The comment was to try again. When I did, I got the message
>> that
>> the updates were already downloaded and ready to install. When I tried,
>> the
>> install failed with the same message. I did not get an error code. I
>> tried
>> to use the troubleshooter, google, and this news group but did not find
>> an
>> answer. However, a number of posters seem to have the same problem.
>>
>> I went to the download center, individually downloaded & installed the
>> two
>> updates without a problem. They do not show up on my update log but are
>> in
>> the add/delete program list. I also ran the MSRT from the download center
>> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis and
>> have not found a problem. The November updates and MSRT downloaded and
>> installed without a problem so I do not know what caused the December
>> update.microsoft.com install failure. I know that the logical answer is
>> that I installed some s/w that is causing the problem. I have looked and
>> the only s/w installations between the November update and the December
>> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
>> version update. I have check BIT and Automatic Updates services. Both
>> are
>> automatic and started.
>>
>> Any suggestions?
>>
>> Gateway GX1710; Winxpsp2 home; i.e.6
>>
>> David
>>
>>
>>


Reply With Quote
  #4  
Old 01-05-2006, 05:15 PM
Patti MacLeod
 
Posts: n/a
Default Re: 12-13 update install failure
You're welcome for the answer. From your original post I am assuming that
you have downloaded all the required/critical updates that were available to
you at that time, that being the two that you downloaded manually from the
MS Download Center, hence there would be no remaining "needed" updates for
you to install at this time. If there were, I would ask of you to attempt to
install the remaining updates, taking note of the date and time, and then
post the complete contents in the Windows Update log that reflect that date
and time (thus having a "fresh" log to look over). Might I ask of you then
to post all the entries for 12-13-05 that reflect the time of the most
recent failed install. I'm thinking that there may be something that goes
along with the "Failed to find token for SID <SID value> with hr = 80240018"
that might further point in the right direction for a resolution to the
problem.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User

"David" <david@AAAA.net> wrote in message
news:%23EzfIUZBGHA.984@tk2msftngp13.phx.gbl...
> Hi Patti,
> Thanks for your answer. Now that I know where to look I did find two error
> codes. Neither one is 80240020. (I did a search for 80240020 from the
> beginning of the log and could not find it.)
>
>
> The first, hr=8024a000, happens often and most of the time in the
following
> sequence:
> Shutdwn Install at shutdown: no updates to install
> Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000
> I guess this is not a problem.
>
> The other error code is: hr=80240018. I did a search to find the first
> occurance. It started happening on 12-7-05. On that day there are over 20
> occurrences. The first one is:
> 2005-12-07 11:09:48 1208 4cc Misc WARNING: Failed to find token for SID
> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>
> I have copied the portion of the 12-13-05 WindowsUpdate.log that
identified
> the three downloads and shows the first 80240018 error on that date.
> 2005-12-13 12:39:54 1196 560 DnldMgr *************
> 2005-12-13 12:39:54 1196 560 DnldMgr ** START ** DnldMgr: Downloading
> updates [CallerId = MicrosoftUpdate]
> 2005-12-13 12:39:54 1196 560 DnldMgr *********
> 2005-12-13 12:39:54 1196 560 DnldMgr * Priority = 3, ServiceId =
> {7971F918-A847-4430-9279-4A52D1EFE18D}
> 2005-12-13 12:39:54 1196 560 DnldMgr * Updates to download = 3
> 2005-12-13 12:39:54 1196 560 Agent * Title = Update for Windows XP
> (KB910437)
> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
> {88ECB294-6967-4250-BCB7-8C37B83915A8}.101
> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
> 2005-12-13 12:39:54 1196 560 Agent *
> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
> 2005-12-13 12:39:54 1196 560 Agent * Title = Cumulative Security Update
for
> Internet Explorer for Windows XP (KB905915)
> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
> {B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101
> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
> 2005-12-13 12:39:54 1196 560 Agent *
> {C26A1380-04FA-4BD7-A394-22C8BE220403}.101
> 2005-12-13 12:39:54 1196 560 Agent * Title = Windows Malicious Software
> Removal Tool - December 2005 (KB890830)
> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
> {E9497F41-3D87-4237-AF23-A44A93B28D13}.100
> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
> 2005-12-13 12:39:54 1196 560 Agent *
> {54FE0B51-6023-47A7-A9CB-F83C04EA625A}.100
> 2005-12-13 12:39:54 3648 4b4 DtaStor Update service properties: service
> registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download job
> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
> 2005-12-13 12:39:54 1196 560 DnldMgr * Queueing update for download
handler
> request generation.
> 2005-12-13 12:39:54 1196 560 DnldMgr Generating download request for
update
> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
> 2005-12-13 12:39:54 1196 560 Handler Windows Patch download for UpdateId =
> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}: selected action is download
> full-file.
> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download job
> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
> 2005-12-13 12:39:54 1196 560 Misc WARNING: Failed to find token for SID
> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>
> I have looked at the registry and everything looks OK.
>
>
> 80240018?
>
> David
>
> "Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
> news:4BD2DF5C-5D4E-4064-B0A3-B9FA7AF07765@microsoft.com...
> > Hi David,
> >
> > Check the WindowsUpdate.log file for error codes that are related to the
> > failed install. The WindowsUpdate.log file can be found in the
C:\Windows
> > folder (if there are 2 log files for Windows Update, open the one where
> > WindowsUpdate is displayed as one word in the filename). Copy the
entries
> > in
> > that file that match the date and time of the last failed install and
then
> > paste these entries into a reply to this thread.
> >
> > A fairly common error code, it seems, when updates download but fail to
> > install is 80240020
> > If this is the error code displayed in your WindowsUpdate.log file, here
> > are
> > a couple of things for you to check.....
> >
> > Open the registry editor and navigate to:
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
> > Check for the existence of a Notify_Disabled subkey under Winlogon. If
> > that
> > subkey exists, delete it. Now, navigate to:
> >
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Noti
fy
> > Check for the existence of a SensLogn subkey. If SensLogn does not
exist,
> > you will need to add this missing key and its values.
> > 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.
> >
> > ********************
> > 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. Restart your computer for the changes to take effect.
> >
> >
> >
> > Regards,
> >
> > --
> > Patti MacLeod
> > Microsoft MVP - Windows Shell/User
> >
> >
> > "David" wrote:
> >
> >> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from
> >> "Microsoft
> >> Update,
> >> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us."
> >> The
> >> files were downloaded but would not install. The error message was: "A
> >> problem on your computer is preventing updates from being downloaded or
> >> installed." The comment was to try again. When I did, I got the message
> >> that
> >> the updates were already downloaded and ready to install. When I tried,
> >> the
> >> install failed with the same message. I did not get an error code. I
> >> tried
> >> to use the troubleshooter, google, and this news group but did not find
> >> an
> >> answer. However, a number of posters seem to have the same problem.
> >>
> >> I went to the download center, individually downloaded & installed the
> >> two
> >> updates without a problem. They do not show up on my update log but are
> >> in
> >> the add/delete program list. I also ran the MSRT from the download
center
> >> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis
and
> >> have not found a problem. The November updates and MSRT downloaded and
> >> installed without a problem so I do not know what caused the December
> >> update.microsoft.com install failure. I know that the logical answer
is
> >> that I installed some s/w that is causing the problem. I have looked
and
> >> the only s/w installations between the November update and the December
> >> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
> >> version update. I have check BIT and Automatic Updates services. Both
> >> are
> >> automatic and started.
> >>
> >> Any suggestions?
> >>
> >> Gateway GX1710; Winxpsp2 home; i.e.6
> >>
> >> David
> >>
> >>
> >>
>
>


Reply With Quote
  #5  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
Hi Patti,

Reviewing my history again, I found that I tried to download and install NET
Framwork 2 on 12-7-05. That must have been the first 80240018 failure that
I found and sent today. After the installation failure, I did a manual
download and install that I think worked. I guess that I got caught in the
KB886904 hotfix problem that I just read about. So today, I removeed
..Net1.1, the hot fix, .Net 2, ran the .NET cleanup, deleated some registry
keys and deleted some folders. I have not reinstalled .NET 1.1 or 2

I did find two other errors, 0x800704dd & 0x80240020. So far, google has
not helped me much on them either.

You are correct. All critical winxpsp2 updates are installed so this effort
is to fix things before the January update round.

The update log for 12-13-05 is too large to send to the news group both in
the message and as an attachment. Maybe you can tell me more about what to
look for so I can cut it down in size.

David



"Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
news:%23ZM5IkbBGHA.272@TK2MSFTNGP11.phx.gbl...
> You're welcome for the answer. From your original post I am assuming that
> you have downloaded all the required/critical updates that were available
> to
> you at that time, that being the two that you downloaded manually from the
> MS Download Center, hence there would be no remaining "needed" updates for
> you to install at this time. If there were, I would ask of you to attempt
> to
> install the remaining updates, taking note of the date and time, and then
> post the complete contents in the Windows Update log that reflect that
> date
> and time (thus having a "fresh" log to look over). Might I ask of you then
> to post all the entries for 12-13-05 that reflect the time of the most
> recent failed install. I'm thinking that there may be something that goes
> along with the "Failed to find token for SID <SID value> with hr =
> 80240018"
> that might further point in the right direction for a resolution to the
> problem.
>
>
>
> Regards,
>
> --
> Patti MacLeod
> Microsoft MVP - Windows Shell/User
>
> "David" <david@AAAA.net> wrote in message
> news:%23EzfIUZBGHA.984@tk2msftngp13.phx.gbl...
>> Hi Patti,
>> Thanks for your answer. Now that I know where to look I did find two
>> error
>> codes. Neither one is 80240020. (I did a search for 80240020 from the
>> beginning of the log and could not find it.)
>>
>>
>> The first, hr=8024a000, happens often and most of the time in the
> following
>> sequence:
>> Shutdwn Install at shutdown: no updates to install
>> Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000
>> I guess this is not a problem.
>>
>> The other error code is: hr=80240018. I did a search to find the first
>> occurance. It started happening on 12-7-05. On that day there are over 20
>> occurrences. The first one is:
>> 2005-12-07 11:09:48 1208 4cc Misc WARNING: Failed to find token for SID
>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>
>> I have copied the portion of the 12-13-05 WindowsUpdate.log that
> identified
>> the three downloads and shows the first 80240018 error on that date.
>> 2005-12-13 12:39:54 1196 560 DnldMgr *************
>> 2005-12-13 12:39:54 1196 560 DnldMgr ** START ** DnldMgr: Downloading
>> updates [CallerId = MicrosoftUpdate]
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Priority = 3, ServiceId =
>> {7971F918-A847-4430-9279-4A52D1EFE18D}
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Updates to download = 3
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Update for Windows XP
>> (KB910437)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {88ECB294-6967-4250-BCB7-8C37B83915A8}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Cumulative Security Update
> for
>> Internet Explorer for Windows XP (KB905915)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {C26A1380-04FA-4BD7-A394-22C8BE220403}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Windows Malicious Software
>> Removal Tool - December 2005 (KB890830)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {E9497F41-3D87-4237-AF23-A44A93B28D13}.100
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {54FE0B51-6023-47A7-A9CB-F83C04EA625A}.100
>> 2005-12-13 12:39:54 3648 4b4 DtaStor Update service properties: service
>> registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>> job
>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Queueing update for download
> handler
>> request generation.
>> 2005-12-13 12:39:54 1196 560 DnldMgr Generating download request for
> update
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>> 2005-12-13 12:39:54 1196 560 Handler Windows Patch download for UpdateId
>> =
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}: selected action is download
>> full-file.
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>> job
>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>> 2005-12-13 12:39:54 1196 560 Misc WARNING: Failed to find token for SID
>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>
>> I have looked at the registry and everything looks OK.
>>
>>
>> 80240018?
>>
>> David
>>
>> "Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
>> news:4BD2DF5C-5D4E-4064-B0A3-B9FA7AF07765@microsoft.com...
>> > Hi David,
>> >
>> > Check the WindowsUpdate.log file for error codes that are related to
>> > the
>> > failed install. The WindowsUpdate.log file can be found in the
> C:\Windows
>> > folder (if there are 2 log files for Windows Update, open the one where
>> > WindowsUpdate is displayed as one word in the filename). Copy the
> entries
>> > in
>> > that file that match the date and time of the last failed install and
> then
>> > paste these entries into a reply to this thread.
>> >
>> > A fairly common error code, it seems, when updates download but fail to
>> > install is 80240020
>> > If this is the error code displayed in your WindowsUpdate.log file,
>> > here
>> > are
>> > a couple of things for you to check.....
>> >
>> > Open the registry editor and navigate to:
>> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
>> > Check for the existence of a Notify_Disabled subkey under Winlogon. If
>> > that
>> > subkey exists, delete it. Now, navigate to:
>> >
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Noti
> fy
>> > Check for the existence of a SensLogn subkey. If SensLogn does not
> exist,
>> > you will need to add this missing key and its values.
>> > 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.
>> >
>> > ********************
>> > 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. Restart your computer for the changes to take effect.
>> >
>> >
>> >
>> > Regards,
>> >
>> > --
>> > Patti MacLeod
>> > Microsoft MVP - Windows Shell/User
>> >
>> >
>> > "David" wrote:
>> >
>> >> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from
>> >> "Microsoft
>> >> Update,
>> >> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us."
>> >> The
>> >> files were downloaded but would not install. The error message was: "A
>> >> problem on your computer is preventing updates from being downloaded
>> >> or
>> >> installed." The comment was to try again. When I did, I got the
>> >> message
>> >> that
>> >> the updates were already downloaded and ready to install. When I
>> >> tried,
>> >> the
>> >> install failed with the same message. I did not get an error code. I
>> >> tried
>> >> to use the troubleshooter, google, and this news group but did not
>> >> find
>> >> an
>> >> answer. However, a number of posters seem to have the same problem.
>> >>
>> >> I went to the download center, individually downloaded & installed the
>> >> two
>> >> updates without a problem. They do not show up on my update log but
>> >> are
>> >> in
>> >> the add/delete program list. I also ran the MSRT from the download
> center
>> >> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis
> and
>> >> have not found a problem. The November updates and MSRT downloaded and
>> >> installed without a problem so I do not know what caused the December
>> >> update.microsoft.com install failure. I know that the logical answer
> is
>> >> that I installed some s/w that is causing the problem. I have looked
> and
>> >> the only s/w installations between the November update and the
>> >> December
>> >> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
>> >> version update. I have check BIT and Automatic Updates services.
>> >> Both
>> >> are
>> >> automatic and started.
>> >>
>> >> Any suggestions?
>> >>
>> >> Gateway GX1710; Winxpsp2 home; i.e.6
>> >>
>> >> David
>> >>
>> >>
>> >>
>>
>>
>
>




Reply With Quote
  #6  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
Hi Patti,

Reviewing my history again, I found that I tried to download and install NET
Framwork 2 on 12-7-05. That must have been the first 80240018 failure that
I found and sent today. After the installation failure, I did a manual
download and install that I think worked. I guess that I got caught in the
KB886904 hotfix problem that I just read about. So today, I removed
..Net1.1, the hot fix, .Net 2, ran the .NET cleanup, deleted some registry
keys and deleted some folders. I have not reinstalled .NET 1.1 or 2

I did find two other errors, 0x800704dd & 0x80240020. So far, google has
not helped me much on them either.

You are correct. All critical winxpsp2 updates are installed so this effort
is to fix things before the January update round.

The update log for 12-13-05 is too large to send to the news group both in
the message and as an attachment. Maybe you can tell me more about what to
look for so I can cut it down in size.

David


"Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
news:%23ZM5IkbBGHA.272@TK2MSFTNGP11.phx.gbl...
> You're welcome for the answer. From your original post I am assuming that
> you have downloaded all the required/critical updates that were available
> to
> you at that time, that being the two that you downloaded manually from the
> MS Download Center, hence there would be no remaining "needed" updates for
> you to install at this time. If there were, I would ask of you to attempt
> to
> install the remaining updates, taking note of the date and time, and then
> post the complete contents in the Windows Update log that reflect that
> date
> and time (thus having a "fresh" log to look over). Might I ask of you then
> to post all the entries for 12-13-05 that reflect the time of the most
> recent failed install. I'm thinking that there may be something that goes
> along with the "Failed to find token for SID <SID value> with hr =
> 80240018"
> that might further point in the right direction for a resolution to the
> problem.
>
>
>
> Regards,
>
> --
> Patti MacLeod
> Microsoft MVP - Windows Shell/User
>
> "David" <david@AAAA.net> wrote in message
> news:%23EzfIUZBGHA.984@tk2msftngp13.phx.gbl...
>> Hi Patti,
>> Thanks for your answer. Now that I know where to look I did find two
>> error
>> codes. Neither one is 80240020. (I did a search for 80240020 from the
>> beginning of the log and could not find it.)
>>
>>
>> The first, hr=8024a000, happens often and most of the time in the
> following
>> sequence:
>> Shutdwn Install at shutdown: no updates to install
>> Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000
>> I guess this is not a problem.
>>
>> The other error code is: hr=80240018. I did a search to find the first
>> occurance. It started happening on 12-7-05. On that day there are over 20
>> occurrences. The first one is:
>> 2005-12-07 11:09:48 1208 4cc Misc WARNING: Failed to find token for SID
>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>
>> I have copied the portion of the 12-13-05 WindowsUpdate.log that
> identified
>> the three downloads and shows the first 80240018 error on that date.
>> 2005-12-13 12:39:54 1196 560 DnldMgr *************
>> 2005-12-13 12:39:54 1196 560 DnldMgr ** START ** DnldMgr: Downloading
>> updates [CallerId = MicrosoftUpdate]
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Priority = 3, ServiceId =
>> {7971F918-A847-4430-9279-4A52D1EFE18D}
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Updates to download = 3
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Update for Windows XP
>> (KB910437)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {88ECB294-6967-4250-BCB7-8C37B83915A8}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Cumulative Security Update
> for
>> Internet Explorer for Windows XP (KB905915)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {C26A1380-04FA-4BD7-A394-22C8BE220403}.101
>> 2005-12-13 12:39:54 1196 560 Agent * Title = Windows Malicious Software
>> Removal Tool - December 2005 (KB890830)
>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>> {E9497F41-3D87-4237-AF23-A44A93B28D13}.100
>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>> 2005-12-13 12:39:54 1196 560 Agent *
>> {54FE0B51-6023-47A7-A9CB-F83C04EA625A}.100
>> 2005-12-13 12:39:54 3648 4b4 DtaStor Update service properties: service
>> registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>> job
>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>> 2005-12-13 12:39:54 1196 560 DnldMgr * Queueing update for download
> handler
>> request generation.
>> 2005-12-13 12:39:54 1196 560 DnldMgr Generating download request for
> update
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>> 2005-12-13 12:39:54 1196 560 Handler Windows Patch download for UpdateId
>> =
>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}: selected action is download
>> full-file.
>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>> job
>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>> 2005-12-13 12:39:54 1196 560 Misc WARNING: Failed to find token for SID
>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>
>> I have looked at the registry and everything looks OK.
>>
>>
>> 80240018?
>>
>> David
>>
>> "Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
>> news:4BD2DF5C-5D4E-4064-B0A3-B9FA7AF07765@microsoft.com...
>> > Hi David,
>> >
>> > Check the WindowsUpdate.log file for error codes that are related to
>> > the
>> > failed install. The WindowsUpdate.log file can be found in the
> C:\Windows
>> > folder (if there are 2 log files for Windows Update, open the one where
>> > WindowsUpdate is displayed as one word in the filename). Copy the
> entries
>> > in
>> > that file that match the date and time of the last failed install and
> then
>> > paste these entries into a reply to this thread.
>> >
>> > A fairly common error code, it seems, when updates download but fail to
>> > install is 80240020
>> > If this is the error code displayed in your WindowsUpdate.log file,
>> > here
>> > are
>> > a couple of things for you to check.....
>> >
>> > Open the registry editor and navigate to:
>> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
>> > Check for the existence of a Notify_Disabled subkey under Winlogon. If
>> > that
>> > subkey exists, delete it. Now, navigate to:
>> >
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Noti
> fy
>> > Check for the existence of a SensLogn subkey. If SensLogn does not
> exist,
>> > you will need to add this missing key and its values.
>> > 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.
>> >
>> > ********************
>> > 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. Restart your computer for the changes to take effect.
>> >
>> >
>> >
>> > Regards,
>> >
>> > --
>> > Patti MacLeod
>> > Microsoft MVP - Windows Shell/User
>> >
>> >
>> > "David" wrote:
>> >
>> >> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from
>> >> "Microsoft
>> >> Update,
>> >> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us."
>> >> The
>> >> files were downloaded but would not install. The error message was: "A
>> >> problem on your computer is preventing updates from being downloaded
>> >> or
>> >> installed." The comment was to try again. When I did, I got the
>> >> message
>> >> that
>> >> the updates were already downloaded and ready to install. When I
>> >> tried,
>> >> the
>> >> install failed with the same message. I did not get an error code. I
>> >> tried
>> >> to use the troubleshooter, google, and this news group but did not
>> >> find
>> >> an
>> >> answer. However, a number of posters seem to have the same problem.
>> >>
>> >> I went to the download center, individually downloaded & installed the
>> >> two
>> >> updates without a problem. They do not show up on my update log but
>> >> are
>> >> in
>> >> the add/delete program list. I also ran the MSRT from the download
> center
>> >> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis
> and
>> >> have not found a problem. The November updates and MSRT downloaded and
>> >> installed without a problem so I do not know what caused the December
>> >> update.microsoft.com install failure. I know that the logical answer
> is
>> >> that I installed some s/w that is causing the problem. I have looked
> and
>> >> the only s/w installations between the November update and the
>> >> December
>> >> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
>> >> version update. I have check BIT and Automatic Updates services.
>> >> Both
>> >> are
>> >> automatic and started.
>> >>
>> >> Any suggestions?
>> >>
>> >> Gateway GX1710; Winxpsp2 home; i.e.6
>> >>
>> >> David
>> >>
>> >>
>> >>
>>
>>
>
>


Reply With Quote
  #7  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
Hi Patti,

Reviewing my history again, I found that I tried to download and install NET
Framwork 2 on 12-7-05. That must have been the first 80240018 failure that
I found and sent today. After the installation failure, I did a manual
download and install that I think worked. I guess that I got caught in the
KB886904 hotfix problem that I just read about. So today, I removed
..Net1.1, the hot fix, .Net 2, ran the .NET cleanup, deleted some registry
keys and deleted some folders. I have not reinstalled .NET 1.1 or 2

I did find two other errors, 0x800704dd & 0x80240020. So far, google has
not helped me much on them either.

You are correct. All critical winxpsp2 updates are installed so this effort
is to fix things before the January update round.

The update log for 12-13-05 is too large to send to the news group both in
the message and as an attachment. Maybe you can tell me more about what to
look for so I can cut it down in size.

David

P.S. I tried to reply to your post but even without the attachment, the
server rejects it.


Reply With Quote
  #8  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
Sorry for the multiple posts but I kept getting "can not post" error
messages.

David


"David" <david@AAAA.net> wrote in message
news:OkBNyIcBGHA.2356@tk2msftngp13.phx.gbl...
> Hi Patti,
>
> Reviewing my history again, I found that I tried to download and install
> NET Framwork 2 on 12-7-05. That must have been the first 80240018 failure
> that I found and sent today. After the installation failure, I did a
> manual download and install that I think worked. I guess that I got
> caught in the KB886904 hotfix problem that I just read about. So today, I
> removed .Net1.1, the hot fix, .Net 2, ran the .NET cleanup, deleted some
> registry keys and deleted some folders. I have not reinstalled .NET 1.1 or
> 2
>
> I did find two other errors, 0x800704dd & 0x80240020. So far, google has
> not helped me much on them either.
>
> You are correct. All critical winxpsp2 updates are installed so this
> effort is to fix things before the January update round.
>
> The update log for 12-13-05 is too large to send to the news group both in
> the message and as an attachment. Maybe you can tell me more about what
> to look for so I can cut it down in size.
>
> David
>
>
> "Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
> news:%23ZM5IkbBGHA.272@TK2MSFTNGP11.phx.gbl...
>> You're welcome for the answer. From your original post I am assuming that
>> you have downloaded all the required/critical updates that were available
>> to
>> you at that time, that being the two that you downloaded manually from
>> the
>> MS Download Center, hence there would be no remaining "needed" updates
>> for
>> you to install at this time. If there were, I would ask of you to attempt
>> to
>> install the remaining updates, taking note of the date and time, and then
>> post the complete contents in the Windows Update log that reflect that
>> date
>> and time (thus having a "fresh" log to look over). Might I ask of you
>> then
>> to post all the entries for 12-13-05 that reflect the time of the most
>> recent failed install. I'm thinking that there may be something that goes
>> along with the "Failed to find token for SID <SID value> with hr =
>> 80240018"
>> that might further point in the right direction for a resolution to the
>> problem.
>>
>>
>>
>> Regards,
>>
>> --
>> Patti MacLeod
>> Microsoft MVP - Windows Shell/User
>>
>> "David" <david@AAAA.net> wrote in message
>> news:%23EzfIUZBGHA.984@tk2msftngp13.phx.gbl...
>>> Hi Patti,
>>> Thanks for your answer. Now that I know where to look I did find two
>>> error
>>> codes. Neither one is 80240020. (I did a search for 80240020 from the
>>> beginning of the log and could not find it.)
>>>
>>>
>>> The first, hr=8024a000, happens often and most of the time in the
>> following
>>> sequence:
>>> Shutdwn Install at shutdown: no updates to install
>>> Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000
>>> I guess this is not a problem.
>>>
>>> The other error code is: hr=80240018. I did a search to find the first
>>> occurance. It started happening on 12-7-05. On that day there are over
>>> 20
>>> occurrences. The first one is:
>>> 2005-12-07 11:09:48 1208 4cc Misc WARNING: Failed to find token for SID
>>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>>
>>> I have copied the portion of the 12-13-05 WindowsUpdate.log that
>> identified
>>> the three downloads and shows the first 80240018 error on that date.
>>> 2005-12-13 12:39:54 1196 560 DnldMgr *************
>>> 2005-12-13 12:39:54 1196 560 DnldMgr ** START ** DnldMgr: Downloading
>>> updates [CallerId = MicrosoftUpdate]
>>> 2005-12-13 12:39:54 1196 560 DnldMgr *********
>>> 2005-12-13 12:39:54 1196 560 DnldMgr * Priority = 3, ServiceId =
>>> {7971F918-A847-4430-9279-4A52D1EFE18D}
>>> 2005-12-13 12:39:54 1196 560 DnldMgr * Updates to download = 3
>>> 2005-12-13 12:39:54 1196 560 Agent * Title = Update for Windows XP
>>> (KB910437)
>>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>>> {88ECB294-6967-4250-BCB7-8C37B83915A8}.101
>>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>>> 2005-12-13 12:39:54 1196 560 Agent *
>>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>>> 2005-12-13 12:39:54 1196 560 Agent * Title = Cumulative Security Update
>> for
>>> Internet Explorer for Windows XP (KB905915)
>>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>>> {B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101
>>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>>> 2005-12-13 12:39:54 1196 560 Agent *
>>> {C26A1380-04FA-4BD7-A394-22C8BE220403}.101
>>> 2005-12-13 12:39:54 1196 560 Agent * Title = Windows Malicious Software
>>> Removal Tool - December 2005 (KB890830)
>>> 2005-12-13 12:39:54 1196 560 Agent * UpdateId =
>>> {E9497F41-3D87-4237-AF23-A44A93B28D13}.100
>>> 2005-12-13 12:39:54 1196 560 Agent * Bundles 1 updates:
>>> 2005-12-13 12:39:54 1196 560 Agent *
>>> {54FE0B51-6023-47A7-A9CB-F83C04EA625A}.100
>>> 2005-12-13 12:39:54 3648 4b4 DtaStor Update service properties: service
>>> registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
>>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>>> job
>>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>>> 2005-12-13 12:39:54 1196 560 DnldMgr * Queueing update for download
>> handler
>>> request generation.
>>> 2005-12-13 12:39:54 1196 560 DnldMgr Generating download request for
>> update
>>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101
>>> 2005-12-13 12:39:54 1196 560 Handler Windows Patch download for UpdateId
>>> =
>>> {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}: selected action is download
>>> full-file.
>>> 2005-12-13 12:39:54 1196 560 DnldMgr *********** DnldMgr: New download
>>> job
>>> [UpdateId = {C729D82A-2CE3-497F-82C4-E0EA6149E5F3}.101] ***********
>>> 2005-12-13 12:39:54 1196 560 Misc WARNING: Failed to find token for SID
>>> S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
>>>
>>> I have looked at the registry and everything looks OK.
>>>
>>>
>>> 80240018?
>>>
>>> David
>>>
>>> "Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
>>> news:4BD2DF5C-5D4E-4064-B0A3-B9FA7AF07765@microsoft.com...
>>> > Hi David,
>>> >
>>> > Check the WindowsUpdate.log file for error codes that are related to
>>> > the
>>> > failed install. The WindowsUpdate.log file can be found in the
>> C:\Windows
>>> > folder (if there are 2 log files for Windows Update, open the one
>>> > where
>>> > WindowsUpdate is displayed as one word in the filename). Copy the
>> entries
>>> > in
>>> > that file that match the date and time of the last failed install and
>> then
>>> > paste these entries into a reply to this thread.
>>> >
>>> > A fairly common error code, it seems, when updates download but fail
>>> > to
>>> > install is 80240020
>>> > If this is the error code displayed in your WindowsUpdate.log file,
>>> > here
>>> > are
>>> > a couple of things for you to check.....
>>> >
>>> > Open the registry editor and navigate to:
>>> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon
>>> > Check for the existence of a Notify_Disabled subkey under Winlogon. If
>>> > that
>>> > subkey exists, delete it. Now, navigate to:
>>> >
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon\Noti
>> fy
>>> > Check for the existence of a SensLogn subkey. If SensLogn does not
>> exist,
>>> > you will need to add this missing key and its values.
>>> > 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.
>>> >
>>> > ********************
>>> > 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. Restart your computer for the changes to take effect.
>>> >
>>> >
>>> >
>>> > Regards,
>>> >
>>> > --
>>> > Patti MacLeod
>>> > Microsoft MVP - Windows Shell/User
>>> >
>>> >
>>> > "David" wrote:
>>> >
>>> >> On 12/13/05, I downloaded KB905915, KB910437, and the MSRT from
>>> >> "Microsoft
>>> >> Update,
>>> >> http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us."
>>> >> The
>>> >> files were downloaded but would not install. The error message was:
>>> >> "A
>>> >> problem on your computer is preventing updates from being downloaded
>>> >> or
>>> >> installed." The comment was to try again. When I did, I got the
>>> >> message
>>> >> that
>>> >> the updates were already downloaded and ready to install. When I
>>> >> tried,
>>> >> the
>>> >> install failed with the same message. I did not get an error code. I
>>> >> tried
>>> >> to use the troubleshooter, google, and this news group but did not
>>> >> find
>>> >> an
>>> >> answer. However, a number of posters seem to have the same problem.
>>> >>
>>> >> I went to the download center, individually downloaded & installed
>>> >> the
>>> >> two
>>> >> updates without a problem. They do not show up on my update log but
>>> >> are
>>> >> in
>>> >> the add/delete program list. I also ran the MSRT from the download
>> center
>>> >> without a problem. I have and ran SBS&D; AdAware; avast; & HiJackThis
>> and
>>> >> have not found a problem. The November updates and MSRT downloaded
>>> >> and
>>> >> installed without a problem so I do not know what caused the December
>>> >> update.microsoft.com install failure. I know that the logical answer
>> is
>>> >> that I installed some s/w that is causing the problem. I have looked
>> and
>>> >> the only s/w installations between the November update and the
>>> >> December
>>> >> update are the avast Dec 4.6.739 build update and ccleaner v.1.26.218
>>> >> version update. I have check BIT and Automatic Updates services.
>>> >> Both
>>> >> are
>>> >> automatic and started.
>>> >>
>>> >> Any suggestions?
>>> >>
>>> >> Gateway GX1710; Winxpsp2 home; i.e.6
>>> >>
>>> >> David
>>> >>
>>> >>
>>> >>
>>>
>>>
>>
>>
>
>


Reply With Quote
  #9  
Old 01-05-2006, 05:15 PM
Patti MacLeod
 
Posts: n/a
Default Re: 12-13 update install failure
Hi David,

You said "I did find two other errors, 0x800704dd & 0x80240020. So far,
google has not helped me much on them either." Those two errors often go
hand-in-hand, and my first response to you referenced the 0x80240020 error.
From a quick search of google groups, I have found that the missing SensLogn
key in the registry (which I had mentioned in that post) is most often the
culprit.

Since the log for 12-13-05 is too large to send to the newsgroup, look for a
line in the log that looks something like this:

COMAPI -- START -- COMAPI: Install [ClientId = MicrosoftUpdate]

Copy from that line down to the bottom of the log for 12-13-05 if possible.
Usually the "main" error code(s) appear near the bottom of the log file for
the particular Windows Update session.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User


"David" wrote:

> Hi Patti,
>
> Reviewing my history again, I found that I tried to download and install NET
> Framwork 2 on 12-7-05. That must have been the first 80240018 failure that
> I found and sent today. After the installation failure, I did a manual
> download and install that I think worked. I guess that I got caught in the
> KB886904 hotfix problem that I just read about. So today, I removed
> ..Net1.1, the hot fix, .Net 2, ran the .NET cleanup, deleted some registry
> keys and deleted some folders. I have not reinstalled .NET 1.1 or 2
>
> I did find two other errors, 0x800704dd & 0x80240020. So far, google has
> not helped me much on them either.
>
> You are correct. All critical winxpsp2 updates are installed so this effort
> is to fix things before the January update round.
>
> The update log for 12-13-05 is too large to send to the news group both in
> the message and as an attachment. Maybe you can tell me more about what to
> look for so I can cut it down in size.
>
> David
>
> P.S. I tried to reply to your post but even without the attachment, the
> server rejects it.
>
>
>
Reply With Quote
  #10  
Old 01-05-2006, 05:15 PM
David
 
Posts: n/a
Default Re: 12-13 update install failure
When I looked for the 80240020 error I typed it wrong and search for a
different number. I have looked at the registry three times, checked off
each item against your post, and the entries are correct. I did not make
any changes.

Here is a part of the log file. It is the first occurance of
COMAPI--START--COMAPI. I did not go to the end because this section is near
the start. The log for 12-13 is 95 KB. Following this, there is a section
with the first 0x800704dd and 0x80240020 errors

David

2005-12-13 12:37:59 3104 a24 COMAPI -------------
2005-12-13 12:37:59 3104 a24 COMAPI -- START -- COMAPI: Search [ClientId =
MicrosoftUpdate]
2005-12-13 12:37:59 3104 a24 COMAPI ---------
2005-12-13 12:37:59 3104 a24 COMAPI - Online = Yes; Ignore download
priority = No
2005-12-13 12:37:59 3104 a24 COMAPI - Criteria = "IsInstalled=0 and
IsHidden=1"
2005-12-13 12:37:59 3104 a24 COMAPI - ServiceID =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2005-12-13 12:37:59 3104 a24 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = MicrosoftUpdate]
2005-12-13 12:37:59 1196 124 Agent *************
2005-12-13 12:37:59 1196 124 Agent ** START ** Agent: Finding updates
[CallerId = MicrosoftUpdate]
2005-12-13 12:37:59 1196 124 Agent *********
2005-12-13 12:38:00 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:00 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:13 1196 124 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-12-13 12:38:13 1196 124 PT + ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2005-12-13 12:38:20 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:20 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:23 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:23 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:23 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:26 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:27 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:29 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:29 1196 124 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2005-12-13 12:38:29 1196 124 PT + ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2005-12-13 12:38:29 1196 124 Misc WARNING: Failed to find token for SID
S-1-5-21-680338518-1412893358-3394653975-1003 with hr = 80240018.
2005-12-13 12:38:29 3648 4b4 DtaStor WARNING: Attempted to add URL
http://www.download.windowsupdate.co...a9d896b8.ca b
for file oTSJMsjj/cYDvFWspvKH/qnYlrg= when file has not been previously
added to the datastore
2005-12-13 12:38:29 3648 4b4 DtaStor WARNING: Attempted to add URL
http://www.download.windowsupdate.co...bd1752b4.ca b
for file zdEv/RNy9hrDwj+ryP5W+L0XUrQ= when file has not been previously
added to the datastore
2005-12-13 12:38:29 3648 4b4 DtaStor WARNING: Attempted to add URL
http://www.download.windowsupdate.co...0b9495f3.ca b
for file NMBXLtyxqgCtpdGMvLfYtQuUlfM= when file has not been previously
added to the datastore
2005-12-13 12:38:30 1196 124 Agent * Added update
{515BF752-CC2A-46A7-9222-D81D48540B65}.100 to search result
2005-12-13 12:38:30 1196 124 Agent * Found 1 updates and 11 categories in
search
2005-12-13 12:38:30 1196 124 Report *********** Report: Initializing static
reporting data ***********
2005-12-13 12:38:30 1196 124 Report * OS Version = 5.1.2600.2.0.66304
2005-12-13 12:38:30 1196 124 Report * Computer Brand = Gateway
2005-12-13 12:38:30 1196 124 Report * Computer Model = 7510GX
2005-12-13 12:38:30 1196 124 Report * Bios Revision = 66.04.00
2005-12-13 12:38:30 1196 124 Report * Bios Name = BIOS Version 66.04.00
2005-12-13 12:38:30 1196 124 Report * Bios Release Date =
2005-06-15T00:00:00
2005-12-13 12:38:30 1196 124 Report * Locale ID = 1033
2005-12-13 12:38:30 1196 124 Agent *********
2005-12-13 12:38:30 1196 124 Agent ** END ** Agent: Finding updates
[CallerId = MicrosoftUpdate]
2005-12-13 12:38:30 1196 124 Agent *************
2005-12-13 12:38:30 3104 e08 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = MicrosoftUpdate]
2005-12-13 12:38:30 3104 e08 COMAPI - Updates found = 1
2005-12-13 12:38:30 3104 e08 COMAPI ---------
2005-12-13 12:38:30 3104 e08 COMAPI -- END -- COMAPI: Search [ClientId =
MicrosoftUpdate]
2005-12-13 12:38:30 3104 e08 COMAPI -------------
2005-12-13 12:38:30 3104 a24 COMAPI -------------
2005-12-13 12:38:30 3104 a24 COMAPI -- START -- COMAPI: Search [ClientId =
MicrosoftUpdate]
2005-12-13 12:38:30 3104 a24 COMAPI ---------
2005-12-13 12:38:30 3104 a24 COMAPI - Online = No; Ignore download
priority = No
2005-12-13 12:38:30 3104 a24 COMAPI - Criteria = "IsInstalled = 0 and
IsHidden = 0"
2005-12-13 12:38:30 3104 a24 COMAPI - ServiceID =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2005-12-13 12:38:30 3104 a24 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = MicrosoftUpdate]
2005-12-13 12:38:30 1196 124 Agent *************
2005-12-13 12:38:30 1196 124 Agent ** START ** Agent: Finding updates
[CallerId = MicrosoftUpdate]
2005-12-13 12:38:30 1196 124 Agent *********
2005-12-13 12:38:31 1196 124 Agent * Added update
{88ECB294-6967-4250-BCB7-8C37B83915A8}.101 to search result
2005-12-13 12:38:31 1196 124 Agent * Added update
{B7C71E84-3A27-4458-B3E5-98512AA5EF36}.101 to search result
2005-12-13 12:38:31 1196 124 Agent * Added update
{E9497F41-3D87-4237-AF23-A44A93B28D13}.100 to search result
2005-12-13 12:38:31 1196 124 Agent * Found 3 updates and 11 categories in
search
2005-12-13 12:38:31 1196 124 Agent *********
2005-12-13 12:38:31 1196 124 Agent ** END ** Agent: Finding updates
[CallerId = MicrosoftUpdate]
2005-12-13 12:38:31 1196 124 Agent *************
2005-12-13 12:38:31 3104 e08 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = MicrosoftUpdate]
2005-12-13 12:38:31 3104 e08 COMAPI - Updates found = 3
2005-12-13 12:38:31 3104 e08 COMAPI ---------
2005-12-13 12:38:31 3104 e08 COMAPI -- END -- COMAPI: Search [ClientId =
MicrosoftUpdate]
2005-12-13 12:38:31 3104 e08 COMAPI -------------
2005-12-13 12:38:35 1196 124 Report REPORT EVENT:
{8C2B646F-D991-49EB-B966-083D19429E6F} 2005-12-13 12:38:30-0800 1 147 101
{00000000-0000-0000-0000-000000000000} 0 0 MicrosoftUpdate Success Software
Synchronization Agent has finished detecting items.
2005-12-13 12:39:54 3104 a24 COMAPI -------------
2005-12-13 12:39:54 3104 a24 COMAPI -- START -- COMAPI: Download [ClientId
= MicrosoftUpdate]
2005-12-13 12:39:54 3104 a24 COMAPI ---------
2005-12-13 12:39:54 3104 a24 COMAPI - Forced: No; Download priority: 3
2005-12-13 12:39:54 3104 a24 COMAPI - Updates in request: 3
2005-12-13 12:3