Virtualbox Windows 7 Base System Device Driver
Phyllis Sterlin
I am trying to convert several VMware images towards Virtualbox images. I have succesfully been able to convert my Windows Server 2003 image, but I haven't been able to convert any Windows Server 2008 image.
One solution involves creating a new image giving the previous .vmdk as hard disk. When I try to startup the image, I get a blue screen during booting. (I also tried to delete VMware tools before importing the image, which didn't work).
The HDD types need to match. If you were using SCSI on VMware you need to be using SCSI in VirtualBox. In rare occasions you actually need to experiment a bit with disk types (ie a SCSI VMware disk will work properly only on SATA controler in VirtualBox, go figure).
Another thing that causes instability and bootup problems are IO APIC and PAE/Nx settings under System. Experiment with those. It can take couple of boots till you get it right but so far I've never had a physical (or virtual) machine I couldn't get onto VirtualBox using VMware tools.
Copy the virtual disk image files (vmdk) into the newly created VirtualBox VM folder. If you want, you can rename the disk files. I did that at this point, because, I wanted to have the disk type (C and D) reflected in the file name.
Then, I did choose to add a hard disk, and selected choose existing disk and selected the .vmdk file representing the first disk of the VM. Because, I had two disks, I did repeat this step once for the second disk. You also need to pay attention which on is disk 1 and which one is disk 2. If the OS is on disk 2, the VM will not boot.
Uninstall VMWare tools when booted in VMWare workstation (I didn't do this on first attempt and I had problems with some services not starting and I was unable to remove VMWare tools when booted under Virtual Box)
Combined vmdk file into 1 file (as vmdk had been created with default of split into files of no more than 2GB). You can use vmware-vdiskmanager for this but I was running out of space on vmdk so I created a new bigger vmdk in VMWare workstation, then booted virtual machine using a Linux Live CD (I used Ubuntu 12.04) and did a dd from old disk to new disk and then I extended partition using gparted (on Linux Live CD) into the unused part of the bigger vmdk.
Installed virtualbox additions - this resolved base system device driver which had a question mark in Device Manager and installed video driver which allows any resolution video screen which changes as you resize window.
If you've recently paid your Device Manager a visit and found something called a "Base System Device" giving you a warning you may have no idea what it is. However, before you hit the panic button and start fiddling with your Device Manager, it's a good idea to explore what this mysterious device is and why it's there.
The reason it's appearing as a "Base System Device" is because your system cannot properly interact with the device. This is usually because your computer doesn't have the device's official driver to work with.
Before you can help your PC identify a mysterious Base System Device, you need to determine what device your computer is trying to recognize. In most cases, it's your chipset, Bluetooth, or SD card reader. Sometimes, installing a virtual machine on your PC can also cause this problem.
However, if you think none of those are the root cause of the problem, you'll need to find the device's hardware ID. That way, you can then match the ID to the product and identify which device is giving your computer trouble.
Your first port of call should be downloading the correct driver from your device's manufacturer. You could ask Windows to find the driver for you, but there's a good chance that this error occurred because Windows failed to find anything to download.
Related: How to Find & Replace Outdated Windows DriversIf you don't have the original driver disk for your device, try searching online for your device name or its manufacturer. Then, go to the manufacturer's website and download the relevant drivers. For instance, if you want to install the driver for your Intel-based chipset, you can use Intel's Chipset Installation Utility.
Once you find the appropriate drivers, right-click on the Base System Device from the Device Manager and select Update driver. On the following screen, select Browse my computer for drivers and navigate to the folder where you've stored the driver files.
If you want to give Windows' automatic update feature a shot, go to the Update Driver menu as above. However, select Search automatically for drivers instead of Browse my computer for drivers.
Windows will then search for an appropriate driver. If it finds one, you can install the driver by following the setup steps Windows provides you. If it doesn't, you could try running a Windows Update to see if that helps.
If you couldn't fix the issue, there's a possibility that the problem is with your hardware. You can test the hypothesis by using the hardware on a different PC. For instance, you could plug the SD card into another PC and see if it works fine.
I have installed all the latest drivers for my motherboard from the Asus website. The problem still persists with many "Base System Devices" listed in the Device manager. I have compared the Device Manager in my new install with the Device manager in my old install (which I still have available on another drive). The devices which are not being recognised correctly are related to the "Intel(R) Xeon(R) processor P family" entries. Please see the attached screenshot with my install on the left and my new install on the right.
Since your system seems to be working fine and the issue is after a clean installation of Windows 11, we would like to confirm if you have contacted Microsoft for support regarding this matter. Also, we found a thread from the Microsoft Support Forum with some recommendations regarding a similar issue.
I have since down graded to a clean installation of Windows 10 with the above latest drivers installed and I still have the "Base System Devices" listed in the Device Manager. It is not a hardware issue as I have been running the same system without the problem for several years now and the issue only appeared after I upgraded the operating system recently. I will try downgrading to the previous version of the chipset driver over the weekend.
We are glad to know that the issue is not present when downgrading the chipset driver. Since the issue seems to be related to the latest Driver available on the Asus Website, the best course of action is to report this problem to Asus support since this is a driver-related issue and can be caused by their driver customizations.
I then tried to install the previous "Intel Chipset Driver" just to make sure and it asked me if I was sure I wanted to downgrade so I cancelled the install. That confirmed my thinking that the latest drivers had been installed. The Intel Driver & Support Assistant also said "No supported driver or software updates are available for your system." So I assumed the chipset drivers were all installed OK.
It is important to mention that motherboard manufacturers provide Chipset drivers. Intel DSA does not provide Chipset Drivers, if the motherboard or system is manufactured by third-party companies, contact the system manufacturer for the latest updates and technical support information.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
Before upgrading to win7 I installed virtualbox on my XP system and booted/tested this XP image successfully. I then upgraded to Win7 x64, installed virtualbox, and was confident the same XP image would work. I was wrong. It comes up, signs in, runs for about 30 seconds then crashes with the attached "guru meditation":
When I boot the XP image in safe mode, it doesn't crash. Also, there are two devices in the image's device manager that don't have drivers attached: "Base System Device: 80EE / CAFE" and "Video Controller: 80EE / BEEF". It was this way when the host was XP and it didn't cause a problem then...
Virtualization-based security, or VBS, uses hardware virtualization and the Windows hypervisor to create an isolated virtual environment that becomes the root of trust of the OS that assumes the kernel can be compromised. Windows uses this isolated environment to host a number of security solutions, providing them with greatly increased protection from vulnerabilities in the operating system, and preventing the use of malicious exploits which attempt to defeat protections. VBS enforces restrictions to protect vital system and operating system resources, or to protect security assets such as authenticated user credentials.
One such example security solution is memory integrity, which protects and hardens Windows by running kernel mode code integrity within the isolated virtual environment of VBS. Kernel mode code integrity is the Windows process that checks all kernel mode drivers and binaries before they're started, and prevents unsigned or untrusted drivers or system files from being loaded into system memory. Memory integrity also restricts kernel memory allocations that could be used to compromise the system, ensuring that kernel memory pages are only made executable after passing code integrity checks inside the secure runtime environment, and executable pages themselves are never writable. That way, even if there are vulnerabilities like a buffer overflow that allow malware to attempt to modify memory, executable code pages cannot be modified, and modified memory cannot be made executable.
Memory integrity is sometimes referred to as hypervisor-protected code integrity (HVCI) or hypervisor enforced code integrity, and was originally released as part of Device Guard. Device Guard is no longer used except to locate memory integrity and VBS settings in Group Policy or the Windows registry.
d3342ee215