System.Reflection.ReflectionTypeLoadException on built game

One of our players reported that they can't start the game. I checked out the logs and I found this at the beginning:

Mono path[0] = 'D:/Steam/steamapps/common/AcademiaSchoolSimulator/Academia64_Data/Managed'
Mono config path = 'D:/Steam/steamapps/common/AcademiaSchoolSimulator/MonoBleedingEdge/etc'
Loading player data from D:/Steam/steamapps/common/AcademiaSchoolSimulator/Academia64_Data/data.unity3d
Initialize engine version: 2019.2.2f1 (ab112815d860)
[XR] Discovering subsystems at path D:/Steam/steamapps/common/AcademiaSchoolSimulator/Academia64_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1050 Ti (ID=0x1c8c)
Vendor:
VRAM: 4018 MB
Driver: 24.21.13.9836
Begin MonoManager ReloadAssembly
- Completed reload, in 0.446 seconds
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.882872 ms
Uploading Crash Report
ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
at System.Reflection.Assembly.GetTypes () [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0
at Unity.Entities.TypeManager.InitializeAllComponentTypes () [0x000f0] in <c11d72444b4a4b4bb6aa8d477dd09d37>:0
at Unity.Entities.TypeManager.Initialize () [0x000e4] in <c11d72444b4a4b4bb6aa8d477dd09d37>:0
at Unity.Entities.EntityManager..ctor (Unity.Entities.World world) [0x00006] in <c11d72444b4a4b4bb6aa8d477dd09d37>:0
at Unity.Entities.World..ctor (System.String name) [0x00046] in <c11d72444b4a4b4bb6aa8d477dd09d37>:0
at Unity.Entities.DefaultWorldInitialization.Initialize (System.String worldName, System.Boolean editorWorld) [0x00016] in <155313dc8e4f4b42846f6dfe35dd4b3b>:0
at Unity.Entities.AutomaticWorldBootstrap.Initialize () [0x00000] in <155313dc8e4f4b42846f6dfe35dd4b3b>:0

Because of this, it caused more errors that the game wasn't able to start. It doesn't happen in other machines. Not sure why it's happening here.

Not sure if it helps but the bug was reported through User Diagnostics. We were able to get this more info:

CPU:Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz