why ‘reinstall’ instead of trying to find out what file or folder causes this? For example, checking for subdirectories and files by modified date and cut/pasting them out to a backup directory.
Reinstalling should never be needed and by doing such instead of/without keeping the old install around you destroy valuable evidence of a specific kind of corruption/breakage in the off chance a reinstall does help and the issue is in fact a bug…
Managed to get to a PC and check the trace, seems to be an unnamed background thread taking some sort of eternity, code in background thread is owned by nvwgf2umx.dll which means you’re going to have to report this to NVIDIA. We can’t do shit about yet another NVIDIA bug without repro, and the call stack shows just a single function looping over itself for a long time without calling any external APIs, so it’s impossible for anyone not NVIDIA to tell what it does or what might cause it, unless you actually have a repro (which we don’t, we don’t have your PC/OS install/anything, and neither is it occurring on any system we have access to).
The reason I reinstalled once was to be sure it was FiveM related, I then kept the corrupted install.
Anyway I did what you asked and I can get Fivem to start in 5sec instead of 2 minutes by deleting 1 files.
The file is called 9c5f7b879d7fe84968bc4b735912ce81_fce8395c8fd8a9c7_e3a7f04b6c3546c0_0_1.0.toc and is located in FiveM\FiveM.app\data\cache\NV_