In Windows 10 Pro based computers after installing the Security Update KB3147458 (April 12, 2016), the following error is appeared (2 times) when opening Group Policy Editor (gpedit.msc): “Resource ‘$(string.RequirePrivateStoreOnly)’ referenced in attribute displayName could not be found. File C:WINDOWSPolicyDefinitionsWindowsStore.admx, line 140, column 9. ”
Because of this error, the “Store“option(s) under the following two (2) locations inside Local Computer Policy editor (gpedit.msc) are missing:
- Computer Configuration -> Administrative Templates -> Windows Components -> Store
- User Configuration -> Administrative Templates -> Windows Components -> Store
To fix the “Resource ‘$(string.RequirePrivateStoreOnly)” issue and restore the Store options in Windows 10 Group Policy Editor, uninstall the Cumulative update KB3147458 (Windows 10 Version 1511 and Windows Server 2016), by following the instructions below, until Microsoft fixes the issue.
How to resolve the “Resource ‘$(string.RequirePrivateStoreOnly” issue and restore the “Store” setting(s) in Windows 10 Pro Group Policy Editor.
1. From the Start menu choose the Settings app.
2. At Settings choose Update and security.
3. At Update & Security click Advanced options.
4. At Update Advanced options select View your update history and at the next window select Uninstall Updates.
5. From the list of Installed updates select the Security Update for Microsoft Windows (KB3147458), and select Uninstall.
6. Let Windows to remove the selected update and then restart your computer.
7. After restart, launch Group Policy Editor (gpedit.msc). The “Resource $(String.RequirePrivateStoreOnly)” error should disappear and the Store settings will reappear under “Computer Configuration -> Administrative Templates -> Windows Components” & ” User Configuration -> Administrative Templates -> Windows Components”.
8 Finally prevent the KB3147458 Update from reinstalling in the feature by following the instructions on this tutorial: How to prevent a specific Windows 10 Update or Driver from installing.
That’s all! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.