Thanks for the answer, Marjin.
The reports are complete, I selected the entire text files on Notepad++ and pasted the contents onto pastebin.
I’m not quite sure what that ASUS ROG Live Service is, all ASUS related software I have was installed together with drivers for my motherboard, iirc.
As soon as you mentioned a Razer Chroma file in the System32 folder, I knew that had to be the problem, since Overwatch always had that option to sync the game’s colours to your Razer peripherals, and I’ve stopped using Razer and uninstalled all Razer software from my computer over 2 years ago. The problem wasn’t the fact that the Razer DLL was there, it was that it was very outdated.
I have no idea why would that file even still exist there, so I deleted it and the game is starting up fine now.
Really weird that I’ve been able to play for the last 2 years with no problems, and out of nowhere a Razer software leftover DLL starts causing issues… But when the Razer software was uninstalled that file should’ve been removed, I think.
My startup programs may be crowded, but I’ve only got a few enabled (NGenuity2, lghub, glasswire, GameplayTimeTracker, iCUE Launcher, RtkAudUService64, nw), and even if I enabled all those programs, they certainly would not impact a system to a point that a game couldn’t start. (and only one specific game, for that matter)
Salad is not a malicious program at all, I have no idea where you could’ve gotten that information. Check their website.
I had also already checked the support articles you linked, most of them were steps on the Overwatch 2 Crashing at Startup article, which I had already completed.
I hope this problem gets more well-known, since many people could have it happen to them, (anyone who stopped using Razer products and got that outdated DLL on their system) and the fix is really, really simple, and doesn’t require doing any system checks/updates, or any of that non-sense. I now have to re-enable the overlays I was using, and I’ve lost many hours with memory checks, game repairs and re-installations, when the problem would take around 30 seconds to solve.
Thank you so, so much for your help! I would’ve never known to check System32 for outdated DLLs.
EDIT:
Summary on how to solve the issue, for anyone who may encounter it:
If you no longer use Razer software, delete outdated “RzChromaSDK64.dll” located in Windows/System32.
If you use Razer software, update the software and it should fix the problem.