Settings>Privacy>Location Crashes


  1. Posts : 81
    Windows 10 Pro 64-Bit 21H1
       #1

    Settings>Privacy>Location Crashes


    Running Win 10 Pro 64-bit 21H1...

    Every time I attempt to go to Settings>Privacy>Location, the Settings app crashes and closes. All other entries under Settings>Privacy work as normal. Never seen the Settings app crash before.

    Any ideas?
      My Computer


  2. Posts : 5,330
    Windows 11 Pro 64-bit
       #2

    Re-register settings app, open Command Prompt with administrative privileges and execute following command:

    Code:
    PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage *immersivecontrolpanel*).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"
      My Computer


  3. Posts : 81
    Windows 10 Pro 64-Bit 21H1
    Thread Starter
       #3

    Thanks for the suggestion. First I ran sfc /scannow. Then I reset the settings app. Finally, I did the re-register command. Problem still persists...

    Event Viewer indicates Exception code: 0xc0000409 in KERNELBASE.dll, which AFAIK is a generic code that provides no useful information.

    Subsequently, I ran the following commands:

    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    chkdsk /scan

    No errors reported.

    - - - Updated - - -

    I observed that Settings>System was crashing. I rebooted in Safe Mode. When I attempted Settings>System, I saw this:

    Settings>Privacy>Location Crashes-img_20211016_214154-min.jpg

    So I performed a System Restore from a few days ago. So far, all parts of Settings appear to be working again. Still don't know exactly what happened, but at least things are back to normal...
      My Computer


  4. Posts : 5,330
    Windows 11 Pro 64-bit
       #4

    I'm glad to know the problem resolved.
      My Computer


  5. Posts : 81
    Windows 10 Pro 64-Bit 21H1
    Thread Starter
       #5

    Preliminary evidence suggests the cause may have been upgrading PowerShell from 7.1.4 to 7.1.5.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:31.
Find Us




Windows 10 Forums