Troubleshooting
Problem
Symptom
Affected Windows 10/11 devices may show one or more of the following symptoms:
- Location Services cannot be enabled, remaining stuck in the Off position or greyed out.
- “Some settings are managed by your organization” appears when attempting to toggle location.
- Apps (e.g., Maps, Senturo) cannot determine device location.
- Automatic timezone settings fail or revert, suggesting underlying location detection issues.
Cause
· Intune policy not configured or not applied
Devices require specific location-access settings for consistent operation.
· Conflicting GPO or registry settings disabling Location Services
Corporate policies, legacy GPOs, or manual registry keys can disable location features.
· Location service (lfsvc) disabled or modified by security baselines
Windows baselines or hardening tools can disable required services.
· Privacy settings hidden or suppressed during Autopilot
Autopilot configurations may hide privacy prompts, preventing users from granting access.
· Incorrect fallback location settings leading to bad time zone/location resolution
Investigations show devices may misinterpret location if default location info is wrong.
Environment
Intune
Diagnosing The Problem
1. Validate Intune Policy Configuration
Confirm that the following Intune settings are enabled:
| Setting | Location | Required Value |
|---|---|---|
| Let Apps Access Location | Privacy → Let Apps Access Location | Enabled → Force Allow |
| Turn off location (User) | Windows Components → Location and Sensors | Disabled (optional but recommended) |
Steps:
- Go to Intune admin center → Devices → Configuration profiles.
- Open your Windows 10/11 profile.
- Confirm the above settings are present and not overridden by another policy.
If multiple conflicting profiles exist, consolidate them.
2. Check for GPO Conflicts (Hybrid or Legacy Environments)
Devices joined to on‑prem AD may still process GPOs that disable location.
Verify the following policies:
- Computer Configuration → Administrative Templates → Windows Components → Location and Sensors
- Ensure Turn off location is Not configured or Disabled.
Registry Keys to check
(Values must be 0)
HKLM\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors\DisableLocation
HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LocationAndSensors\DisableLocation
3. Confirm the Windows Location Service (lfsvc) is Running
Location Services rely on the lfsvc service.
Check service state:
- Open Services.msc
- Verify:
- Geolocation Service (lfsvc) → Startup: Manual (Trigger Start) or Automatic
- Status: Running
Baselines or hardening may disable this service.
4. Validate Privacy Settings (Post‑Autopilot Enrollment)
If Autopilot hides privacy prompts, devices may never receive user consent for location.
Fix:
- Change Autopilot profile to show privacy settings, or
- Enforce “Let Apps Access Location → Force Allow” to bypass user prompts.
5. Test Built‑in Apps for Location Accuracy
Use Windows Maps to validate location resolution.
Issues may include:
- Maps pinpointing geographically incorrect areas (e.g., Africa).
Additional resources:
Microsoft Learn – How Windows determines location, permissions, and app access
Microsoft Learn – Known Issues with Microsoft Intune
Microsoft Learn – Configure device restriction settings in Microsoft Intune
- Location only refreshes after reboot.
Fixes:
- Set a default location in Maps → Settings.
- Clear location history (Settings → Privacy → Location).
6. Restart the Windows Location Stack
Run elevated PowerShell:
PowerShell
Get-Service lfsvc | Restart-Service
Stop-Service wlidsvc -Force; Start-Service wlidsvc
Show more lines
This forces reinitialization of location components.
7. Remove Residual “Your organization manages this setting” Registry Keys
If location settings are greyed out, remove obsolete registry remnants.
Only run in testing or with caution:
BAT
reg delete "HKCU\Software\Policies" /f
reg delete "HKLM\Software\Policies" /f
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies" /f
Show more lines
Reboot afterward.
8. Check for Windows Version‑Specific Issues
Location‑related issues may arise after Windows updates (e.g., 24H2/25H2 update cycles).
While recent known issues do not explicitly cite Location Services, Windows 25H2 is known for other post‑update regressions, so check the Windows Release Health Dashboard if issues coincide with an update.
Advanced Diagnostics
Check capability access via PowerShell
PowerShell
Get-CimInstance -Namespace root\cimv2\mdm\dmmap -ClassName MDM_Policy_Config01_Privacy02
Show more lines
Confirm AAD MDM policies
PowerShell
dsregcmd /status
Show more lines
Check event logs
- Event Viewer → Applications and Services Logs → Microsoft → Windows → Location → Operational
Look for policy application failures or service errors.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
23 January 2026
UID
ibm17257084