Debugging error message

Microsoft Windows

I know that there is a page in the support section trying to solve the
problem ver very similar to the one i have... but its not useful because it
tell me i should get the latest update for the media center... which i
already have... and had before the problem started.

The problem is that when i try to open Media Center... a mesesage box pops up.
it reads:
title bar:
ehshell.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be

Process id=0xf9c (3996), Thread id=0x930 (2352)

Click OK to terminate the application.
Click CANCEL to debug the application.

when i press CANCEL to debug... it tells me that a registered JIT debugger
is not available... and that an attempt to launch the JIT debugger resulted
in an error code of 0x2 (2). and tells me to check the computer settings...
and when i click retry to have the process wait while attaching a debugger
namually... nothing really happens... .and i really dont know what to do
next... does anyone have the same problem? and know of a way to fix it?
Yes, I have similar problems. I get the same message box, but with different
error codes, except for the debugger code(ox2)2. I get:

Process ID=ox100(256 Thread ID=ox80(128)

I also get an Execution error: ox7927eo3e when I first try to open MCE. Do
you remember how to find the page you are refering to? I have suspected
that this is related to Microsoft updates and/or Rollup 2 I've downloaded.
Please refer to my post (Bobcat321, 1-2-06, pg. 4 at this time,"Updates
causing fatal execution error").;en-us;820121

that's the link to the page i was refering to...
by the way... i ended up getting my media center to work by ATTEMPTING to
install the update"rollup 2"... but the sad thing is... even though it now
works... i still have to fix this debugging problem... because i can't update
it... AHHH

another thing you might want to try is downloading this
apparently it helped some people with similar problems as us according to a
person from the dell community... supposedly a similar problem is caused due
to spyware... which might be what's happened with me... because i had
uninstalled my spy sweeper recently... though i can't remember if i had this
problem before or after...

well.. i still haven't had any luck in fixing my problem... but i hope you
have a better luck...