Prev: Error code 0x8007f0e9
Next: Error 80070005, can't update, please help
From: JuliusCaesar on 20 Feb 2005 07:29
Since this week I received a message that installation of windows security
updates fail. When I look in the installation history it says error 8007F05A.
Try to google on this number, but no result. Looking through this discussion
group I tried to follow some recommendations like deleting all temp-files
etc. Nothing helps.
Does someone have a solution?
From: Pat Walters [MSFT] on 22 Feb 2005 17:53
"JuliusCaesar",

Would you mind trying this again with just one update? Please try the
following procedure, and we can see the moment by moment steps--this should
help us figure out the issue:

On Windows XP:
1. Close all Internet browsers
2. Open a single Internet Explorer window.
3. In the Internet Explorer window, click Tools
4. Click Windows Update
5. When you reach the Windows Update site, click Custom Install
6. click Review and Install Updates
7. When presented with multiple updates, uncheck all of them except for one
update (your choice)
8. Look down at the System clock and note the time. Let the minute move
forward one, so that there is no other activity associated with this
attempt.
9. Click Install. Wait for Windows Update to fail. If it succeeds, reply
back and let us know.
10. Assuming it failed, Click Start
11. Click Run
12. Type: %WINDIR%\WindowsUpdate.log
13. Press <Enter> or Click OK
14. When the log opens, scroll down to the hour and minute you memorized in
step 8.
15. Starting at the beginning of the first entry for that minute, click and
drag down and to the right selecting the rest of the log.
16. Click Edit, then Copy, or just press the <CTRL> and <C> keys.
17. Reply to this posting.
18. When that window opens, Tell us what update you attempted to install,
and where it failed from our observation.
19. After this, on a new line, state the following and press <Enter>: Log
entries follow:
20. Place the cursor on the line under the entry from step 19, and then
click Edit, then Paste, or just press the <CTRL> and <V> keys.
21. The log entries copied in steps 15-16 should have copied into your
posting.
22. Send it to us, and let us take a look at this failure.

On Windows 2000
Repeat steps 1-22 above, with the following changes:
6. Skip this step
12. The file is "%WINDIR%\Windows Update.log" (please INCLUDE the quotes and
notice the space between windows and update)

On Windows 98
This is identical to Windows 2000, but %windir% does not exist in Windows
98. Instead:
12. Change %WINDIR% to %WINBOOTDIR%

Sincerely,

Pat Walters [MSFT]

"JuliusCaesar" wrote:

> Since this week I received a message that installation of windows security
> updates fail. When I look in the installation history it says error 8007F05A.
> Try to google on this number, but no result. Looking through this discussion
> group I tried to follow some recommendations like deleting all temp-files
> etc. Nothing helps.
> Does someone have a solution?
From: JuliusCaesar on 25 Feb 2005 12:01
Hi Pat,

Tried the procedure you asked for. Indeed the update failed again. The
package I selected to be installed was the update of KB886903. It failed when
the package should be installed.

Log entries follow:
2005-02-25 17:44:10+0100 1424 784 AU Client approved 1 updates for install
2005-02-25 17:44:10+0100 1424 784 WU client succeeds
CClientCallRecorder::BeginInstallUpdates from AutomaticUpdates with call id
{2B89646C-D4F2-471F-BB99-5C447F62C227}
2005-02-25 17:44:10+0100 1424 784 Successfully initiated install for 1 updates
2005-02-25 17:44:10+0100 1424 750 WU client executing call
{2B89646C-D4F2-471F-BB99-5C447F62C227} of type Install call
2005-02-25 17:44:10+0100 1424 750 validate updates before Install
2005-02-25 17:44:13+0100 1424 750 prune update list before Install
2005-02-25 17:44:13+0100 1424 750 setting system restore point
2005-02-25 17:44:23+0100 1424 7f0 WU client calls back to install call
{2B89646C-D4F2-471F-BB99-5C447F62C227} with code Call progress and error 0
2005-02-25 17:44:23+0100 1424 750 WU client starts install in user context
2005-02-25 17:44:25+0100 1424 750 WU client is installing update
{B0F400F2-C431-405F-8367-54B20B3FC8B3}.101
2005-02-25 17:45:17+0100 1424 7f0 Install failed: 80070643
2005-02-25 17:45:17+0100 1424 784 OS Version = 5.1.2600.2.0.66304
2005-02-25 17:45:17+0100 1424 784 Failed to load reporting information from
Win32_ComputerSystem with hr = 80041003.
2005-02-25 17:45:17+0100 1424 784 Failed to load reporting information from
Win32_BiosProperties with hr = 80041003.
2005-02-25 17:45:17+0100 1424 784 Locale ID = 1043
2005-02-25 17:45:17+0100 1424 784 ClientVersion: iuengine.dll = 5.4.3790.2182
2005-02-25 17:45:17+0100 1424 784 ClientVersion: wuapi.dll = 5.4.3790.2182
2005-02-25 17:45:17+0100 1424 784 ClientVersion: wuauclt.exe = 5.4.3790.2182
2005-02-25 17:45:17+0100 1424 784 ClientVersion: wuauclt1.exe = 5.4.3790.2182
2005-02-25 17:45:17+0100 1424 784 ClientVersion: wuaucpl.cpl = 5.4.3790.2182
2005-02-25 17:45:17+0100 1424 784 ClientVersion: wuaueng.dll = 5.4.3790.2182
2005-02-25 17:45:18+0100 1424 784 ClientVersion: wuaueng1.dll = 5.4.3790.2182
2005-02-25 17:45:18+0100 1424 784 ClientVersion: wuauserv.dll = 5.4.3790.2180
2005-02-25 17:45:18+0100 1424 784 ClientVersion: wucltui.dll = 5.4.3790.2182
2005-02-25 17:45:18+0100 1424 750 WU client finishes installing update
{B0F400F2-C431-405F-8367-54B20B3FC8B3}.101 with result 0x8024200b
2005-02-25 17:45:18+0100 1424 750 system restore point set
2005-02-25 17:45:18+0100 1424 750 WU client finished installing updates
2005-02-25 17:45:18+0100 1424 750 Install call completed.
2005-02-25 17:45:18+0100 1424 750 Install complete for all calls, reboot NOT
needed
2005-02-25 17:45:18+0100 1424 750 WU client calls back to install call
{2B89646C-D4F2-471F-BB99-5C447F62C227} with code Call complete and error 0
2005-02-25 17:45:18+0100 1424 750 WU client completed and deleted call
{2B89646C-D4F2-471F-BB99-5C447F62C227}
2005-02-25 17:45:23+0100 1424 750 REPORT EVENT:
{4C996CD8-6E52-4726-8DF6-3CF4B91A5483} 547 2005-02-25
17:45:17+0100 1 182 101 {66216830-74FA-4A91-BEA8-212E6A5A43DD} 101 80070643 AutomaticUpdates Failure Content
Install Installation Failure: Windows failed to install the following update
with error 0x80070643: KB886903: Beveiligingsupdate voor Microsoft .NET
Framework versie 1.1 Service Pack 1.
2005-02-25 17:45:23+0100 1424 750 REPORT EVENT:
{543216DA-FCBA-4485-9DC8-CC6310483035} 548 2005-02-25
17:45:18+0100 1 182 101 {B0F400F2-C431-405F-8367-54B20B3FC8B3} 101 80070643 AutomaticUpdates Failure Content
Install Installation Failure: Windows failed to install the following update
with error 0x80070643: KB886903: Beveiligingsupdate voor Microsoft .NET
Framework versie 1.1 Service Pack 1.
2005-02-25 17:45:23+0100 1424 750 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{F8F91C6C-F4D3-4FC0-B78F-63045EDD8E97}.bin for writing.
2005-02-25 17:45:23+0100 1424 798 Resetting cached installation status
2005-02-25 17:45:23+0100 1424 1b4 AU received event of 1
2005-02-25 17:45:23+0100 1424 1b4 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id
{0F5FBA64-737A-4477-89FA-6F0CBF714DEB}
2005-02-25 17:45:23+0100 1424 7bc Resetting cached installation status
2005-02-25 17:45:23+0100 1424 750 WU client executing call
{0F5FBA64-737A-4477-89FA-6F0CBF714DEB} of type Search Call
2005-02-25 17:45:23+0100 1424 1b4 AU received event of 1
2005-02-25 17:45:24+0100 1424 750 WU client add update
{62C88996-8493-43E4-AA10-DA19D00660D4}.101 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{66216830-74FA-4A91-BEA8-212E6A5A43DD}.101 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{9A127D52-45FA-44BA-ACC5-5EA9A637FE4E}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{D275095E-E695-466C-B42A-FC63DA718A12}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{BB758AAA-8024-44D0-8434-73CEFE8CA80B}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{4B689082-CA9C-46CC-B2FC-720FEDE21299}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{4E57D979-58B2-4D06-8233-689BA4F10116}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{3A7EFDB0-D88D-42A6-8439-C7D0B1BCAC82}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{DD2CC470-501A-4BF2-BC57-88C8F52439EB}.101 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{BB642BE1-0DEA-4782-8C40-BFDBAA3DA376}.100 to search result
2005-02-25 17:45:24+0100 1424 750 WU client add update
{1FD3B3AC-9E83-4286-8369-D122669C24F6}.101 to search result
2005-02-25 17:45:24+0100 1424 750 WU client found 11 updates and 11
categories in search
2005-02-25 17:45:24+0100 1424 750 WU client finished Searching for update
2005-02-25 17:45:24+0100 1424 750 AU Detection callback: 11 updates detected
2005-02-25 17:45:24+0100 1424 750 WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2005-02-25 17:45:24+0100 1424 750 WU client completed and deleted call
{0F5FBA64-737A-4477-89FA-6F0CBF714DEB}
2005-02-25 17:46:09+0100 1896 408 10 updates are ready to be installed at
shutdown.
2005-02-25 17:46:23+0100 1424 1b4 AU received event of 0
2005-02-25 17:46:24+0100 1424 594 Service received logoff notification
2005-02-25 17:46:24+0100 1424 1b4 AU received event of 3
2005-02-25 17:46:29+0100 1424 7bc AU Restart required....
2005-02-25 17:46:29+0100 1424 1b4 AU received event of 1
2005-02-25 17:46:29+0100 1424 1b4 AU is paused, not initializing any handlers
2005-02-25 17:46:31+0100 1424 594 Service received SERVICE_CONTROL_SHUTDOWN
control
2005-02-25 17:46:31+0100 1424 1b4 Exiting Service Main
2005-02-25 17:46:31+0100 340 1a0 Out of proc datastore is shutting down
2005-02-25 17:46:31+0100 1424 1b4 WUAUENG ServiceMain exits. Exit code is
0x240001
2005-02-25 17:46:33+0100 340 1a0 Out of proc datastore is now inactive
2005-02-25 17:47:50+0100 844 350 WUCheckForUpdatesAtShutdown failed,
hr=8024000C
2005-02-25 17:47:50+0100 1400 16c Service Main starts
2005-02-25 17:47:50+0100 1400 16c Using BatchFlushAge = 34938.
2005-02-25 17:47:50+0100 1400 16c Using SamplingValue = 11.
2005-02-25 17:47:50+0100 1400 16c Successfully loaded event namespace
dictionary.
2005-02-25 17:47:50+0100 1400 16c Successfully loaded client event namespace
descriptor.
2005-02-25 17:47:50+0100 1400 16c Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2005-02-25 17:47:50+0100 1400 16c Successfully initialized NT event logger.
2005-02-25 17:47:50+0100 1400 16c Successfully initialized event uploader 0.
2005-02-25 17:47:50+0100 1400 16c Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{E309E64A-738C-487F-A601-FA3168BFAD72}.bin for writing.
2005-02-25 17:47:50+0100 1400 16c Successfully initialized event uploader 1.
2005-02-25 17:47:50+0100 1400 16c WU client with version 5.4.3790.2182
successfully initialized
2005-02-25 17:47:50+0100 1400 16c Service status is now SERVICE_RUNNING
2005-02-25 17:47:55+0100 1388 570 Trying to make out of proc datastore active
2005-02-25 17:47:57+0100 1388 570 Out of proc datastore is now active
2005-02-25 17:47:57+0100 1400 76c Client Call Recorder finished delayed
initialization
2005-02-25 17:47:58+0100 1400 76c AU finished delayed initialization
2005-02-25 17:47:58+0100 1400 76c AU Restart required....
2005-02-25 17:47:58+0100 1400 16c AU received event of 1
2005-02-25 17:47:58+0100 1400 16c AU is paused, not initializing any handlers
2005-02-25 17:48:01+0100 1400 57c Service received SERVICE_CONTROL_SHUTDOWN
control
2005-02-25 17:48:01+0100 1400 16c Exiting Service Main
2005-02-25 17:48:01+0100 1388 570 Out of proc datastore is shutting down
2005-02-25 17:48:01+0100 1400 16c WUAUENG ServiceMain exits. Exit code is
0x240001
2005-02-25 17:48:02+0100 1388 570 Out of proc datastore is now inactive
a


"Pat Walters [MSFT]" wrote:

> "JuliusCaesar",
>
> Would you mind trying this again with just one update? Please try the
> following procedure, and we can see the moment by moment steps--this should
> help us figure out the issue:
>
> On Windows XP:
> 1. Close all Internet browsers
> 2. Open a single Internet Explorer window.
> 3. In the Internet Explorer window, click Tools
> 4. Click Windows Update
> 5. When you reach the Windows Update site, click Custom Install
> 6. click Review and Install Updates
> 7. When presented with multiple updates, uncheck all of them except for one
> update (your choice)
> 8. Look down at the System clock and note the time. Let the minute move
> forward one, so that there is no other activity associated with this
> attempt.
> 9. Click Install. Wait for Windows Update to fail. If it succeeds, reply
> back and let us know.
> 10. Assuming it failed, Click Start
> 11. Click Run
> 12. Type: %WINDIR%\WindowsUpdate.log
> 13. Press <Enter> or Click OK
> 14. When the log opens, scroll down to the hour and minute you memorized in
> step 8.
> 15. Starting at the beginning of the first entry for that minute, click and
> drag down and to the right selecting the rest of the log.
> 16. Click Edit, then Copy, or just press the <CTRL> and <C> keys.
> 17. Reply to this posting.
> 18. When that window opens, Tell us what update you attempted to install,
> and where it failed from our observation.
> 19. After this, on a new line, state the following and press <Enter>: Log
> entries follow:
> 20. Place the cursor on the line under the entry from step 19, and then
> click Edit, then Paste, or just press the <CTRL> and <V> keys.
> 21. The log entries copied in steps 15-16 should have copied into your
> posting.
> 22. Send it to us, and let us take a look at this failure.
>
> On Windows 2000
> Repeat steps 1-22 above, with the following changes:
> 6. Skip this step
> 12. The file is "%WINDIR%\Windows Update.log" (please INCLUDE the quotes and
> notice the space between windows and update)
>
> On Windows 98
> This is identical to Windows 2000, but %windir% does not exist in Windows
> 98. Instead:
> 12. Change %WINDIR% to %WINBOOTDIR%
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> "JuliusCaesar" wrote:
>
> > Since this week I received a message that installation of windows security
> > updates fail. When I look in the installation history it says error 8007F05A.
> > Try to google on this number, but no result. Looking through this discussion
> > group I tried to follow some recommendations like deleting all temp-files
> > etc. Nothing helps.
> > Does someone have a solution?
From: JuliusCaesar on 26 Feb 2005 08:39
After I send the log-file I discovered that in one way or another (I really
don't know how that could have been happened) the security settings of the
C:\Windows seem to have been such the neither the Administrators nor the
System account had full control to it. Only one user was allowed to the
directory. After changing the security settings to the C:\Windows directory
to having both Administrators and System full control, the automatic updates
work well (so using the "ballon" that appears in the taskbar).

However, when I want to use the manual Windows Update (through the Windows
Internet Explorer for example) I get an error that I have to be in the group
of ADMINISRATORS, but the account that I use IS a member of the group (error
number: 0x8DDD0002). Looking through the Windows Update discussion group (and
Google) I have seen many entries on this subject. I have almost followed
every hint that was given for example:

- http://support.microsoft.com/default.aspx?scid=316524
- Forcing the right security setting to C:\Windows\SoftwareDistribution folder

etc.

Nothing helps. Maybe someone has another clue looking through the following
part of my WindowsUpdate.log file, which is the part that is appended when I
click on Extra->Windows Update in IE6.0 (please note: I use the Dutch version
of Windows XP Home Edition with SP2 and all security updates that appear
automatically). Apparently the SusExtractFiles command for target
C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab fails with an error
0x80070005.

2005-02-26 14:15:48+0100 208 5e8 Trying to make out of proc datastore active
2005-02-26 14:15:49+0100 208 5e8 Out of proc datastore is now active
2005-02-26 14:15:49+0100 1416 b84 WU client succeeds
CClientCallRecorder::EnumerateService
2005-02-26 14:15:51+0100 1416 d74 WU client succeeds
CClientCallRecorder::EnumerateService
2005-02-26 14:15:56+0100 3056 bf4 Checking for different Redirector at:
http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2005-02-26 14:15:56+0100 3056 bf4 WinInet: Server file is not newer.
Skipping download.
2005-02-26 14:15:56+0100 3056 bf4 Successfully refreshed Redirector cab.
2005-02-26 14:15:56+0100 3056 bf4 WinInet: Server file is not newer.
Skipping download.
2005-02-26 14:15:56+0100 3056 bf4 SusExtractFiles for target
C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab failed with error
0x80070005
2005-02-26 14:15:56+0100 3056 bf4 CheckIfClientUpdateNeeded failed: error
0x80070005





"JuliusCaesar" wrote:

> Hi Pat,
>
> Tried the procedure you asked for. Indeed the update failed again. The
> package I selected to be installed was the update of KB886903. It failed when
> the package should be installed.
>
....
From: JuliusCaesar on 27 Feb 2005 08:35
After I discovered that apparently something had screwed up the windows
directory and not only windows update but also some other programs started to
go crazy I decided to do a system restore. Had to go back in time till
23-1-2005, but now it seems that everything works fine again.


"JuliusCaesar" wrote:

> After I send the log-file I discovered that in one way or another (I really
> don't know how that could have been happened) the security settings of the
> C:\Windows seem to have been such the neither the Administrators nor the
> System account had full control to it. Only one user was allowed to the
> directory. After changing the security settings to the C:\Windows directory
> to having both Administrators and System full control, the automatic updates
> work well (so using the "ballon" that appears in the taskbar).
>
> However, when I want to use the manual Windows Update (through the Windows
> Internet Explorer for example) I get an error that I have to be in the group
> of ADMINISRATORS, but the account that I use IS a member of the group (error
> number: 0x8DDD0002). Looking through the Windows Update discussion group (and
> Google) I have seen many entries on this subject. I have almost followed
> every hint that was given for example:
>
> - http://support.microsoft.com/default.aspx?scid=316524
> - Forcing the right security setting to C:\Windows\SoftwareDistribution folder
>
> etc.
>
> Nothing helps. Maybe someone has another clue looking through the following
> part of my WindowsUpdate.log file, which is the part that is appended when I
> click on Extra->Windows Update in IE6.0 (please note: I use the Dutch version
> of Windows XP Home Edition with SP2 and all security updates that appear
> automatically). Apparently the SusExtractFiles command for target
> C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab fails with an error
> 0x80070005.
>
> 2005-02-26 14:15:48+0100 208 5e8 Trying to make out of proc datastore active
> 2005-02-26 14:15:49+0100 208 5e8 Out of proc datastore is now active
> 2005-02-26 14:15:49+0100 1416 b84 WU client succeeds
> CClientCallRecorder::EnumerateService
> 2005-02-26 14:15:51+0100 1416 d74 WU client succeeds
> CClientCallRecorder::EnumerateService
> 2005-02-26 14:15:56+0100 3056 bf4 Checking for different Redirector at:
> http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
> 2005-02-26 14:15:56+0100 3056 bf4 WinInet: Server file is not newer.
> Skipping download.
> 2005-02-26 14:15:56+0100 3056 bf4 Successfully refreshed Redirector cab.
> 2005-02-26 14:15:56+0100 3056 bf4 WinInet: Server file is not newer.
> Skipping download.
> 2005-02-26 14:15:56+0100 3056 bf4 SusExtractFiles for target
> C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab failed with error
> 0x80070005
> 2005-02-26 14:15:56+0100 3056 bf4 CheckIfClientUpdateNeeded failed: error
> 0x80070005
>
>
>
>
>
> "JuliusCaesar" wrote:
>
> > Hi Pat,
> >
> > Tried the procedure you asked for. Indeed the update failed again. The
> > package I selected to be installed was the update of KB886903. It failed when
> > the package should be installed.
> >
> ...
 | 
Pages: 1
Prev: Error code 0x8007f0e9
Next: Error 80070005, can't update, please help