{"id":16055,"date":"2020-09-24T00:23:00","date_gmt":"2020-09-23T22:23:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=16055"},"modified":"2020-09-23T23:18:30","modified_gmt":"2020-09-23T21:18:30","slug":"windows-10-problem-mit-gruppenrichtlinieneditor","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/09\/24\/windows-10-problem-mit-gruppenrichtlinieneditor\/","title":{"rendered":"Windows 10: Update KB4571756 causes an error in group policy editor"},"content":{"rendered":"

[German<\/a>]I'll take up the topic, which was raised by a blog reader, here. After September 2020 patchday and installing update KB4571756)the reader gets an error in the group policy editor that the SetProxyBehaviorForUpdateDetection<\/em> element is not found – but under Windows 10 Home 2004 (32bit) – reported. But there is a simple solution, but with pitfalls.<\/p>\n

<\/p>\n

\"\"German blog reader Dennis T. uses Windows 10 Home 2004 in a 32-bit version. The Home edition does not have a group policy editor (gpedit.msc) by default. But Dennis mentioned, that gpedit.msc <\/em>can be installed without problems (see this article<\/a> for instance). <\/p>\n

Update KB4571756 raises an error in gpedit.msc<\/h2>\n

However, the blog reader noticed that installing the update KB4571756<\/a> from September 2020 causes him to get an error in the Group Policy Editor. The reader wrote:<\/p>\n

\n

after installing the cumulative Updates KB4571756 Win 10 Home 2004 (32bit) I got two popups with the following message when I started the group policy editor:<\/p>\n

The policy element \"SetProxyBehaviorForUpdateDetection\" referenced in presentation \"CorpWuURL\" was not found. File C:\\WINDOWS\\PolicyDefinitions\\WindowsUpdate.admx, row 393, column 13<\/p>\n<\/blockquote>\n

So the group policy editor gpedit.msc<\/em> has problems reading the required WindowsUpdate.admx<\/em>. But the blog reader has also found a solution.<\/p>\n

The solution of the problem<\/h2>\n

Blog reader Dennis has found a very simple solution to this problem. He writes about it in his solution:<\/p>\n

\n

The file \"WindowsUpdate.adml\" in \"C:\\Windows\\PolicyDefinitions\\en-DE\" has as date 10.09.2020 14:09; but the \"WindowsUpdate.admx\" in \"C:\\Windows\\PolicyDefinitions\" has as date 31.05.2020 04:13. This is where MS has been sloppy again, because the new file is located in the folder \"C:\\Windows\\PolicyDefinitions\":<\/p>\n

C:\\Windows\\WinSxS\\x86_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_10.0.19041.508_none_ed7bff8eb90e43c4\\WindowsUpdate.admx<\/p>\n

with date of 09\/10\/2010 14:08 exists, but is not installed after C:\\Windows\\PolicyDefinitions. <\/p>\n

If I copy it to C:\\Windows\\PolicyDefinitions the GPEditor starts normally, but sfc \/scannow shows this as an error and (repaired) copies the file from 31.05.20 back again. Then sfc \/scannow runs through without errors, but the GPEditor starts again with the above error popups. It's no big deal, but annoying! Maybe it's helpful for one or the other.<\/p>\n<\/blockquote>\n

It remains to be seen when Microsoft recognizes and fixes this. Thanks to Dennis for this hint and the description of the solution. Anyone else affected by this bug?<\/p>\n

Similar articles:<\/strong>
Windows Server 2016: Update KB4577015 throws a GPO MMC wsecedit.dll error<\/a>
Windows Server 2016: Workaround for GPO-MMC wsecedit.dll<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]I'll take up the topic, which was raised by a blog reader, here. After September 2020 patchday and installing update KB4571756)the reader gets an error in the group policy editor that the SetProxyBehaviorForUpdateDetection element is not found – but under … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[2221,47,76],"class_list":["post-16055","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-gpo","tag-issue","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/16055","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=16055"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/16055\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=16055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=16055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=16055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}