{"id":335,"date":"2019-03-29T09:38:02","date_gmt":"2019-03-29T14:38:02","guid":{"rendered":"http:\/\/itblog.ldlnet.net\/?p=335"},"modified":"2019-03-29T09:38:02","modified_gmt":"2019-03-29T14:38:02","slug":"unable-to-open-settings-from-the-settings-app-in-windows-server-2016-2019","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2019\/03\/29\/unable-to-open-settings-from-the-settings-app-in-windows-server-2016-2019\/","title":{"rendered":"Unable to open settings from the Settings App in Windows Server 2016\/2019"},"content":{"rendered":"\n

In Windows Server 2016\/2019 you have been upgraded to the Windows 10 Desktop Experience GUI. So, in the new versions, you are directed to use the \"Gear to get to your settings. What was happening within the Settings is that I would choose a setting that calls on the control.exe file to open a Control Panel app. I would get the following error when attempting to do that function:<\/p>\n\n\n\n

\"\"
Permission Denied to Open a CPL Applet through control.exe<\/figcaption><\/figure><\/div>\n\n\n\n

I immediately think it is a permissions issue. So I go to try to validate the permissions so that I could change them. Turns out, that due to it being a Windows System directory, I couldn’t modify the permissions without compromising directory security with NTFS permissions:<\/p>\n\n\n\n

\"\"
The options are all greyed out for the directory on purpose<\/figcaption><\/figure><\/div>\n\n\n\n

Now, if I open Control Panel, Network Sharing Center, etc…, I was able to access the applets with no issues. This was just happening in the Settings Gear Box Application. So, I started looking around and found that there is a registry key that needs to be modified so that your Administrator account can open these settings apps through the Settings Application:<\/p>\n\n\n\n

1) Launch the\u00a0Registry Editor<\/strong>\u00a0(regedit.exe)
2) Navigate to:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System<\/strong>

3) Change the value of\u00a0FilterAdministratorToken\u00a0(REG_DWORD) from 0 to 1<\/strong>\u00a0(If you don’t see that key, you can create it by right-clicking on any empty space from the right panel and select New > DWORD value, type the name and set the value to 1)
4)\u00a0Reboot\u00a0<\/strong>the computer and then it will be working fine. <\/p>\n\n\n\n

I decided to create a Group Policy in AD to add this registry key so that it would propagate to all my 2016\/2019 Servers:<\/p>\n\n\n\n

1) Launch the\u00a0Group Policy Manager
2) Create a new GPO and Link it to your Domain
3) Go to Computer Configuration > Preferences > Windows Settings > Registry > New Registry Key (DWORD)
4) Set the Action to “Replace”
5) Set the path as:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System<\/strong>
6) Set the Key as FilterAdministratorToken<\/strong>
7) Set the Value as 1 (Decimal Format) and Save
8) Run gpupdate \/force on your servers.
9)\u00a0Schedule a Reboot of those servers for the change to truly take effect. <\/p>\n\n\n\n

\"\"
GPO Settings<\/figcaption><\/figure><\/div>\n\n\n\n

After the reboot of the server, all the apps launched correctly from the Settings Application within Windows. I am going to research a little more to see why this is like that. If you have a comment, or more information, please feel free to post!<\/p>\n\n\n\n

HAPPY TROUBLESHOOTING!
PLEASE COMMENT!
<\/h2>\n","protected":false},"excerpt":{"rendered":"

In Windows Server 2016\/2019 you have been upgraded to the Windows 10 Desktop Experience GUI. So, in the new versions, you are<\/p>\n

Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":159,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48,2,16],"tags":[158,160,159,162,161,164,153,165,163,157,166,20],"class_list":["post-335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-active-directory","category-general","category-windows","tag-control-panel","tag-control-exe","tag-error","tag-gpo","tag-group-policy","tag-hklm","tag-permissions","tag-policy","tag-registry","tag-settings","tag-system","tag-windows","odd"],"_links":{"self":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":1,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"predecessor-version":[{"id":340,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/335\/revisions\/340"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media\/159"}],"wp:attachment":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}