OneDrive Admin Checklist: Windows startup fails after reboot for shared devices

When shared devices in your organization fail to start Windows correctly after a reboot, the root cause is often a conflict between OneDrive sync settings and the shared PC configuration. This problem typically appears on computers used by multiple users, such as lab machines, kiosks, or hot-desking workstations. The failure can manifest as a black screen, a stalled login process, or Windows loading without the desktop shell. This article provides a structured admin checklist to diagnose and resolve the startup failure caused by OneDrive on shared devices.

Why OneDrive Causes Windows Startup Failure on Shared Devices

OneDrive by default attempts to start and sync user files immediately after sign-in. On a shared device where multiple user profiles exist, OneDrive may try to load a profile that is corrupted, partially configured, or missing sync tokens. This process can block the Windows shell from loading, resulting in a startup failure. The issue is exacerbated when Known Folder Move is enabled, because OneDrive tries to redirect Desktop, Documents, and Pictures folders for each user at login. If the network connection to the OneDrive service is slow or unavailable, the startup process stalls.

Shared devices often have disk space constraints and aggressive cleanup policies. When OneDrive attempts to download files for a new user during login, the system may run out of free space, causing Windows to hang or fail to complete the startup sequence. Additionally, if the shared PC uses Windows 10 or Windows 11 in shared PC mode, OneDrive is not designed to work with that configuration, leading to unpredictable behavior.

Admin Checklist to Fix OneDrive Startup Failure on Shared Devices

Follow these steps in order. Each step targets a specific cause of the startup failure. Apply these changes using Group Policy, Intune, or a provisioning package depending on your environment.

1. Disable OneDrive auto-start via Group Policy
   Open the Group Policy Management Console. Navigate to Computer Configuration > Administrative Templates > OneDrive > Prevent OneDrive from starting automatically after sign-in. Set this policy to Enabled. This stops OneDrive from launching at user login, removing the sync process that blocks the Windows shell.
2. Configure the DisableLibrariesDefaultSync registry key
   On each shared device, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive\Accounts\PersonalSilentAccountConfig. Create a DWORD value named DisableLibrariesDefaultSync and set it to 1. This prevents OneDrive from syncing the user’s known folders automatically, reducing the startup load.
3. Restrict OneDrive sync to domain-joined PCs
   In the Microsoft 365 admin center, go to Settings > OneDrive > Sync. Under Allow syncing only on PCs joined to specific domains, enter the domain names your organization uses. Save the setting. This stops OneDrive from syncing on devices that are not joined to your domain, which includes many shared or unmanaged PCs.
4. Enable shared PC mode in Windows
   If the device runs Windows 10 or Windows 11, enable shared PC mode by running the following PowerShell command as Administrator: Set-EDUConfiguration. This configures Windows to delete user profiles after logout, disable OneDrive auto-launch, and prevent background sync. Reboot the device after applying.
5. Remove OneDrive from the startup folder for all users
   Navigate to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp. Delete any OneDrive shortcut present. This ensures OneDrive does not start at boot for any user on the device.
6. Verify the user profile service is not blocked
   Open Services.msc and confirm that the User Profile Service is running. If it is stopped, set its startup type to Automatic and start the service. A stopped profile service can prevent OneDrive from loading and cause startup failure.

If Windows Startup Still Fails After the Main Fix

OneDrive shows a red X on shared Office files

A red X indicates that OneDrive cannot sync the file. On a shared device, this often happens when the user does not have a valid OneDrive license or the file is stored in a location that requires exclusive access. Check the user’s license in the Microsoft 365 admin center. If the device is in shared PC mode, instruct users to save files to a network share instead of OneDrive.

Windows boots to a black screen after login

This symptom occurs when OneDrive attempts to load a corrupted user profile. Boot into Safe Mode by pressing F4 during startup. In Safe Mode, sign in as an administrator and delete the affected user profile folder from C:\Users. Reboot normally. The user will get a fresh profile on next login. Then apply the Group Policy to disable OneDrive auto-start to prevent recurrence.

OneDrive continues to launch despite policy settings

If OneDrive still starts after applying Group Policy, the policy may not be applying correctly. Run gpupdate /force from an elevated command prompt and reboot. Check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive for the DisableLibrariesDefaultSync value. If the value is missing, the policy did not apply. Verify that the Group Policy object is linked to the correct organizational unit.

OneDrive Startup Behavior: Default vs Shared PC Configuration

Item	Default Configuration	Shared PC Configuration
OneDrive auto-start at login	Enabled	Disabled via policy or shared PC mode
Known Folder Move sync	Automatic for new users	Disabled via DisableLibrariesDefaultSync
User profile retention	Persistent across reboots	Deleted on logout in shared PC mode
Startup failure risk	Low on personal devices	High without configuration changes

Use this checklist to systematically eliminate the causes of Windows startup failure on shared devices. Disable OneDrive auto-start and restrict sync to domain-joined PCs as the primary fixes. If the problem persists, check user profiles and apply shared PC mode. These steps will restore reliable startup behavior for all users on the device. For advanced management, consider deploying a provisioning package that pre-configures these settings during OS deployment.