Is this expected that System.Net.Sockets.Socket.Receive raises an unhandled exception during Windows shutdown?

[dragmz]

I've got a native app that calls a .NET 6 assembly via a generated .comhost.dll using COM. The .NET 6 assembly call blocks on Socket.Receive.

When the OS is shutting down, the Socket.Receive throws native exception internally (code 0xE0434352) that isn't wrapped into a .NET Exception by the runtime but the native exception is propagated back into my native code, instead of being translated into an HRESULT.

This results in Windows reporting my service as crashed (Informational APPCRASH entry in the Event Viewer).

Is this expected and documented? I would expect the call to return a FAILED(HRESULT) instead which is what happens if a Socket.Receive error occurs while not shutting down the OS.

I know closing the Socket in a response to SERVICE_CONTROL_PRESHUTDOWN fixes this but I'm looking for some documentation when to expect COM calls into managed assemblies to raise exceptions instead of returning an HRESULT.

Thank you.