The game will not start and I got a popup that says "An internal exception occured (Address: 0x634dcd24) Please visit royals.ms/forum and report this issue on the bug reports section. Thank you!" After clicking ok I get a popup that says "The application was unable to start correctly (0xc0000142). Click ok to close the application." Anyone know how to fix this? EDIT: I uninstalled the game and then made an antivirus exception for the entire C drive and this time I got the same popup except with address 0x6337cd24.
This error message occurs when you're trying to play on a Mac, which the client does not support. Is this the case for you?
I would reinstall again and before starting royals i would make a specific exception in windows defender or whatever virus program you use for the royals executable, Royals.exe Its possible a file needed to run royals is still getting eaten and the client is throwing up errors when you try to start royals
making an exception for the .exe (IMG and WZ) did not work and I'm getting the same popups for the WZ files
just the default windows defender. ive turned off the firewall and all the protections that I can see. now im tinkering around with the superuser account and group policy editor
Better not mess with those, just making exception is enough Would recommend trying to install Royals on a different location instead of the default C, maybe Desktop or Documents
Did he try also running as an admin? Weird C drive should be fine. Maybe check the compatibility settings and set it to windows 11
now after doing a computer wipe and OS reinstall, I'm getting the message "Unable to execute file: (gives path to exe file) ShellExecuteEx failed; code 193. %1 is not a valid Win32 application.
This error usually occurs due to anti virus blocking the process, or locking up the files Already set an exception for Royals folder?
yes, i installed it to a folder on the desktop and made an exception for that folder and the exe file
Can I see a screenshot of the exception made? Can't think of any other reasons that this occur would occur (could be OS specific for Windows 11)
now it giving another address error code and the same dll error code. I'm gonna try something else. for some reason windows defender keeps eating the dll file