Hello there,
This might be due to the Locally cached copy of roaming profiles.
To investigate a roaming profile load/unload issue you can enable userenv logging on a couple of clients' machines.
This log will capture all the information ie what happens in the background when a profile is trying to load/unload. To understand how to review the userenv logs you can read the following blog post. One problem with Userenv logging, especially on a busy terminal server with lots of logon activity, is that the log is overwritten before you get a chance to find the useful information in it.
Understanding How to Read a Userenv Log – Part 1 https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/understanding-how-to-read-a-userenv-log-8211-part-1/ba-p/395765
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–