Solving Performance Problems with Microsoft Dynamics GP and Windows 10 – Part 2

David Meego - Click for blog homepageFollowing on from my previous post: Solving Performance Problems with Microsoft Dynamics GP and Windows 10 – Part 1, I was still not happy with the performance of Dexterity and Microsoft Dynamics GP on my newly updated Windows 10 development machine.

This article takes you through the steps to get your Dexterity and/or Dynamics system running fast on Windows 10.

I normally don’t post multiple articles in one day, but it was worth posting this one and the previous two as soon as possible to help others out there facing the same issues.

Performance Problem

After resolving the pause on exit issue discussed in the previous post, I noticed that Dexterity and Microsoft 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.

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.

I have seen issues before with anti virus or malware solutions causing performance issues for Microsoft Dynamics GP and Dexterity, and the easiest way to resolve them is to add some exclusions to the settings for the application.

Part of the issue is that the Dynamics dictionary is a very large single file and the anti virus solution often wants to check the entire file when only a small part of it is being read. So you want to exclude the file type with the extension .DIC.

This is the same issue with the database and log files maintained by SQL Server. So you want to exclude the folder where SQL Server stores its .mdf and .ldf data files.

As a final step (that delivered some of the best performance improvement), I also excluded the executables for Dexterity, Dexterity Utilities and Dynamics. I have five versions of each installed, so that needed 15 entries.


To make the changes on your Windows 10 system running Windows Defender follow the steps below. If using a different anti virus or malware solution, you can add the same exclusions anyway.

  1. Select Start >> Settings
  2. Select Update & Security >> Windows Defender
  3. Under Exclusions, click Add an exclusion
  4. Under Folders, click Exclude a folder
  5. Locate the SQL Server Data folder and exclude it. On my system it was
    C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA
  6. Under File Types, click Exclude a file extension
  7. Add .dic as an exclusion
  8. Under Processes, click Exclude a .exe, .com or .scr process
  9. Navigate to the Dex.exe, Dexutils.exe for each version of Dexterity and add it
  10. Also navigate to the Dynamics.exe for each version of Microsoft Dynamics GP and add it

Now test out how fast your system runs Dexterity and/or Microsoft Dynamics GP. Zoom Zoom. 🙂

Hope you are happy with your Windows 10 upgrade now.


PS: 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.

This article was originally posted on

8 thoughts on “Solving Performance Problems with Microsoft Dynamics GP and Windows 10 – Part 2

  1. I too was experiencing this massive slowdown due to Windows Defender while trying to run a new test instance of GP 2015 in preparation for our 2010-2015 upgrade. as soon as I turned off real time protection GP would spring to life and work properly. I am adamant that I will not make Defender exceptions in order for the two programs to coexist properly so I decided to dig deeper.

    Using Procmon from SysInternals, I was able to watch the process activity for both the Dynamics.exe and the MsMpEng.exe. It quickly became clear that both processes were hitting the DEXSQL.LOG file A LOT. I am familiar with DEXSQL.LOG since our GP partner has had us turn on logging before to track down problems. I went into the DEX.INI file and saw that indeed, the DEXSQL logging was set to TRUE in this new test instance of GP 2015. I turned off DEXSQL logging, and voila, everything started working properly again the next time I ran GP and Windows defender with Real Time Protection turned on. I did NOTHING special to Defender and made no special exclusions.

    Added this information here in case it will help others who may also have inadvertently turned on DEXSQL logging. In that case, making super special GP exclusions in Defender will indeed “fix” the problem, but in reality the REAL problem is still there and the exclusions are only a Band-Aid covering up the real issue.


    • Hi Chris

      Thanks for your analysis and the information you have provided. My performance issues occurred when I was not using DEXSQL.LOG logging. I never use the Dex.ini Settings to turn logging on and off as GP Power Tools can control five types of logging without changing the Dex.ini.

      I will also exclude the DEXSQL.LOG file which is still used when logging is on (using Dex.ini settings or GP Power Tools).



Please post feedback or comments

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.