windows update error code 80080005 windows 7 64 bit

[carling43]

Hello,

My windows update has stopped working some time ago. I have followed as many fixes as possible. I have followed 'Tom984' instructions on "Windows update posting instructions", however, I cannot follow the
"sfc/scannow" command. (I get this error.. "Windows Resource Protection could not start the repair service"
I did zip the CBS folder.

I should also note that I get the message on the splash screen about 'Preparing to configure updates.... failure configuring updates, reverting changes".. etc.. as well as blue screen etc...

I have attached the CBS zip file, as per Tom984 instructions.

I will try to provide whatever info I can.

Thank you for any assistance you can provide..

Cheers

 

[NoelDP]

The errors in the CheckSUR report explain your inability to update....

Checking Packages
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514  failed to get CurrentState
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514  failed to get Visibility
(f) CBS Registry Error [B]0x80070103[/B] WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256  [B]failed to get owner for package[/B].

It's that last one that I suspect is responsible for your WU giving an access denied error - that package is the core of the WU process.

I can't do it tonight - but I'll work on a fix for that in the morning, hopefully.

Some of the errors in the CBS.log appears related.....

 Line 3687: 2013-01-04 14:16:01, Info                  CBS    Failed to open online package store: PackagesPending\Package_26_for_KB2574819~31bf3856ad364e35~amd64~~6.1.1.7. [HRESULT = 0x80070005 - E_ACCESSDENIED]
 Line 28: 2013-01-04 14:13:37, Info                  CBS    Missing Current State value for package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514, force absent so at least it can be re-installed
 Line 29: 2013-01-04 14:13:37, Info                  CBS    Failed to get visibility for package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

Some appear to have resolved themselves since you first ran CheckSUR and cured a large number of errors, but a couple remain - which may resolve if we can cure the few remaining CheckSUR problems.

 

[carling43]

Thank you

Noel,

Thank you so much for looking in to this for me!
I'm trying to learn, and truly appreciate your assistance.

I look forward to hearing from you.

Cheers!

 

[NoelDP]

I think I need a little more information before I start with the repair....

Please run the following commands in an Elevated Command Prompt, and post the results...

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514" /S

 

[carling43]

Hi Noel,

Thank you so much for the quick response. I hope I did this correctly..

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e3
5~amd64~~7.6.7600.256" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600
.256
InstallClient REG_SZ WindowsUpdateAgent
InstallName REG_SZ WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~am
d64~~7.6.7600.256.mum
InstallLocation REG_SZ \\?\C:\Windows\SoftwareDistribution\SelfUpdate\
Packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256\
CurrentState REG_DWORD 0x70
SelfUpdate REG_DWORD 0x0
Visibility REG_DWORD 0x2
Trusted REG_DWORD 0x1
InstallTimeHigh REG_DWORD 0x1cd5001
InstallTimeLow REG_DWORD 0x19bce759
InstallUser REG_SZ S-1-5-18

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600
.256\Owners


C:\Windows\system32>

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf38
56ad364e35~amd64~en-US~6.1.7601.17514" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~
en-US~6.1.7601.17514\Owners
Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6
.1.7601.17514 REG_DWORD 0x30070


C:\Windows\system32>


Cheers,

(Jim)

 

[NoelDP]

That's fine - and it looks like it may be fairly easy to fix.

We'll do the WU updater patch first - because it's the easiest one, and should be controllable if it goes wrong


If you don't understand anything please ask!
First create a System Restore point, then....
Open Regedit
Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256

Right-click on the Key in the left pane, and select Permissions
Click on the Advanced button
Click on the Owner tab
Highlight Administrators, and put a tick in the 'Replace owner on...' box
Click Apply
(Current Owner should change to Administrators)
Click OK - ONCE
Click on the Permissions tab
In the Permission entries box, highlight Administrators
click Edit
put a tick in the Allow /Full Control box (all the other Allow boxes should automatically be ticked)
put a tick in the 'Apply these permissions....' box
Click OK out to Regedit
Close Regedit

Now download the file 256auxcomp.zip from my Skydrive here....
Noel's SkyDrive

and extract the contained file.
right-click on the extracted file and select Merge
You'll get a couple or warnings, and then hopefully a 'success' message.

reboot, and then run another CheckSUR scan and post the new CheckSUR.log file
Then run another SFC /SCANNOW and post the new CBS.log file

 

[carling43]

Hi Noel,

I trust this is the CheckSUR log you requested.. I will continue with the rest of your instructions and post in a moment.

Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 17.0
2013-02-02 16:17

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 failed to get Visibility
(f) CBS Registry Error 0x80070103 WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256 failed to get owner for package.

Checking Component Store

Summary:
Seconds executed: 66
Found 3 errors
CBS Registry Error Total count: 3

Please note...


put a tick in the Allow /Full Control box (all the other Allow boxes should automatically be ticked) (This already was ticked)



You'll get a couple or warnings, and then hopefully a 'success' message. (I got success!!! )



reboot, and then run another CheckSUR scan and post the new CheckSUR.log file (nb. got the windows messages on startup regarding preparing to configure updates... reverting changes.. I don't know if this matters at this point, just wanted to point it out.. )

I will now try the SFC/SCANNOW and post the CBS.log file..

Thank you.

 

[carling43]

I ran SFC/SCANNOW and received the same error "Windows Resource Protection could not start the repair service"

 

[NoelDP]

Hmmm - the reg file should have corrected one of the CheckSUR errors - please run the following command and we'll see whether it worked as expected, or not.....

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514" /S

post the results

 

[carling43]

Hi Noel,

I'm sorry to take so long getting back to you. I just got home from work. Here is the results. Dumb question, but...
I copied the first line to the command prompt, pasted, then selected all, and pasted here. I then did the same thing with the second line. I assume that is the correct way?

Thank you.

Cheers,

Jim


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e3
5~amd64~~7.6.7600.256" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600
.256
InstallClient REG_SZ WindowsUpdateAgent
InstallName REG_SZ WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~am
d64~~7.6.7600.256.mum
InstallLocation REG_SZ \\?\C:\Windows\SoftwareDistribution\SelfUpdate\
Packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256\
CurrentState REG_DWORD 0x70
SelfUpdate REG_DWORD 0x0
Visibility REG_DWORD 0x2
Trusted REG_DWORD 0x1
InstallTimeHigh REG_DWORD 0x1cd551a
InstallTimeLow REG_DWORD 0xf229ed24
InstallUser REG_SZ S-1-5-18

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600
.256\Owners
WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256 REG_DWORD
0x30070


C:\Windows\system32>


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf38
56ad364e35~amd64~en-US~6.1.7601.17514" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~
en-US~6.1.7601.17514\Owners
Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6
.1.7601.17514 REG_DWORD 0x30070


C:\Windows\system32>

 

[NoelDP]

You can copy both at the same time - the buffer will usually remember the minor details like new lines

The registry fix definitely did the job it was supposed to

I must have had more to drink than I remember yesterday - I could have sworn that the error was still present in the latest CheckSUR report, but rechecking just now, it's clear - so false alarm! (mea culpa)

The repairs on the other points are required in the second line - and I need to establish a little information from elsewhere in your registry and filesystem before attempting to fix them

Please run the following commands, and post the results.

DIR C:\Windows\servicing\packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
DIR C:\Windows\servicing\packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.cat
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514" /S

Then with a bit of luck, we'll get that one sorted, and get on to ironing out any remaining problems.

 

[carling43]

hahaha,

No worries at all Noel.

Thank you again for your help with this!




Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DIR C:\Windows\servicing\packages\Microsoft-Windows-Client-D
rivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
Volume in drive C has no label.
Volume Serial Number is 141C-91B2

Directory of C:\Windows\servicing\packages

11/20/2010 12:37 PM 45,501 Microsoft-Windows-Client-Drivers-Package~
31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum
1 File(s) 45,501 bytes
0 Dir(s) 84,308,656,128 bytes free

C:\Windows\system32>



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DIR C:\Windows\servicing\packages\Microsoft-Windows-Client-D
rivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.cat
Volume in drive C has no label.
Volume Serial Number is 141C-91B2

Directory of C:\Windows\servicing\packages

11/20/2010 01:29 PM 143,197 Microsoft-Windows-Client-Drivers-Package~
31bf3856ad364e35~amd64~en-US~6.1.7601.17514.cat
1 File(s) 143,197 bytes
0 Dir(s) 84,308,619,264 bytes free

C:\Windows\system32>



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf38
56ad364e35~amd64~~6.1.7601.17514" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~
~6.1.7601.17514
InstallClient REG_SZ DISM Package Manager Provider
InstallName REG_SZ Microsoft-Windows-Client-Drivers-Package~31bf3856ad
364e35~amd64~~6.1.7601.17514.mum
InstallLocation REG_SZ \\?\C:\BVTBin\Tests\installpackage\Package\win7
sp\KB976932\SAND\87C8A3D4-58A3-4100-9B5A-FC2AC7014E79\
CurrentState REG_DWORD 0x70
SelfUpdate REG_DWORD 0x0
Visibility REG_DWORD 0x2
InstallTimeHigh REG_DWORD 0x1cb892d
InstallTimeLow REG_DWORD 0xd20dd14c
InstallUser REG_SZ S-1-5-21-3053783715-499189888-2895902266-500

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~
~6.1.7601.17514\Owners
Microsoft-Windows-EnterpriseEdition~31bf3856ad364e35~amd64~~6.1.7601.17514
REG_DWORD 0x30000
Microsoft-Windows-HomeBasicEdition~31bf3856ad364e35~amd64~~6.1.7601.17514
REG_DWORD 0x30000
Microsoft-Windows-HomePremiumEdition~31bf3856ad364e35~amd64~~6.1.7601.17514
REG_DWORD 0x30000
Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~6.1.7601.17514
REG_DWORD 0x30070
Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~6.1.7601.17514 R
EG_DWORD 0x30000
Microsoft-Windows-UltimateEdition~31bf3856ad364e35~amd64~~6.1.7601.17514
REG_DWORD 0x30040


C:\Windows\system32>

 

[NoelDP]

OK - we'll have to do a little preparatory work before we can apply the fix....

We need to change permissions on the registry Key we need to change....
Open Regedit
Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514

Right-click on the Key in the left pane, and select Permissions
Click on the Advanced button
Click on the Owner tab
Highlight Administrators, and put a tick in the 'Replace owner on...' box
Click Apply
(Current Owner should change to Administrators)
Click OK - ONCE
Click on the Permissions tab
In the Permission entries box, highlight Administrators
click Edit
put a tick in the Allow /Full Control box (all the other Allow boxes should automatically be ticked)
put a tick in the 'Apply these permissions....' box
Click OK out to Regedit
Close Regedit

Now download the file driversus.zip from my Skydrive here....
Noel's SkyDrive

and extract the contained file.
right-click on the extracted file and select Merge
You'll get a couple or warnings, and then hopefully a 'success' message.

reboot, and then run another CheckSUR scan and post the new CheckSUR.log file

Then test Windows Update - first run a manual check for updates, and see what happens

 

[NoelDP]

(please note - I changed the target in regedit after posting! check the post for the latest/correct one, as the one in your email will be wrong.)

 

[carling43]

Hi Noel,

Thanks, I printed your instructions from here.. on the site. I will post the CBS log, then try a manual update.

Cheers.

 

[carling43]

I just tried to manually update and did not have any luck, I got the dreaded Code 80080005 again. :-((

 

[NoelDP]

There's a strange error in your CBS log

2013-02-02 10:43:01, Info                  CSI    00000005 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0x174fa90
2013-02-02 10:43:01, Error                 CSI    [EMAIL="00000006@2013/2/2:18:43:01.480"]00000006@2013/2/2:18:43:01.480[/EMAIL] (F) d:\win7sp1_gdr\base\xml\udom_xmlcursor.cpp(47): Error STATUS_ILLEGAL_CHARACTER originated in function CXmlCursor::Next expression: RtlXmlNextLogicalThing( &m_State, &m_Namespaces, &m_CurrentThing, &m_AttributeList )
[gle=0x80004005]
2013-02-02 10:43:01, Error                 CSI    00000007 (F) HRESULT_FROM_WIN32(582) #130# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = (unknown enumerant 0)[3]" | "0)[gle=0x80070246]
2013-02-02 10:43:01, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2013-02-02 10:43:01, Info                  CBS    Current global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback

there's also this error set...

2013-02-02 10:43:01, Info                  CBS    CBS has signaled TrustedInstaller that a reboot is required.
2013-02-02 10:43:01, Info                  CBS    Startup: Failed, restart required to try again.
2013-02-02 10:43:01, Info                  CBS    Startup: Processing complete. [HRESULT = 0x80070bc2 - ERROR_SUCCESS_REBOOT_REQUIRED]
2013-02-02 10:43:01, Info                  CBS    Restored system sleep block state: 0x80000000
2013-02-02 10:43:01, Info                  CBS    May have successfully finished startup processing but another reboot and executing startup processing again is required to be sure.
2013-02-02 10:43:01, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x80070bc2 - ERROR_SUCCESS_REBOOT_REQUIRED]
2013-02-02 10:43:01, Info                  CBS    Startup processing thread terminated normally
2013-02-02 10:43:07, Info                  CBS    Failed to create session. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]

There's some very complex stuff going on at the end of the CBS log - and I don't understand it much.

Please reboot again, and note the time, then wait 15 minutes, and run another SFC /SCANNOW.
then post the new CBS.log (only)

Your CheckSUR log is now clear

 

[carling43]

Hi Noel, great news with the CheckSUR log!! Yayyyy.!!! I tried to run SFC /SCANNOW however, I still get the error
" Windows Resource Protection could not start the Repair Service"
I do apologize for giving you fits with this.. if worse comes to worse, I'll just reinstall windows and be done with it. (I hope!!) I don't want to take up too much of your time.

 

[NoelDP]

It's solving things like this that keep me getting up in the morning

I think I've worked out what the problem is.
Your system is repeatedly attempting a rollback of an update, and it's failing

 Line 265675: 2013-02-04 20:16:52, Info                  CBS    Startup: Processing advanced operation queue, startupPhase: 0
 Line 265676: 2013-02-04 20:16:52, Info                  CSI    00000005 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0xf7f7c0
 Line 265703: 2013-02-04 20:17:22, Info                  CBS    Startup: Processing advanced operation queue, startupPhase: 0
 Line 265704: 2013-02-04 20:17:22, Info                  CSI    00000005 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0x17ffae0

The problem files here appear to be

 Line 265735:     CmdLine: [154]""C:\Windows\WinSxS\amd64_microsoft-windows-i..-setieinstalleddate_31bf3856ad364e35_9.4.8112.16421_none_7d153fec93ad1dcf\SetIEInstalledDate.exe" /uninstall"
 Line 265755:     CmdLine: [150]""C:\Windows\WinSxS\amd64_microsoft-windows-ie-gc-registeriepkeys_31bf3856ad364e35_9.4.8112.16421_none_9c87145ef6731d4a\RegisterIEPKEYs.exe" /uninstall"
 Line 265775:     CmdLine: [231]""C:\Windows\WinSxS\amd64_microsoft-windows-ie-pdm_31bf3856ad364e35_9.4.8112.16421_none_621428eebb2fac97\PDMSetup.exe" /uninstall C:\Windows\WinSxS\amd64_microsoft-windows-ie-pdm_31bf3856ad364e35_8.0.7600.16385_none_6425238b793ee910"
 Line 265795:     CmdLine: [165]""C:\Windows\WinSxS\amd64_microsoft-windows-i..eoptionalcomponents_31bf3856ad364e35_9.4.8112.16421_none_765820a329e47a35\ConfigureIEOptionalComponents.exe" /uninstall"
 Line 265815:     CmdLine: [148]""C:\Windows\WinSxS\x86_microsoft-windows-ie-gc-registeriepkeys_31bf3856ad364e35_9.4.8112.16421_none_406878db3e15ac14\RegisterIEPKEYs.exe" /uninstall"
 Line 265835:     CmdLine: [152]""C:\Windows\WinSxS\x86_microsoft-windows-i..-setieinstalleddate_31bf3856ad364e35_9.4.8112.16421_none_20f6a468db4fac99\SetIEInstalledDate.exe" /uninstall"
 Line 265855:     CmdLine: [163]""C:\Windows\WinSxS\x86_microsoft-windows-i..eoptionalcomponents_31bf3856ad364e35_9.4.8112.16421_none_1a39851f718708ff\ConfigureIEOptionalComponents.exe" /uninstall"
 Line 265875:     CmdLine: [227]""C:\Windows\WinSxS\x86_microsoft-windows-ie-pdm_31bf3856ad364e35_9.4.8112.16421_none_05f58d6b02d23b61\PDMSetup.exe" /uninstall C:\Windows\WinSxS\x86_microsoft-windows-ie-pdm_31bf3856ad364e35_8.0.7601.17514_none_0a379bcfbdcffb74"

But I currently have no idea how to deal with them (and it's way past my bedtime!)
Perhaps the WindowsUpdate.log file may help?

Please attach the log to a reply - C:\Windows\windowsupdate.log (you may have to copy it to the desktop first)

 

[carling43]

Here you go Noel,

I'm just heading off also..

Cheers..