D
Doug JL
Temporary solution: Uninstalling update KB4592438 fixed the problem -- for now.
The problem is that I receive a "Bad Image" error when an application tries to open and loads a DLL, saying
"...dll is either not designed to run on Windows or it contains an error".
The application is over 20 years old, completely unsupported, something I use pretty much all day every day, and very important to me.
(Until now I've been impressed that Windows has continued to support it this long).
I'm guessing that this security update thinks there's something wrong and perhaps dangerous about the application.
How can I certify to the update that the application is OK?
"SFC /scannow" says all is well. Reloading the application produced the same result.
I don't see anything anywhere in the Event Viewer at the time of the problem.
No problems are reported by Microsoft Security.
Continue reading...
The problem is that I receive a "Bad Image" error when an application tries to open and loads a DLL, saying
"...dll is either not designed to run on Windows or it contains an error".
The application is over 20 years old, completely unsupported, something I use pretty much all day every day, and very important to me.
(Until now I've been impressed that Windows has continued to support it this long).
I'm guessing that this security update thinks there's something wrong and perhaps dangerous about the application.
How can I certify to the update that the application is OK?
"SFC /scannow" says all is well. Reloading the application produced the same result.
I don't see anything anywhere in the Event Viewer at the time of the problem.
No problems are reported by Microsoft Security.
Continue reading...