error 0x80070420 won't allow update download

I am trying to download instant update. it will not allow it. error code
0x80070420

sooner,

Try reregistering msxml3.dll first ( that's an L, not a 1 )
1. Click Start.
2. Choose Run.
3. Type in the Open with: line

regsvr32 msxml3.dll

Click OK


If no joy, reregister these files :

1. Click Start.
2. Choose Run.
3. Type in the Open with: line (click OK after *each* line)

net stop wuauserv

regsvr32 wuapi.dll
regsvr32 wups.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wuweb.dll
regsvr32 jscript.dll
regsvr32 msxml3.dll
regsvr32 qmgr.dll
regsvr32 qmgrprxy.dll

net start wuauserv

HTH,
MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============


sooner wrote:

> I am trying to download instant update. it will not allow it. error code
> 0x80070420

Great Tip - Thanks - worked great

One small point, "regsvr32 qmgr.dll" yielded a small error stating
system could not find entry point.

PS. I am retired vol firefighter as well as previously had office in
World Trade on 79th floor. God bless and remember all firefighters -
those lostand those who give of themselves everyday to protect others.


--
mikeleibo
Posted via http://ms-os.com Forum to Usenet gateway

"mikeleibo" <> wrote in message
news:...
>
> Great Tip - Thanks - worked great
>
> One small point, "regsvr32 qmgr.dll" yielded a small error stating
> system could not find entry point.


There should be an entry point for DllRegisterServer in that module.
So the regsvr32.exe command should have worked cleanly.
(assuming I suppose you are using WUv6 with BITS)

It's possible that the error message is trying to interpret another symptom
with a dependent module but only that message is available to indicate that
there is a problem. E.g. if a dependent module was missing you would see
code 00000002 but if all the dependent modules are there and something
goes wrong in one of them perhaps that would be construed as a problem
with the registration of the main module; then reporting that the system could
not find the main entry point would be misleading but might be what actually
happens.

Similarly, unexpected environmental conditions could cause various
misleading error symptoms. E.g. problems with user authorization
or permissions could be misinterpreted as program failures instead
of being reported more precisely.

To check for such possibilities you could use DependencyWalker
with its Profiler feature to trace some of the .dll usage done by
the regsvr32.exe command with that operand.

In any case it may help to retry the same re-registration in a safe mode
boot, e.g. to ensure that the BITS service and other potentially interfering
programs would not be running when you tried it.


HTH

Robert Aldwinckle
---