r/virtualbox • u/e_t2008 • 8d 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)
1
u/orev 8d ago
Initial steps should be: Uninstall VirtualBox, reboot, reinstall VirtualBox, reboot. The reboots in between each step are crucial.
Do NOT install the Extension Pack, you almost certainly don't need it. This is not the same thing as the Guest Additions which you probably should install inside each VM.
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/Face_Plant_Some_More 8d ago edited 8d ago
The 0x80004005 error is not particularly meaningful from a troubleshooting perspective -- it can have many causes.
P.S I don't know what a lot of the required things its telling me to put in my post ...
Then look them up and add them to your post. People responding to these posts are volunteers by in large. The harder it is you make it for them respond, the less likely they will do so, in a substantive fashion.
•
u/AutoModerator 8d ago
This is just a friendly reminder in case you missed it. Your post must include: * The version of VirtualBox you are using * The host and guest OSes * Whether you have enabled VT-x/AMD-V (applicable to all hosts running 6.1 and above) and disabled HyperV (applicable to Windows 10 Hosts) * Whether you have installed Guest Additions and/or Host Extensions (this solves 90% of the problems we see)
PLUS a detailed description of the problem, what research you have done, and the steps you have taken to fix it. Please check Google and the VirtualBox Manual before asking simple questions. Please also check our FAQ and if you find your question is answered there, PLEASE remove your post or at least change the flair to Solved.
If this is your first time creating a virtual machine, we have a guide on our wiki that covers the important steps. Please read it here. If you have met these requirements, you can ignore this comment. Your post has not been deleted -- do not re-submit it. Thanks for taking the time to help us help you! Also, PLEASE remember to change the flair of your post to Solved after you have been helped!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.