MicrosoftWe are also having this issue after updating to this version.
Along with the Invalid map(K, T) error in the logfile we are also seeing error "Get token groups (Er is geprobeerd te verwijzen naar een token dat niet bestaat.)" with Event ID 26 in the event log.
When testing i noticed that when i made a new profile disk for a user with the issue the problem didnt happen for that user anymore.
I found a workaround by enabling cleanup invalid sessions, which doesnt fix the issue but a few seconds after the logoff it dismounts the disk anyways.
I agree that the "cleanup invalid sessions" option helps. We have never needed this option in the past. Enabling this new option does seem to resolve the immediate problem but does not address the root issue. The cryptic "Invalid map(K, T)" error needs to be explained by FSLogix.
My biggest concern here is that the FSLogix group pushes this thought that "Customers are required to run the latest version" (in principle); yet, the FSLogix group is completely silent when legitimate issues are encountered.
There should be a public acknowledgement of the issue and an explanation as to what it means and what (if anything) can/should be done. Instead we just have this glowing announcement that this new version is great and everyone should upgrade. Hate to be critical here but I don't think this situation is good.
Has there been any progress on this issue?
