Title: WRobot.exe does not open - no window, System.TypeLoadException at startup

Hi,

WRobot.exe does not open at all. No window appears, no error message is shown, and the process never stays in Task Manager. Windows only records the crash in Event Viewer.

SYSTEM

- Windows 10 Version 22H2 (fully updated with Windows Update, including KB5066791)

- .NET Framework 4.8.1 installed and repaired

- Visual C++ Redistributable 2015-2022, both x86 and x64, installed

- WRobot folder: C:\hobby\WRobot\WRobot (fresh download from the official site)

WHAT I ALREADY TRIED (none of this fixed it)

1. Run WRobot.exe as administrator

2. Unblocked the files (Properties > Unblock)

3. Checked the antivirus: Windows Security protection history is empty, nothing was blocked or quarantined

4. Repaired .NET Framework 4.8.1 and rebooted

5. Downloaded a fresh copy of WRobot and extracted it to a new folder

6. Installed Visual C++ Redistributables x86 and x64 and rebooted

7. Updated Windows with Windows Update

8. Ran Updater.exe: it opens and updates correctly

9. Renamed the Settings folder to Settings_old so WRobot creates a new one

EVENT VIEWER ERROR (Application log)

Source: Application Error

Faulting application name: WRobot.exe, version: 1.0.0.0, time stamp: 0x6acfefbc

Faulting module name: KERNELBASE.dll

Exception code: 0xe0434352

Faulting application path: C:\hobby\WRobot\WRobot.exe

Source: .NET Runtime

Application: WRobot.exe

Framework version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception info: System.TypeLoadException

at (obfuscated method names)

at -.iI11I1IlllIi..cctor()

Exception info: System.TypeInitializationException

at -.iI11I1IlllIi.()

The error is the same before and after all the steps above.

Could you tell me which type or assembly WRobot fails to load at startup, and what I can do to fix it? I can send screenshots or any extra logs you need.

Thanks!

Hello,

It's a bug in the last update, WRobot doesn't start on a new install. It will be fixed in the next version (today or tomorrow).

In the meantime, create a file named WRobot.exe.config in the same folder as WRobot.exe with this content, then run WRobot.exe again:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup>
    <useLegacyV2RuntimeActivationPolicy>true</useLegacyV2RuntimeActivationPolicy>
    <supportedRuntime version="v4.0" />
  </startup>
  <runtime>
    <loadFromRemoteSources enabled="true" />
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="Bin;Products;FightClass" />
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <system.net>
    <settings>
      <servicePointManager expect100Continue="false" />
    </settings>
  </system.net>
</configuration>

Make sure Notepad doesn't save it as WRobot.exe.config.txt. If you use the Relogger, add a copy of this file named Relogger.exe.config next to it.

54 minutes ago, Droidz said:

Hola,

Se trata de un error en la última actualización: WRobot no se inicia en una instalación nueva. Se solucionará en la próxima versión (hoy o mañana).

Mientras tanto, cree un archivo con el mismo nombre WRobot.exe.configen la misma carpeta que WRobot.exe con este contenido y, a continuación, vuelva a ejecutar WRobot.exe:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup>
    <useLegacyV2RuntimeActivationPolicy>true</useLegacyV2RuntimeActivationPolicy>
    <supportedRuntime version="v4.0" />
  </startup>
  <runtime>
    <loadFromRemoteSources enabled="true" />
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="Bin;Products;FightClass" />
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <system.net>
    <settings>
      <servicePointManager expect100Continue="false" />
    </settings>
  </system.net>
</configuration>

Asegúrese de que el Bloc de notas no lo guarde como WRobot.exe.config.txt. Si utiliza el Relogger, añada una copia de este archivo llamada Relogger.exe.config junto a él.

Si funciona