How to Make Microsoft Dynamics GP Play Well With Windows 10: Two Experts Dive In

That seems to be the case when it comes to running a range of existing versions of Microsoft Dynamics GP on machines that have been upgraded to run Windows 10, Microsoft’s new operating system. Two Dynamics GP veterans have been grappling with this problem, and they have also shared their discoveries and fixes.

Dynamics GP MVP Mariano Gomez, EVP of Midmarket Solutions at Intelligent Partnerships, LLC reported that he recently ran across a post in a partner forum written by consultant who described a slow performance issue when closing (exiting) Microsoft Dynamics GP 2015. Apparently, the problem started when the consultants’ client upgraded the company’s Windows workstations to Windows 10.

And other users were having the same issue.

A Microsoft support engineer acknowledged that “there have been a few people experiencing this issue,” according to Gomez. “The recommendation to bypass the slow application closing is to change or add the following Dex.ini setting to see if it resolves the issue on exit. The setting changes a Microsoft Dynamics GP global variable and avoids the pause that seems to be occurring during the exiting process.”

Gomez details the fix here but cautions you should only make the changes to your environment if you are having the same problem.’

Over on the Winthrop Development Consultants blog, GP veteran David Musgrave said that he has been noticing performance issues now that he’s developing for Dynamics GP and Dexterity on Windows 10.

Musgrave said the “pause on exit” problem was occurring in both the runtime and development environments of Dynamics GP 2010, GP 2013 and GP 2015. He also noted he didn’t have this issue on his other Windows 10 machine, only on his primary development machine.

He provides a workaround in his blog post. However, after resolving the pause on exit issue Musgrave said he noticed that Dexterity and Dynamics GP where still very sluggish when running.

“It was taking much too long to log in and everything was like I was running through molasses,” he wrote. “Checking the Task Manager, I could see fairly high CPU usage. Sorting by the CPU column, the culprit was the Antimalware Service Executable. This Windows process is the real-time processing component for Windows Defender.”

Musgrave said this isn’t the first time anti-virus or malware solutions cause performance issues for Dynamics GP and Dexterity. He said the easiest way to resolve them is to add some exclusions to the settings for the application.

He takes you through the steps here.

“I know adding exclusions weakens your protection, but it does stop you pouring a liquid into the machine in the hopes of dissolving the molasses,” he noted.