GPO Mapped Shared Drives Disappearing - Unable to run gpupdate

A Childs 161 Reputation points

Our IT team has noticed a problem with a variety of seemingly related symptoms on several different machines, with multiple different user accounts, each in a different OU for policy.

The initial problem that is obvious is that user's network drives are disappearing when then sign in. These drives are currently mapped via group policy, but we suspect that the the replace/delete option is not working cleanly and causing things to hang up. I was able to get one error specific to mapping the drives in event viewer indicating the drive was already in use, even though it was not (details at end).

In addition to the network drives disappearing, or only partially showing up, we have noticed the following related issues.

Can't run programs as admin: This is the most frustrating, because it prevents you from running diagnostics such as event viewer, or other commands that require elevation. When you try to sign in as an admin (domain or local), it takes you to the UAC login prompt, but then it waits on a blank screen for about 1 - 2 minutes and then times out. The exact time might vary. After about 3 or four attempts, I was finally able to get past this, but then you have to redo it if you want to use a different admin account (attempt logging in several times, wait for it to not do anything for several minutes, try again, etc.)

The computer is unable to update Group Policy: We have tried running "gpupdate /force" on the user's profile when this issue occurs, and it does not do anything. The command prompt window literally sits there. The current window I am waiting on has been attempting to run for over 1 hour and 30 minutes and it has not finished, thrown an error, or timed out. At that point, I closed it out and tried running it again, once again it just sat there, when a successful completion usually takes less than a minute.

"Net Use" takes several minutes to run: I ran it the first time, it took 10 - 15 minutes, finally returned that the shared drive was disconnected.
Ran it immediately after, took another 10-15 minutes to say it was reconnecting.
Ran it immediately after that, said it was disconnected again, this time giving immediate results as expected.
Running again pulled up no shared connections.

Slow File Explorer: depending on what point in the process you are at, file explorer will be stuck on the green loading bar after trying to access the shared drives. This is presumable because something is telling file explorer that the drives are there, but when you run "net use" they are disconnected. As file explorer tries to connect, it slows down everything else, potentially contributing to some of the other issues.
You are however able to ping the network drives and navigate to them via file explorer (when it does not freeze), provided that you do not click on the network drive. One you click on the network drive, it freezes up, sometimes crashing causing very few programs to work when you try to restart explorer.exe

Slow Sign off and Restart: Attempts to sign off or restart when these issues are being experienced will cause the computer to hang with the spinning wheel for over 10 - 20 minutes. wait long enough, and it might do something. Generally a force shutdown by holding the power button will allow you to power on again.

Known (temporary) fix: We have been able to temporarily fix the issue by forcing a shutdown, signing in as another user (mostly tested as a domain admin), running a gpupdate, and then signing out. The gpupdate works, and when the user that was having issues before signs in, all of their shared drives work and there are no issues.... until they sign out or restart their machine, and then it acts up all over again.

Log Name: Application
Source: Group Policy Drive Maps
Date: 10/1/2021 2:56:08 PM
Event ID: 4098
Task Category: (2)
Level: Warning
Keywords: Classic
Computer: XXX.XXX
The user 'Z:' preference item in the 'drives - PUBLIC (all users) {XXXXXXXXXXXXXX}' Group Policy Object did not apply because it failed with error code '0x80070055 The local device name is already in use.' This error was suppressed.
Event Xml:
<Event xmlns="">
<Provider Name="Group Policy Drive Maps" />
<EventID Qualifiers="34305">4098</EventID>
<TimeCreated SystemTime="2021-10-01T18:56:08.1806002Z" />
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Security UserID="XXXXX" />
<Data>drives - PUBLIC (all users) {XXXXXXXXXXXXXXXXXXXXXXXXX}</Data>
<Data>0x80070055 The local device name is already in use.</Data>

Log Name: Application

Source: Group Policy Drive Maps

Date: 10/1/2021 3:38:38 PM

Event ID: 4098

Task Category: (2)

Level: Warning

Keywords: Classic


Computer: XXX,XXX

Description: The user 'S:' preference item in the 'drives - IT {XXXXXXXXXXXXXXXXXXXX}' Group Policy Object did not apply because it failed with error code '0x80070079 The semaphore timeout period has expired.' This error was suppressed.

Event Xml:">

A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,044 questions
0 comments No comments
{count} votes

Accepted answer
  1. A Childs 161 Reputation points

    To update this post, we believe that we have found the fix, and it has nothing to with our group policy.

    The issue appears to be with windows explorer crashing when you attempt to open a network drive.

    Implementing fix number 6, adding a registry key appears to have resolved the issue for us. While we are still doing some additional testing, I am closing this ticket with this marked as the solution.

    "Create a new Value in Windows Registry
    Another method to fix this issue is to create a new Value in Windows Registry. We have listed the instructions for this below. But before you proceed, it is better if you create a backup of Registry so that you can restore it if any problem occurs.

    create new value in Registry

    1] Press Win + R hotkeys to launch the Run command box. Type regedit and click OK. Click Yes if you receive a UAC prompt message.

    2] In the Registry Editor, copy the following path, paste it into its address bar, and hit Enter:

    3] Make sure that you have selected the NetworkProvider key on the left side. Now, right-click on the right side and go to “New > DWORD (32-bit) Value.” Name this newly created Value RestoreConnection. Now, double-click on it and set its Value Data to zero."

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Limitless Technology 39,506 Reputation points


    Thank you for your question.

    1. Please check in your GPO what are recent changes have been made , for example any logon screen ,software deployment, file copying , Task scheduler using GPO.
    2. Please check if AD health is good and synced across other DCs. you can use Active Directory Replication Status Tool from Microsoft.
    3. Please try to disable any firewall or antivirus program which may block connections to AD DC.
    4. Disable synchronous logins when on a slow link.
    5. Please check if there is no time \ date difference between client PCs and DC.
    6. In Windows, you can enable the display of detailed status information that allows users and the administrator to visually understand at what stage of computer loading the greatest delay is observed. If you enable this policy, the information about GPO components being applied is also displayed. in Windows 8/10 : Computer Configuration -> Policies -> System -> Display highly detailed status messages -> Enabled
    7. Please uninstall any Windows update installed recently on Widows client PCs.
    8. Please check preferred DNS and Gateway ips are correct on Widows client PCs.
    9. Please check if there are no ping timeout or ping latency between Widows client PCs and DC.

    --If the reply is helpful, please Upvote and Accept as answer--