W10 14971 Certificate is invalid

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).
AndyMidd
Posts: 16
Joined: 12. Apr 2016, 10:42

Re: W10 14971 Certificate is invalid

Post by AndyMidd »

Socratis: Thanks for response. Yes, you assumed correctly about versions. Fast brain, slow fingers, I think.
Uninstalling explicitly, and reinstalling (as a "normal" admin user) succeeded.

So, that begs another question: why did the upgrade fail?

Before uninstalling, I checked the VB version reported by the manager: it was 5.1.10. And there were no errors reported during the upgrade. And I rebooted, too. Oh well: I should have tried uninstalling first....
rseiler
Posts: 158
Joined: 5. Feb 2009, 20:26

Re: W10 14971 Certificate is invalid

Post by rseiler »

AndyMidd wrote:So, that begs another question: why did the upgrade fail?
Because of your "failure" to do this:
viewtopic.php?f=6&t=67923&p=322433

Now, I should have responded to the ticket, but I never received notification of the response, so forgot about it.

It's still an inexplicable problem and an accident waiting to happen, as you found.
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: W10 14971 Certificate is invalid

Post by Jacob Klein »

I have confirmed the fixes on all 3 VirtualBox branches. Great work and response time, Oracle!

soulraventnt / Forum Moderators:
Would you please consider editing the first post to say:
The problem in this thread, has been fixed with:
- Oracle VirtualBox v5.1.10 Build 112026
- Oracle VirtualBox v5.0.29 Test Build 112021
- Oracle VirtualBox v4.3.41 Test Build 112025 --> https://www.virtualbox.org/download/tes ... 25-Win.exe
bird:
Thanks for picking up the 4.3.x branch. It is a relief for me, knowing that my older huge BOINC VM tasks (with 450+ days runtime each so far), might complete on Windows 10! I'm not sure what your plans are for 4.3.x, but I'd recommend a silent public non-Test release, when a showstopper bug like this is fixed, and maybe silently release it at the same time as the 5.0.x maintenance release.

Thanks again guys!
Jacob Klein
Post Reply