Open Raina1007 opened 3 months ago
Thanks for filing the issue. I'm running Windows 11 22H2 22621.3958. Here's a screenshot of the error since it seems like the log file doesn't have as much traceback depth.
I was able to fix the issue by:
C:/{user}/AppData/Roaming/WowUpCf
and everything out of C:/{user}/AppData/Local/Programs/wowup-cf
It seems to be functioning normally for at least the first run after that process, will monitor to see if it happens again. Notably, deleting everything in C:/{user}/AppData/Local/Programs/wowup-cf
including app.asar
by itself wasn't sufficient to fix the issue, the roaming data needed to be deleted in order to fix it. So there could be something in that folder which is inducing it that might help to root cause in case this later impacts other users. If anyone has a thought about what files could be involved, I can scan them for any PII and then attach here, just let me know.
Issue seems to be a general windows issue and not solely related to windows 11 as another user had similar popup that Jacbo posted the screenshot. Following the sames steps posted here, that user was able to get WowUp CF to work as intended. Screenshot of that error message is attached.
Describe the bug Jacob contacted via discord in the help me channel stating: Seeing an issue where WowUp-CF 2.12 won't launch (Windows 11). Was working fine yesterday, haven't edited any of the files manually, tried an uninstall and reinstall. They provided logs of what is happening. After looking at the log, confirmed they had not put in a token in the GitHub spot in Options - Addons. As the error mentions a token issue in the error message, but it also mentions a URL issue w/ json. The logs show everything is working and from one second to the next it stops. Confirmed no windows 11 updates hit recently, an anti-virus update did hit, but connection to CF is being maintained after the error message happens. As a test had them install WowUp Wago as a test to see if it was WowUp in general or different electron versions might be the cause. WowUp Wago started up w/o issue. It looks to be related to the older electron Wowup CF is running on causing this. I have attached the logs for further examination.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Jacbo main.log