I have the same problem, noticed that it is the nat service which is failing, but I have not found a solution, even after starting the service it crashes again after a few seconds.

event viewer error:

Faulting application name: vmnat.exe, version: 17.5.0.49595, time stamp: 0x652515c0
Faulting module name: vmnat.exe, version: 17.5.0.49595, time stamp: 0x652515c0
Exception code: 0xc0000005
Fault offset: 0x00012c41
Faulting process id: 0x0x6AA8
Faulting application start time: 0x0x1DA05D476CC2063
Faulting application path: C:\WINDOWS\SysWOW64\vmnat.exe
Faulting module path: C:\WINDOWS\SysWOW64\vmnat.exe
Report Id: eb919a7b-acd5-4f5c-9130-226f6cdd9fbf
Faulting package full name:
Faulting package-relative application ID:

event viewer information:

Fault bucket 1711524447639117690, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: vmnat.exe
P2: 17.5.0.49595
P3: 652515c0
P4: vmnat.exe
P5: 17.5.0.49595
P6: 652515c0
P7: c0000005
P8: 00012c41
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f66f1948-29dc-4bf4-b6a0-23ed030b9909.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f1c94acf-b910-4c6d-984b-1d7126af41bc.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6a6342f0-6e60-4afa-8ddc-deb1db16b4e4.tmp.csv