This issue occurs because the system stores GUID records in a different hash table than the place where the system looks for them. The fix that's described in the "Resolution" section makes sure that the system stores and looks for GUID records from the correct hash table.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3164088 - Last Review: Feb 14, 2017 - Revision: 1
Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows RT 8.1