OneDrive for Business Windows startup fails after reboot for virtual desktops: Fix Guide

After rebooting a virtual desktop, OneDrive for Business may fail to start automatically. You see no OneDrive icon in the system tray, and files do not sync until you manually launch the app. This problem occurs because virtual desktop environments often block or delay startup applications through Group Policy, user profile restrictions, or logon script conflicts. This guide explains why OneDrive startup fails on virtual desktops and provides five working fixes to restore automatic launch after every reboot.

Why OneDrive Startup Fails on Virtual Desktops

Virtual desktop environments such as Windows 10 or Windows 11 multi-session, Azure Virtual Desktop, or VMware Horizon use mandatory profiles, roaming profiles, or FSLogix profile containers. These profile types can strip or reset user-specific startup registry keys every time the user logs off. OneDrive relies on a run key under HKCU\Software\Microsoft\Windows\CurrentVersion\Run to launch at sign-in. If the virtual desktop profile solution deletes or overwrites that key, OneDrive will not start automatically.

Additionally, Group Policy objects in virtual desktop deployments often disable OneDrive startup through the “Do not run specified Windows applications” policy or by blocking the Run registry path entirely. Logon scripts that clear startup entries for performance reasons can also remove the OneDrive entry. The result is the same: after reboot, OneDrive is absent from the notification area.

FSLogix Profile Containers and OneDrive Startup

FSLogix profile containers store the user registry hive inside a VHDX file mounted at logon. If the container is not properly excluded from OneDrive sync or if the registry hive is read-only during logon, the OneDrive startup entry may not persist. Administrators must ensure that the FSLogix profile exclusion list includes the OneDrive cache path and that the user registry hive is writable during the startup process.

Steps to Restore OneDrive Automatic Startup on Virtual Desktops

Before applying any fix, sign in to the virtual desktop and verify that OneDrive is installed. Open the Start menu, type “OneDrive,” and confirm the app appears. If OneDrive is not installed, deploy it using the per-machine installer from the Microsoft 365 admin center. After confirming installation, proceed with the following methods.

Method 1: Enable OneDrive in Task Manager Startup

1. Open Task Manager
   Press Ctrl + Shift + Escape simultaneously. If Task Manager opens in compact view, click “More details” at the bottom.
2. Go to the Startup tab
   Click the Startup tab at the top of the window. Locate “Microsoft OneDrive” in the list of applications.
3. Enable OneDrive
   If the Status column shows “Disabled,” right-click Microsoft OneDrive and select “Enable.” Close Task Manager and restart the virtual desktop to test.

Method 2: Add OneDrive Startup Entry via Registry

If Group Policy or a logon script removes the OneDrive startup key, add it back manually through Registry Editor. This method works on both Windows 10 and Windows 11.

1. Open Registry Editor
   Press Windows Key + R, type regedit, and press Enter. Click Yes when User Account Control prompts.
2. Navigate to the Run key
   In the left pane, expand HKEY_CURRENT_USER, then Software, then Microsoft, then Windows, then CurrentVersion, and finally Run.
3. Create a new String Value
   Right-click in the right pane, select New > String Value. Name it OneDrive.
4. Set the value data
   Double-click the new OneDrive entry. In the Value data field, paste the following path: %LocalAppData%\Microsoft\OneDrive\OneDrive.exe /background. Click OK and close Registry Editor. Restart the virtual desktop.

Method 3: Deploy OneDrive Startup via Group Policy

For managed virtual desktop environments, use Group Policy to enforce the OneDrive startup entry for all users. This method overrides local profile resets.

1. Open Group Policy Management Console
   On a domain controller or management workstation, open Group Policy Management Console. Right-click the organizational unit containing the virtual desktop computers and select “Create a GPO in this domain, and Link it here.” Name the GPO OneDrive Startup Policy.
2. Navigate to the Run key policy
   Edit the new GPO. Go to Computer Configuration > Preferences > Windows Settings > Registry. Right-click Registry, select New > Registry Item.
3. Configure the registry item
   Set Action to Update. Hive: HKEY_CURRENT_USER. Key path: Software\Microsoft\Windows\CurrentVersion\Run. Value name: OneDrive. Value type: REG_SZ. Value data: %LocalAppData%\Microsoft\OneDrive\OneDrive.exe /background. Click OK. Close the GPO editor and run gpupdate /force on the virtual desktop host.

Method 4: Exclude OneDrive from FSLogix Profile Cleanup

If your virtual desktop uses FSLogix profile containers, configure FSLogix to preserve the OneDrive startup key.

1. Open FSLogix Registry Editor
   On the virtual desktop host, open Registry Editor. Navigate to HKLM\Software\FSLogix\Profiles.
2. Add registry exclusion
   Create a new Multi-String Value named RegistryExclusions. Add the following path: Software\Microsoft\Windows\CurrentVersion\Run\OneDrive. Click OK and restart the host.
3. Verify the exclusion
   Sign in as a test user. Check that the OneDrive startup key persists after a logoff and logon cycle.

Method 5: Use a Logon Script to Launch OneDrive

If all other methods fail, deploy a logon script that starts OneDrive silently after the user profile loads.

1. Create the script
   Open Notepad. Paste the following line: "%LocalAppData%\Microsoft\OneDrive\OneDrive.exe" /background. Save the file as StartOneDrive.cmd on a network share accessible to virtual desktop users.
2. Assign the script via Group Policy
   Open Group Policy Management Console. Edit the GPO linked to the virtual desktop computers. Go to User Configuration > Policies > Windows Settings > Scripts (Logon/Logoff). Double-click Logon. Click Add, browse to the StartOneDrive.cmd file, and click OK. Run gpupdate /force on the virtual desktop host.

If OneDrive Still Fails to Start After Reboot

If OneDrive does not launch after applying these fixes, check the following additional factors.

OneDrive Startup Entry Is Blocked by AppLocker or Windows Defender Application Control

Virtual desktop environments often use AppLocker or WDAC to restrict executable launch. If OneDrive.exe is not allowed by the policy, it will not start even if the registry key exists. Check the AppLocker Event Log under Applications and Services Logs > Microsoft > Windows > AppLocker. Add OneDrive.exe to the allowed publisher rules or path rules for %LocalAppData%\Microsoft\OneDrive\.

OneDrive Is Not Installed Per-Machine

The per-user OneDrive installer places the executable under the user profile. On virtual desktops with non-persistent profiles, the installer must be run per-machine. Download the OneDrive per-machine installer from the Microsoft 365 admin center under Setup > OneDrive > Sync. Run the installer with the /allusers switch: OneDriveSetup.exe /allusers.

User Profile Is Read-Only During Logon

Some virtual desktop profile solutions mount the user registry hive as read-only until the logon script finishes. If the OneDrive startup entry is written during logon but the hive is still read-only, the write fails. Configure the profile solution to mount the registry hive as writable before the logon script runs, or use a delayed startup task via Task Scheduler to add the OneDrive entry after the profile is fully writable.

Task Manager Startup vs Registry Entry: Key Differences

Item	Task Manager Startup	Registry Entry (HKCU Run)
Configuration method	Graphical UI per user	Registry Editor or Group Policy
Persistence across profile reset	Lost if profile is recreated	Lost unless added via Group Policy
Override by Group Policy	Can be disabled by policy	Can be removed by policy
Best for	Individual user troubleshooting	Enterprise deployment with managed profiles

OneDrive for Business can start automatically on virtual desktops after reboot if you address the specific profile and policy barriers in your environment. Start with the Task Manager startup check, then move to the registry method or Group Policy deployment. If FSLogix is in use, add the registry exclusion to preserve the startup key. For environments where policy cannot be changed, a logon script provides a reliable fallback that launches OneDrive silently after the user signs in.