For those of you experiencing this problem, do you have one environment working and one not working?
In non working environment, do you have this in profile logs in Fslogix?
Configuration setting not found: SOFTWARE\FSLogix\Profiles\GroupPolicyState. Using default: 0
In working environment, do you have this in profile logs in Fslogix?
Configuration setting not found: SOFTWARE\FSLogix\Profiles\GroupPolicyState. Using default: 1
Thats what I have, GroupPolicyState dword registry is not much described or mentioned in the registry keys list of fslogix.
I am testing this out now in non working environment: SOFTWARE\FSLogix\Profiles GroupPolicyState Dword:0001
Further in the same log
[07:09:48.134][tid:000014ac.00000958][ERROR:0000139f] Handle could not be recovered. DetachVirtualDisk will fail (The group or resource is not in the correct state to perform the requested operation.)
[07:09:48.134][tid:000014ac.00000958][ERROR:0000139f] DetachVirtualDisk failure (The group or resource is not in the correct state to perform the requested operation.)
[07:09:48.134][tid:000014ac.00000958][INFO] ErrorCode set to 5023 - Message: The group or resource is not in the correct state to perform the requested operation.
I assuming this "bug" or error has something to do related to same problem where the "include group" entries in policy had to changed from replace to update. No clue, but think it worth a try. When this grouppolicystate registry is used with default values "0" then it sometime could have problems locate user in the same group or something, and then not able to release the locks of file...... not sure.
Any explanation according to this registry setting or feedback on testing, is highly appreciated!