Windows Update Problems

F

FormerUser73968

Member
Joined
Jan 8, 2014
Posts
51
Windows Update Troubleshooter says

Potential Windows Update Database error detected 0x80070490 [Fixed]

Windows Update Components must be repaired [Fixed]

No matter how many times it says "Fixed" it never fixes it though...

What's going on with Windows Update?
 
Hello!

Nothing much of interest in that logfile. Can you please run DISM again and upload the entire C:\Windows\Logs\CBS folder.

Thank you!

Richard
 
DISM says "The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully."

What do I do now, press the red exit button, or do something else first?
 
Close the program then zip up and upload your CBS log please!

C:\Windows\Logs\CBS\CBS.log
 
Looks good to me!

Code: 
Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 1482 seconds.

Any difference?

Tom
 
Why does windows update troubleshooter still say this?

Potential Windows Update Database error detected 0x80070490 [Fixed]

Windows Update components must be repaired [Fixed]
 
Hello again :)

Are you actively having problems with Windows Update, or is it just the troubleshooter reporting problems? Any failing updates?

DISM is a reliable tool. You can trust it in its belief of no problems found. The troubleshooter, however, is a much more prone to the potential for mistakes because of the way it works.

But as you say, we should not write off its find as immediately invalid. All of the tools scan different areas, do different things (otherwise they wouldn't all exist). DISM has not found any corruption in the areas it has looked, but that does not mean that none exists elsewhere.

Please run the following Fix-It: http://support.microsoft.com/kb/971058

Close the pop-up Fix-It and choose the one embedded into the article. Then run it with the Aggressive Mode box checked.

Then restart your computer and re-run the troubleshooter. Finally, if it proves necessary, we may backup and delete a couple of logfiles. But most important question of all, as given in first line, is Windows Update actually having a problem?

Richard
 
I don't know if these commands were successful or not.


Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
-I'm assuming this command was successful because the first time i tried it without quotations.
The second time i copied and pasted quotations and all.
The third time it said it could not find it, and it showed a path to where it was...




None of these commands went through for some reason.
Ren %systemroot%\SoftwareDistribution\DataStore *.bak
Ren %systemroot%\SoftwareDistribution\Download *.bak
Ren %systemroot%\system32\catroot2 *.bak






The module "mshtml.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "mshtml.dll" is a valid DLL or OCX file and then try again.


The module "shdocvw.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "mshtml.dll" is a valid DLL or OCX file and then try again.


The module "browseui.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "mshtml.dll" is a valid DLL or OCX file and then try again.


The module "msxml.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "gpkcsp.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "sccbase.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "slbcsp.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "initpki.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "wuaueng1.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "wucltui.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "wuweb.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.


The module "qmgr.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "qmgr.dll" is a valid DLL or OCX file and then try again.


The module "muweb.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.
 
I also can't run "aggressive mode" from Microsoft's "FixIt" because Microsoft decided it was a genius idea to replace that troubleshooter with a more "updated" version that helps me less...

Running DBAN *which is supposed to wipe my whole hard drive* (to me that includes system files) and reinstalling using genuine hp OEM discs doesn't help.

Running this command: Dism /Online /Cleanup-Image /RestoreHealth from command prompt helps a little, but it doesn't repair everything. Yeah, there are no corruptions, but why

were there still errors in my CBS log?
 
iJoshstephen said:
None of these commands went through for some reason.
Ren %systemroot%\SoftwareDistribution\DataStore *.bak
Ren %systemroot%\SoftwareDistribution\Download *.bak
Click to expand...

These are the only commands I really care about. I used the Fix-It just to do this. But since we can't, I need you have have another go.

Did you remember the
net stop bitsnet stop wuauserv

lines first?
 
Yes i disabled bits and wuauserv.

Renaming the DataStore to (.bak) worked. I figured out i had to delete (*) but renaming the Download folder gives me an error.

"A duplicate file name exists, or the file cannot be found."
 
Further issues with this machine have let to a reinstallation. Case closed.
 
Windows Update is installing updates fine now. The only problems i'm having is the troubleshooter showing errors. Why did I have those errors when re registering the dll's? I think there are still problems somewhere because of this and the fact that I have clean installed my pc. I hope the troubleshooter is wrong, but I want to make sure.
 
oJoshstephen said:
Windows Update is installing updates fine now. The only problems i'm having is the troubleshooter showing errors. Why did I have those errors when re registering the dll's? I think there are still problems somewhere because of this and the fact that I have clean installed my pc. I hope the troubleshooter is wrong, but I want to make sure.
Click to expand...

The .dll registration errors are normal. The troubleshooter actively seeks out problems it can repair, problems it can't repair, and problems it can't detect but can repair. It makes the assumption that if you're running it, you must be having problems with Windows Update. If it can't detect any problems, it assumes that the problems it can't detect but can repair must be the cause, and attempts to fix them. This is all that is happening here. There is nothing wrong with your computer. Just ignore the troubleshooter result.

Richard
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top