LosslessCut won't start on Windows. No error message... Just nothing.

[TechManiacHD]

Hi guys!

My LosslessCut that has been bought via Windows Store doesn't work. Click and simply... Not starting. There is no message with error, not a thing. Honestly don't know where to start and how to fix this issue.

It was working perfectly fine. Then I went for a one-month holiday, went back and it's not working. What's more! Asus Armoury Crate has similar problem. Seems like start loading, and then nothing at all... Uninstalling/reinstalling solves nothing. I went to Windows updates to catch up with everything on my Windows 11 Pro, a few restarts, a few days and both, Armoury Crate and LosslessCut won't start.

Would you have any idea how to solve this? Do those two depend on some SW that has been... IDK, broken by itself? xD

[mifi]

Hi. that's very odd. It definitely sounds like something changed on your system causing these apps to stop working all of a sudden.

• Can you open the Event Viewer and see if anything gets logged there?
• Or start LosslessCut.exe from the command prompt and see if any error gets printed (you'd need to find the installed path to LosslessCut then, I think it should be somewhere under C:\Program Files\WindowsApps\).
• Another wild shot is to try to run it as administrator.
• check if it could be an anti-virus/firewall causing problems (maybe try to temporarily turn it off)
• Check if Google Chrome has a similar problem (LosslessCut is based on Electron/Chromium)
• Check if other electron-based apps has the same problem (Slack/Discord/MS Teams/Skype)

[TechManiacHD]

Thank you for the prompt response.

• The Event Viewer doesn't show any new issues when attempting to start LosslessCut.
• I skipped it.
• I tried running it as an administrator, but to no avail.
• I disabled AdGuard and Bitdefender, yet the issue persists.
• Chrome is functioning perfectly.
• Discord is also working; I don't use any other applications.

My solution wasn't exactly a fix. I restored a backup that I made about 50 days ago. It seems to be working so far. I am in the process of updating Windows. Should the issue recur, I will inform you. Otherwise, I don't know what caused the problem.