Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).

Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Jacob Klein » 7. Jul 2017, 23:41

VirtualBox VMs are failing to start on the Windows 10 Insider Build 16237, released today.

Oracle:
Could you please fix both v5.0.x and v5.1.x, as time allows?


The primary errors deal with 2 dll files:
bcrypt.dll
3500.1bbc: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\bcrypt.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 60 a9 01 80 01 00 00 00
bcryptprimitives.dll
3500.1bbc: supR3HardenedScreenImage/Imports: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 40 16 06 80 01 00 00 00

I've confirmed the problematic behavior on these 3 versions of VirtualBox:
- Oracle VirtualBox v5.0.40 Build 115130
- Oracle VirtualBox v5.1.22 Build 115126
- Oracle VirtualBox v5.1.23 Test Build 116680

Attachments have more relevant logging information.

I am now using my Slow partitions, with Build 16232, as a workaround.

Thanks,
Jacob Klein
Attachments
VirtualBox 5.1.23 r116680.txt
(5.41 KiB) Downloaded 584 times
VirtualBox 5.1.22.txt
(5.49 KiB) Downloaded 558 times
VirtualBox 5.0.40.txt
(5.48 KiB) Downloaded 661 times
Last edited by Jacob Klein on 10. Jul 2017, 19:23, edited 3 times in total.
Jacob Klein
 
Posts: 581
Joined: 20. Nov 2013, 01:07

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Jacob Klein » 7. Jul 2017, 23:42

Here is an example of a full VBoxHardening.log file, attached.
Attachments
VBoxHardening.log
(103.38 KiB) Downloaded 594 times
Jacob Klein
 
Posts: 581
Joined: 20. Nov 2013, 01:07

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby rseiler » 8. Jul 2017, 04:32

We had a good run. If a subsequent test build works, please post back.
rseiler
 
Posts: 157
Joined: 5. Feb 2009, 20:26

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby sniem » 10. Jul 2017, 11:41

I have the very same error starting with Win 10 Pro 16237 x64 German for existing and newly created Windows VMs running VB Version 5.1.22 r115126 (Qt5.6.2)
sniem
 
Posts: 11
Joined: 10. Jul 2017, 11:35

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby sinnedt » 10. Jul 2017, 18:30

Also experiencing this. Tried on 5.1.22 and 5.1.23 r116680.

VBoxHardening.txt attached.
Attachments
VBoxHardening.log
(101.95 KiB) Downloaded 446 times
sinnedt
 
Posts: 1
Joined: 10. Jul 2017, 18:25

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Lexcyn » 10. Jul 2017, 19:21

Yep can confirm ... I rolled back to the previous build (16232) and my VM's start as normal.
Lexcyn
 
Posts: 2
Joined: 3. Feb 2017, 16:32

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby boredog » 10. Jul 2017, 21:19

Lexcyn wrote:Yep can confirm ... I rolled back to the previous build (16232) and my VM's start as normal.


Hello

I am having same problem as everyone else. Where can I find build 16232? Are you talking about windows 10 insider build 16232?

Also I do not think this is a Virtual Box issue. This problem goes way back to last years builds on this windows Preview version. 16237
Also doesn't anyone from Virtual Box post on these forums?

thanks
boredog
 
Posts: 4
Joined: 10. Jul 2017, 21:18

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Jacob Klein » 10. Jul 2017, 23:24

Windows 10 Insider - Fast Ring - is currently using 16237.
Windows 10 Insider - Slow Ring - is currently using 16232.

For Build 16237, VirtualBox DOES have the errors in post 1.
For Build 16232, VirtualBox does NOT have the errors in post 1. It works fine in Build 16232.

Microsoft changed things in Build 16237, such that Oracle's "Process Hardening logic" doesn't work with it. This has happened several times before, over the past 2 years. Typically this type of problem requires that Oracle adjust their hardening process, to account for Microsoft's changes. But that can take time - Oracle doesn't support Insider Builds, because they change before becoming "Release/Public".

So, we just wait patiently for Oracle to fix it or explain why they wouldn't. It could take days, weeks, or even months.

In the mean time, if you require VirtualBox to work ... it's recommended to either roll back your 16237 build, or (if you setup multiple partitions or PCs) start using your "Slow Ring" partitions/PCs. For me, all 4 PCs are now using their "Slow Ring" partitions, until Oracle can fix it. And if Microsoft pushes 16237 to the Slow Ring without Oracle's fix, then I'll switch to my "Release Ring" partitions. Such is the life of an Insider.
Last edited by socratis on 10. Jul 2017, 23:44, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Jacob Klein
 
Posts: 581
Joined: 20. Nov 2013, 01:07

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Lexcyn » 11. Jul 2017, 04:24

You can always roll back to the previous insider build... which in this case is 16232. It is definitely a Windows issue and not a VB issue though.
Lexcyn
 
Posts: 2
Joined: 3. Feb 2017, 16:32

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby rseiler » 11. Jul 2017, 04:31

As the previous post described: In a way. Windows caused it, but the effect is that it's now broken. Since MS will never fix it, as this is well outside their orbit of interest considering how much they have on their plate (compatibility with everything everywhere), it will be up to Oracle to fix. Maybe not fair, but that's the way it goes and has gone many times before.
Last edited by socratis on 12. Jul 2017, 13:01, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
rseiler
 
Posts: 157
Joined: 5. Feb 2009, 20:26

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby PetrGasparik » 12. Jul 2017, 11:37

So, basically, we have to wait for next VirtualBox build to try to fix MS's fault?

Jus FYI, build Windows 5.1.x revision 116680 does not solve this. I didn't try Development snapshot, as development revision 115147 looks older than Test Build.
PetrGasparik
 
Posts: 2
Joined: 12. Jul 2017, 11:34

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby socratis » 12. Jul 2017, 13:15

I'm not sure if there's a DevRing in Win10, but if the VirtualBox devs gets the FastRing releases the same day as you guys, it's expected that there is going to be a delay until they get around fixing the ever-so-popular MS break-the-Win10 game. I expect they're not the only ones (VirtualBox) that have to deal with this $#!&.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27690
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby PetrGasparik » 12. Jul 2017, 14:42

I was talking about VirtualBox versions, not Win10

Win10 has FastRing and SlowRing. Right now, VBox is working on Slow one, and not on Fast.

I was trying Test Build of VBox, which I assume is newer than Developer Build.
PetrGasparik
 
Posts: 2
Joined: 12. Jul 2017, 11:34

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby Jacob Klein » 12. Jul 2017, 15:20

socratis:

1) There are additional rings that are "Faster than Insider Fast", but I have no idea if they are available to 3rd party devs. Not likely at all.
See here: https://blogs.windows.com/windowsexperience/2015/03/09/frequency-and-predictability-of-builds-for-windows-insiders/

2) Yes, I know there will be a delay in getting things fixed. Sure most people don't find that acceptable, and even I didn't at one point, but now that I've grown accustomed to it (ie: It can take on the order of days or many weeks, before Oracle applies resources to fix it), I have imbued a sense of patience in my posts.

3) Of the ~70 apps that I use, Virtualbox's "Process Hardening" is the only one that gets routinely tripped up, when the Insider Fast ring builds are updated. None of my other programs have failures. We had a long run (~6 months!) where it didn't break, but alas, it's broken now.

Note: I'm still using VirtualBox v5.0.x, because I have long-running BOINC VBoxWrapper tasks that require that version. I'm hoping v5.0.x gets updated, and I politely put in the request, but I also understand that the version listing here:
https://www.virtualbox.org/wiki/Download_Old_Builds
... now shows it as "not supported" as of 5/2017. I get that. And I'll employ workarounds on my end if needed, as I did when I still had v4.3.x tasks but it wasn't working on the latest Win10 releases. :)

Thanks for your understanding,
Jacob
Jacob Klein
 
Posts: 581
Joined: 20. Nov 2013, 01:07

Re: Win10 Build 16237 - VMs fail to start - bcrypt.dll and bcryptprimitives.dll

Postby bird » 13. Jul 2017, 12:07

Thanks for reporting this! We'll have a fix for this out early next week, I hope.
-bird
Knut St. Osmundsen
Oracle Corporation
bird
Oracle Corporation
 
Posts: 123
Joined: 10. May 2007, 10:27

Next

Return to VirtualBox on Windows pre-releases

Who is online

Users browsing this forum: No registered users and 1 guest