In my opinion, this is kind of a strange decision as the reason you’re in recovery mode may be caused by a setting. Also, note that the Settings app is unavailable from within Windows Recovery mode. These commands - actually the whole ms-settings: URI schema - will not work on older versions of Windows like Windows 8 and 8.1. Or, you can spell it out fully using the PowerShell commandlets (as shown below.) Start-Process 'ms-settings:' You can use the same command in PowerShell - where start is an alias for Start-Process. App developers and web authors should take care to link their users directly to the right section in Settings, reducing documentation needs and user friction. There’s no penalty for guessing wrong, so just take a guess and maybe you’ll drop straight into settings:windowsupdate without using the mouse. For example, ms-settings:network will go directly to the Network and Internet section of the Settings app. You can optimistically type in an English language keyword after the colon to direct you towards the right section of the Settings app. You’ll still need to use the start program if you want to launch the Settings app from a batch file, however.

The Run dialog will recognize the Settings app’s URI scheme ( ms-settings) without passing it through ‘ start’ and start the Settings app accordingly. Omit the start program prefix from the above command if you want to run it from the Run dialog ( Windows key + R) instead of from within a Command Prompt session. You can open the Settings app directly from the Command Prompt ( cmd.exe) in Windows 10 using the following command: start ms-settings:

You can open the legacy Windows Control Panel by starting control.exe, but how do you open the Windows Settings app from the Command Prompt or PowerShell?

Mac command tab settings