Windows Stuck at "Applying Group Policy"

If your Microsoft Windows computer is in a corporate or school environment, you may have a problem where the computer gets stuck at “Applying Group Policy” while logging onto the computer. This process shouldn’t take more than a few minutes, but sometimes can get stuck for hours. If you’re stuck, try these steps.

Disconnect From Network

If you’re in a pinch and can’t wait any longer, try disconnecting your network cable if you’re connected via a wired network. If you’re connected via Wi-Fi, try turning it off.

Once you disconnect from the network, you should get logged right in. Reconnect the network cable and proceed working as normal. You can try to restart your computer and let Group Policy apply when you have more time.

If the problem persists, you should contact your IT department for help.

Troubleshoot Why Computer Sticks at “Applying Group Policy”

Use the disconnect from network trick above to get logged into the computer, then perform these steps to figure out the group policy problems.

Enable Group Policy Debug Logging.
Ensure the “usermode” folder is created at “C:\Windows\Debug“.
Restart the computer, then wait for the computer to stick at “Applying Group Policy“. Note where exactly it gets stuck (i.e. “Registry Policy” , “Drive Maps Policy”, “Files Policy”, etc.).
After a few minutes stuck, disconnect the computer from the network.
Once the computer proceeds to login, re-connect the network cable.
Check the debug log. It will be located at “C:\Windows\Debug\usermode“.
Check the timestamps in the log file to see where Group Policy is sticking. The log and the knowledge of where exactly things got stuck you acquired during step 3 should clue you in to what group policy you need to modify.

Here are some other tips to help you troubleshoot this issue:

Use the command “gpresult.msc” to see the list of group policies that are being applied to the com
Check to see if there are patches or updates released by Microsoft that may fix your issue.
You may end up troubleshooting connection issues with this problem. Drive mapping policies are usually a problem if there is a weak network connection.