Share via

Settings won't open after I changed language settings (Windows 11)

Anonymous
2024-06-24T06:21:37+00:00

Hello.

I just received a new ACER laptop. I live in Japan so I needed to change windows to english. I did so, the computer reset, and when I tried logging back in (putting in my pin), it would take me to a black screen. I tried opening and closing the laptop and re-entering my pin and the same black screen would appear.

I then used the power button to turn off my laptop, that is when japanese writing came up with a percentage. I tried translating it and am pretty sure it was saying something like don't turn off your computer yet and that its 30% complete. But since I hit the power button, the computer still turned off.

I turned on the laptop again to find things were in english now (not everything, but most), but I cannot open my settings app. I found some articles giving me tips on trying to fix it, and I'm not having any luck. I'll post what I've tried below. If there is anything else you know that I can do, please let me know :(

  1. I tried this...
  2. Press Windows + R to open the Runwindow.
  3. In the Run window, enter the following command: ms-settings:
  4. I tried this...
    If Settings are not opening on Windows 11 due to missing or corrupt system files, an SFC Scan will fix it.
  5. Search for Command Prompt in the Windows Search bar.
  6. Click on Run as administrator to open the Command Prompt window.
  7. Type the following command in the Command Promptwindow and hit Enter to execute it: SFC /SCANNOW
  8. Reboot your system after the scan.
  9. I tried this... I couldn't actually do this though because it wasn't previously set up

If the Settings app had been working fine earlier, then a recent change might have caused the problem.

  1. Search for Recovery****in the Windows Search barand click on it.
  2. Select Open System Restore
  3. Select Next.
  4. Select the Restore Point and click on Next.
  5. Click on Finish.
  6. I tried this...

Some apps and malware can disable the Settings app from the Registry Editor itself. You can re-enable it as follows:

  1. Press Windows + R to open the Runwindow.
  2. Type the command REGEDITin the Run window and hit Enterto open the Registry Editor.
  3. Go to the following path in the Registry Editor window: HKEY_CURRENT_USER\Software\Microsoft\ Windows\CurrentVersion\Policies\Explorer
  4. Right-click on the open space on the right pane.
  5. Select **New >> DWORD (32-bit)**entry.
  6. Name this newly created DWORD (32-bit) entry NoControlPanel.
  7. Double-click on the newly created entry and change the value of the Value Data to 0.
  8. Click on OKto save the settings.
  9. The Settingsapp should work now.
  10. I tried this...

If Settings are not opening on Windows 11, you can re-register the app through Windows PowerShell.

  1. Search for Windows PowerShellin the Windows Search bar.
  2. Click on Run as administratorin the right pane to open the Windows PowerShell window.
  3. Copy-paste the following command and hit Enterto execute it: powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootImmersiveControlPanelAppxManifest.xm
  4. Check if it fixes the problem.

When i tried this, after entering the command it game me this message and I didn't know what to do...
cmdlet Add-AppxPackage at command pipeline position 1

                    Supply values for the following parameters: 

                    Path:
  1. I tried this...
  2. Search for Command Promptin theWindows Search bar.
  3. Click on Run as administratorin the right-pane to open the Command Promptwindow
  4. Copy-paste the following command and hit Enter to execute it: Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}
  5. Reboot your system and the Settings app should work. When I tried this, after entering the command it gave me this message...
    'Get-AppXPackage' is not recognized as an internal or external command,
                 operable program or batch file.  
    
  6. I tried this...
    If Settings are not opening on Windows 11, you can consider resetting it.
  7. Search for Reset this PC in the Windows Search bar.
  8. Click on the option that appears.
  9. SelectReset PC.
  10. Click on Keep my files.
  11. Select Cloud download
  12. Click on Next I couldn't get passed step one of this because I can't do anything related to my devices settings

Is there anything else I can do? Surely there has to be a way to wipe my computer...As it's new, I would not mind doing so as there really isn't any saved data on it, maybe besides whatever it's preinstalled with (which I'm not sure is important or not).

Windows for home | Windows 11 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2024-06-24T06:36:41+00:00

Wahoo I found a different solution that worked! If someone comes across this issue, here is the answer that worked for me!

When the Settings app is not opening in Windows 11, you should clear the Settings cache. This is effective because it removes problematic temporary files, fixes conflicting cache data, and forces app data regeneration that may trigger the problem.

  1. Press Windows + R to open the run dialog.
  2. Type the command below and hit Enter to clear the Settings app cache. Note that this will remove all customized settings. cmd /c rd /s %localappdata%\Microsoft\Windows\Settings

Settings cache - How to Fix Settings Not Opening in Windows 11

3a. (this one wasn't mentioned, but it's a step I had to do) Agree to letting this happen by typing "Y" and then clicking enter.

  1. Restart your computer.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Ramesh 176.3K Reputation points Volunteer Moderator
    2024-06-24T06:57:36+00:00

    Hi Mac,

    Glad it's fixed. Thanks for sharing the solution.

    Was this answer helpful?

    0 comments No comments