Hello,
We have the same problem. We are using Horizon 2406 with FSLogix in Instant Clone but with persistent machines. We try to migrate our users on the new Teams but after a few days of use, the users have this error “48v35”. Restarting Windows solves the problem.
- ChrisHenrriquezMar 22, 2025Copper Contributor
By any chance does your environment have more than 1 VM. I ask because I usually see this behavior whenever users have been logged in to a host, and they don't close their sessions appropriately (i.e. the session is just disconnected or the host is turned off and then when they log in to another host then they get that error).
- MarcC78Jan 19, 2025Copper Contributor
Except restarting the machine or forcing log off/log on doesn't actually fix it in the long term. It will come back for people in that VM eventually.
- carolwJan 19, 2025Copper Contributor
Restarting fixed for me too, thanks