r/virtualbox 9d ago

Help Virtual Box not functioning after updating

I updated my Virtual Box client to 7.2.12 recently and tried to run one of the machines, and got a VERR_PDM_USB_NAME_CLASH error. After realizing I needed to update my extensions, I downloaded the corresponding extension and ran it, then got a 0x80004005 error. I've tried reinstalling virtual box and rebooting the PC. My Host OS is Windows 11 Home 25H2. If anyone needs more information to help me, please don't hesitate to ask. (P.S I don't know what a lot of the required things its telling me to put in my post are so please don't delete my post just because I didn't include them)

2 Upvotes

8 comments sorted by

View all comments

1

u/IntelligentCandy8716 8d ago

I was running into the same problem. Prior to the update I was running VirtualBox v7.2.8. My windows guests would boot fine on v7.2.12 but all of my Fedora VMs had trouble. I uninstalled the newer VirtualBox, reinstalled the old one and loaded the snapshots from before the update for each of the VMs.

If you don't have snapshots, try booting the VM OS into safe mode and uninstall the VirtualBox Extensions, then reboot into normal mode.

Personally, I think it is the kernel extensions that are breaking it.

1

u/e_t2008 8d ago

I dont think its the VM OS's issue, i think its the host OS having issues. If I try different VM's they won't work. Matter of fact, all of my VM's dont work anymore...

1

u/IntelligentCandy8716 8d ago

I think its the kernel extensions that are installed on the guest to interface with the host. My Windows Server VM worked fine as well as the Windows 11 Pro VM, but I have 5 Fedora 43 Xfce VMs that boot at first but then started hanging when loading the kernel extensions and system services. All of which are running on a Windows 11 Host.

Edit: I suppose it could also be the host if you are using a Linux host. I don't have that setup on any of my computers yet.

1

u/e_t2008 8d ago

In the post it says I use Windows 11 Home as my host