Issue Description: When a client PC is restarted and after the user sign-in to the computer, Error message “Windows cannot Access \\<server>\<foldername>” pop-up shows on the desktop screen and user is unable to see any desktop icons and Task bar Pinned items. This issue generally occur when you have re-directed Desktop and Documents folder to a file server using Folder Redirection GPO and is usually fixed (temporarily) by performing multiple restarts of the PC.
Error 1: Windows cannot access \\server\<re-directed folder> (In my case it was Desktop folder which was re-directed it to a file server (as you can see in below screenshot):
Error 2: You will find Event ID 1124 is generated in the event viewer due of this issue.
Event Viewer Error (Event ID 1124)
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
Error 3: On the Client PC (Target Machine) – When i ran gpupdate /force on the client PC i got below warning regarding the Client Side Extension Folder Redirection.
“The Group Policy Client Side Extension Folder Redirection was unable to apply one or more settings because the changes must be processed before system start-up or user logon.”
The error is generally in the category of Folder Redirection, Security Settings, Software Installation on the computer start-up.
Asynchronous Processing – When a process(es) does not depend on the output of the other process and can occur at the same time.
Synchronous Processing – This refers to processes that depend on each other’s outcome. Synchronous process must wait for the previous process to finish before next process can start execution.
CSE (Client Side Extensions) like Folder Redirection and Drive maps are designed to require Synchronous processing to apply the new settings on windows computer. Fast Logon Optimization may cause you to sign in or restart the computer multiple times before certain Group Policy settings are applied to the client computer.
Check the full list of the CSE at HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions registry location on any client PC.
Recommended: All below settings are computer configuration settings, therefore please create a test OU and move your test PC or problematic machine into that OU and then apply below policy to test before rolling out to all other users.
I) ✨Disable “Require use of fast startup” on Windows 10 computer either using GPO or manually on each PC.
Please note that when Fast Startup is Disabled, then computer will perform full shutdown when you restart your computer and will result in longer start-up times.
1.1) Manually Disabling Fast Startup: If you have few machines like 3-4 machines and you have administrator rights on those machines, then you can configure this setting by logging on to each PC and going to Power & Sleep Settings -> Additional Power Settings -> Advanced Power Settings -> Click Choose what the power buttons do -> Uncheck “Turn on fast Startup”
1.2) Using GPO / GPP to disable Fast Startup on multiple machines: You can use the GPO / GPP if you have a lot of machines where you want to disable Fast Startup by using registry Entry HiberbootEnabled and set its value to 0 and also disable “Require use of fast startup” under Computer Configuration/Policies/Administrative Templates/System/Shutdown/Require use of fast startup
HiberbootEnabled – DWORD value 0 -> Fast Startup Disabled
HiberbootEnabled – DWORD value 1 -> Fast Startup Enabled
II) ✨ Enable a Group Policy Setting Always wait for the network at computer startup and logon Under Computer Configuration\Administrative Templates\System\Logon\ and Apply it to the computer having issues.
III) ✨ Create below registry entries on the machine (via GPP):
GpNetworkStartTimeoutPolicyValue – Set this value to 60 Seconds or 90 Seconds depending upon your requirement. I used the decimal value 60 which fixed the issue.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon “GpNetworkStartTimeoutPolicyValue“= dword: 60 (Decimal)