Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll error?

[Allen Drake]

Allen Drake wrote:
On 1/13/2012 4:31 PM, Allen Drake wrote:
Today I got this pop up message:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll is
either not designed to run on Windows or it contains an error. Try
installing the program again using the original installation media or
contact your system administrator or the software vendor for support.

Now what in the world is this all about? Upon opening Outlook it went
through some reconfiguration something or other and opened. I can no
longer run iReboot and who knows how many other applications.

I tried system restore. Did not help so I undid that. I tried
removing iReboot and reinstalling but that didn't do anything. I still
get the popup and can not run iReboot. I looked for
Microsoft.NET\Framwork64\v2.0.5027 but that is not on the menu. I
searched for a fix but saw nothing that looked right but a bunch of
hoop jumping that seemed like it might take who knows how long.

Can anyone decipher this and explain to me what exactly went on? I
haven't installed any new apps other then Windows updates which now
seems to me to be my whole problem.

Did MS do it to me yet again?
<http://techtrickz.com/download/intelligently-re-boot-your-pc-into-another-os-with-ireboot/>


<copied>

iReboot works on Windows 7, Vista and XP (required .Net Framework 2 or
above for XP) and can be downloaded at here.

<end>

http://support.microsoft.com/kb/908077
<http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=6523>


Did you try to uninstall this IReboot and install it back?

You should call the software vendor for IReboot and discuss your course
of action concerning the error message.


As I mentioned in my post I removed iReboot and still got the error
message. I removed and .NET Framework 2 and tried reinstalling but it
says it is already on the system. Do you have any experience with this
error yourself or am I simply trying things like an Automobile
mechanic? Do you know the cause of this error? Everything was fine
until today which leads me to believe it was an MS Windows update
related problem. I would like to know the time I am spending is
something that has been verified and a known cure for a known
difficulty.

I have been using iReboot for many months with no problems so
obviously this is am MS generated mishap.

Yes? No? Unknown?

To me, it sounds like mscorwks.dll is corrupted.

One thing you can try, is the .NET verifier, which could
well run into the same kind of problem. It all depends on whether
there are enough test cases in this thing, to test loading
mscorwks or not.

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

https://skydrive.live.com/?cid=27e6a35d1a492af7&id=27E6A35D1A492AF7!376

"netfx_setupverifier_new 12/29/2011"

You'd want to verify .NET 2.0, judging by the error message. Yours
is likely patched to .NET 2.0 SP2.

I'd probably do a fair bit of testing, before arriving at a final
conclusion. For example, you could try a program like paint.net as
a test case. I was trying that yesterday, as part of some .NET
screwing around. It's an example of a program that uses .NET. You'd
need a lot more programs like this, to get some degree of test coverage
that the file is OK.

http://www.getpaint.net/download.html

http://www.dotpdn.com/files/Paint.NET.3.5.10.Install.zip

*******

The thing is, on an OS like Windows 7, a certain
level of .NET is installed as part of the basic
install. What that should mean, is it isn't listed
in the Add/Remove. Whereas, on an older OS like WinXP,
more of the .NET things would be removable from
Add/Remove.

My concern would be, removing too much of .NET and breaking
something bad enough you can't use the OS any more.

Is there a System File Checker for Windows 7 ? Would
.NET 2.0 be considered part of the OS, and covered by
something like that ?

http://answers.microsoft.com/en-us/...o-x3-pro/3e59db7b-14ad-4b23-b935-20ef20ed157d

This KB claims to help you run SFC on Windows 7, but
the content is a bit on the comedic side. Such as,
where exactly is the "known good" file in temp in this
article coming from ? Hahaha.

http://support.microsoft.com/kb/929833

Aaron Stebner also offers a cleanup tool.
But that would be about the last thing I'd try (and would
do a backup image before trying it). Read the caveats here
first, before trying it. You would also want the standalone
installers ready, to put it all back again.

http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

*******

These are files I can see on my laptop. My laptop is Home Premium SP1
patched up to date (has latest updates as of yesterday).

Windows/Microsoft.NET/Framework64/v2.0.50727

9,990,992 bytes July 08, 2011, 5:31:16 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 1:48:43 AM

Windows/Microsoft.NET/Framework/v2.0.50727

5,924,176 bytes July 08, 2011, 5:33:44 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 5:50:30 AM

It looks like the file is rather large, and there is one
for 64 bit and one for 32 bit cases. Your 64 bit one is failing.

I can generate checksums for the files. This article has the checksum tool.
Using the "-both" argument, gets both checksum types. Usually, only
one checksum is enough.

http://support.microsoft.com/kb/841290

x64 mscorwks.dll
MD5 = 951500ad4685b89423ab52665cadf653
SHA1 = d067dabb99bebc0c7aa10655b117864b287609ad

x32 mscorwks.dll
MD5 = 96076b8fcdff3c6db4ccfbf7fe3a9b28
SHA1 = 06b48a4df6ce00683a2fc2a488d39a74a7a32a6d

That should give you enough info to compare against my copy.

HTH,
Paul

To begin with running setupverifier shows:

[01/14/12,05:52:16] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:52:16] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,05:59:59] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:59:59] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,06:00:41] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:00:41] ****ERROR**** Verification failed for product .NET
Framework 3.0 SP2
[01/14/12,06:01:07] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:01:07] ****ERROR**** Verification failed for product .NET
Framework 3.5 SP1
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not
installed on the system
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is
not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\WPFFontCache_v0400.exe
is not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpftxt_v0400.dll
is not installed on the system
[01/14/12,06:02:35] SetupVerifier exiting with return value 0

It looks like I am missing much of what is needed as many of my apps
no longer work. Unless you have a solution as to how to restore what
somehow has been lost I am considering abandoning the install and
moving on. I just wish I knew what happened so I can avoid a
reoccurrence.

According to the description here, Stebners cleanup tool won't
remove dotnet files that came with the OS. The cleanup tool would
only remove things installed after a basic OS install (i.e. dotnet 4.0).

http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

It's possible they're covered by SFC, and this blog entry makes
mention of how to run sfc. Give SFC a try.

http://blogs.msdn.com/b/astebner/ar...es-and-registry-entries-on-windows-vista.aspx

Paul

I seem to have narrowed it down a bit. It now makes reference to
WebUpdater.exe but it must have a different name because I find no
such application on my system. I am thinking of removing app by app to
see where it might be attached to. I could always reinstall Win7 as it
would have taken less time then I have already lost with this
situation but for now I will keep looking including trying your latest
possible fixes.

As I mentioned in a previous post I am now seeing a failure of Event
Viewer to function.

"MMC could not create the snap-in"

Al.

 

[Allen Drake]

Allen Drake wrote:
On 1/13/2012 4:31 PM, Allen Drake wrote:
Today I got this pop up message:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll is
either not designed to run on Windows or it contains an error. Try
installing the program again using the original installation media or
contact your system administrator or the software vendor for support.

Now what in the world is this all about? Upon opening Outlook it went
through some reconfiguration something or other and opened. I can no
longer run iReboot and who knows how many other applications.

I tried system restore. Did not help so I undid that. I tried
removing iReboot and reinstalling but that didn't do anything. I still
get the popup and can not run iReboot. I looked for
Microsoft.NET\Framwork64\v2.0.5027 but that is not on the menu. I
searched for a fix but saw nothing that looked right but a bunch of
hoop jumping that seemed like it might take who knows how long.

Can anyone decipher this and explain to me what exactly went on? I
haven't installed any new apps other then Windows updates which now
seems to me to be my whole problem.

Did MS do it to me yet again?
<http://techtrickz.com/download/intelligently-re-boot-your-pc-into-another-os-with-ireboot/>


<copied>

iReboot works on Windows 7, Vista and XP (required .Net Framework 2 or
above for XP) and can be downloaded at here.

<end>

http://support.microsoft.com/kb/908077
<http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=6523>


Did you try to uninstall this IReboot and install it back?

You should call the software vendor for IReboot and discuss your course
of action concerning the error message.


As I mentioned in my post I removed iReboot and still got the error
message. I removed and .NET Framework 2 and tried reinstalling but it
says it is already on the system. Do you have any experience with this
error yourself or am I simply trying things like an Automobile
mechanic? Do you know the cause of this error? Everything was fine
until today which leads me to believe it was an MS Windows update
related problem. I would like to know the time I am spending is
something that has been verified and a known cure for a known
difficulty.

I have been using iReboot for many months with no problems so
obviously this is am MS generated mishap.

Yes? No? Unknown?

To me, it sounds like mscorwks.dll is corrupted.

One thing you can try, is the .NET verifier, which could
well run into the same kind of problem. It all depends on whether
there are enough test cases in this thing, to test loading
mscorwks or not.

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

https://skydrive.live.com/?cid=27e6a35d1a492af7&id=27E6A35D1A492AF7!376

"netfx_setupverifier_new 12/29/2011"

You'd want to verify .NET 2.0, judging by the error message. Yours
is likely patched to .NET 2.0 SP2.

I'd probably do a fair bit of testing, before arriving at a final
conclusion. For example, you could try a program like paint.net as
a test case. I was trying that yesterday, as part of some .NET
screwing around. It's an example of a program that uses .NET. You'd
need a lot more programs like this, to get some degree of test coverage
that the file is OK.

http://www.getpaint.net/download.html

http://www.dotpdn.com/files/Paint.NET.3.5.10.Install.zip

*******

The thing is, on an OS like Windows 7, a certain
level of .NET is installed as part of the basic
install. What that should mean, is it isn't listed
in the Add/Remove. Whereas, on an older OS like WinXP,
more of the .NET things would be removable from
Add/Remove.

My concern would be, removing too much of .NET and breaking
something bad enough you can't use the OS any more.

Is there a System File Checker for Windows 7 ? Would
.NET 2.0 be considered part of the OS, and covered by
something like that ?

http://answers.microsoft.com/en-us/...o-x3-pro/3e59db7b-14ad-4b23-b935-20ef20ed157d

This KB claims to help you run SFC on Windows 7, but
the content is a bit on the comedic side. Such as,
where exactly is the "known good" file in temp in this
article coming from ? Hahaha.

http://support.microsoft.com/kb/929833

Aaron Stebner also offers a cleanup tool.
But that would be about the last thing I'd try (and would
do a backup image before trying it). Read the caveats here
first, before trying it. You would also want the standalone
installers ready, to put it all back again.

http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

*******

These are files I can see on my laptop. My laptop is Home Premium SP1
patched up to date (has latest updates as of yesterday).

Windows/Microsoft.NET/Framework64/v2.0.50727

9,990,992 bytes July 08, 2011, 5:31:16 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 1:48:43 AM

Windows/Microsoft.NET/Framework/v2.0.50727

5,924,176 bytes July 08, 2011, 5:33:44 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 5:50:30 AM

It looks like the file is rather large, and there is one
for 64 bit and one for 32 bit cases. Your 64 bit one is failing.

I can generate checksums for the files. This article has the checksum tool.
Using the "-both" argument, gets both checksum types. Usually, only
one checksum is enough.

http://support.microsoft.com/kb/841290

x64 mscorwks.dll
MD5 = 951500ad4685b89423ab52665cadf653
SHA1 = d067dabb99bebc0c7aa10655b117864b287609ad

x32 mscorwks.dll
MD5 = 96076b8fcdff3c6db4ccfbf7fe3a9b28
SHA1 = 06b48a4df6ce00683a2fc2a488d39a74a7a32a6d

That should give you enough info to compare against my copy.

HTH,
Paul

To begin with running setupverifier shows:

[01/14/12,05:52:16] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:52:16] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,05:59:59] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:59:59] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,06:00:41] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:00:41] ****ERROR**** Verification failed for product .NET
Framework 3.0 SP2
[01/14/12,06:01:07] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:01:07] ****ERROR**** Verification failed for product .NET
Framework 3.5 SP1
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not
installed on the system
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is
not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\WPFFontCache_v0400.exe
is not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpftxt_v0400.dll
is not installed on the system
[01/14/12,06:02:35] SetupVerifier exiting with return value 0

It looks like I am missing much of what is needed as many of my apps
no longer work. Unless you have a solution as to how to restore what
somehow has been lost I am considering abandoning the install and
moving on. I just wish I knew what happened so I can avoid a
reoccurrence.

According to the description here, Stebners cleanup tool won't
remove dotnet files that came with the OS. The cleanup tool would
only remove things installed after a basic OS install (i.e. dotnet 4.0).

http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

It's possible they're covered by SFC, and this blog entry makes
mention of how to run sfc. Give SFC a try.

http://blogs.msdn.com/b/astebner/ar...es-and-registry-entries-on-windows-vista.aspx

Paul

After running SFC I need to view CBS.log (txt) but can not access
this file. Do you know how to gain access?

Al.

 

[Ed Cryer]

I am about to give it up. I started opening a few apps. I found some
that wouldn't run so I removed them either with their uninstall
feature or from Windows Control Panel. I still have many left to try.
All have been there long before the problem started. I am tired of
debugging another version of Windows that seems to have gone corrupt
possibly from Windows Update. I know understand why many have gone to
Linux. I have a few other systems that are running cleaner Win7 setups
that I think I will use and let this sit while I take a rest from this
MS BS.

I went to Windows update and found some downloads that were not
available until now regarding different .NET versions so I let WU have
it's way with my machine. It may have helped or not. I am not sure at
this time.

I also noticed Event Viewer is hosed so I have a whole different
situation to search about.

(Big Red X)

MMC could not create the snap-in. The snap-in might not have been
installed correctly.

Name: Event Viewer

CLSID: FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}

I feel your pain here. And I think it's about time for a restore or a
re-install.
You've got to the point where more and more errors are being revealed at
each new look inside, and all the joy's gone from using your computer.
You could limp on for a while until you feel like hurling the box at the
wall; or you could agree with my conclusion.

I'd do the following. (Excuse me if I've missed a post or two of your
problems.)
1. sfc /VERIFYONLY in Command Prompt; to get some idea of the extent of
system corruption. Should take about 5 minutes.
2. Consider when problem started, and look for a restore point before then.
3. Simply reformat and re-install Windows and everything.

There are lots of very helpful and knowledgeable people in this group
who will help you through. But the 3 above are far simpler than the
individual errors you're reporting. And the building process itself will
heal your dampened spirits and confidence.

Ed

 

[Allen Drake]

I feel your pain here. And I think it's about time for a restore or a
re-install.
You've got to the point where more and more errors are being revealed at
each new look inside, and all the joy's gone from using your computer.
You could limp on for a while until you feel like hurling the box at the
wall; or you could agree with my conclusion.

I'd do the following. (Excuse me if I've missed a post or two of your
problems.)
1. sfc /VERIFYONLY in Command Prompt; to get some idea of the extent of
system corruption. Should take about 5 minutes.
2. Consider when problem started, and look for a restore point before then.
3. Simply reformat and re-install Windows and everything.

There are lots of very helpful and knowledgeable people in this group
who will help you through. But the 3 above are far simpler than the
individual errors you're reporting. And the building process itself will
heal your dampened spirits and confidence.

Ed

Well Ed, I am not at wits end because I have a new System on standby
that is never used. A much newer and faster machine that is just
sitting on a desk a few feet from me now. I also new laptop to my left
that has not been used since I got it in the spring. All have Win7
installed and the laptop has all my email in Outlook waiting for me to
open. I can walk away from this beast and not notice a single loss of
a single app. I also have an clone of this system from a few months
back if I want to take the time to install it. I have cloned drives in
my other new systems already installed also if I fell like firing
either of them up right now. I just like this chair and would hate to
rearrange my sitting configuration so I am well prepared.

I did run SFC and got to a point where I was about to read a log but
it won't let me so I have to figure out how to access it. That is
where things stand right now. I guess I will continue to screw around
with this disaster and see what ultimately happens. Maybe this is why
they call this OS Windows 7 Ultimate

If I didn't already post this in this thread I got rid of the popup
about .NET not being happy by using MSCONFIG and disabling some on the
useless apps so I can actually leave it at that if I can figure out
how to get Event Viewer to respond. That is what led me to wonder if I
can simply move that MMC.exe app from another system. I can't find
MMC.exe/config file so maybe that won't work after all.

Thanks for the reply. I hate to turn this situation into an EPIC so
if there are no other suggestions from anyone I will just turn out the
lights and fans and move over one seat to my right.

Al.

 

[Ed Cryer]

Well Ed, I am not at wits end because I have a new System on standby
that is never used. A much newer and faster machine that is just
sitting on a desk a few feet from me now. I also new laptop to my left
that has not been used since I got it in the spring. All have Win7
installed and the laptop has all my email in Outlook waiting for me to
open. I can walk away from this beast and not notice a single loss of
a single app. I also have an clone of this system from a few months
back if I want to take the time to install it. I have cloned drives in
my other new systems already installed also if I fell like firing
either of them up right now. I just like this chair and would hate to
rearrange my sitting configuration so I am well prepared.

I did run SFC and got to a point where I was about to read a log but
it won't let me so I have to figure out how to access it. That is
where things stand right now. I guess I will continue to screw around
with this disaster and see what ultimately happens. Maybe this is why
they call this OS Windows 7 Ultimate

If I didn't already post this in this thread I got rid of the popup
about .NET not being happy by using MSCONFIG and disabling some on the
useless apps so I can actually leave it at that if I can figure out
how to get Event Viewer to respond. That is what led me to wonder if I
can simply move that MMC.exe app from another system. I can't find
MMC.exe/config file so maybe that won't work after all.

Thanks for the reply. I hate to turn this situation into an EPIC so
if there are no other suggestions from anyone I will just turn out the
lights and fans and move over one seat to my right.

Al.

You're a pioneer, sir; and you obviously have the stamina for the
journey. That puts a completely different picture on it.

My machine is only a couple of months old, including the Win7 HP.
MMC.exe has the following details;
File version 6.1.7600.16385
Date modified 14/07/2009 02.39

in Windows/ System32 folder, and definitely up to date.

Check details before copying.
But maybe a Windows repair install would clear all your problems.


Ed

 

[Char Jackson]

Well Ed, I am not at wits end because I have a new System on standby
that is never used. A much newer and faster machine that is just
sitting on a desk a few feet from me now. I also new laptop to my left
that has not been used since I got it in the spring. All have Win7
installed and the laptop has all my email in Outlook waiting for me to
open. I can walk away from this beast and not notice a single loss of
a single app. I also have an clone of this system from a few months
back if I want to take the time to install it. I have cloned drives in
my other new systems already installed also if I fell like firing
either of them up right now. I just like this chair and would hate to
rearrange my sitting configuration so I am well prepared.

I did run SFC and got to a point where I was about to read a log but
it won't let me so I have to figure out how to access it. That is
where things stand right now. I guess I will continue to screw around
with this disaster and see what ultimately happens. Maybe this is why
they call this OS Windows 7 Ultimate

If I didn't already post this in this thread I got rid of the popup
about .NET not being happy by using MSCONFIG and disabling some on the
useless apps so I can actually leave it at that if I can figure out
how to get Event Viewer to respond. That is what led me to wonder if I
can simply move that MMC.exe app from another system. I can't find
MMC.exe/config file so maybe that won't work after all.

Thanks for the reply. I hate to turn this situation into an EPIC so
if there are no other suggestions from anyone I will just turn out the
lights and fans and move over one seat to my right.

Is there a lesson to be learned here?

In situations like this, I like to remind (some of) my customers to
just use the computer the way it was intended to be used. Don't be too
eager to mess around in the Registry, don't get excited about
msconfig, don't go exploring the inner folders on the Windows drive,
and so on.

None of that may apply to you, but I feel better having said it.

 

[Paul]

After running SFC I need to view CBS.log (txt) but can not access
this file. Do you know how to gain access?

Al.

I tried running SFC here.

1) Go to start and type in "cmd". When the search finds it, right click
and select "Run as Administrator".

2) In the MSDOS window, I tried

sfc /verifyonly

3) Next, I tried to search the C: drive to find the log, and only
found one reference to a file of that name.

4) I navigated manually to:

C:\WINDOWS\logs\CBS\CBS.log

If I double-clicked on that in a file explorer window, it said

"Access Denied".

5) Next, I went back to the administrator-level MSDOS window. The "dir"
was to verify the file was present, before opening it.

cd \
cd WINDOWS\logs\CBS
dir
notepad CBS.log

That time, it opened, and I could scroll to the bottom and look at
the results. Since no probs were found, the log entry was pretty short.

That file also appeared to be actively being used for some other
maintenance activity in the background. I suspect running sfc isn't
completely above board - I saw a few complaints when I shut down the
laptop just now about something it was still doing.

In any case, that'll give you access to the file.

*******

Your mmc snapin problem could be a file problem or a registry problem,
and I'd be tempted to think "registry" for some reason. It really
depends on whether you feel that there is massive file damage or not.
Perhaps it's malware that is doing it ? I would think malware
disabling mmc would be useful for it, to prevent you from analyzing
what is going on.

I'd probably be using my Kaspersky offline AV scanner right about now,
just to be sure. Having a couple different areas attacked is... unusual.

Paul

 

[Allen Drake]

You're a pioneer, sir; and you obviously have the stamina for the
journey. That puts a completely different picture on it.

My machine is only a couple of months old, including the Win7 HP.
MMC.exe has the following details;
File version 6.1.7600.16385
Date modified 14/07/2009 02.39

in Windows/ System32 folder, and definitely up to date.

Check details before copying.
But maybe a Windows repair install would clear all your problems.


Ed

Yes, that did cross my mind. Most times I would have just replaced
this drive with a clone and be done with it. A clean install would
have taken less time. I had no idea that things were so screwed up and
after reading all those that have been having .NET problems for so
long and finding no solution. This was one reason I finally moved up
from XP but I see some things will never change with MS quality
control.

 

[Allen Drake]

Is there a lesson to be learned here?

In situations like this, I like to remind (some of) my customers to
just use the computer the way it was intended to be used. Don't be too
eager to mess around in the Registry, don't get excited about
msconfig, don't go exploring the inner folders on the Windows drive,
and so on.

None of that may apply to you, but I feel better having said it.

I totally agree. I had been very reluctant to do anything with this
relatively new install and left everything very much alone. That has
been my whole approach and why I have several Win7 machines. All have
their own purpose in life and never get bloated with applications that
are not needed. This is the only one I use to go online with and only
now that I got my first indication of non compliance was I forced into
search and repair mode. Now that I have spent so much time searching
for a fix for this and that have I seen so many others with as many
problems as there ever was with any other version of Windows.

Some might call Win7 progress. I call it BAU @ MS.

 

[Allen Drake]

I tried running SFC here.

1) Go to start and type in "cmd". When the search finds it, right click
and select "Run as Administrator".

2) In the MSDOS window, I tried

sfc /verifyonly

3) Next, I tried to search the C: drive to find the log, and only
found one reference to a file of that name.

4) I navigated manually to:

C:\WINDOWS\logs\CBS\CBS.log

If I double-clicked on that in a file explorer window, it said

"Access Denied".

5) Next, I went back to the administrator-level MSDOS window. The "dir"
was to verify the file was present, before opening it.

cd \
cd WINDOWS\logs\CBS
dir
notepad CBS.log

That time, it opened, and I could scroll to the bottom and look at
the results. Since no probs were found, the log entry was pretty short.

That file also appeared to be actively being used for some other
maintenance activity in the background. I suspect running sfc isn't
completely above board - I saw a few complaints when I shut down the
laptop just now about something it was still doing.

In any case, that'll give you access to the file.

*******

Your mmc snapin problem could be a file problem or a registry problem,
and I'd be tempted to think "registry" for some reason. It really
depends on whether you feel that there is massive file damage or not.
Perhaps it's malware that is doing it ? I would think malware
disabling mmc would be useful for it, to prevent you from analyzing
what is going on.

I'd probably be using my Kaspersky offline AV scanner right about now,
just to be sure. Having a couple different areas attacked is... unusual.

Paul

Thanks yet again Paul. I will give it a do over and try what worked
for you. I will also go with a some malware apps in safe mode. I will
post back when I have some results. Most likely sometime during the
week. I have another 60hr work week ahead that I am really looking
forward to. Man I love my job

 

[Ed Cryer]

Is there a lesson to be learned here?

In situations like this, I like to remind (some of) my customers to
just use the computer the way it was intended to be used. Don't be too
eager to mess around in the Registry, don't get excited about
msconfig, don't go exploring the inner folders on the Windows drive,
and so on.

None of that may apply to you, but I feel better having said it.

Ah, man, you're taking the fun away. I think Allen's like me. We have
more fun playing with the system settings than anything else.
I suppose he's in the same situation as I am; with a couple of stand-by
machines ready for instant use for the email exchange and such like.

And before you lay into either of us, just pay attention to all the
things Paul does with his stuff. He performs a great public service, and
he often needs to stretch his system to the limits to help the poor punters.

Ed

 

[Char Jackson]

Yes, that did cross my mind. Most times I would have just replaced
this drive with a clone and be done with it. A clean install would
have taken less time. I had no idea that things were so screwed up and
after reading all those that have been having .NET problems for so
long and finding no solution. This was one reason I finally moved up
from XP but I see some things will never change with MS quality
control.

Why do you think it's a quality control issue? If that were the case,
wouldn't more people be affected?

 

[Char Jackson]

Ah, man, you're taking the fun away. I think Allen's like me. We have
more fun playing with the system settings than anything else.
I suppose he's in the same situation as I am; with a couple of stand-by
machines ready for instant use for the email exchange and such like.

And before you lay into either of us, just pay attention to all the
things Paul does with his stuff. He performs a great public service, and
he often needs to stretch his system to the limits to help the poor punters.

I have no problem with anyone intentionally screwing up their system
and don't mean to take any fun away. I just hate to see problems
blamed on external sources, though, when it seems more likely that the
real problem is much closer to home. ;-)

 

[Paul]

I have another 60hr work week ahead that I am really looking
forward to. Man I love my job

Well, the other option would be "not having a job".
And then where would you be ?

Paul

 

[Gene E. Bloch]

I did run SFC and got to a point where I was about to read a log but
it won't let me so I have to figure out how to access it. That is
where things stand right now. I guess I will continue to screw around
with this disaster and see what ultimately happens. Maybe this is why
they call this OS Windows 7 Ultimate

OK, I got a good laugh out of that last remark!

And I'm pleased to see that you're handling it with a good bit of
humor, since such messes can be depressing...

 

[Gene E. Bloch]

On Sun, 15 Jan 2012 16:41:42 +1100, John Morrison

Allen Drake wrote:
On 1/13/2012 4:31 PM, Allen Drake wrote:
Today I got this pop up message:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll is
either not designed to run on Windows or it contains an error. Try
installing the program again using the original installation media or
contact your system administrator or the software vendor for support.

Now what in the world is this all about? Upon opening Outlook it went
through some reconfiguration something or other and opened. I can no
longer run iReboot and who knows how many other applications.

I tried system restore. Did not help so I undid that. I tried
removing iReboot and reinstalling but that didn't do anything. I still
get the popup and can not run iReboot. I looked for
Microsoft.NET\Framwork64\v2.0.5027 but that is not on the menu. I
searched for a fix but saw nothing that looked right but a bunch of
hoop jumping that seemed like it might take who knows how long.

Can anyone decipher this and explain to me what exactly went on? I
haven't installed any new apps other then Windows updates which now
seems to me to be my whole problem.

Did MS do it to me yet again?

<http://techtrickz.com/download/intelligently-re-boot-your-pc-into-another-os-with-ireboot/>


<copied>

iReboot works on Windows 7, Vista and XP (required .Net Framework 2 or
above for XP) and can be downloaded at here.

<end>

http://support.microsoft.com/kb/908077
<http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=6523>


Did you try to uninstall this IReboot and install it back?

You should call the software vendor for IReboot and discuss your course
of action concerning the error message.


As I mentioned in my post I removed iReboot and still got the error
message. I removed and .NET Framework 2 and tried reinstalling but it
says it is already on the system. Do you have any experience with this
error yourself or am I simply trying things like an Automobile
mechanic? Do you know the cause of this error? Everything was fine
until today which leads me to believe it was an MS Windows update
related problem. I would like to know the time I am spending is
something that has been verified and a known cure for a known
difficulty.

I have been using iReboot for many months with no problems so
obviously this is am MS generated mishap.

Yes? No? Unknown?


To me, it sounds like mscorwks.dll is corrupted.

One thing you can try, is the .NET verifier, which could
well run into the same kind of problem. It all depends on whether
there are enough test cases in this thing, to test loading
mscorwks or not.

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

https://skydrive.live.com/?cid=27e6a35d1a492af7&id=27E6A35D1A492AF7!376

"netfx_setupverifier_new 12/29/2011"

You'd want to verify .NET 2.0, judging by the error message. Yours
is likely patched to .NET 2.0 SP2.

I'd probably do a fair bit of testing, before arriving at a final
conclusion. For example, you could try a program like paint.net as
a test case. I was trying that yesterday, as part of some .NET
screwing around. It's an example of a program that uses .NET. You'd
need a lot more programs like this, to get some degree of test coverage
that the file is OK.

http://www.getpaint.net/download.html

http://www.dotpdn.com/files/Paint.NET.3.5.10.Install.zip

*******

The thing is, on an OS like Windows 7, a certain
level of .NET is installed as part of the basic
install. What that should mean, is it isn't listed
in the Add/Remove. Whereas, on an older OS like WinXP,
more of the .NET things would be removable from
Add/Remove.

My concern would be, removing too much of .NET and breaking
something bad enough you can't use the OS any more.

Is there a System File Checker for Windows 7 ? Would
.NET 2.0 be considered part of the OS, and covered by
something like that ?

http://answers.microsoft.com/en-us/...o-x3-pro/3e59db7b-14ad-4b23-b935-20ef20ed157d

This KB claims to help you run SFC on Windows 7, but
the content is a bit on the comedic side. Such as,
where exactly is the "known good" file in temp in this
article coming from ? Hahaha.

http://support.microsoft.com/kb/929833

Aaron Stebner also offers a cleanup tool.
But that would be about the last thing I'd try (and would
do a backup image before trying it). Read the caveats here
first, before trying it. You would also want the standalone
installers ready, to put it all back again.

http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

*******

These are files I can see on my laptop. My laptop is Home Premium SP1
patched up to date (has latest updates as of yesterday).

Windows/Microsoft.NET/Framework64/v2.0.50727

9,990,992 bytes July 08, 2011, 5:31:16 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 1:48:43 AM

Windows/Microsoft.NET/Framework/v2.0.50727

5,924,176 bytes July 08, 2011, 5:33:44 PM mscorwks.dll
2.0.50727.5448 (Win7SP1GDR.050727-5400)
Digital signature July 07, 2011 5:50:30 AM

It looks like the file is rather large, and there is one
for 64 bit and one for 32 bit cases. Your 64 bit one is failing.

I can generate checksums for the files. This article has the checksum
tool. Using the "-both" argument, gets both checksum types. Usually, only
one checksum is enough.

http://support.microsoft.com/kb/841290

x64 mscorwks.dll
MD5 = 951500ad4685b89423ab52665cadf653
SHA1 = d067dabb99bebc0c7aa10655b117864b287609ad

x32 mscorwks.dll
MD5 = 96076b8fcdff3c6db4ccfbf7fe3a9b28
SHA1 = 06b48a4df6ce00683a2fc2a488d39a74a7a32a6d

That should give you enough info to compare against my copy.

HTH,
Paul

To begin with running setupverifier shows:

[01/14/12,05:52:16] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:52:16] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,05:59:59] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,05:59:59] ****ERROR**** Verification failed for product .NET
Framework 2.0 SP2
[01/14/12,06:00:41] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:00:41] ****ERROR**** Verification failed for product .NET
Framework 3.0 SP2
[01/14/12,06:01:07] ****ERROR**** Process 'Netfx20TestApplication.exe'
exited with return code -2147024703
[01/14/12,06:01:07] ****ERROR**** Verification failed for product .NET
Framework 3.5 SP1
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not
installed on the system
[01/14/12,06:01:27] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is
not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\WPFFontCache_v0400.exe
is not installed on the system
[01/14/12,06:01:28] ***WARNING*** File
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpftxt_v0400.dll
is not installed on the system
[01/14/12,06:02:35] SetupVerifier exiting with return value 0

It looks like I am missing much of what is needed as many of my apps
no longer work. Unless you have a solution as to how to restore what
somehow has been lost I am considering abandoning the install and
moving on. I just wish I knew what happened so I can avoid a
reoccurrence.

Have you heard about snipping?

I've heard of it. So why didn't YOU do it?

Wahahahaha...................

 

[Allen Drake]

Why do you think it's a quality control issue? If that were the case,
wouldn't more people be affected?

I guess in with the case and track record of MS OSes it would be a
beta thing. The beta testers are the quality control people. I doubt
everyone would ever be affected by most problems that pop up. I think
the problem is with Windows Update. If one fails during an install who
knows what could happen. I do know the .NET problems have been around
since the beginning and I have seen many posts that don't end well.
These updates never seem to be called fixes. I wonder why that is?

 

[Allen Drake]

OK, I got a good laugh out of that last remark!

And I'm pleased to see that you're handling it with a good bit of
humor, since such messes can be depressing...

I've been there so I know what to stay away from. Can't take the
world serious now can we?

 

[Allen Drake]

Well, the other option would be "not having a job".
And then where would you be ?

Paul

Oh, I've been there before. No fun at all. I have been in the work
force for almost 50 years now and plan on putting in another 10 or 20
if I can. That's how much I enjoy what I do.

 

[Allen Drake]

I tried running SFC here.

1) Go to start and type in "cmd". When the search finds it, right click
and select "Run as Administrator".

2) In the MSDOS window, I tried

sfc /verifyonly

3) Next, I tried to search the C: drive to find the log, and only
found one reference to a file of that name.

4) I navigated manually to:

C:\WINDOWS\logs\CBS\CBS.log

If I double-clicked on that in a file explorer window, it said

"Access Denied".

5) Next, I went back to the administrator-level MSDOS window. The "dir"
was to verify the file was present, before opening it.

cd \
cd WINDOWS\logs\CBS
dir
notepad CBS.log

That time, it opened, and I could scroll to the bottom and look at
the results. Since no probs were found, the log entry was pretty short.

That file also appeared to be actively being used for some other
maintenance activity in the background. I suspect running sfc isn't
completely above board - I saw a few complaints when I shut down the
laptop just now about something it was still doing.

In any case, that'll give you access to the file.

*******

Your mmc snapin problem could be a file problem or a registry problem,
and I'd be tempted to think "registry" for some reason. It really
depends on whether you feel that there is massive file damage or not.
Perhaps it's malware that is doing it ? I would think malware
disabling mmc would be useful for it, to prevent you from analyzing
what is going on.

I'd probably be using my Kaspersky offline AV scanner right about now,
just to be sure. Having a couple different areas attacked is... unusual.

Paul

I just had time to look at CBS.log and it is long and hard to
understand what it all means. I will have to go over it again later
tonight to see if I can make anything out of it.

The event viewer problem references a registry key.

CLSID: FX:{b00566ad-fe9c-4363-be05-7a4cbb7cb510}

Whatever that means.