Fix error 0X00000944 NERR_ProfileCleanup Windows

This error pops up when Windows can't clean up old network connections during profile unload. The fix is a quick registry tweak that gives the system more time to disconnect.

What this error means

You're logging off and Windows throws error 0X00000944 — "The system cannot delete current connections to network resources". It's the NERR_ProfileCleanup error. It usually shows up as a dialog box right before the logoff finishes, or in the Event Viewer under User Profile Service events. I've seen this most often on Windows 10 Pro and Windows 11 workstations that map drives to a file server via Group Policy or logon scripts.

The short version: Windows tries to close all your network drives and printer connections when your user profile unloads. But something — a hung SMB session, an open file handle, a slow server — is blocking the cleanup. After a short wait (default is 2 seconds), Windows gives up and shows this error. The profile might still unload, but the connections stay in a weird state.

The fix: increase the profile unload timeout

The real fix is in the registry. You're going to add a DWORD that tells Windows to wait longer before it gives up on disconnecting network resources. I've used this on dozens of machines. It works.

Press Windows + R, type regedit, and hit Enter. Click Yes if UAC asks.

In the left pane, navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network

Right-click the Network key (folder) in the left pane. Choose New → Key. Name it Users. After creating it, you should see the Users folder appear under Network.
Click on the new Users key you just created.
Right-click in the right pane, choose New → DWORD (32-bit) Value. Name it ProfileUnloadTimeout.
Double-click ProfileUnloadTimeout. Set the base to Decimal, then enter 30 (this is 30 seconds — more than enough). Click OK.
Close Registry Editor. Restart the computer for the change to take effect.

After the restart, try logging off normally. The error should be gone.

If it's still happening after the change, go back and double-check the path. I've seen people accidentally put the DWORD under Control instead of Network\Users. Make sure you're at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Users.

Why this works

Windows has a built-in timeout for cleaning up network connections during profile unload. The default is 2 seconds. That's not a typo — two seconds. On a modern network with fast SSDs and gigabit connections, that's usually fine. But if you have mapped drives to a server that's a bit slow, or you have a printer share that's not responding, two seconds isn't enough time to close everything gracefully.

The ProfileUnloadTimeout DWORD overrides that default. Setting it to 30 seconds gives Windows plenty of time to send the close commands, wait for acknowledgments, and clean up the connection table. The Registry Editor doesn't validate this key — it just works. Microsoft documents it in the Windows Server 2012 and later documentation, but it works on Windows 10 and 11 too.

I've seen some people try to fix this by removing network drives manually before logoff. That works as a workaround, but it's clunky and easy to forget. The registry fix is set-and-forget.

Less common variations

Sometimes the registry fix alone isn't enough. Here are three other scenarios I've run into:

1. Stale SMB sessions

If you're connecting to a Windows file server (especially older ones like Windows Server 2008 R2 or 2012), the server might hold the SMB session open even after the client tries to disconnect. Run this command on the client (not the server) in an elevated Command Prompt:

net use * /delete /y

This forces all mapped drives to disconnect immediately. Then test a logoff. If the error goes away, the problem is likely a stuck SMB session on the server side. On the server, check the Computer Management → Shared Folders → Sessions for stale connections from your machine. Disconnect them manually.

2. Group Policy drive maps are slow to remove

Group Policy deployed drives (via Drive Maps preference) sometimes take longer to disconnect than manually mapped drives. The profile unload doesn't wait for the Group Policy extension to finish. If the registry fix above doesn't work, try a different approach: remove the drive maps via a logoff script. Create a batch file with net use * /delete and assign it via gpedit.msc under User Configuration → Windows Settings → Scripts (Logoff).

3. Third-party network software

I've seen this error with backup software (like older versions of Arcserve or Symantec Backup Exec) that holds open network file handles during logoff. Also VPN clients — especially those that use virtual network adapters — can block the disconnection. If the problem started after installing a new app, uninstall it and test. If it goes away, contact the vendor for a fix or a workaround.

Prevention tips

You can avoid this error coming back by keeping a few things in check:

Don't map drives with IP addresses — use DNS names. IP-based connections can time out faster during cleanup.
Update network drivers — outdated NIC drivers, especially Realtek and Intel, can cause random network hangs during logoff. Check the manufacturer's site, not Windows Update.
Disable slow link detection for Group Policy drive maps (if you use them). It's in the Drive Maps preference advanced settings. Slow link detection adds delays that can interfere with cleanup.
Monitor Event ID 4646 in the System log — it logs profile unload failures. If you see it paired with error 0X00000944, you know the timeout fix is the right path.

That's it. The registry change is the cleanest fix I know. It's been working for me since Windows 7 days, and it hasn't failed yet. Try it first before messing with scripts or drivers.