[RESOLVED] After upgrading from .NET 3.1 to .NET 9 — “file hash did not match entry hash” and “Could not resolve CoreCLR path” errors

[Kbaytan99]

Hey everyone,

I’m trying to migrate my RAGE:MP C# project from .NET Core 3.1 to .NET 9.0.
The project builds successfully, but when I start the RAGE:MP server, I get the following log output:

 

Considering entry [Microsoft.Extensions.Options/8.0.0/lib/net8.0/Microsoft.Extensions.Options.dll]
The file hash did not match entry hash ... Skipping... match hash failed
...
Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE=1

After that, the server still says “ready to accept connections”, but my C# resource doesn’t initialize properly.
Everything is compiled as .NET 9.0, and I’m publishing like this:

 

dotnet publish -c Release -r win-x64 --self-contained false /p:PublishTrimmed=false

 

Edited October 7, 2025 by Kbaytan99

[Kbaytan99]

If you want to use a different .NET version, you only need to replace the .dll files — the .json and .gsop.json files must remain exactly the same. This ensures the RAGE:MP bridge dependency mappings stay intact.

The “Could not resolve CoreCLR path” error can also be machine-specific, so try testing it on another system or reinstalling the .NET runtime cleanly to confirm.

⚠️ Important: Any .NET version above 3.1 is not officially supported by RAGE:MP. If you decide to use .NET 5, 6, 8, or 9, you do so entirely at your own risk — issues are very likely to occur, and RAGE:MP developers will not provide support for them.

For better stability, stick to .NET 3.1 (the officially supported version) or use .NET 8 LTS only if you fully understand the risks.

 

Runtime for .NET9: https://workupload.com/start/5ZKMFBQwdLd (Change this with the server-files/dotnet)

Virustotal: https://www.virustotal.com/gui/url/e4a31bf065bf3999379981a401b038214534d116df116e021b2fe65450745c7e?nocache=1

Discord: thechosenkaan

Edited October 7, 2025 by Kbaytan99