Welcome back! Ask questions, get answers, and join our large community of tax professionals.
cancel
Showing results for 
Search instead for 
Did you mean: 

Lacerte or DMS Stops Responding or Freezes in Windows 10

Highlighted
Intuit
last updated ‎July 20, 2020 9:38 PM

Lacerte or DMS Stops Responding or Freezes in Windows 10

In Windows 10 when the database is on a windows server, such as Server 2008, 2012 or later and when the group policy is used to map network drivers, the following issues may occur:

  • When Lacerte logs a user out for inactivity, the program locks up or hangs at the login screen.
  • The Lacerte client list is duplicated by whichever client is at the top of the client list. (This is a refresh issue and data nor clients are lost.  Closing and re-opening the program will correct the issue.)
  • The appointment manager fields on the client are blank. (This is a refresh issue and data nor clients are lost.  Closing and re-opening the program will correct the issue.)
  • Lacerte loses it connection to the network drives. The following message appears: The shared system file path is currently not available.  You have been disconnected from the network.  The Lacerte program cannot start without a valid system file path.  Would you like to work offline using the options and settings on this computer?
  • DMS will freeze up somewhere around every 90 minutes.

In Windows 7, these automatic maps only occur at logon. In Windows 10, they are remapping at every background refresh of Group Policy (every 90 minutes). This is temporarily disconnecting the drive Lacerte and DMS need, causing the issue mentioned above.

Solution:

Before you begin: Back up your registry before attempting to do anything in it.  See How to back up and restore the registry in Windows on how to do this. 

Your Network admin will need to adjust this registry key on the Windows 10 workstations that are having the issue:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{5794DAFD-BE60-433f-88A2-1A31939AC01F}

Then change value "NoBackgroundPolicy" to 1 (You may need to create this DWord).

  1. In the Open (Search) field, type Regedit and then click OK.
  2. Using the folders on the left, browse to and select the following:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{5794DAFD-BE60-433f-88A2-1A31939AC01F}
  3. Change value "NoBackgroundPolicy" to 1.
    • Note: If NoBackgroundPolicy does not exist, right-click in the right side panel, point to New and click DWORD Value. Name the new entry NoBackgroundPolicy and repeat step 3.
  4.  Reboot the workstation.

In some instances, the admin may need to take ownership of the registry to add or change the NoBackroundPolicy value.

  1. Right-click {5794DAFD-BE60-433f-88A2-1A31939AC01F} and select Permissions.
  2. Click the Advanced button.
  3. Then click Change next to Owner at the top of the window.
  4. In the Enter the object to select field, type the username of the user that needs to take ownership. Example: JDoe
  5. Click OK
  6. On the Permissions tab, click the Add button.
  7. Click Select a principal.
  8. Type the users username again in the Enter the object name to select field (Example: JDoe) and click OK.
  9. In the Basic Permissions section, click Full Control and then click OK.
  10. Click OK and then OK again. 
  11. Then attempt to modify or add the NoBackgroundPolicy key.

Note: If the network admin can't change the permissions on the registry key to allow the change, Download and install psexec from sysinternals and Use the System Account to run Regedit: psexec -i -d -s c:\windows\regedit.exe in a cmd line, then make the necessary change.

Related Topics:

Was this helpful?

You must sign in to vote, reply, or post