Reply 100 of 185, by AngryLittleAlchemist
I somehow ended up going down a rabbit hole of supposed fixes to the "bad image error"(or at least that's what I think it's called?). I got recommended messing with Windows 10 updates because apparently a lot of the forced ones ruin compatibility with certain software so I had to go and stop delete the updates and then stop Microsoft from automatically downloading them, didn't work. Somehow that led to a Bios update being a possible fix, which I was skeptical of, and while that was easy to do it took me 10 minutes to realize that the BIOS wouldn't recognize my keyboard because it was in the USB 3.0 slot instead of the USB 2.0 slot. That didn't work either.
I downloaded the microsoft debug tool from the debug layer thread and I don't think that did anything (although honestly I'm pretty sure I didn't use it correctly). If there's one thing I've learned from all this it's that I'm in no way a computer expert ...
edit: Sorry, I know that i'm not being very helpful, no one here probably knows the answer, just thought i'd log it to be sure, and also to vent 😀 🤣
edit 2: I just tried scanning the DLL file, scanning windows files. Spent a bunch of time making commands that would unregister and re-register dlls, none of it worked. 😠