Windows 10 May Update 1903

After updating to the latest windows build and trying to launch flywheel am prompted with these errors.

Unable to start the VM: …\VboxMange.exe startvm local-by-flywheel --type headliness failed:

VBoxManage.exe: error: Call to WHvSetupPartiiton failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)

VboxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsolveWrap, interface IConsole

Details: 00:00:00,912072 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005))

I’m assuming this will just have to be waited out until Windows 10 patches, but if not any help would be great.

Why is no-one of the support team answering this question? It seems like a rather serious issue and keeps me from updating Windows.

Can someone in the support team please shed some light on this?

I had the same problem, but was able to overcome it and finally have Local running faster than previously. Here’s what worked for me:

  • Uninstall Local
  • Reboot
  • Install the latest version of Local (3.2.1)
  • Reboot
  • Run the Oracle VM app and check for updates, install if necessary
  • Reboot
  • Should be good to go from here

I’m sorry, so I have to do all kinds of actions to get LbF working again after a Windows update?
And you think that’s normal?
Well, I don’t.

SO, I’d like to know whether this problem is related to LbF or VirtualBox.

In any case, I’d like to have some clarification from the LbF support team.

Not that they seem to be pro-active, but we’re still hoping they might, maybe, if they’re up to it, if they’re willing, if they feel like it, or if they have some spare time, might (if we’re lucky) reply to this…

Well, I took the plunge and installed Windows May update 1903.
After that was done, started LbF (I’m running version 3.2.0).
No problem at all. There was twice a VirtualBox prompt: “Do you allow this app to make changes to your device?” Clicked yes twice and LbF ran without problem.
I have VirtualBox version 5.2.26 installed.

I’m not sure why it went wrong for @plugged and @KhakiMan. They didn’t mention any VirtualBox prompts, like I had when launching LbF after the Windows update.

1 Like

Glad you got it working first try. I actually reverted back Windows for now. Hopefully when do I update again things will go smoothly.