Issue: Under certain circumstances you might not be able to link an existing GPO to an organizational unit from a Windows Server 2016 or a Windows 10 environment, or you might not be able to display the GPO’s list of links.
Workaround #1: Use an earlier version of a Windows operating system such as Windows Server 2012 R2 or Windows 8 to create the link or display the GPO’s list of links.
Workaround #2:
On a Windows Server 2012 R2 machine, go to C:\\Windows\SysWOW64 and copy the gpedit.dll file.
Paste the file into the <GPA installation path>\Bin folder on the Windows 10 or Windows Server 2016 machine.
Go back to the C:\\Windows\SysWOW64 folder and locate the appropriate language folder. For instance, if you are running an English language environment, locate the en-US folder.
Copy the gpedit.dll.mui file from the langauge folder.
Go to the <GPA installation path>\Bin folder on the Windows 10 or Windows Server 2016 machine and create a folder and give it the appropriate language name. For example, en-US.
Paste the gpedit.dll.mui file into the language folder.
NOTE:This change will not impact native and other external applications. Only the GPA Console will use the local copy of gpedit.dll while launching the appropriate user interfaces.