You might experience one of these symptoms:

  • <USERNAME> ran ROYALTS.EXE, which tried to access C:\USERS\<USERNAME>\APPDATA\ROAMING\CODE4WARD, violating the rule "XYZ", and was blocked.
  • <USERNAME> hat ROYALTS.EXE ausgeführt. Dieser Prozess hat versucht, auf C:\USERS\<USERNAME>\APPDATA\ROAMING\CODE4WARD zuzugreifen, hat damit die Regel "XYZ" verletzt und wurde daher blockiert.
  • Access to the path 'C:\Users\%username%\AppData\Roaming\code4ward\RoyalTS_Chomium_WP.exe' is denied.
  • Der Zugriff auf den Pfad 'C:\Users\%username%\AppData\Roaming\code4ward\RoyalTS_Chomium_WP.exe' wurde verweigert.


The way how the Chromium engine is being loaded has changed quite much due to several reasons in release 4.3.61005. Once following executable file "C:\Users\%username%\AppData\Roaming\code4ward\RoyalTS_Chromium_WP.exe" is whitelisted everything should back working normally as expected. For determining what exactly is blocking the file, the Windows Eventviewer might be a good place to start looking for.

For technical reasons the 3rd-party-framework we're using for the Chromium engine requires a dedicated wrapper file to start the Chromium engine in a different way - causing a few unexpected problems. We were pre-testing this change in our current Royal TS v5 beta without noticeable impact and therefore we did not expect many issues here.

More detailed explanation

By default the Chromium engine started using "rundll32" of Windows (as a kind of subprocess), which caused issues for a few users due to memory limitation on Windows-side of the rundll32.dll file.

Starting with the recent release of Windows 10 1809 this way was totally broken and using the Chrome plugin wasn't possible anymore. So we have backported the changes from Royal TS v5 to use a dedicated wrapper executable (which is the .exe file being blocked in your case) to spawn the Chromium processes in a different way, which removes a few limitations and issues. This file is being copied once Royal TS is started.

Unfortunately this brings a few other side-effects we didn't expect, e.g. when antivirus software is blocking the file or AppLocker is blocking running executables in specific directories. We're currently looking into some other ideas. For example placing required executable file into an own folder in LocalAppData, instead of the Roaming folder.


Whitelist the above mentioned executable file at the specific location.


When you're not having Windows 10 1809 installed on your machine and not experiencing any issues with the Chromium plugin, you're basically also fine with the previous stable release before the changes were introduced. This release can be downloaded here:

Sorry for the inconvenience! If you have any further questions, please open a new support ticket at us. You may find all directories and files Royal TS v4 is using in this following KB article.