Hmm. Thanks for the suggestion. It didn't fix the problem, but it did lead
me towards the solution.
I followed your directions as close as possible. (I generally used the UI
rather than command line, but the result is the same.) The UI didn't get any
better, and the actual windows update system stopped working.
I then went to remove your fix using the shadow copy rollback option on each
file. (I'd checked for shadow copies before and had not found any.) Once
all the files had been reverted to their previous state, everything started
working again!
Theories: I had some disk corruption issues a few weeks ago, about when all
this broke. I bet one of these files got corrupted. I think windows
wouldn't show me a shadow copy because it didn't think anything had actually
changed. By replacing the files it let me then access good shadow copies
that I used to fix the system. I also suspect your fix would have worked for
me if I had not used a SP0 installer disk to try repairing an SP1
instillation.
Hint: I believe this could be done without safe mode by skipping the files
that are currently in use (that won't allow overwriting). When I rolled back
I did the easy files first and the UI started working (after restarting the
service).
Thanks!
"martyp" wrote:
>
> Hello.
>
> I've been lurking for a while to see if any answers were posted to this
> problem. For the past several weeks I, too, have been "suffering" from
> a Windows Update screen devoid of text. None of the proposed solutions
> worked. That was the bad news. Here's the good news. I believe I can
> help. My Windows Update works again. Before I share the steps I took
> to fix the problem, let me first say that I'm fully aware that there
> are people out there who can come up with shortcuts based on what I
> post. Great. Whether I took too many steps to accomplish the goal or
> not, it worked. It was a long, tedious process, but here goes. Please
> let me/us know if it works for you.
>
> Note: The following assumes that you have, or have access to the
> original Vista 32-bit .iso or can otherwise utilize the file
> install.wim contained within the .iso.
>
> 1. Place the original Vista .iso on your hard drive.
> 2. Extract install.wim from the iso.
> 3. Extract all c:\windows\system32\wu*.* files from install.wim.
> 4. Place all extracted wu*.* files in their own folder, e.g., C:\wu for
> later use.
> 5. Run Start, All Programs, Accessories. Right click on Command Prompt
> and click on Run as administrator.
> 6. Navigate to your System32 directory.
> 7. In order to replace current wu*.* files in the System32 directory,
> you'll need to first take ownership of each of them as follows:
> Run: takeown /f "path and file name" [note: I ran this command for
> each of the wu*.* files, one at a time]
> then
> Run: cacls "path and file name" /G <your username>:F
> 8. Replace all wu*.* files using those from c:\wu
> 9. Register each of the original wu*.dlls in System32 - for example
> (regsvr32 wuapi.dll)
> 10. Reboot
> 11. Place Windows Update in manual mode as a test and run it.
>
> That’s it
>
> I have not yet placed Windows Update in automatic mode, but I suspect
> (hope) it'll work.
>
> By the way, one of the hints that the wu*.* files in Windows\System32
> needed replacement with the originals was that I noticed that a couple
> of the file dates changed to some date in June of this year. That's
> what broke Windows Update.
>
> Marty
>
>
> --
> martyp
> ------------------------------------------------------------------------
> martyp's Profile: http://forums.techarena.in/member.php?userid=28898
> View this thread: http://forums.techarena.in/showthread.php?t=791034
>
> http://forums.techarena.in
>
>
Linear Mode
