virtualbox.org

Hello,
I run Ubuntu 14.04 LTS in VirtualBox 5.1.6 on Windows 10. Hyper-V is disabled.

Everything has worked great until the host system was upgraded with KB3181403 (Windows 10 anniversary update).

When accessing content via an HTPS* conncetion I get the following error in my terminal now: It doesn't happens with curl.
I have noticed the behavior with my own service application and with apt-get update. Last one fails now for all packages with an HTPS* source.

Any suggestions how to fix this issue?
Thanks,
Sebastian

* T in HTPS means TT. Posting urls isn't allowed for the first post on this board. But the validation here means that HTPS* is already one.

I don't know the solution to this problem, but you may need to attract Linux users. Try editing your post title to "TLS issues in Linux guest after Windows 10 anniversary update"

I guess, that this issue isn't related to Linux. The point is the same VM works as expected on W7 and W8, but fails on W10 since the anniversary update.
MS has done some changes on the network stack (I can't post links, so please search for announcing-new-transport-advancements-in-the-anniversary-update-for-windows-10-and-windows-server-2016), also with view on TLS.
The Host works, the guest as well, so I would say that this is an VirtualBox issue, or isn't it?

You're quite right. You may need to put this on the Bugtracker as well, since the developers may not be aware there's a problem yet and they'd be the ones to fix it.

But Linux users would likely be the ones running Ubuntu, so they may be able to help, thus the title-change suggestion.

Thank you. I have created #16055 for this issue.

Did you try to search for "gnutls_handshake() failed" on its own, forgetting for a minute that you're on a VM? I did a quick search and it definitely seems it's an issue. Just not one that has to do with VirtualBox.

scottgus1 wrote:you may need to attract Linux users

Done. Moving to "Linux Guests" from "Windows Hosts".

Yes, this I have already tried and applied some of the suggestions, without success.

Let me ask the other way:
Is someone with the configuration I have (W10 + Anniversary Update as host and Linux as guest) able to run apt-get update without running into this issue?

Just a generic advice; try to be as specific as possible with your setup details, i.e. instead of saying "Linux guest on a Win10 Anniv. Update", say "Ubuntu 14.04 LTS (3.2.0-109-generic-pae) on a Win10 (1607 build 14393.0)".

The way the updates are delivered these days, especially with Win10, can make the difference between light and darkness.