I'm running into a frustrating issue with a fresh Windows 11 (23H2) installation. Every time I boot, I get a "Bad Image" error (code: 0xc000012f) related to `SecurityHealthSystray.exe`, which states that `SecurityHealthSSO.dll` is either not compatible or has an error. I also experience random BSODs with the error `SYSTEM_THREAD_EXCEPTION_NOT_HANDLED` (0x7E), generally pointing towards `ndis.sys`, typically occurring during network activity.
Interestingly, I've noticed my secondary Patriot 500GB SATA SSD is not being detected at all and I've disconnected it, suspecting it could be causing I/O problems. Despite running `sfc /scannow`, `DISM /CheckHealth`, and `DISM /ScanHealth`, all of which report no issues, the "Bad Image" error keeps showing up.
I've attempted two clean installs from USB, removed the problematic secondary SSD, and even reset the Security Health app using PowerShell. I believe Windows Update might be corrupting its own files during setup because the "Bad Image" state continues to linger even after removing the SSD. I'm currently downloading a fresh ISO to try another clean install or an in-place upgrade. Has anyone experienced a similar "Bad Image" error that SFC/DISM can't seem to fix? I'm looking for any advice before I go through the hassle of wiping everything again.
5 Answers
If you’re downloading a fresh ISO, look for a version that ensures updated drivers and fixes for issues like yours. It might help with that persistent Bad Image error. If you go through with another clean install, make sure to check the integrity of your hardware connections too—you never know if something might be off there.
It sounds like you're dealing with a tricky situation! First, make sure you're letting the updates complete during the OOBE setup stages. Sometimes skipping updates can lead to these kinds of issues. If you haven’t done a full offline install yet, that could help too. Also, consider remaking your install media in case the image you're using is corrupted. Trying a different USB port or even a different USB drive might solve the issue as well. There are quite a few variables at play, so it’s worth checking them all out.
I wonder if your installation media might be at fault. Have you considered a complete offline install? Using the OOBEBYPASSNRO command to skip WiFi setup might help as well. It’s also a good idea to double-check your USB drive and port for any issues—sometimes those can even lead to installation problems. If the error persist even after you've switched things up, let us know how it goes!
I suggest checking for any dump files after experiencing those BSODs. If you can boot into Windows, navigate to C:WindowsMinidump and look for any crash logs. You can zip the folder and upload it to a file-sharing site. Having multiple dump files really helps with diagnosing BSOD issues. If you don't see any dump files, try changing your settings to create small memory dumps. Those logs can provide valuable insights into what's going wrong.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures