Intuit Help
Intuit
‎12-05-2019 05:06 PM

Help Articles

In Windows 10, when your database is using a Windows server and you're using the group policy to map network drivers, you may experience the following issues:

  • When Lacerte logs a user out for inactivity, the program locks up or hangs at the sign-in screen.
  • The Lacerte client list is duplicated by whichever client is the first in the client list. (This is a refresh issue and data nor clients are lost. Closing and reopening 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 reopening the program will correct the issue.)
  • Lacerte loses its connection to the network drives and 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 freezes up around every 90 minutes.

Make sure you're using a supported version of Windows

Make sure your computer meets the 2020 Lacerte system requirements:

Lacerte and DMS currently support the following Workstation OS:

  • Windows 10 (version 1607 or later)
  • Windows 8.1 (64-bit only)

Windows 7 and Windows Server 2008 are no longer supported.

Lacerte and DMS currently support the following File Server OS:

  • Windows Server 2012
  • Windows Server 2016
  • Windows Server 2019

Network Attached Storage drives are no longer supported.

How to resolve response issues and freezing

Before you begin: Back up your registry before trying anything. See How to back up and restore the registry in Windows for detailed instructions. 

Your Network admin will need to adjust the registry key below on the Windows 10 workstations that are experiencing issues:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogonGPExtensions{5794DAFD-BE60-433f-88A2-1A31939AC01F}

Change the value "NoBackgroundPolicy" to 1 (You may need to create this as a DWORD).

To change the NoBackgroundPolicy key:

  1. In your Windows Taskbar, enter Registry Editor, then select OK.
  2. In the Registry Editor window, select the following file path:
    • HKEY_LOCAL_MACHINE
    • SOFTWARE
    • Microsoft
    • Windows NT
    • CurrentVersion
    • Winlogon
    • GPExtensions
    • {5794DAFD-BE60-433f-88A2-1A31939AC01F}
  3. Change the value NoBackgroundPolicy to 1.
    • If NoBackgroundPolicy isn't listed:
      1. Right-click and hover over New.
      2. Select DWORD (32-bit) Value.
      3. Name the new entry, NoBackgroundPolicy, and repeat step 3.
  4. Reboot your workstation.

In some cases, your admin may need to take ownership of the registry to add or change the NoBackgroundPolicy value.

To take ownership and gain full permissions of the {5794DAFD-BE60-433f-88A2-1A31939AC01F} key:

  1. Right-click the {5794DAFD-BE60-433f-88A2-1A31939AC01F} key and select Permissions.
  2. In the Permissions window, select Advanced.
  3. Next to the field Owner: field, select Change.
  4. In the Enter the object name to select field, enter the user ID of the user that needs to take ownership.
  5. Select OK.
  6. On the Permissions tab, select the Add button, then Select a principal.
  7. Enter the user's user ID again in the Enter the object name to select field and select OK.
  8. Select OK, then OK. 
  9. Try to modify or add the NoBackgroundPolicy key.

If the network admin can't change the permissions on the registry key to allow the change:

  1. Download and install psexec from sysinternals.
  2. Use the System Account to run Regedit: psexec -i -d -s c:\windows\regedit.exe in the command line
  3. Change permissions and modify the NoBackgroundPolicy key.

Related topics: