You might start with the profiles where the Duplicates were not created.
Can you share the Event ID you are getting while you run this process?
This thread explains a similar situation and the points discussed here might be helpful https://learn.microsoft.com/en-us/answers/questions/194877/rds-w2019-default-printer-lost-on-session-disconne
You can also use tools like procmon to identify the root cause.
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry, and process/thread activity. You can get the tool from here https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–