When a new user profile signs into a Windows 10 or Windows 11 computer for the first time, OneDrive for Business should start automatically and begin syncing files. Instead, many IT administrators and users report that OneDrive fails to launch after reboot, leaving the sync app inactive and files unavailable. This issue typically occurs because the OneDrive startup registry entry or scheduled task is missing, disabled, or blocked by Group Policy settings applied to new profiles. This guide explains why OneDrive does not start for new profiles after reboot and provides step-by-step fixes to restore automatic startup.
Key Takeaways: Restoring OneDrive Auto-Start for New Profiles
- Registry path HKCU\Software\Microsoft\Windows\CurrentVersion\Run: OneDrive must have a valid string value named “OneDrive” pointing to the correct executable path for automatic launch at sign-in.
- Scheduled task \Microsoft\Windows\OneDrive\OneDrive Standalone Update Task: This task triggers OneDrive startup for new users; if disabled or missing, the app will not start after reboot.
- Group Policy setting “Prevent the usage of OneDrive for file storage”: When enabled for new profiles, this policy blocks OneDrive from running entirely, overriding local startup settings.
Why OneDrive Fails to Start After Reboot for New Profiles
OneDrive for Business relies on a combination of a registry entry and a scheduled task to launch automatically when a user signs in. For a new profile, Windows creates these startup mechanisms during the first run of OneDrive. If the user or an administrator has not completed the initial OneDrive setup, or if Group Policy objects suppress the creation of these entries, OneDrive will not appear in the startup list and will not run after reboot. Additionally, the OneDrive executable path can differ between Windows 10 and Windows 11, and a mismatch in the registry can prevent launch. The most common root cause is that the registry Run key is missing or points to an incorrect location, or the scheduled task is disabled by a system administrator via domain policy or local security settings.
Steps to Fix OneDrive Startup Failure for New Profiles
- Verify the OneDrive executable path
Press Ctrl + Shift + Esc to open Task Manager. Go to the Startup tab and look for Microsoft OneDrive. If the status is Disabled, right-click it and select Enable. If OneDrive is not listed, proceed to the next step to check the registry. - Check the registry Run key for OneDrive
Press Windows key + R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Look for a string value named OneDrive. If it is missing, right-click in the right pane, select New > String Value, name it OneDrive, and set its value data to the correct path: for 64-bit Windows, use C:\Program Files\Microsoft OneDrive\OneDrive.exe. For 32-bit Windows, use C:\Program Files (x86)\Microsoft OneDrive\OneDrive.exe. If the value exists but points to a different location, correct the path. - Enable or recreate the OneDrive scheduled task
Press Windows key + R, type taskschd.msc, and press Enter. In Task Scheduler, navigate to Task Scheduler Library > Microsoft > Windows > OneDrive. Look for the task named OneDrive Standalone Update Task. If the task is disabled, right-click it and select Enable. If the task is missing, open an elevated Command Prompt as administrator and run the following command: schtasks /create /tn “Microsoft\Windows\OneDrive\OneDrive Standalone Update Task” /tr “%localappdata%\Microsoft\OneDrive\OneDriveStandaloneUpdater.exe” /sc daily /mo 1 /ru “SYSTEM” /f. This recreates the task that triggers OneDrive startup for new users. - Run OneDrive setup for the new profile
Press Windows key + R, type %localappdata%\Microsoft\OneDrive\OneDrive.exe, and press Enter. If OneDrive launches, complete the initial setup by signing in with your work or school account. This action creates the necessary registry entry and scheduled task for future reboots. After setup, restart the computer and verify that OneDrive starts automatically. - Check Group Policy settings
If OneDrive still fails to start, Group Policy may be blocking it. Press Windows key + R, type gpedit.msc, and press Enter. Navigate to Computer Configuration > Administrative Templates > Windows Components > OneDrive. Double-click the policy Prevent the usage of OneDrive for file storage. If it is set to Enabled, change it to Not Configured or Disabled. Click OK, then run gpupdate /force in Command Prompt as administrator. Restart the computer and test OneDrive startup. - Verify OneDrive is installed for all users
Open Command Prompt as administrator and run: “C:\Program Files\Microsoft OneDrive\OneDrive.exe” /allusers. This command ensures that OneDrive is installed in the per-machine location, making it available to new profiles. After running the command, repeat step 4 to complete setup for the current user.
If OneDrive Still Has Issues After the Main Fix
OneDrive shows error code 0x8004de40 after reboot
This error indicates a corrupted OneDrive cache or credential issue. Reset OneDrive by pressing Windows key + R, typing %localappdata%\Microsoft\OneDrive\OneDrive.exe /reset, and pressing Enter. Wait 60 seconds, then launch OneDrive again from the Start menu. If the error persists, sign out of OneDrive settings, restart the computer, and sign in again.
OneDrive does not appear in the startup list in Task Manager
The startup entry may be missing because OneDrive was not run at least once for the user profile. Run OneDrive manually from the Start menu or the executable path in step 4. After the initial sign-in, the startup entry is created automatically. If it still does not appear, check the registry key from step 2 and ensure the value is present and correct.
Group Policy prevents OneDrive for new users despite local fix
If you are on a domain-joined computer, the domain Group Policy may override local settings. Contact your IT administrator to verify that the OneDrive policy is set to Not Configured or Disabled at the domain level. You can also run gpresult /h gpresult.html in Command Prompt as administrator to generate a report showing which policies apply to the user and computer.
Manual Startup vs Automatic Startup: Key Differences
| Item | Manual startup | Automatic startup |
|---|---|---|
| Trigger | User launches OneDrive from Start menu or desktop shortcut | Windows launches OneDrive at user sign-in via Run key or scheduled task |
| Prerequisites | OneDrive installed and user has signed in at least once | Registry Run key present with correct path and scheduled task enabled |
| Reliability after reboot | OneDrive does not start until user manually launches it | OneDrive starts automatically without user action |
| Impact on sync | Files may not sync until user signs in, causing delays | Files begin syncing immediately after sign-in |
| Management via Group Policy | Not affected by startup policies | Can be blocked or enforced via the Prevent the usage of OneDrive for file storage policy |
After completing the steps above, OneDrive for Business should start automatically for new profiles after each reboot. The registry Run key and the scheduled task are the two critical components that control this behavior. As an advanced tip, you can deploy the registry fix and scheduled task creation via a startup script or Group Policy Preferences to apply the fix to multiple new profiles across your organization without manual intervention.