"techbird" <techbird@xxxxxx> wrote in message
>I have this same error. I unchecked the KB941649 update and installed the
> other updates (i.e. KB941600, KB941229, and KB905866) which all installed
> successfully.I then Installed the download patch for KB941649 (the 64 bit
> versio since I'm using the x64 version of Vista Home Premium). It says it
> installed successfully but still tries to install through Windows Update. But
> now I get an error 80070426 when it fails installation instead of the
> 8007007e error code. Could this change in error code be because I by-passed
> it and installed the other updates first or is the change of error code due
> to installing the download patch and then trying to install the Windows
> update for KB941649?
> I don't know if the other people who still have problem installing this
> update are getting a change in error code. But maybe all of you Vista Gurus
> out there might know something of this error code because all I can find
> pertaining to this error code is that a service isn't started. I don't know
> which one or how to get it started.
You're more likely to find Vista Gurus in Vista-specific newsgroups. ; )
Cross-posting to one for convenience of reference.
F:\>set /a c = 0x426
F:\>net helpmsg %c%
The service has not been started.
F:\>set /a c = 0x7e
F:\>net helpmsg %c%
The specified module could not be found.
As I always say, codes are useless without their context.
Otherwise, which service? Which module?
That's why I would Run... ProcMon to supplement the install logs.
> "Potter41" wrote:
>> I am getting the same problem on Vista Home Premium using Microsoft update.
>> I tried to solve it by installing the patch direct from KB941649 web page.
>> That said it installed successfully but the seemingly same patch from
>> Microsoft update still wants to install every time I boot up, but then fails.
>> I hope Microsoft are going to fix this soon.
>> "bariguy" wrote:
>> > I've been trying to install this patch on Windows Vista since it's release
>> > tuesday and I keep getting a failed status after it does all it's normal
>> > rebooting. The error is 8007007E apparently undocumented, unless someone can
>> > point me in the right direction.
>> > Thanks!