Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

eggplantSword's avatar

Homestead failing fresh install

I'm going crazy here with my homestead, it doesn't work after the computer closes or i run vagrant halt, i get this error everytime

Bringing machine 'homestead' up with 'virtualbox' provider...
==> homestead: Checking if box 'laravel/homestead' version '13.0.0' is up to date...
==> homestead: Clearing any previously set forwarded ports...
==> homestead: Clearing any previously set network interfaces...
==> homestead: Preparing network interfaces based on configuration...
    homestead: Adapter 1: nat
    homestead: Adapter 2: hostonly
==> homestead: Forwarding ports...
    homestead: 80 (guest) => 8000 (host) (adapter 1)
    homestead: 443 (guest) => 44300 (host) (adapter 1)
    homestead: 22 (guest) => 2222 (host) (adapter 1)
==> homestead: Running 'pre-boot' VM customizations...
==> homestead: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "95500a64-0f0a-489f-ae77-297fb4ef4fbb", "--type", "headless"]

Stderr: VBoxManage.exe: error: Could not open the medium 'C:\Users\Programador\VirtualBox VMs\homestead\ubuntu-20.04-amd64-disk001.vmdk'.
VBoxManage.exe: error: VMDK: inconsistent references to grain directory in 'C:\Users\Programador\VirtualBox VMs\homestead\ubuntu-20.04-amd64-disk001.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
VBoxManage.exe: error: VD: error VERR_VD_VMDK_INVALID_HEADER opening image file 'C:\Users\Programador\VirtualBox VMs\homestead\ubuntu-20.04-amd64-disk001.vmdk' (VERR_VD_VMDK_INVALID_HEADER)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MediumWrap, interface IMedium

The file is there, it's always there but I still always get this message.

I installed everything fresh yesterday and after struggling for hours I managed to get the vagrant working on vagrant up but when i closed it as vagrant halt and trying vagrant up today I get this error again.

At this point idk what to do and what is going on. I had this issue after cloning to a new hard drive but gave up trying to fix it and deleted everything and installed it again but that seems to only have worked for yesterday.

I have VirtualBox 6.1.42 and Vagrant 2.3.4.

0 likes
0 replies

Please or to participate in this conversation.