Member Avatar for vikyboss

I installed windowsxp repair pro 2007 , a software for keeping windows stable. I started running. After finished scanning, i click repair, a window pops up. Saying that "unhandeled exception occured, Common language runtime detected an invalid program" When i click details, it shows---
---------------------------------------------------------------------------------------------------------------------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidProgramException: Common Language Runtime detected an invalid program.
at b.f()
at g.dg(Object A_0, EventArgs A_1)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
XPRepairPro
Assembly Version:
Win32 Version:
CodeBase: file:///C:/Program%20Files/XP%20Repair%20Pro%202007/XPRepairPro.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version:
Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/__b77a5c561934e089/System.Xml.dll
----------------------------------------
CustomMarshalers
Assembly Version:
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


------------------------------------------------------------------------------

Could anyone please tell me how to fix this. Thanks.

  • 2 Contributors
  • 1 Reply
  • 272 Views
  • 20 Hours Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

A short, practical add-on to the thread from (and +1 to for suggesting vendor support): the exception you saw is a CLR/JIT failure — the runtime refused to compile a method because the IL or runtime state looked invalid. That can be caused by a bad/obfuscated third‑party binary, a bug in the app, or a damaged .NET installation. (stackoverflow.com)

Try this quick, ordered triage (each step can fix the problem without needing vendor help):

  1. Reboot, then run the XP Repair Pro executable as Administrator or reinstall the program (clean uninstall, reboot, reinstall).
  2. Repair the .NET installation: run the official Microsoft .NET Framework Repair Tool and/or use Windows to “repair” the installed .NET runtime or reinstall the specific .NET version the app needs. These are the supported Microsoft procedures. Repair the .NET Framework · Microsoft .NET Framework Repair Tool. (learn.microsoft.com)

If you only want to stop the popup (note: this does not fix the root cause), Just‑In‑Time debugging can be disabled in Visual Studio or by removing the JIT registry keys — but do that only after saving the error details for support. Microsoft documents these steps. (learn.microsoft.com)

Gather evidence before contacting the vendor: capture the .NET / Application events from Windows Event Viewer (Application log), note the exact .NET and OS versions, and reproduce the crash so timestamps match. Send those event entries to vendor support; they’ll usually ask for the same logs or a dump. How to check Event Viewer / .NET error entries. (learn.microsoft.com)

If the repair steps above don’t help, vendor support is the right next move (they may have a patched build).

Member Avatar for caperjack

looks like a question for "windowsxp repair pro 2007" tech support or even check there FAQ's link below ,i have never used or ever will use the program . fixes 60,000 errors ,if i had that many windows errors i would switch to watching TV.lol

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.