I can’t say I’ve seen that before. I’d suspect that there may be a long-running action or property thst is leaving something locked on the machine, but it’s just a guess.
When the client hangs, was there a running Action? It might be shown in recent log entries, or it could be an action started much earlier, so I’d check the status in the Console for action history on the computer before restarting the client.
You may need to enable client debug logging to see whether you can identify a particular property that is getting evaluated and taking a long time to run. The procmon utility from microsoft.com/sysinternals may be helpful as well, if you can see the besclient.exe process still trying to do anything while it’s in this hung state.
If you don’t have a support ticket open yet, you should probably create one so the support team can guide you on troubleshooting it.