On 2017-07-11 15:13, Tracy Pearson wrote:
mbsoftwaresolutions@mbsoftwaresolutions.com wrote on 2017-07-11:
On 2017-06-08 13:57, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
UPDATE FROM CLIENT:
"[Local IT guy] suggested trying to run the program in Windows 7 Compatibility mode. We tried that on several machines, including Billy K’s, and nothing ghosted. Hopefully that will continue to be the case and we can go forward happily. Suggest you have other customers switching to Windows 10 use 7 compatibility mode."
This still baffles me as to why/how this is happening on Win10 and is resolved by the Win7 Compatibility mode.
Mike,
We had a client do that to us. I remoted in to the workstation and found out the overzealous anti-virus was killing our application due to its "call home" feature. We check for an update to the current version periodically at start up.
When the customer put the program in Compatibility mode, it runs it with more administrative privileges and outside where anti-virus was able to determine it was running. To me, and suddenly aware the tech, it showed how that anti-virus can be avoided. The tech changed out the anti-virus on the computer and our software runs without being in compatibility mode.
Hi Tracy,
The only A/V software is the native Windows Defender, and we had programmed exclusions for all the VFP data file types as well as excluded the local app and network database folder.
Odd.