Unable to run SFCscan,Windows Updates error 80004002,IE,Troubleshooter

[butterflyred6]

Okay, I was finally able to run the sfc scan; however it said there was a repair pending, to restart the computer. When I did that and ran sfc scan again, it said the same thing again.

 

[VistaKing]

After the restart did you run SFC from within Windows or the the repair disc ?

 

[butterflyred6]

I tried both. With the same previous results for each.

 

[NoelDP]

If there's pending operations, with luck there'll be a pending.xml file
Do a search for it (I can't remember whereabouts it hides) and post it if you find it.
Either way, please post the CBS log, and it may tell us more about what's going on, even without the SFC data.

 

[butterflyred6]

Search didn't return anything with a pending.xml Here is the cbs log:

 

[VistaKing]

Take a look in C:\Windows\winSxS for the pending.xml file

 

[NoelDP]

I've never - ever - seen a CBS log with two years of data in it! It's more usually less than 10 days-worth!


See if this helps.

Open an Elevated Command Prompt
at the prompt, type

SC config TRUSTEDINSTALLER start= auto

Close the window, and reboot.

Now wait 10 minutes, then attempt another SFC /SCANNOW, and see what happens.

 

[butterflyred6]

Here is the pending file I found.

 

[butterflyred6]

same result for the sfc scan.

 

[NoelDP]

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[butterflyred6]

Here's the file:

 

[NoelDP]

Hmm That's clear - I was hoping that it would find something that would trigger a repair.
I think the pending file that you found was simply the initial installation file, which the system keeps as a backup.

 

[butterflyred6]

What is my next step? Here are the results from some other things I ran while I was in there that looked like they might give some info? idk lol

 

[NoelDP]

I am NOT an expert at reading the windowsupdate.log file - but it seems to me that the likely cause of the problem is this....

2013-05-05 15:26:04:811  960 17f4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-05-05 15:26:06:900  960 17f4 Setup WARNING: Cbs StartSession, error = 0x80004002
2013-05-05 15:26:06:901  960 17f4 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" failed, error = 0x80004002
2013-05-05 15:26:06:902  960 17f4 Setup FATAL: SelfUpdate check failed, err = 0x80004002
2013-05-05 15:26:06:921  960 17f4 Agent   * WARNING: Skipping scan, self-update check returned 0x80004002

If that is the case, then I would have expected CheckSUR to spot it - but it is a fairly limited tool in its way.

The problem is that without some assistance from such tools, it's very difficult to pin down this error and attempt to fix it in a meaningful way.

Please run the following commands, and post the results.

REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_0.0.0.0_none_62d84d22ab3b4066" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_0.0.0.0_none_bef6e8a66398b19c" /S
 
.

 

[butterflyred6]

Nothing found.

 

[NoelDP]

Oh, b&gg$r!

That almost certainly means that the only option left is a repair install

 

[butterflyred6]

Okay, how do I do that? All the backup history, etc is erased. Do I need to buy the disc?

 

[VistaKing]

butterflyred6

Take a look here

:ar: http://www.sevenforums.com/tutorials/3413-repair-install.html

If you don't have the disc take a look at this tutorial here

:ar: http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Look at number one it has a link where you could download an Windows 7 SP1 iso file and burn it to a disc(DVD) or USB drive.

Back up all of your data first . Just in case you have to do a Clean installation .