VM start error on Win10 1809 32b (#17977)

[andyp73]

What delay to fix this problems in Windows 10 1809 32 bits

This is a user-to-user forum and so we can't comment on what the devs are working on and what their priorities are. If they don't have enough information to be able to figure out what the problem is then they can't fix it.

simply does not open the virtual machines

What does that mean in your context? VirtualBox is usually good at displaying error messages and generates comprehensive log files. The same symptoms don't necessarily have the same cause.

Is there no partnership between Oracle and Microsoft?

Unsurprisingly, Oracle's priorities for VirtualBox development are driven by their paying customers!

This new build 5.2.20 did not fix the problem

If the release notes don't say it is fixed, then it probably isn't!

-Andy.

[Paul Co]

I only care when the problem will be corrected, there is already such a report on the label number #17977! So who has the appropriate contacts, please send to the collaborators!! Thank you!

[socratis]

I only care when the problem will be corrected

Great. I really admire the patience in someone, especially when they're focused, a rare virtue these days.

there is already such a report on the label number #17977!

Yes, we know. It's in the title, the first post summary and in a couple of references already. Thank you for the reminder.

So who has the proper contacts, please get to the developers!!

I'm sorry, I might have missed your contract support number. Because if you don't have one, the only contact you get to have is with us, your fellow users. Oh, and print that into a sticker and stick it on top of your monitor, it's going to help you with your understanding of whom you're talking to.

You're not a customer, we're not your customer support. If you want proper customer support and potential (to slim) access to the developers (I assume to pull their ear for not having addressed this), consider going though your Oracle support representative. It's going to set you back 6100 dollars to begin with. Let's see how far that gets you...

Thank you!

You're welcome!

[Paul Co]

Come on developers, fix the bug and make us happy!

[MeghanM]

Seems that the latest 5.2.x revision 126141 totally fixes this issue. At least it did for myself and two others.

[socratis]

Go for the latest 5.2 Testbuilds - revision 126140 and later should have the fix for the fix.

[Babylon]

Heureka,
it really works again with version 5.2.21. You've done a good job.

[socratis]

@infinidim
I deleted your new post about this issue. Please follow the advice and download the latest test build.

PS. Partial logs are not that helpful I'm afraid. Next time ZIP and attach the full log. But not in a duplicate, it's going to be removed.