My PC won't Update Windows

did a system scan and it revealed that I do have some corrupt files, and Microsoft could not repair some of them. it gave me a Cbs log, whatever that is. What should I do now?

While I agree with JM on the idea, the execution may need to be refined a bit. This is based on a search of my system and also with the information gleaned from winvistaclub.com's article about being unable to update Windows using Windows Update. I've also included the name of each file in parentheses but you only want to enter each line up to and including the .dll into the Run box (Click Start and then type Run in the Search box/press Enter/then type each line into the Run box).

%windir%\system32\regsvr32.exe wuapi.dll       (Windows Update Client API)

%windir%\system32\regsvr32.exe wuaueng.dll   (Windows Update Agent)

%windir%\system32\regsvr32.exe wucltux.dll     (Windows Update Client User Experience)

%windir%\system32\regsvr32.exe wudriver.dll    (Windows Update WUDriver Stub)

%windir%\system32\regsvr32.exe wups.dll        (Windows Update client proxy stub)

%windir%\system32\regsvr32.exe wups2.dll       (Windows Update client proxy stub 2)

%windir%\system32\regsvr32.exe wuwebv.dll    (Windows Update Vista Web Control)

I would stop with these seven files and see if it does the trick. I have personally tried to reregister the msxml files before and had problems. After looking around a bit I found that I wasn't the only one that had problems with those files. The other two files (qmgr.dll and qmgrprxy.dll) have to do with the Background Intelligent Transfer Service). JM, if you can fill us in on those two it would be great. :smileyhappy:

Backgrounf Intelligent Transfer Service (BITS) is the process by whihc downloads are conducted.  By default, (I believe), it is set to manual instaed of automatic to prevent rogue downloads. 

In this user's case, some sort of malware could have corrupted those .dll's and that why they need to be re-registered.

I was thinking of the malware angle myself. Any idea why the msxml files refuse to be modified on mine? No malware on my system and yet I get the permission error. It's strange because I only have one user account and it's the admin account. I'm wondering if there is a service that needs to be shut down in order to reregister them but I did make sure that no other programs were running. However, come to think of it there may have been some in the background that begin in Startup. I do think I may have a glitch because I have had other users do things that I tried and when I did them I had to run them as administrator while they didn't. Strange. Perhaps I have a poltergeist or a gremlin. :smileyhappy:

Did you notice the minor changes in the filenames between our two lists? I was wondering as I read yours if you may have modified some of them at one point.

That list is from an Enterpise environment that reports to WSUS instead of directly to Microsoft.  That may be where those last two files are coming from.

 With a WSUS environment you also use this command to make the client immediately report:

wuauclt /detectnow  (from a Run Command)

RB, you've lost me a little bit. Who are the other users? As I mentioned in my post with the list of the files to register it would be best to stop after the files that start with wu. When it comes to the last two files, the ones that JM mentioned are the BITS files, I sort of expected that to fail because that service is most likely running on your system already. I don't believe that it's possible to register files that are already in use. That may also be the case with the msxml files. JM is looking at it from an enterprise perspective and that may be making a difference in what we're seeing. In case you were curious, the WSUS that JM mentioned stands for Windows Server Update Services and is enterprise based.

Edit: Also, be sure before you use the Run command that you have closed all other applications. That is especially true if you have Windows Update open. That may be why you are unable to register the files if you have Windows Update running already.

okay guys, I ran all of the cmd prompts, only three succeeded that was "wuapi.dll" , "wups2.dll" and "qmgrprxy.dll" all the others fail to load. Some Stating that it loaded but the call to Dll Register Server failed with  error code  "0x80070005"

It seems that my DELL Register Server  has malfunctioned.