Well, thanks to Bill WD is slowly being tamed, although it is stil

[Guest]

work in progress. After many futile attempts, using both known fixes and
reinstalls, to rectify error 0x8007064c, I finally just gave up on it in
February. Then a few weeks ago I installed the latest version. The update
to definition file ending in .6 was really bizarre. All attempts were
unsuccessful, both through WD and Auto Update and WD. Then one morning,
several days and pc shutdowns later, shutdown hung up and informed me it was
installing updates. The next time I checked it was at .6. On to definition
..8, again unsuccessful I was informed, however, I'd read Bill's fix in the
forum using Add/Remove>Change and that worked perfectly. .10 had it's own
interesting twist. It claimed it was successful from the get go, yet the
definition number never changed. I used both WD and Auto to no avail.
Finally this morning I used the ADD/Remove fix and it now shows .10.

Yes, there are maybe millions of different pc
configurations out there and, if you only knew that, you could understand
these glitches. However, there are thousands of programs, including all
kinds of freeware, that update with out a problem all the time, and this is
what makes these issues quite hard to understand, especially since we talking
about MS here!

 

[Bill Sanderson MVP]

What can I say? I know that this is getting looked at hard by good eyes.
They are interested in both WindowsUpdate log fragments from failures and in
MSI installer logs (if one is generated by the failed install--in my case,
it never got that far)--you have to turn on MSI logging via a KB article,
and there's some downside risk to leaving it on--it fills the temp space
with files over time.