In a rare situation when you’re finished a Windows OS installation and trying to open up gpedit.msc (Local Group Policy Editor), you may received multiple prompts saying “Resource XXXXX referenced in attribute displayName could not be found…” error message like the one showing below.
This type of error message could be daunting for some technicians especially it throw up multiple error windows with just one “OK” button. You will have to clicking on all of these buttons until it vanished to be able to manipulate these local group policies. But the truth is that this type of issue can be resolved easily via the following steps.
This issue usually caused due to missing the Language packs(LPs) or Language Interface Packs(LIPs). Or when you’re installed an Asian language-based Windows OS and trying to switch to English. (For example, in my case I installed the Windows Server 2022 with Chinese language based and switched to English). Even installed the English language pack from Settings some apps still displayed incorrectly.
To resolve this issue simply follow below steps (in my case from Chinese to English):
1.Installing the English language pack from the Settings app. When finished performing a reboot or sign-out.
2.Open PowerShell or Command Prompt with admin rights > enter “gpedit.msc” to open Local Group Policy Editor. (If the issue still persists then move on step 3)
3.Open PowerShell or Command Prompt with admin rights > enter “sfc /scannow”. If running without extra error, you should receive a message from Notification Center saying “We are adding some new features to Windows.”
4.When the verification reaches to 100% perform a reboot.
5. Sign-in back to Windows and open up Local Group Policy Editor to verify. All good without error message prompt.
However, for some reason the Asian language-based Windows OS still displayed partially with localized Asian language, but it does not affect most of applications. It might be a bug as I’ve seen this kind of issue happens long time ago…
