Servicing occasionally results in mesh child abnormal exit name="vmm" code=57005 during post-servicing AP startup

[smalis-msft]

The various servicing tests can very rarely result in an apparently crashing openvmm with exit code 57005 (0xDEAD). It is unknown where this exit code is coming from or what it means. Attempts to catch this in a debugger or dump have so far been unsuccessful.

Next step is probably to add process lifetime ETW tracing to the host.