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

[Dafyd]

---

ModEdit; related ticket: #17977: VirtualBox cannot start VMs on 32-bit x86 builds of the upcoming October 2018 Update of Windows => fixed in svn

---

Hi all,

VMs fail to start on my freshly updates Windows 10 1809 32b. Same problem with a fresh VM, I attach le log...
Any ideas ?

Thanks

[socratis]

c84.19b8: supR3HardenedScreenImage/Imports: rc=Unknown Status -626 (0xfffffd8e) fImage=1
        fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\crypt32.dll:
        Grown load config (160 to 164 bytes) includes non-zero bytes: 44 0a f1 5c

This is the problem, and it's documented in ticket #17977: VirtualBox cannot start VMs on 32-bit x86 builds of the upcoming October 2018 Update of Windows => fixed in svn, opened on 2018-09-11, and last modified on 2018-09-25 to indicate that the fix is in the tree:

The October 2018 Update has added a new pointer-sized field to the end of IMAGE_LOAD_CONFIG_DIRECTORY32 & IMAGE_LOAD_CONFIG_DIRECTORY64 structures and for some DLLs, this field is set to point to an opaque blob. Such DLLs are being rejected by VirtualBox

Given that the latest 5.2.x test build is from 2018-09-28, I'm not so sure if the fix has made it yet. Try to download it and see. If not, the only thing you can do is to wait for an update, or the next release.

PS. For future reference you should ZIP your logs. It helps save a (virtual) tree or two...

Edit: We're still on 2018, not 2019... Thanks Jacob!

[Dafyd]

Hi,

Thank you very much, I will download the test build.

Have a nice day !

[socratis]

Could you please let me know if the test build fixes your problem? And what's the test build version that you tried?

[infinidim]

---

ModEdit; posts split from VBox v5.2.18 incompatible with Windows 10 v1809

---

I have followed the above using the released version of Virtual box (5.2.18) and it still comes up with -

Failed to open a session for the virtual machine XP Machine.

The virtual machine 'XP Machine' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\jlh42\VirtualBox VMs\XP Machine\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

About to try the test version.

Regards

Infinidim

[infinidim]

It came up with exactly the same error with 5.2.19 (test version). See following -

Failed to open a session for the virtual machine XP Machine.

The virtual machine 'XP Machine' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\jlh42\VirtualBox VMs\XP Machine\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Not good.

All I did was update to Windows 10 v1809 and like the other person had to remove VBox before it would upgrade.

Any ideas folks?

Regards

Infinidim

[infinidim]

The other bit of information is that even if you create a new virtual machine it still doesn't work.

I'm running the 32 bit version of Windows 10 v1809 and trying to run either the XP / Windows 7 virtual image which I have been running for a couple of years now or a new test version of Windows 10.

Regards

Infinidim

[socratis]

@infinidim
You posted in an unrelated thread (VBox v5.2.18 incompatible with Windows 10 v1809), with a different error. You didn't have a problem with "REGDB_E_CLASSNOTREG". You have a hardening error.

I'm running the 32 bit version of Windows 10 v1809

That's a known issue. I merged your thread with the one that deals with the problem. Read the posts before yours.

But to be absolutely sure, please post a ZIPPED VBoxHardening.log, the one mentioned in the error dialog, or look for that specific error yourself.

[socratis]

5.2.19 r125704 came out today, can you try it? Or anything later than that. From the 5.2.x Test Builds.

[MeghanM]

This is for a 32 bit system with 1809-

When using build 125751 the initial error message has changed to:

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}

Log attached.

[socratis]

@MeghanM
You also posted in the thread "VBox v5.2.18 incompatible with Windows 10 v1809 (#17977)". Can you please stick at one thread per problem? Preferably the one that you've already posted?

What has changed is that you against the advice of not installing 3rd party antivirus, that's what changed:

28c.1348: supR3HardenedWinFindAdversaries: 0x800
28c.1348: \SystemRoot\System32\drivers\cmdguard.sys:
...
28c.1348:     ProductName:     COMODO Internet Security Sandbox Driver

BTW, the original problem is still there...

138c.1f30: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1
        fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Windows\System32\ucrtbase.dll: Grown
        load config (160 to 164 bytes, dir 164) includes non-zero bytes: b4 b2 00 10

[MeghanM]

Socratis-I was unaware of this thread aboutt he 32 bit issue when I posted initially- I apologized for this and see no cause for rudeness on your part. Also, the addition of the 3rd part AV is not the issue; after a total uninstall of that security solution the error persists:

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}

I'm not at rookie and had already tested various system configurations before I understood that it is solely a Vbox issue with 1809. I was just trying to assist in a problem that I'm sure many others have. Sorry to have bothered you with such apparent trivia.

[socratis]

and see no cause for rudeness on your part

Rudeness? Which part was rude? Honestly, I don't see it.

I was unaware of this thread aboutt he 32 bit issue when I posted initially

It's the same thread in a sense, I should have merged them at their birth. Now, it's too late.

But.. you were definitely aware of the issue, there was my reply just before your post. Of course, on the other hand and by your admission, you posted before even reading the thread. That's not how it usually works; you first read the thread, you then decide if it relevant, and finally you post.

Sorry to have bothered you with such apparent trivia.

Oh, come on now, please...

[Babylon]

VBoxHardening.7z

(3.78 KiB) Downloaded 34 times

Hi all,
I also have the problem, that none of my VM's are starting since Windows 10-32bit Update 1809 . Error messages are as described above by others for VB 5.2.18.
Now I updated to Virtualbox 5.2.20, but VM's still not starting with error:
E_FAIL (0x80004005)
MachineWrap
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Seems to be not a singular problem. Any hints?

[Paul Co]

Hello!

What delay to fix this problems in Windows 10 1809 32 bits, simply does not open the virtual machines! Is there no partnership between Oracle and Microsoft? This new build 5.2.20 did not fix the problem. We're waiting! Has anyone tested the Beta version?