Target machine cant load drivers, bad image.

It was OK yesterday, then today it wouldnt connect to windbg, had to mess around with it, turned off defender, firewall, got it to connect, and now the sys file wont load, says it is a bad image.

Just tried the exact same binary on another win 10 x64 system and it loads OK of course, so it isnt the build, or external dependencies. The target is in test mode of course, with the test cert on it (as I said, this was working OK yesterday).

Any one else seen this weirdness?

This target PC is certainly a strange one!

Yep, didnt think this would get any response, it is pretty screwed up.