In our stack, we have a rule base compiler which is an exe-file that generates bat-file and calls it. Yesterday, right after installing monthly updates from Microsoft, this compiler has stopped working properly on some of our Windows 7 sp1 x64 machines, throwing the «Applcation has stopped working» window at the moment of calling bat-file from exe. Bat-file ran fine separately. Neither UAC no Security Essentials deactivating helped, as well as running the stuff as Administrator. Finally, we got the soft working right after setting "Compatibility: Windows 7" for our exe. It seems that Microsoft has shipped a strange security update which treats exe-s that run bat-s as "bad". Our bat actually read registry, because it ran vsvars32.bat. Maybe an MS intern plays pranks? :) We didn't figure out what exactly the update it was, hope they'll fix the problem in a couple of weeks.
No comments:
Post a Comment