Error VERR_VD_VDI_INVALID_HEADER using VBox v6.1.27 Test Build 147422 on Windows 11 22471

[Jacob Klein]

Error VERR_VD_VDI_INVALID_HEADER using VBox v6.1.27 Test Build 147422 on Windows 11 22471

When I try to start a new VM, I get:

Could not open the medium 'E:\VirtualBox VMs\MSEdge - Win10\MSEdge - Win10-disk001.vdi'.
VDI: error reading pre-header in 'E:\VirtualBox VMs\MSEdge - Win10\MSEdge - Win10-disk001.vdi' (VERR_UNRESOLVED_ERROR).
VD: error VERR_VD_VDI_INVALID_HEADER opening image file 'E:\VirtualBox VMs\MSEdge - Win10\MSEdge - Win10-disk001.vdi' (VERR_VD_VDI_INVALID_HEADER).
Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}

The VBox.log says:
00:00:02.159822 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:02.660471 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:02.660501 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (Display::setVideoModeHint)}, preserve=false aResultDetail=0
00:00:02.660618 GUI: Aborting startup due to power up progress issue detected...

Is this version of VirtualBox -- Oracle VirtualBox v6.1.27 Test Build 147422.exe -- bugged?

[Jacob Klein]

I'm doing additional testing. This may be something with my PC, somehow, not sure.

[scottgus1]

Hey there Jacob!
Invalid Header means the disk file went south. If you roll back to 6.1.26 does the VM start working again?

[Jacob Klein]

Well, considering it was setting up a new VM using File > Import Appliance ... then it wasn't a problem with an older disk file.

After I got the error on Oracle VirtualBox v6.1.27 Test Build 147422, I uninstalled it and installed Test Build 147346, which I had previously validated as successful. But it too was now giving the same error.

So I restarted the Host PC, and now both versions work fine. I don't know why. Maybe something in Windows 11 Build 22471, somehow interfered, and a restart unlocked something.

I think I have to consider this issue resolved for now.

[scottgus1]

Good ol' "If at first you don't succeed, reboot."

Sounds good, glad it's working again.

[Jacob Klein]

Whatever happened, shouldn't have happened, but because I can't actively repro on demand, I just documented it and moved on.