The runtime version supported by this application is unavailable

Unity 2018.2.3 on Windows 10
Player settings: Android, .NET 4.x, IL2CPP

I see this error message constantly appearing:

In specified folder `C:\Program Files\Unity-2018.2.3\Editor\Data\Mono\lib\mono\` I don't have `1.0\` subfolder, but do have `2.0\` one.

What does it mean?

/cc @JoshPeterson

 

Any comments on this Unity bug?

 

Can you show a screenshot? Is this at compile time? Googling for this error seems to imply that if that folder location you mentioned is in your Path, it would find it and use it.

 

I'm trying to start Unity on this project to make screenshot for you, but now it just crashes with Editor.log:

Code (csharp):

1.  COMMAND LINE ARGUMENTS:
2. C:\Program Files\Unity-2018.2.4\Editor\Unity.exe
3. D:/Viktor/Pg3d/pg3d-2018
4. Loading GUID <-> Path mappings...0.000095 seconds
5. Loading Asset Database...Crash!!!
6. ...
7. ========== OUTPUTTING STACK TRACE ==================
8.  
9. 0x0000000141FBF4B4 (Unity) LibraryRepresentation::Transfer<StreamedBinaryRead>
10. 0x0000000141FBE813 (Unity) Asset::Transfer<StreamedBinaryRead>
11. 0x0000000141FC86A1 (Unity) StreamedBinaryRead::TransferSTLStyleMap<std::map<UnityGUID,Asset,std::less<UnityGUID>,std::allocator<std::pair<UnityGUID const ,Asset> > > >
12. 0x0000000141FBED74 (Unity) AssetDatabaseV1::Transfer<StreamedBinaryRead>
13. 0x0000000141FF3C8F (Unity) AssetDatabaseV1::VirtualRedirectTransfer
14. 0x0000000140C8146C (Unity) SerializedFile::ReadObject
15. 0x0000000140C63D90 (Unity) PersistentManager::ReadAndActivateObjectThreaded
16. 0x0000000140C6443F (Unity) PersistentManager::ReadObjectThreaded
17. 0x0000000140C64164 (Unity) PersistentManager::ReadObject
18. 0x000000014058928A (Unity) PPtr<Object>::operator Object * __ptr64
19. 0x0000000141FE21BC (Unity) AssetInterface::LoadAssetDatabase
20. 0x0000000141FE12F1 (Unity) AssetInterface::Initialize
21. 0x0000000141F9CDBF (Unity) AssetDatabase::InitializeAssetDatabase
22. 0x000000014143DF99 (Unity) Application::InitializeProject
23. 0x00000001415EA958 (Unity) WinMain
24. 0x000000014242E5AA (Unity) __scrt_common_main_seh
25. 0x00007FF9A3E93034 (KERNEL32) BaseThreadInitThunk
26. 0x00007FF9A4181431 (ntdll) RtlUserThreadStart
27.  
28. ========== END OF STACKTRACE ===========
29.  
30. A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
31.  * C:/Users/Victor/AppData/Local/Temp/Unity/Editor/Crashes

...And last dir does not exist.

Ok, I will try upgrading Unity from 2018.2.4 to 2018.2.5...

 

Yes.

Why it should be in Path? Is it Unity installer's responsibility to add it there if Unity requires it in Path?

 

https://prnt.sc/klznoa

 

Regardless, I trust that you tried putting it in the path in the meantime? If it turns out that it resolves the issue, we could likely properly include it in the product.

 

I tried adding existing 2.0/ folder to the Path, it didn't help.
https://prnt.sc/kmbmof

 

I also just ran into this issue. Any ideas on what the problem is?

 

I faced the same problem and solved the problem in the following way.
My Unity version: 2018.2.14f1
Player Setting: .NET 4.x Equivalent, IL2CPP, .NET 4.x

I uploaded the project using the Collaborate feature,
I came back to Colabo from another computer.
I loaded the project normally, but I got the same error as the interrogator.
I checked the Player Setting, so the .NET Compatibility Level does not show .NET 4.x.
I changed the .NET version to 3.5, restarted the editor, and changed .NET back to 4.x.
After that, .NET 4.x appeared correctly in the Api Compatibility Level and the error was fixed after the change.

Good luck.

 

I don't know. Our long existing project is still on 5.5.0p4 From time to time I try to estimate how difficult it will be to migrate to up-to-date Unity. (It's tough task, and often leads to dead ends.) Since last time in August I didn't attempt to make it compiling and running in Unity 2018.2.*. So I'm not sure if it is still reproducing in 2018.2.14.

I'll let you know next time I'll be making another (desperate?) attempt to update Unity.

 

WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v1.1.4322 , this happen to me when adding 5.6 old webgl template in asset folder under WEBGL TEMPLATE folder .2018.2, updating the js file inside fix the problem , in your case i think you are using old third party plugins in your project.

 

Which js-file? What exactly is to be fixed there?

 

Just had this happen again, Unity 2018.2.13f1

 

Full error is:
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v1.1.4322
The assembly mscorlib.dll was not found or could not be loaded.
It should have been installed in the `/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/scripting/lib/mono/1.0/mscorlib.dll' directory.

that path looks corrupt to me...

 

this is happen usually when using old third party plugins or old Template for webgl . i had this problem many times but when removing these old plugins "for exemple ; webgl file uploader" , everthing go to normal state , but if the problem presist again , just create new project and migrate only asset folder from old projects.

 

I am also facing the exact same error

 

This error seems to pop up randomly now again again. The fix that I've found is go to player settings, change your .net runtime, restart unity, go change back to the runtime you want, restart unity again. Then you should be good

 

Running into a similar issue on MAC OSX Mojave. IF I switch to .NET 4.x instead of NET standard 2 it works fine.