.Net error

L

LMO

Hello all.
I started getting the following error upon bootup:
".NET Framework Initialization Error:
C:\Windows\Microsoft.NET\Framework\v1.1.4322\mscowrks.dll could not be
loaded"

What can I do to correct it? The error windows comes up as soon as the
first screen initializes upon bootup.
I found an article in the MS Knowledgebase about it
(http://support.microsoft.com/search...=.NET+Framework+Initialization+Error&x=8&y=13)
, but all it does is describe it, not say how to correct it. Anyone have any
idea how to correct this so I don't continually get that error msg on
bootup?
Thanks.
 
S

S.Sengupta

There are lots of reasons behind this error.Has it started after
installation of ATI Radeon graphic card?
You may install the .NET Service pack to fix the issue.
regards,
ssg MS-MVP
pronetworks.org
 
L

LMO

Okay, I found and installed the .NET SP on the MS update site. However, I am
still getting the same error upon reboot. Any other suggestions?
You were right. I installed an ATI Radeon 9600 card. Why would that affect
whatever this is?
Again, thanks.
 
A

Alex Nichol

LMO said:
Hello all.
I started getting the following error upon bootup:
".NET Framework Initialization Error:
C:\Windows\Microsoft.NET\Framework\v1.1.4322\mscowrks.dll could not be
loaded"

What can I do to correct it? The error windows comes up as soon as the
first screen initializes upon bootup.
I found an article in the MS Knowledgebase about it
(http://support.microsoft.com/search...=.NET+Framework+Initialization+Error&x=8&y=13)
, but all it does is describe it, not say how to correct it.

They confirm a bug in the .NET framework (mscorwks.dll is its main run
time library). Now if your message says specifically mscowrks.dll (a
file that does not exist) then there is a fault in the program you are
trying to run; if it is mscorwks then the program is hitting the bug.

Either way try to identify what program it is; Start - Run and run
MSConfig.exe; try identifying on the Startup page; copy Command column
entries into a Start - run to see if the message arises. Then uncheck
that line, and consult the people who provided the program, referring to
the KB article 327434

As far as the bug goes, MS have confirmed its existence but not yet got
as far even as a work-around
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top