Page 1 of 1
Kernel Module Version mismatch on windows
Posted: 7. Jan 2021, 11:06
by sureshhhh
I had two VM in the box and tried to upgrade the Virtual Box from 6.1.6 to 6.1.16 , the attached error message is popping up. i have tried to uninstall the entire things , restarted my host machine and re-install the latest version VM box, still am facing same issue. can anyone help me to workable with by two machines
Re: Kernel Module Version mismatch on windows
Posted: 7. Jan 2021, 11:43
by mpack
This question concerns your host, so it is not a "Windows Guests" question. I will move the topic to "Windows Hosts".
The error indicates that you previously copied VirtualBox executables to a new location on your PC. That was ok until you upgraded, and now there's a version mismatch between the foreground executable and the background DLLs it relies on. Only you can know the details of exactly what you did.
Re: Kernel Module Version mismatch on windows
Posted: 7. Jan 2021, 11:50
by sureshhhh
mpack wrote:This question concerns your host, so it is not a "Windows Guests" question. I will move the topic to "Windows Hosts".
The error indicates that you previously copied VirtualBox executables to a new location on your PC. That was ok until you upgraded, and now there's a version mismatch between the foreground executable and the background DLLs it relies on. Only you can know the details of exactly what you did.
am new to here , thanks mpack to redirect to the right channel. yes you are absolutely correct , before upgrade had my installation path in custom way instead of default path, how to overcome this
Re: Kernel Module Version mismatch on windows
Posted: 7. Jan 2021, 15:02
by mpack
Although there is nothing wrong per se with choosing a different install path for VirtualBox, there is absolutely no benefit in doing so, so you shouldn't do it as unexpected configurations have nothing but downside. Note that a non-standard install path will NOT control where VMs go.
As to the fix, you need to discard any desktop shortcuts and the like which embed the obsolete executable path. The simplest thing to do would be to recreate those shortcuts. As I said before, only you know exactly what you did, so I can't be more precise than that.