Subject Re: EXE will not run Windows 10 From Andy Taylor <andy.taylor.1959@outlook.com> Date Mon, 12 Oct 2020 07:05:30 -0400 Newsgroups dbase.getting-started Greg, If the same exe works on some machines running wndows10 then your thread heading is incorrect. Your dBASE executable does work under Windows10 and you can point to the machines where it can be seen to be working. Further, if you have installed the same dBASE runtime version on all the machines then you can say with certainty that the reason why 2 machines refuse to run it is that they are configured differently to the ones that do run it. Full stop.  It has nothing to do with dBASE. Show your IT guys the problem you are facing as you see it. If I were in your shoes (and I have been in similar positions in the past) I would invite them to come and figure out why the 2 rogue machines do not do what the other machines do (it is in their interests to make sure all the machines do the same thing as it makes their lives much easier). You can, of course, do your own detective work which would involve comparing and contrasting every single security setting within windows and any anti-virus or similar programs on the machines.  In Windows 10 that means going through all the settings you have access to especially those around app and browser control then checking out the AV programs in use if it's not just Windows Defender. This looks to me as if there is some software that checks every "exe" and says "yes you can run" or "No you can't and I'm shutting you down and not telling the user why".  That strongly points to a vanilla implementation of Anti-Virus software that is set to stop everything running except the programs "officially installed" by the IT crew.  What normally happens there is that the settings chosen override the normal question to the user "are you happy to run this software" which just never gets asked.  I seem to remember it was BitDefender that was involved the last time this happened to me (but my memory is hazy so it may not have been).   I know this isn't solving the issue but I hope it strengthens your case and your determination. Good luck, Andy > > Greg, > > > > I would start asking your "managed update" IT guys what software has recently come into the environment that will kill > > any exe stone dead that it does not recognise.  Usually Windows10 is set to ask the user if they are happy to run an exe > > that is outside normal parameters (i.e. certified code that MS recognises) but some paranoid IT crews that I have come across think that all users are cretins and need to be saved from themselves.... > > > > Hope that helps, > > Andy > > > > > Ken Mayer Wrote: > > > > > > > On 10/8/2020 12:51 PM, Greg Lockwood wrote: > > > > > Good to see a long time valued name like yourself still involved with dBase. I am using version 10.3.1.0 and build b2504 and BDE 5.2.0.2 I was thinking of upgrading but I wasn't sure it would fix the issue. Thanks. > > > > > > > > The application should run on Windows 10. Have you tried reinstalling > > > > the application? The runtime? > > > > > > > > While it's a long shot, you might check to see DEP settings (Data > > > > Execution Prevention). There's a small amount of detail here, although > > > > it shouldn't be a problem: > > > > > > > > http://www.goldenstag.net/dbase/#samplecode > > > > > > > > Otherwise, maybe someone else will have some ideas. > > > > > > > > Ken > > > > > > > > > > > > -- > > > > *Ken Mayer* > > > > Ken's dBASE Page: http://www.goldenstag.net/dbase > > > > The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp > > > > dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm > > > > dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm > > > > > > thanks Ken. I have uninstalled runtime and app. Same result. It has been running on win 10 for ages on 5 pc's but stopped recently on 2 machines and runs on my win 10 PC and 2 others still. I looked at DEP recently too but haven't check or studied up a lot. I will check this out. Thanks. > > > > > > Thanks Andy for your comments. I think it is something to do with a windows 10 update but of course IT are convinced it has nothing to do with them and it's the software. I have bit the bullet and upgraded to 2019.1 but have not yet tested a recompile EXE and runtime on either problem PC's. I am really hoping it's not an issue with the BDE because there are no updates. Hopefully in the next day or so it will be OK and then I will let the newsgroup know of the outcome. Hopefully a good result :)