[Resolved] VB 5.10.2 suddenly throwing error 80004005 for Win 10 VM on OSX 10.13.4

[ZuluLaunchpad]

I'm having an issue with a VirtualBox VM I set up to run windows 10 a few weeks ago, it's been running fine until today, regularly update it as the notifications pop up.

I closed the VM last night as I needed the resources for something else, I suspended the session as I normally do.

Tried to open it up this morning and now get this error:
"Failed to open a session for the virtual machine Windows 10.

The VM session was closed before any attempt to power it on.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}"

I've combed through these forums topics in search of a solution but nothing I've tried so far has worked and a lot of the solutions seem to be unique to the individuals.

I've uninstalled and cleaned up the app paths etc, tried both V5.1.36 and V5.2.10 with no luck, I keep getting the same error.

I haven't changed anything in terms of config or folder structure at all.

I'm lost here so any help would be greatly appreciated, I have a lot of work on that instance I'd rather not lose

[andyp73]

We will need to see the VBox.log file from the guest in question. Boot the guest, make sure the problem occurs then shut the guest down (by force if necessary). zip the log file and post it.

-Andy.

[socratis]

I haven't changed anything in terms of config or folder structure at all.

Right... Don't take it personally, but how is it that no one changes anything on their setup and all of a sudden thing go belly up? Still a mystery, that random change in the entropy of the universe...

First of all, I'd like to know what the installation looks like. Try the just released 5.2.12. Not that it's going to change anything, more so that we're on the same page. You might want to print the following steps, or save them in a test file on your desktop, because there are a couple of reboots, and you don't want to go "hunting" in the forums...

1. Download the latest release, if you don't already have it.
2. Reboot.
3. Make sure you're part of the "admin" group. If you are logged in with the primary user account/owner, you are part of the admin group.
4. Mount the DMG from the previous step. Run "VirtualBox_Uninstall.tool". Make sure there are no error messages. If there are, please post them, exactly as they appear.
5. Reboot.
6. Mount the DMG from the previous steps. Double-click the "VirtualBox.pkg". As soon as you start the installation, press "Cmd+L" to show the log. Select "Show All Logs" from the drop-down menu. Before the last step of the installation (Done), click the "Save" in the log window. ZIP and attach that file.
7. Start VirtualBox. If it crashes, open "Console.app" and look at "~/Library/Logs". Is there a VirtualBox related log with the current date/time? ZIP and attach that file as well.

Then after that, follow Andy's advice about the "VBox.log"...

[ZuluLaunchpad]

I get that nothing should fail if nothing's changed, but these days things are constantly updating in the background so who knows.

In any case I've done as suggested and attached the logs.

The only VirtualBox logs that were generated when the instance failed to boot were:

OSErr AERemoveEventHandler(AEEventClass, AEEventID, AEEventHandlerUPP, Boolean)(aevt,quit handler=0x7fff2e7af52c isSys=NO) err=0/noErr
OSErr AERemoveEventHandler(AEEventClass, AEEventID, AEEventHandlerUPP, Boolean)(GURL,GURL handler=0x7fff2e7af52c isSys=NO) err=0/noErr
00:00:01.515876 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VM cannot start because the saved state file '/Volumes/Mac HD3/Windows 10/2018-05-09T19-32-28-304539000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false aResultDetail=0

I see from one of the errors it suggests I delete the saved state before starting the VM, tried that and got the following errors from the log.

VirtualBox VM 5.2.12 r122591 darwin.amd64 (May  9 2018 11:58:54) release log
00:00:01.530022 Log opened 2018-05-10T21:12:36.815174000Z
00:00:01.530024 Build Type: release
00:00:01.530041 OS Product: Darwin
00:00:01.530052 OS Release: 17.5.0
00:00:01.530061 OS Version: Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64
00:00:01.530175 DMI Product Name: Macmini6,2
00:00:01.530242 DMI Product Version: 1.0
00:00:01.530254 Host RAM: 16384MB (16.0GB) total, 6554MB (6.4GB) available
00:00:01.530257 Executable: /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
00:00:01.530258 Process ID: 1279
00:00:01.530258 Package type: DARWIN_64BITS_GENERIC
00:00:01.532342 Installed Extension Packs:
00:00:01.532359   None installed!
00:00:01.533827 Console: Machine state changed to 'Starting'
00:00:01.534234 Qt version: 5.6.3
00:00:01.551777 SUP: Loaded VMMR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:01.551830 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:01.556722 Guest OS type: 'Windows10_64'
00:00:01.560120 Enabling CMPXCHG16B for Windows 8.1 / 2k12 or newer guests
00:00:01.562928 fHMForced=true - No raw-mode support in this build!
00:00:01.572590 VMSetError: /Users/vbox/tinderbox/5.2-mac-rel/src/VBox/Main/src-client/ConsoleImpl2.cpp(1982) int Console::i_configConstructorInner(PUVM, PVM, util::AutoWriteLock *); rc=VERR_NOT_FOUND
00:00:01.572599 VMSetError: Implementation of the USB 3.0 controller not found!
00:00:01.572600 Because the USB 3.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 3.0 support in the VM settings
00:00:01.611758 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.724528 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Implementation of the USB 3.0 controller not found!
00:00:01.724547 Because the USB 3.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 3.0 support in the VM settings (VERR_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:01.724759 Console: Machine state changed to 'PoweredOff'
00:00:01.728040 Power up failed (vrc=VERR_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))
00:00:02.230125 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1920x950
00:00:02.230187 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:02.230240 GUI: Aborting startup due to power up progress issue detected...

Turns out the extension pack I installed a little while ago disappeared as far as the VB was concerned, had to reinstall, solved the issue.

[socratis]

00:00:01.532342 Installed Extension Packs:
00:00:01.532359 None installed!

00:00:01.572600 Because the USB 3.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 3.0 support in the VM settings

I isolated the two error messages that were key to your VM not starting...

Turns out the extension pack I installed a little while ago disappeared as far as the VB was concerned, had to reinstall

Turns out that every time you install a new version of VirtualBox, you need to reinstall the ExtPack. And since you just installed 5.2.12, your ExtPack didn't just "disappear", you simply never installed the 5.2.12 ExtPack.

Marking as [Resolved].