NAT No longer working on Win10 Guests w/VB Version 5.2.28 r 130011

[TurboPascal]

I updated my VB software to Version 5.2.28 r 130011 on 4/27. Then I did some WIn10 updates. Went to use the VMs and I kept getting Certificate Authority Errors and unable to reach the Windows Update Service. Pulling my hair out for hours thinking the VMs with Win10 are now hosed. I was about to trash the VMs when I decided to check how they are networked. They were all using NAT for the Adaptor 1. I changed them to Bridged and now everything is working again.

Not sure if this is a change to Windows 10 or a change to VirtualBox but NAT is no longer working and I have had to change all my Windows VMs to Bridged for them to work

Anyone know if this is a know issue?

[socratis]

I can't reproduce it here on my OSX host, I'm going to try it on my Win and Mint19 hosts as well, I will update the thread if there's a difference in attitude.

This was a VM frozen in time; snapshot taken on 2017-08-04, VirtualBox 5.1.26 GAs, Win10-x64 (1607, 14393.969, Anniversary Update). Updated the GAs to 5.2.28 and booted from "Win10_1809Oct_English_x64.iso", updated to 1809, downloaded all related updates with the NAT option being the only available networking option in the guest...

Not sure how a VBox.log would help in that case, but... we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.