No Microsoft-published known issue currently identifies OneDrive build 26.198.1011.0006 as causing a visible but nonresponsive File Explorer Share command, so the next discriminating check is whether Explorer.exe and OneDrive.exe run at the same non-elevated integrity level.^1^
1. Check the invocation context
- Open Task Manager → Details.
- Right-click a column heading → Select columns → enable Elevated.
- Record the value for both
explorer.exe and OneDrive.exe.
OneDrive does not support running elevated, and elevation can make its Explorer menu items unavailable.^2^
- If either process says Yes: sign out and back in, then start OneDrive normally—not from an elevated terminal, scheduled task, software-deployment process, or “Run as administrator” shortcut. The reported
Program Files location indicates a per-machine installation, but it does not establish that the current launch context is correct. Have device management identify what launches OneDrive elevated.
- If both say No: elevation mismatch is excluded. Microsoft’s UAC article is primarily for missing OneDrive menu items, so its policy configuration is only a diagnostic branch for this visible-but-unresponsive command, not a confirmed fix.^3^
If the security team approves testing that branch, first export or record the effective settings under secpol.msc → Local Policies → Security Options, then configure:
| User Account Control policy |
Value |
| Virtualize file and registry write failures to per-user locations |
Enabled |
| Switch to the secure desktop when prompting for elevation |
Disabled |
| Run all administrators in Admin Approval Mode |
Enabled |
| Only elevate UIAccess applications installed in secure locations |
Enabled |
| Only elevate executables that are signed and validated |
Disabled |
| Detect application installations and prompt for elevation |
Enabled |
| Elevation prompt for standard users |
Prompt for credentials |
| Elevation prompt for administrators in Admin Approval Mode |
Elevate without prompting |
| Allow UIAccess applications to prompt without secure desktop |
Disabled |
| Admin Approval Mode for the Built-in Administrator account |
Enabled |
Restart Windows and retest. These settings weaken elevation protections, particularly secure-desktop and administrator prompting. On a managed device, have administrators apply a narrowly scoped domain/Intune test; restore the previous values if it does not resolve the issue. Effective domain or Intune policy can overwrite local changes.
2. Correlate endpoint-control events
Reproduce the failure once and record the exact local time, then inspect:
- Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational
- Event Viewer → Applications and Services Logs → Microsoft → Windows → AppLocker → MSI and Script
Look at events immediately surrounding the click. Code Integrity records executable/DLL policy decisions, while AppLocker’s MSI and Script log covers scripts and COM objects.^4^ Relevant App Control indicators include audit event 3076 and enforcement event 3077; AppLocker enforcement can appear as 8004.^5^^6^
Any matching block must be remediated by the endpoint-security administrator; do not disable application control globally.
3. Capture the failed shell invocation
Use Process Monitor for one tightly bounded reproduction. It captures process, thread, Registry, file-system, and DLL activity.^7^
- Start capture without process-name filters.
- Clear existing events, click OneDrive Share once, wait 10 seconds, then stop capture.
- Open Tools → Process Tree and identify anything spawned by Explorer around that timestamp.
- Repeat with filters for
explorer.exe, OneDrive.exe, and any discovered child process.
- Preserve Process Name, Operation, Result, Path, timestamp, event properties, and stacks where available.
Correlate Process Create, ACCESS DENIED, NAME NOT FOUND, or an immediately exiting child process with the click time. These are investigative leads, not proof by themselves.
4. Check the network boundary only if invocation occurs
If the trace shows OneDrive starts handling the command but no sharing UI completes, have the network team verify required SharePoint Online/OneDrive for Business endpoints—especially *.sharepoint.com, *.sharepointonline.com, *.svc.ms, officeclient.microsoft.com, g.live.com, and oneclient.sfx.ms—over the documented ports.^8^
5. Preserve ODL evidence and escalate
Meaningful ODL analysis requires the actual Business1 bundle and exact reproduction timestamp. No public Microsoft documentation supplies a field-level ODL decoder, so preserve rather than modify:
-
%LocalAppData%\Microsoft\OneDrive\logs\Business1
- Procmon
.PML
- exported Code Integrity/AppLocker logs
- Windows build, OneDrive build, affected item path/type, and exact timestamp
Logs can contain tenant, URL, account, or device metadata; transfer them only through an approved Microsoft 365 support channel. Microsoft’s unresolved OneDrive for work or school guidance directs administrators to create a Microsoft support incident.^9^
References
- OneDrive Sync release notes - SharePoint in Microsoft 365
- Restrictions and limitations in OneDrive and SharePoint | Microsoft Support
- How to change the User Account Control policies to allow OneDrive context menus | Microsoft Support
- App Control debugging and troubleshooting
- Understanding App Control events
- Using Event Viewer with AppLocker
- Process Monitor v4.13
- Microsoft 365 URLs and IP address ranges
- Resolve sync issues in OneDrive for work or school