![]() So even if we can pin down that there are leftover files (expected in some cases, btw, since the VMs and XML definition files are left behind for further reinstalls, like how an uninstall of MS Word does not delete the. Virtualbox 6.1.x may work or will have bugs, but if bugs happen these bugs will no longer be fixed for Windows 7 PCs. This means that Virtualbox no longer gets tested for bugs on Windows 7 host PCs. Some short time ago, (I think within the 6.1.x series) Windows 7 was dropped as a supported host OS. Mpack wrote:Win7 is not a supported host OS for VirtualBox 6.1.26. You can also search for VBox* in the registry. They exist either in the c:\Program Files\Oracle\VirtualBox folder, or they live in system32 folder and are called vbox. VirtualBox files are readily identifiable. ![]() here is the filename, here is the version properties showing that it's a v6 file. Again, if you wish to assert otherwise then again I'd need to see chapter and verse, i.e. Uninstalling VirtualBox v6 and installing v5 should completely remove all installed v6 files. On the other hand, corruption of the certificates database used to be a common problem with Win7 - there was a particularly notorious Windows update that planted the seed. Or it could be pure coincidence, since I'm not aware of any possible interaction between VirtualBox and host OS that can make the host OS think that some other component is unsigned. Since the issue involves the antivirus protection, it is a concern that it seems that virtualbox tries to install a fake microsoft driver. Hopefully there is a process that can be followed to remove everything VB 6 installs, so that I can restore VB 5 and not run into this issue. If uninstalling VB 6 is not complete then VB 5 might inherit this issue from VB 6. And it points to a signed microsoft windows driver (the KSL driver). The objection only comes when opening that first guest VM. ![]() When installing VB 6.1.26 on my windows 7 (64 bit) there were no objections about unsigned drivers or modules. Only when you reboot windows 7 will this popup appear again, one time only, when opening a guest VM. Subsequent openings of any guest VM (with or without an OS in it) do not cause this windows popup message. There has to be some interaction involving this driver with opening that first guest VM. The unsigned driver being flagged is not a VirtualBox driver at all, but a Microsoft antivirus component that is signed. The unsigned driver issue also occurs when I un-install VirtualBox V6 and reinstall VirtualBox V5.Īs I said, I don't recall this issue with VB 5 but I can't be sure as it was some time ago. Note I an relying on hostossupport.html which states VB 6 supports win 7. The guest VM's (I have several created under VirtualBox 5 as well as a couple of new ones under VirtualBox 6) all work fine on my win 7 PC. I was not aware that Win 7 is an un-supported OS for VirtualBox V6.1.26. Yes, I was talking about Win 7 being the OS on a physical machine, which I have taken to be the host. Hoping its nothing to be concerned about and or has a simple setup fix. Opening/showing any subsequent VM never results in this unsigned driver message.īe gentle as I am just a casual user of VirtualBox and don't know a lot about its intricacies. ![]() It concerns me that this relates to the antivirus driver, and hence it seems unwise to defeat unsigned driver checking and installing.Īs I said, this only happens on opening the first VM. I don't remember this issue when I installed VB 5, but when I uninstall VB 6 and reinstall VB 5 this issue remains. This driver is part of the Microsoft Security Essentials antivirus program, which of course is signed. The driver and its location it references to is MpKslDrv.sys. The message from this assistant informs that a recently installed program tried to install an unsigned driver. The very first Virtual Machine (with any guest) I show/open after a windows 7 boot up, always activates the windows program compatibility assistant. This particular issue of unsigned drivers comes about after successfully installing VirtualBox 6.1.26 on a MS windows 7 host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |