locked
gpedit.msc - "Resource '$(string.RequirePrivateStoreOnly)' referenced in attribute displayName could not be found." RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    9
    Sign in to vote

    At some point after installing the last two Windows 10 builds (KB3147458 and KB3140741), I started getting the error message "Resource '$(string.RequirePrivateStoreOnly)' referenced in attribute displayName could not be found." when opening the group policy editor.  It points to WindowsStore.admx, line 140, column 9.

    The referenced string does not exist in ...\EN-US\WindowsStore.adml.  With this being the case, what exactly should I infer?  Did Microsoft remove this particular policy and forget to remove the policy block referencing it in WindowsStore.admx?  Is it safe to remove this block manually, or will that compromise SFC and/or component store integrity?

    Thanks

    Wednesday, April 13, 2016 1:38 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Same here. I instead added the necessary entries to the string table (in WindowsStore.adml) and that suppressed the error message, and brought back the "Store" category under Windows Components.

    Removing the RequirePrivateStoreOnly block from the ADM might work as well. In both cases, this changes the file integrity, and I guess running SFC will replace the modified file(s) anyway.

    >> Did Microsoft remove this particular policy and forget to remove the policy block referencing it in WindowsStore.admx?

    Or may be it's the other way around? WindowsStore.admx seems to have last modified on 3/24/2016, whereas WindowsStore.adml shows the last modified time stamp as 10/30/2015...

    Ramesh Srinivasan  |  The Winhelponline Blog



    Wednesday, April 13, 2016 5:11 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    I am getting the same error on my system, though it started right after installing the latest Cumulative Update for v1511 (KB3147458), I wasn't getting the error before.  Since I opened gpedit before I rebooted with no error, I assume it has something to do with that update.
    Wednesday, April 13, 2016 5:47 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Same error after update.
    Wednesday, April 13, 2016 1:01 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Same issue.

    Wagnard

    Wednesday, April 13, 2016 1:44 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Uninstalling KB3147458, fixed the issue for me. I've shared this post on one asking about issues with the April updates.

    https://social.technet.microsoft.com/Forums/en-US/f742777a-5a4d-4cd6-8ae0-ab139143abd3/anyone-seeing-issues-with-the-april-updates-kb3147461-and-kb3147458?forum=win10itprogeneral



    • Edited by CoMO Tiger Wednesday, April 13, 2016 3:59 PM
    Wednesday, April 13, 2016 3:56 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Same result on my Surface Pro.  I haven't checked my other two PCs yet.  Went in the group policy editor to make a change and made me think there was something corrupt on my install.  This page was the only result when I searched this error.
    Wednesday, April 13, 2016 4:42 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Same here. I instead added the necessary entries to the string table (in WindowsStore.adml) and that suppressed the error message, and brought back the "Store" category under Windows Components.

    Removing the RequirePrivateStoreOnly block from the ADM might work as well. In both cases, this changes the file integrity, and I guess running SFC will replace the modified file(s) anyway.

    >> Did Microsoft remove this particular policy and forget to remove the policy block referencing it in WindowsStore.admx?

    Or may be it's the other way around? WindowsStore.admx seems to have last modified on 3/24/2016, whereas WindowsStore.adml shows the last modified time stamp as 10/30/2015...

    Ramesh Srinivasan  |  The Winhelponline Blog



    Wednesday, April 13, 2016 5:11 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Update:

    For now, removing the "RequirePrivateStoreOnly" Policy markup from the .ADMX file also works. 

    Ramesh Srinivasan  |  The Winhelponline Blog


    Wednesday, April 13, 2016 10:08 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi cousinit99,

    Since this issue occurred after installed KB3147458 and KB3140741, we could try to uninstall them to have a test. Please create a restore point before we made any modifications.

    Meanwhile, I will test it on my side, will post here as soon as I get results.

    .

    Since these KB are released recently, Microsoft is still collecting related issues about these KBs, you could report this issue on your side. 

    For example, here is case about collecting related issues with KB3147458, you could post your issue here as well.

    https://social.technet.microsoft.com/Forums/en-US/f742777a-5a4d-4cd6-8ae0-ab139143abd3/anyone-seeing-issues-with-the-april-updates-kb3147461-and-kb3147458?forum=win10itprogeneral

    Hope it is helpful for you

    .

    Best regards.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 14, 2016 11:10 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Same error in Windows 2016 Technical Preview 4 Build 10586 after recent updates

    /Harti

    Friday, April 15, 2016 9:49 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I experienced this failure detailed above while trying to resolve the following incident on my computer:

    https://support.microsoft.com/en-us/kb/3077013

    Test Environment:

    Microsoft Windows Version 1511 (OS Build 10585.218)


    • Edited by MrLaDeDa Thursday, April 21, 2016 2:21 AM
    Thursday, April 21, 2016 2:18 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Same here on Windows 10 Version 1511 (OS Build 10586.218)
    Thursday, April 21, 2016 1:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi cheecheened,

    You can fix this error by editing the .admx file manually. Ful instructions at http://www.winhelponline.com/blog/gpedit-resource-string-requireprivatestoreonly-windowsstore-admx-kb3147458/

    Hope that helps!

    Ramesh Srinivasan  |  The Winhelponline Blog

    Thursday, April 21, 2016 3:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi cheecheened,

    You can fix this error by editing the .admx file manually. Ful instructions at http://www.winhelponline.com/blog/gpedit-resource-string-requireprivatestoreonly-windowsstore-admx-kb3147458/

    Hope that helps!

    Ramesh Srinivasan  |  The Winhelponline Blog


    That "fix" was problematic for me.  Although it fixed the Group Policy error message, when I ran SFC /SCANNOW it found corruption that it couldn't repair.  So I ran DISM /online /cleanup-image /restorehealth and it restored the component store corruption.  Then, SFC /SCANNOW was able to fix the corrupted file.  After looking in the CBS log, the file that it "repaired" was the WindowsStore.admx that I modified using that link.  So, I think for now, I'd prefer to live with the gpedit.msc error message.
    Sunday, April 24, 2016 5:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes. It's expected. SFC or DISM would see it as integrity violation or file corruption and would restore fresh copy from the source. I'd ignore what SFC says about the file.

    Ramesh Srinivasan  |  The Winhelponline Blog

    Sunday, April 24, 2016 8:39 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Looks like this has been fixed in the May Update Rollup. Just installed it on an affected machine and I no longer get the error. I never uninstalled KB3147458.
    Tuesday, May 10, 2016 9:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Looks like this has been fixed in the May Update Rollup. Just installed it on an affected machine and I no longer get the error. I never uninstalled KB3147458.

    I can confirm, I just booted a laptop that has been off for about a month, and needed to change something on it in the gpedit.msc. Got these errors, but made the change I needed. So, while waiting for updates to install, came upon this thread. Updates have finished and after reboot, no longer get an error. 

    But thanks to those in the thread earlier as well

    Thursday, May 12, 2016 1:36 PM