New
#1
Want to diagnose cause of system error 193.
Is there a tool that can tell me exactly why a particular .exe gets system error 193?
In my case, I have written a program that modifies an existing .exe and writes the modified file back out.
Right now, my program does nothing more than add 1000x to every section RVA and then adjust items in the header -- start of code, and entry point -- and clear the checksum. The tool also adjusts most items in the data directories; however, my input .exe has no data directories.
I have attached output from 'objdump -x' on the input and output files, in case you can spot something I failed to adjust.
Does Windows 10 validate the checksum on all executables now? Microsoft's PE format doc says
The following are checked for validation at load time: all drivers, any DLL loaded at boot time, and any DLL that is loaded into a critical Windows process.