Error on Fresh 2022.2.2f1 Project Preventing Startup

Unity Engine
1

Hey everyone. I’m getting this error with a fresh Unity 2022.2.2f1 project. Can’t even get passed safe mode. I haven’t been able to find anything about this on Google yet. Does anyone have an idea of what would be causing this? It also happens when upgrading from 2022.1.

Unhandled Exception: Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property. EntryPointNotFoundException: Unable to find an entry point named 'MsQuicOpenVersion' in native library.", DebugException="System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.EntryPointNotFoundException: Unable to find an entry point named 'MsQuicOpenVersion' in native library.
   at System.Runtime.InteropServices.NativeLibrary.GetSymbol(IntPtr, String, Boolean) + 0x5e
   at System.Net.Quic.MsQuicApi..cctor() + 0x26f
   at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0xc6
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0x167
   at System.Runtime.CompilerServices.ClassConstructorRunner.CheckStaticClassConstructionReturnNonGCStaticBase(StaticClassConstructionContext*, IntPtr) + 0xd
   at System.Net.Http.HttpConnectionPool..ctor(HttpConnectionPoolManager, HttpConnectionKind, String, Int32, String, Uri) + 0x163
   at System.Net.Http.HttpConnectionPoolManager.SendAsyncCore(HttpRequestMessage, Uri, Boolean, Boolean, Boolean, CancellationToken) + 0x99
   at System.Net.Http.HttpConnectionPoolManager.SendAsync(HttpRequestMessage, Boolean, Boolean, CancellationToken) + 0x89
   at System.Net.Http.HttpConnectionHandler.SendAsync(HttpRequestMessage, Boolean, CancellationToken) + 0x2a
   at System.Net.Http.HttpMessageHandlerStage.SendAsync(HttpRequestMessage, CancellationToken) + 0x30
   at System.Net.Http.DiagnosticsHandler.SendAsync(HttpRequestMessage, Boolean, CancellationToken) + 0x9c
   at System.Net.Http.RedirectHandler.<SendAsync>d__4.MoveNext() + 0x82
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Grpc.Net.Client.Balancer.Internal.BalancerHttpHandler.<SendAsync>d__10.MoveNext() + 0x726
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Grpc.Net.Client.Internal.GrpcCall`2.<RunCall>d__73.MoveNext() + 0xe27")
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Grpc.Net.Client.Internal.Retry.RetryCallBase`2.<GetResponseAsync>d__63.MoveNext() + 0x1c2
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Unity.ILPP.Trigger.TriggerApp.<ProcessArgumentsAsync>d__1.MoveNext() + 0x503
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Unity.ILPP.Trigger.TriggerApp.<RunAsync>d__0.MoveNext() + 0xdc
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Program.<<Main>$>d__0.MoveNext() + 0x1a3
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xb6
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x42
   at Program.<Main>(String[]) + 0x20
   at Unity.ILPP.Trigger!<BaseAddress>+0x4776bb
2

Anyone?

3

That sounds like a non-LTS near-bleeding-edge build of Unity.

Anytime you go beyond LTS you are an unpaid test pilot.

4

Yes, I understand that. That’s why I’m not trying to convert things over to 2023.1, although I did try it on there as well and get the same error. What’s pushing me to get into 2022.2 is the growing number of asset store assets that require 2022.2. Some of the assets would make a huge difference in my game. Otherwise I’d be content with sticking to 2022.1.

I was hoping this would just be something small that I needed to adjust but I’ve not gotten anywhere in the last month with this. Unity has still not yet replied to my bug report back from February and I have not yet been able to find any useful information on Google.

I’ve tried installing the Windows SDK in the hopes that it would update MSQuic as I see that mentioned in the error message. I read that Windows SDK includes the latest version of MSQuic and would update it during the installation. Didn’t work.

I also tried installing gRPC for Unity but I don’t think I’m doing it quite right. It’s not a straight forward process and I keep wondering why I would even need to do this if 2022.1 was fine without it.

I also tried disabling gRPC with -define:GRPC_NATIVE_DISABLE_NATIVE_MSQUIC=1 placed in the Additional Compiler Arguments section of the project settings as I read that would stop it from trying to load but again it didn’t make a difference.

Really at this point I’m just pulling stuff out of my a** and don’t have a clue what else could possibly be causing this error to show up.