virtualbox.org

Windows Update will not work for a Guest OS when the Guest virtual machine is configured to use "NAT". Apparently the SSL connections for Windows Update will not work through two NAT routers (VirtualBox and a NAT broadband router).

The solution to the problem is to put the Guest OS directly on the LAN so that there is only the normal NAT broadband router between Windows and the Windows Update site. To do that you have to create a VirtualBox Host Interface and then bridge the Host Interface adapter to the normal LAN adapter in the Host OS.

You only need to do this when you use Windows Update. If you leave automatic updates enabled in Windows then you need to use this network configuration permanently. Otherwise Windows automatic updates will fail.

I wasted many hours trying to solve this problem, and so far I have not found any way to make Windows Update work through BOTH the VirtualBox NAT and a NAT broadband router. I tried disabling the stateful firewall in my router, and that also didn't solve the problem.

If anyone has other solutions to the problem that allow using NAT in VirtualBox and a NAT broadband router, please post the information.

VirtualBox 3.2.6 on Ubuntu 10.04. Guest OS is Windows XP.

I have the same problem.
The automatic updates fails!

Any new solution up to now?

Thanks and regards,
Michele.

I wonder if the dual NAT is the problem, because I have no issues with WU and MU on my VMs that use NAT, and I have a router too that provides NAT for my systems.

Googleing for the error, this is the first hit I get: http://www.updatexp.com/0x80072f8f.html
Cause: Time differences between system and server.

More Google results: http://www.google.com/search?client=ope ... 8&oe=utf-8

Same problems, I am using Ubuntu Linux and it's not letting me update. I tried bridiging the wireless, but it's not working. I am using a HP Pavilion dv6=3031cl. I believe it has an Atheros wireless card, but it won't bridge using Virtualbox 3.2.10

I know this thread is old, but I wanted to post a solution that worked for me. The ISO I used was XP Pro SP2 for the guest OS and I was unable to update and given the crazy hex error that points you to solutions for firewalls/networks etc.
I downloaded SP3 manually and installed it and it remedied the problem for me; I think the network solution, at least in my case was a red herring. Hopefully this helps others.

For Microsoft Windows 7 (and maybe other) Updates,

Create a second network adapter for the virtual machine in (Settings) and choose (Bridged Adapter) as the type. Choose the (name) of your internet-connected device. Choose (advanced) and set promiscuity to (allow all).

Start your virtual machine and run windows update. After all updates are finished, go back into (settings) and remove 2nd adapter for future network security.

Repeat all this each time you wish to get updates.

@BillWolf
Your solution does not prevent or help with that Windows update error. It may have had in your case, but it is either bad "time" set on the guest, or wrong certificates, both highlighted in the last post by Sasquatch.

What your solution most probably did in your case is to force a new network on the guest, which forced the time to be re-synchronized and corrected in the guest.

Plus, another tip is that once you create a 2nd adapter, you don't have to remove/re-add the adapter, you can simply connect/disconnect the cable, under Advanced options for the adapter.