[FIXED] – MicrosoftSecurityApp.exe Bad Image Error 0xc0e90002 on Windows

With a long list of updates and regular bug fixes, Windows 11 still runs into various errors. One such perplexing issue is the MicrosoftSecurityApp.exe 0xc0e90002 bad image error. This strange error occurs in varied situations and for numerous reasons. However, users mostly encounter it right after a system boot.

Sometimes, the 0xc0e90002 blue screen of death follows a system crash. In some severe instances, the MicrosoftSecurityApp.exe 0xc0e90002 bad image error even results in bricked computers with inaccessible drives.

Let’s read about this error and methods to resolve it.

What is MicrosoftSecurityApp.exe 0xc0e90002 Bad Image Error?

As the name suggests, MicrosoftSecurityApp.exe is a system process associated with Microsoft Security Application. This application is vital in keeping our system safe from viruses and other threats. When encountering an unexpected problem, MicrosoftSecurityApp.exe could generate errors like the 0xc0e90002 error.

Reasons Behind the MicrosoftSecurityApp.exe 0xc0e90002 Bad Image Error

There could be numerous reasons behind the 0xc0e90002 error on your PC. Here are some of these –

• Malfunctioning MicrosoftSecurityApp.exe process
• Corrupted or missing system files
• A buggy system update
• Trying to run an incompatible application
• Malware infection

Methods to Fix the MicrosoftSecurityApp.exe 0xc0e90002 Bad Image Error on Windows 10/11

As the 0xc0e90002 blue screen error is unexpected, it can lead to loss of unsaved files, thereby hampering our workflow. To fix the MicrosoftSecurityApp.exe Bad Image Error 0xc0e90002 on your PC, you can try the following methods.

There are numerous situations in which a user encounters the 0xc0e90002 error code. However, most cases pertain to systems being either bootable but not stable or completely unbootable. Hence, we will broadly look at the methods under two scenarios – Bootable & Unbootable or crashed PC.

Scenario A: Bootable PC

Method 1: Perform a System-Wide Malware Scan

As mentioned earlier, a virus infection can easily cause the MicrosoftSecurityApp.exe Bad Image 0xc0e90002 error. You can fix this by performing a comprehensive system scan to identify and remove malicious applications or files.

Method 2: Disable Windows S Mode

Windows S mode is a built-in feature of Windows OS that enhances the security and performance of the system. While a system is in S mode, the computer only allows and utilizes apps from the Microsoft Store. Although this restriction adds another layer of security, it also creates problems like the 0xc0e90002 Bad Image error.

You can try disabling the Windows S mode to fix the 0xc0e90002 error code. Here’s what to do –

• Press WINDOWS + I to open the Settings app.
• Click on Update & Security.
• Click on Activation in the left pane.
• Find Switch to Windows 10/11 Home or Switch to Windows 10/11 Pro option.
• Click on the Open Store button to open the Microsoft Store.
• Click on Get.

• Follow the instructions on the screen to get out of the S mode.
• Reboot the computer.

If you were facing the 0xc0e90002 error pop-up while trying to run an application not installed from the Microsoft Store, disabling the S mode will help you run them. Many affected users could fix the MicrosoftSecurityApp.exe 0xc0e90002 Bad Image Error by disabling or switching out of the S mode.

Scenario 2: Unbootable PC

Method 1: Use a 16 or 32 GB Pen Drive as a Bootable Media

Many Windows insiders or beta testers who installed Windows 11 on their PCs encountered the 0xc0e90002 BSoD error while trying to switch back to Windows 10.

The error occurred when users used pen drives smaller than 16 GB or larger than 32 GB as installation drives. This is quite unexpected, as storage capacity should not be a factor for using the installation drive. The best explanation could be that Windows OS requires a 32GB partition in the boot drive.

To fix the MicrosoftSecurityApp.exe 0xc0e90002 Bad Image error, use a 16 GB or 32 GB flash drive to create a bootable media. Once it is done, use it to install Windows.

Also, if you face this issue on Windows 10 or 11, install Windows 8 on your PC and then upgrade it to Windows 10/11. Many users were able to fix the 0xc0e90002 error by doing this.

Method 2: Delete ‘Revoke’ Data

Some users reported facing the 0xc0e90002 blue screen of death after installing the Windows insider preview build. This resulted in an unbootable system, making your data inaccessible. Additionally, the error left the system unable to boot into the UEFI recovery environment.

This is a typical problem where even the Windows installation media drives fail to boot Windows installation. However, you can fix this issue by deleting the ‘Revoke’ data stored as EFI variables from the PC. Download the Shell_Full.efi from GitHub or any other reliable source. After that, carefully follow this guide to delete ‘Revoke’ information from your PC.

Note – If you are running 64-bit Windows OS Download the Shell_Full.efi X64. If 32-bit, then download the Shell_Full.efi Ia32.

How to Recover Data from an Unbootable or Crashed PC?

The methods explained above should help you resolve the 0xc0e90002 bad image error. However, if nothing works and your computer remains unbootable, you need to recover your data before it permanently gets lost. For this, you can use a professional data recovery software like Stellar Data Recovery Professional.

Thanks to its advanced data recovery algorithms and powerful features like bootable media recovery, it can easily recover files from an unbootable computer.

Once you have recovered your data, you can reinstall Windows on your PC.

Conclusion

The 0xc0e90002 bad image error occurs in multiple scenarios. This error prevents applications from opening or crashing the system, rendering the system unbootable. In both cases, the data present in the computer inches closer to data loss.

This post highlighted the reasons behind 0xc0e90002 bad image error and various methods to fix it. Finally, we came across a powerful file recovery tool that can aid us in recovering files from a computer crashed due to the 0xc0e90002 BSoD error.

Was this article helpful?

YES1

NO

About The Author

Keshav Katyal

A passionate writer, driven by his interest in everything tech, Keshav Katyal has always been captivated by the latest gadgets since childhood. His interest in gadgets grew when he got his first gaming console, the Nintendo Game Boy Advanced. Hours and days of tinkering with gadgets encouraged the inner geek in him who now loves writing about the latest technologies.