I just updated the Windows 10 ADMX files in the Central Policy Store of my lab domain with the Windows 10 1803 ADMX files. After that I got the error that the resource $(string.Win7Only) referenced in attribute displayName could not be found when accessing the Administrative Templates with the Group Policy Editor.
I checked the mentioned searchocr.admx and the corresponding searchocr.adml file and found out that the modified dates differed by around three years (2015 and 2018).
Looking at the extracted 1803 ADMX files from the download revealed that they only include the SearchOcr.ADML files not the corresponding ADMX.
The c:\Windows\PolicyDefinitions folder of a running instance of Windows 10 1803 does not contain the two files.
Update 2: On 7/13/2018 Microsoft released Version 2.0 of the 1803 ADMX files without the issue
As long as I cannot find the 1803 version of the SearchOcr.admx I restored the old SearchOcr.adml file(s) from my backup and the error went away. Or even better remove the SearchOcr.ADML from every language that you want to import to the Central Policy Store. @Jtracy_ItPro pointed out to me that the SearchOcr.adml is not the only orphaned ADML in the ADMX pack. The following list ADML files are orphaned in the 1803 ADMX pack as well fileservervssagent.adml microsoft-windows-geolocation-wlpadm.adml microsoft-windows-messaging-grouppolicy.adml searchocr.adml terminalserver-winip.adml userdatabackup.adml wwansvc-admin-group-policy-data.adml Any of these files can cause similar errors if you already have an older version of the ADMX and ADML in your Central Policy Store. Therefore I wrote a small PowerShell function to find any orphaned ADMLs in a PolicyDefinitions folder. You can use this function to find and remove any orphaned ADML before importing the files to the Central Policy Store