this post was submitted on 20 Nov 2023
1 points (100.0% liked)

AMD

26 readers
1 users here now

For all things AMD; come talk about Ryzen, Radeon, Threadripper, EPYC, rumors, reviews, news and more.

founded 1 year ago
MODERATORS
 

A week ago, brikulex posted a solution on amd forums and I'm genuinely dumbfounded that this works:

I don't think that AMD is actually working on fixing this.

However I believe I have found something (at least something that works for me).

As always, I am not responsible for what you do, and if following my guide makes your computer explode, it's not my fault.

I am asking some of you who are affected by this bug and ever had Epic Games Launcher installed to try this:

  1. Exit Epic Games Launcher if you have it open (right click it in the notification tray and click Exit)

  2. Open the folder %localappdata%\EpicGamesLauncher\Saved

  3. Rename the Logs folder to something like LogsBackup

  4. Try to open Radeon Software and hope it works

Please respond if it fixed your issue or not, or if you don't even have the EpicGamesLauncher folder.

If I find out it doesn't actually work and it was just a coincidence, I will edit this post to correct it.

Good Luck!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 11 months ago

This solution would only make sense if the problem (Adrenalin crashing/failing to launch) was caused by the game detection part of Adrenalin throwing an unhandled exception when trying to access the Epic Games Launcher folder. Perhaps the permissions/ownership of the folder were changed to restrict who can access the Logs folder, and the game detection routine does not fail gracefully if it can't access the folder properly. That would be bad programming practice, since you never can rely on files on the filesystem being there at all times and under all configurations.

And if that is the case, then some other software that also requires privileged access for their folders would also cause that.

A bad thing to try in this case: Try starting Adrenalin with Administrator privileges. This should not be done for normal usage, and since Adrenalin has a lot of attack surface, it should not be a real solution.

I don't have this problem, although I have several different launchers installed.