Overview

This guide addresses a common issue where OneDrive fails to start on Windows devices configured with Shared PC Mode + OneDrive Sync via Microsoft Intune, even though the custom configuration profile reports “Success.”

Symptom

• Device is enrolled in Intune and assigned the custom profile using the EnableSharedPCModeWithOneDriveSync OMA-URI.
• Intune reports the configuration profile as Success (no errors, no conflicts).
• OneDrive is installed machine-wide (C:\Program Files\Microsoft OneDrive).
• When a user clicks OneDrive to launch it, nothing happens — no window, no sign-in prompt, no process.
• This happens across newly provisioned devices, regardless of user.

Background: The Setting in Question

The SharedPC CSP provides two mutually exclusive policies:

Setting	OMA-URI	Effect
EnableSharedPCMode	./Device/Vendor/MSFT/SharedPC/EnableSharedPCMode	Enables Shared PC mode, disables OneDrive sync
EnableSharedPCModeWithOneDriveSync	./Device/Vendor/MSFT/SharedPC/EnableSharedPCModeWithOneDriveSync	Enables Shared PC mode with OneDrive sync allowed

This setting was introduced starting with Windows 11 version 22H2.

Root Cause

This is a known, documented issue with the EnableSharedPCModeWithOneDriveSync CSP node. Even when Intune reports successful application of the policy, the underlying registry value that actually controls OneDrive access is not always reliably set:

HKLM\SOFTWARE\Policies\Microsoft\Windows\OneDrive
Value: DisableFileSyncNGSC

• 0 = OneDrive sync is allowed
• 1 = OneDrive sync is blocked

In practice, this value can remain (or get set) to 1 even when EnableSharedPCModeWithOneDriveSync is correctly applied — silently blocking OneDrive without generating any error in Intune’s reporting.

Diagnosis Steps

Before applying the fix, confirm this is indeed the cause:

1. Check the Intune deployment status

Go to Intune > Devices > [device] > Configuration profiles (or the profile’s own device status report). Confirm the profile shows Success for all target devices. Note: the reported setting name will show as Windows10CustomConfiguration — this is normal/generic and applies to Windows 11 devices as well.

2. Check the SharedPC setup log on the device

C:\Windows\SharedPCSetup.log

Confirm the EnableSharedPCModeWithOneDriveSync node was processed.

3. Check the registry value directly (this is the key diagnostic step)

On the affected device:

HKLM\SOFTWARE\Policies\Microsoft\Windows\OneDrive\DisableFileSyncNGSC

If this is set to 1, this confirms OneDrive is being actively blocked at the machine level — independent of which user is logged in.

4. Rule out conflicting policies

Generate an MDM diagnostic report to confirm no other policy is setting a conflicting value:

MdmDiagnosticsTool.exe -out C:\temp\MDMDiagReport

Open the resulting HTML report and search for DisableOneDriveFileSync. If this node does not appear at all, it confirms nothing else is forcing OneDrive sync to be blocked — the blockage is coming purely from the SharedPC CSP itself failing to reset the registry value.

Note: gpresult will not work on Entra ID/Intune-managed (non-domain-joined) devices — you’ll get “The user does not have RSoP data.” Use the MDM diagnostic report instead.

The Fix

Add a second, explicit OMA-URI setting to force the registry value to 0, overriding whatever the SharedPC CSP failed to set correctly.

New OMA-URI setting

Field	Value
Name	DisableOneDriveFileSync
OMA-URI	./Device/Vendor/MSFT/Policy/Config/System/DisableOneDriveFileSync
Data type	Integer
Value	0

This is a documented, ADMX-backed policy in the System area of the Policy CSP — the direct MDM equivalent of the classic Group Policy setting “Prevent the usage of OneDrive for file storage.” Its default value is 0 (allowed), so explicitly setting it to 0 is a safe override that doesn’t introduce new restrictions — it simply forces the correct value where the SharedPC CSP left it wrong.

This is also the same approach administrators used before EnableSharedPCModeWithOneDriveSync existed as a native CSP option — it directly and reliably controls the same registry key.

Implementation steps

1. Open your existing custom configuration profile (e.g., “SharedPC Mode with OneDrive Sync”).
2. Add a new OMA-URI setting using the values above.
3. Save the profile. No changes to assignment are needed — it will roll out to all devices already targeted by the profile.
4. On a test device, force a policy sync: Settings → Accounts → Access work or school → [account] → Info → Sync
5. Re-check the registry value: HKLM\SOFTWARE\Policies\Microsoft\Windows\OneDrive\DisableFileSyncNGSC It should now read 0.
6. Launch OneDrive and confirm it starts normally.

If OneDrive Still Doesn’t Start After the Fix

If the registry value is confirmed at 0 but OneDrive still fails to launch, investigate separately:

• Silent sign-in / MFA issues — OneDrive may open but fail to automatically sign users in with their Windows credentials, particularly in Conditional Access / MFA-required environments.
• Event Viewer — check Applications and Services Logs > Microsoft > OneDrive for specific error codes around the time of launch.
• Per-user profile state — test with a completely new user account that has never logged into the device before, to rule out a corrupted local profile.
• Installation type — confirm OneDrive is installed machine-wide (C:\Program Files\Microsoft OneDrive) rather than per-user (%localappdata%\Microsoft\OneDrive), as per-user installs behave inconsistently on shared devices.

Summary

Item	Detail
Root cause	EnableSharedPCModeWithOneDriveSync unreliably fails to reset DisableFileSyncNGSC to 0, despite reporting “Success” in Intune
Fix	Add ./Device/Vendor/MSFT/Policy/Config/System/DisableOneDriveFileSync (Integer, value 0) to the same or a companion custom profile
Verification	Registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\OneDrive\DisableFileSyncNGSC should read 0 after sync