Haven’t had this issue so far for the last month.
The two things I changed simultanously which one of them fixing it (my guess is second):
- Upgraded to UE 5.5.3 github release build
- Changed to process of starting up the Development-Editor
- Previously: Starting VS2022 in Administrator and opening the project and start debugging from there.
- Now: Double-Clicking the project.sln which opens VS2022 in normal mode and start debugging from there.
My guess is that the admin VS2022 unloading process messes somehow up the included UE5 project files.
Still have livecoding, hotreload and fab off just in case.
Turning fab only on when I have an asset to import.
Blocking .NET Ports / Processes still a thing though if you quickly stop and start debugging again after a code change and recompile.