failed to shutdown container: failure in a Windows system call: The interface is unknown. (0x6b5)]

For some time I'm facing strange Windows container (running mcr.microsoft.com/windows:ltsc2019) stops on three different machines.
Windows Event shows:
docker:

failed to shutdown container, and subsequent terminate also failed [container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a module=libcontainerd namespace=moby error=container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5)]


failed to shutdown container [namespace=moby container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a error=container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::Shutdown: failure in a Windows system call: The interface is unknown. (0x6b5)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\vmhostedcontainerorchestrator.cpp(567)\vmcomputeagent.exe!00007FF60911BD91: (caller: 00007FF6090F81EC) Exception(740) tid(1504) 800706B5 The interface is unknown.
    CallContext:[\Bridge_ProcessMessage\ComputeSystemManager_Shutdown\VmHostedContainer_Shutdown] 
 Provider: 00000000-0000-0000-0000-000000000000]: subsequent terminate failed container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5) process=init module=libcontainerd]


sending event [container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a event=exit event-info={ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a init 2520 4294967295 2023-05-09 20:55:20.6206041 +0200 CEST m=+107305.494057601 false failed to shutdown container: container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::Shutdown: failure in a Windows system call: The interface is unknown. (0x6b5)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\vmhostedcontainerorchestrator.cpp(567)\vmcomputeagent.exe!00007FF60911BD91: (caller: 00007FF6090F81EC) Exception(740) tid(1504) 800706B5 The interface is unknown.
    CallContext:[\Bridge_ProcessMessage\ComputeSystemManager_Shutdown\VmHostedContainer_Shutdown] 
 Provider: 00000000-0000-0000-0000-000000000000]: subsequent terminate failed container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5)} module=libcontainerd namespace=moby]

Immediately before that I see Hyper-V-VmSwitch, Hyper-V-Worker, Hyper-V-Compute messages:

[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Queue process notification 65536 / 0x00000000, process ID 2520


[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Query process notification, process ID 2520, result 0x00000000, notification 65536 / 0x00000000


NIC 96E4A63C-1656-4575-82A0-75A5574181B9--AC72BF8D-E1DC-4CCF-A3E9-A1CC0C7D58EC successfully disconnected from port .


The operation 'Delete' succeeded on nic 96E4A63C-1656-4575-82A0-75A5574181B9--AC72BF8D-E1DC-4CCF-A3E9-A1CC0C7D58EC (Friendly Name: ).


'ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a' was turned off. (Virtual machine ID 96E4A63C-1656-4575-82A0-75A5574181B9)


[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Queue system notification: 1 / 0x800706B5


[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Shut down compute system, result 0x800706B5


[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Query compute system notification, result 0x00000000, notification 1 / 0x800706B5

It results as a stopped container. I'm able to manually start it again without any errors.

Start by reproducing shutdown of the mcr.microsoft.com/windows:ltsc2019 container and reviewing the Docker, Hyper-V, and Windows Event logs for error 0x800706B5. Trace the hcsshim/libcontainerd shutdown path around hcs::System::Shutdown and waitBackground; done means identifying the cause and preventing the container from stopping with this error.