Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: A Windows Update instalation failled - Code 800706BE

100 views
Skip to first unread message

PA Bear [MS MVP]

unread,
Mar 22, 2009, 2:05:03 PM3/22/09
to
Are you currently running Vista or Vista SP1? <=just a question, not a
recommendation or suggestion

0X800706BE = RPC_S_CALL_FAILED
The remote procedure call failed.

Rough translation: Your computer cannot communicate with the update servers.

What anti-virus application or security suite is installed and is your
subscription current? Can you manually update this application?

What third-party firewall (if any) are you using?

Has a Norton or McAfee application ever been installed on this machine
(e.g., a free-trial version that came preinstalled when you bought it)?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


Carla wrote:
> My OS is Windows Vista Home Premium 32 bits and I've been having some
> problems with Windows Update; the application works but very, very slow
> (something like 1-2 hours to install a few updates with less of 100 MB!)
> and
> some updates fail to install.
> One of the updates that failed was the Windows Malicious Removal Tool
> Software (March 2009); I've checked in the Updates historical and the
> reason
> pointed for this failure was given the error code 800706BE.
>
> I've tried to find information on the net regarding this error code but
> the
> few information I found was not very clarifying for me.
> Can you please give me some tips regarding this error?
> Has anyone in this forum had the same problem?

caspie

unread,
Mar 30, 2009, 8:11:37 PM3/30/09
to
I am having the same problem, same operating systems, etc. I am using Panda
Internet Security. I only am having trouble with this one and Windows
Defender update for March 2009

trendless

unread,
Apr 10, 2010, 5:12:12 PM4/10/10
to

I'm getting the error on a Vista SP1 32-bit machine while trying to
install SP2 from the redistrib pkg; so it can't [solely] be
communication errors.

I also cannot complete an SFC; gets to 30-40% and fails quits with
"Windows Resource Protection could not complete the requested
operation". Windows Module Installer also crashes at the same time as
SFC if I'm logged in as a normal user that belongs to the administrator
group. I've temporarily activated the built-in administrator account
and am logged in as it to avoid administrator privilege issues, and when
I do SFC from here I can get a few % farther and Windows Module
Installer doesn't crash, but SFC still fails. I tried a chkdsk /r; it
ran overnight and presumably fixed errors, but didn't make any
difference.


The backstory is this:

Had malware, removed it. Was able to install SP2 successfully. Did
additional updates (upon shutdown), after having restarted and fully
completed SP2 installation. Then the system wouldn't reboot properly,
tried the automated startup repair, it failed. Restored to pre-SP2,
failed to restore properly, but the system does boot now. Have tried
repeatedly to reinstall SP2 (I know the redistrib works, I've used it on
myriad other systems successfully). Also tried restoring back farther,
but all restore points fail.


Also, SP2 failure code also includes:
'Error - RPC_S_CALL_FAILED(0x800706be)'


--
trendless
Posted via http://www.vistaheads.com

Ǝиçεl

unread,
Apr 10, 2010, 7:27:01 PM4/10/10
to
In most cases, the 0x800706BE error indicates that the Windows Modules
Installer [TrustedInstaller.exe] has failed.

That may be a sign of file corruption or be due to the presence of
'incompatible' software [ex: Security software such as an antivirus
program, security suite, or even malware]
-=-


"trendless" wrote:

> .
>

Ǝиçεl

unread,
Apr 10, 2010, 7:43:01 PM4/10/10
to

See MowGreen's reply in thread "A Windows Update instalation failled" in
the microsoft.public.windowsupdate dated 4/8/2009 3:17 PM PST
as started by 800706BE.


In most cases, the 0x800706BE error indicates that the Windows Modules
Installer [TrustedInstaller.exe] has failed.

That may be a sign of file corruption or be due to the presence of
'incompatible' software [ex: Security software such as an antivirus
program, security suite, or even malware]


MowGreen
======


Ǝиçεl
-=-

"trendless" wrote:

> .
>

0 new messages