We've had many failures since upgrading to Windows Server 2016 where the mongod service fails to start or the process abruptly terminates after having started. The Windows event logs revealed that after notmyfault.exe is used to crash the virtual machine, the log and data files, or in some cases the mongod.exe executable itself, cannot be opened.

We should collect the recent messages from the Application, Security, and System event logs on Windows using the wevtutil utility in order to have more diagnostics around this issue and for other mysterious ones that will surely come up in the future.