Can't start VS.NET after Microsoft Update!!

[Martin Emanuelsson]

Hello,

I have a big problem which I hope you people can help me with.

When I try starting my VS.NET 2003 I get an error message saying:

Visual Studio .NET is unable to load because the file MSXML3.DLL cannot
be loaded.
Please see Knowledge base article Q306905 at
http://support.microsoft.com.

I've looked at this article but I don't believe that will solve my problem
since it talks about a beta version of MSXML 4.0, which I as far as I know
haven't installed on my computer. Which makes it impossible for me to even
get past the first step of the article, unregistering MSXML4.DLL.

I've downloaded and run the MSXML 3.0 Service Pack 5 files from Microsofts
download-sites but that hasn't fixed it.

I've also tried manually registering the msxml3.dll, which I've read on a
couple of pages should work, for instance here
(http://www.dotnet247.com/247reference/msgs/57/288859.aspx), but when I try
to do this I get another error message. I'm not very familiar with manually
registering DLL's but when I try to execute this command in a command
window, regsvr32 c:\winnt\system32\msxml3.dll, I get an error message saying
"LoadLibrary("C:\winnt\system32\msxml3.dll") failed - A dynamic link library
(DLL) initialization routine failed."

Can anyone please point me to the right direction to how to solve this?

By the way, this all started after I did a "Microsoft Update" instead of a
"Windows Update" which to me doesn't really makes sense. After that update I
first got an error message for my MSN Toolbar, and then I noticed that
VS.NET didn't work either. And after this happened the Windows Update only
shows a white page and the Microsoft update returns error code 0x8007045A.

Best regards
Martin Emanuelsson
Gothenburg, Sweden

[Martin Emanuelsson]

I believe I managed to solve it myself rather quickly, fortunately.

Stumbled across this KB article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;836982) and
followed Method 2 of the resolution part, and I think that solved my
problem.

Best regards
Martin

"Martin Emanuelsson" <martin.em...@guide.se> wrote in message
news:%23SXmqgs...@TK2MSFTNGP10.phx.gbl...

[Selva]

I exactly had the same issue what is posted here and I followed Method 2 of
KB article 836982 and it worked perfect.

Thanks Martin for your posting.

[brian...@gmail.com]

(http://support.microsoft.com/default.aspx?scid=kb;en-us;836982)
Yes, following Method 2 definitely worked for me.

-Brian