Share via

Microsoft Net Framework Error when opening pc

Anonymous
2023-07-28T10:57:26+00:00

Hello, anyone can help me to resolve this issue...See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.BadImageFormatException: Could not load file or assembly '12288 bytes loaded from WinZip, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format. File name: '12288 bytes loaded from WinZip, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' ---> System.BadImageFormatException: Operation did not complete successfully because the file contains a virus or potentially unwanted software. (Exception from HRESULT: 0x800700E1) at System.Reflection.RuntimeAssembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection, Boolean fSkipIntegrityCheck, SecurityContextSource securityContextSource) at System.AppDomain.Load(Byte[] rawAssembly) at ..(Object , EventArgs ) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.9167.0 built by: NET481REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- WinZip Assembly Version: 1.1.0.0 Win32 Version: 1.1.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/MSBuild/WinZip.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.9075.0 built by: NET481REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.9166.0 built by: NET481REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.9166.0 built by: NET481REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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: 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.

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Ramesh 176.2K Reputation points Volunteer Moderator
2023-07-28T13:12:53+00:00

Please run the fix list as follows.

  • Download FixList.txt
  • Save Fixlist.txt in the same folder where FRST64.exe is.
  • Close all program windows.
  • Launch the Farbar Scanner tool and click "Fix".
  • Upload the output log file (FixLog.txt) to your OneDrive.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

9 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-07-28T16:22:13+00:00

    Good day,

    Thanks you so much it resolves the also the issue.

    Keep up the good work. Kudos

    Was this answer helpful?

    0 comments No comments
  2. Ramesh 176.2K Reputation points Volunteer Moderator
    2023-07-28T16:11:07+00:00

    Please try clean booting to see if a third-party service is causing this issue.

    See How to perform a clean boot in Windows - Microsoft Support: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-07-28T16:08:13+00:00

    Good day,

    i have concern upon opening my pc when the windows log screen flash. i just need to wait 10-20sec before i can type my password. when pressing any keys on my keyboard its not working.

    how to resolve that issue.

    Thank you

    Was this answer helpful?

    0 comments No comments
  4. Ramesh 176.2K Reputation points Volunteer Moderator
    2023-07-28T15:51:43+00:00

    The rogue task has been removed, and that resolves the issue. Let me know if you have any questions.

    To remove files/folders created by the Farbar scanner, rename EnglishFRST64.exe to Uninstall.exe and run it. The procedure requires a reboot.

    Was this answer helpful?

    0 comments No comments