New
#11
SystemSettings.exe is the program that launches when it's trying to open a specific page such as "ms-settings:display". Looking at the app manifest in C:\Windows\ImmersiveControlPanel\ it calls on whatever DisplayName it has, which is kind of fun. ms-settings:Cancer now opens the main page. As far as I can tell every page in the ImmersiveControlPanel is called on by the string "ms-settings:DisplayName and the DisplayName is the same as the URI (:display, etc.). I could only edit the DisplayName in Registry Editor but it's kind of a pain to find any one of them. This is probably why you can't run SystemSettings.exe directly, it says it launches by a URL protocol in Registry Editor. If you'd like to find the DisplayName I'd suggest getting a third party Registry scanner to do a filtered search (like "ms-settings:") and going from there.
SystemSettings tiles used to be actual files located in the C:\Windows\ImmersiveControlPanel\ but now it seems to have been restructured. There's Windows.UI.Xaml.dll, multiple immersivecontrolpanel package directories, settings entries configured between manifests, dlls, and xml files. If you want your system to call on a specific page of SystemSettings that needs to be edited, then you'll probably need to use the URL protocol, because that's how the system is using it. If you want to write a script or something that changes something up and have it call on one specific file that defines a page within the program you won't find it because it's been scattered in many different ways, plus the system doesn't directly launch SystemSettings.exe so I don't see it working if you do target it and specify a particular handle. ms-settings:{PublisherDisplayName} may be your best bet for getting some usage out of it and it seems like it's the same as the URIs for each page, though the specific DisplayName is what comes after "ms-settings:".
Hope this helps,
Yokiaza
Quote