This error message, although disruptive, isn’t too big of a problem as dismissing it causes it to go away and then come back, and once it is dismissed for a second time, affected users are free to go about their business in the Local Group Policy Editor. However, the real problem here is that, as part of this issue, the Store folder under User Configuration > Computer Configuration > Windows Components in the Local Group Policy Editor goes missing. Pro Tip: Before proceeding with the steps listed and described above, be sure to navigate to C:\Windows\PolicyDefinitions\ and copy a file named WindowsStore.admx to a safe location as a backup to be restored to its original location in the event that something goes wrong. While a Windows 10 user can deal with having to dismiss a couple of error messages when launching the Local Group Policy Editor, an entire folder of policies going missing is kind of a massive issue. This problem is probably caused because the KB3147458 update has added a new policy setting to the WindowsStore.admx file but failed to add its corresponding string ID to the WindowsStore.adml file. When this issue first came to light, affected users simply uninstalled the KB3147458 update and hid it in anticipation of another Windows update that would fix the issue seeing as though Microsoft became aware of this bug almost immediately. Thankfully, within a month of the surfacing of this problem, Microsoft rolled out a Windows update equipped with a more than viable fix. However, if you can’t install the Windows update that fixes this issue or if you are still experiencing this issue even after installing all available Windows updates, here’s what you need to do in order to fix this problem: Right-click on the Start Menu to open the WinX Menu. Click on Command Prompt (Admin) to launch an elevated Command Prompt that has administrative privileges. One by one, type in the following commands, pressing Enter after each one and also waiting for one command to be executed successfully before typing in the next one: Once Notepad launches, press Ctrl + G, type 133 in the Line number field and press Enter. Select all of the contents of lines 133–166 (including both line 133 and line 166) and press Delete. Note: In case you still don’t get what needs to be deleted, the following are all of the lines that need to be cleared:
Press Ctrl + S to save the changes you have made to the admx file and then close Notepad. Back in the elevated Command Prompt, type in the following command-line and then press Enter to restore ownership of the admx file back to TrustedInstaller.
Once the command-line has been executed successfully, you can close the elevated Command Prompt and restart your computer. Once your computer boots up, you should no longer receive any error messages when launching the Local Group Policy Editor and the Store folder of policies should also be back where it belongs.
How to Open Local Group Policy Editor on Windows 10Disabling the Start Menu on Windows 10 using Group Policy EditorHow to Reset Local Group Policy Settings to Defaults in Windows 10Fix: Windows Defender Blocked by Group Policy Error 0x800704ec
