Can Windows 7 Be Installed On Uefi
Ogier Dudley
Few months back I ran into a situation where i completely destroyed my boot partition of windows trying to multi-boot windows and ubuntu. this situation made me visit the DELL Service center. it was fairly easy for them to fix the system and I got my system back in no time.
To setup a multi-boot system where I should not be prompted by GRUB Boot-loader. I achieved this scenario where the windows was installed on the UEFI option and i was able to install the UBUNTU on the legacy mode of the bios. so whenever i had to run Windows i would just enable the UEFI mode and vice-versa.
The solution to my problem was fairly easy. I just had to add another partition /boot/efi to successfully install Ubuntu 18.04 on my computer, where Windows 10 was installed on the 128GB SSD in Legacy mode and Ubuntu 18.04 was installed on the 100GB partition of the 1TB HDD in UEFI mode.
If you look closely when you install windows or ubuntu from the usb, after you select the boot decies, you know the list of boot devices after pressing i think its F12 for dell computer, you can see for example:
that was the HUGE mess i was doing! i hope i can explain myself. IF you installed Windows 10 in UEFI mode (this is simple to know, when you install in uefi you ALWAYS get 4 partitions on your hard drive) if you installed in Legacy you only get 2 partitions, a fixed one of around 500mb and the "big one"
IF your windows 10 is installaed in uefi, you have to select the "* UEFI Kingston usb ubuntu" so ubuntu will install in uefi, if you select the "* Kingston usb ubuntu" ubuntu will run in legacy and will never appear on your grub menu.
Windows 10 saves your licence number based on your motherboard, so i suggest you BACKUP ALL YOUR DATA, write down which version of windows 10 you have (home, home single languaje, education, pro, etc) download a windows 10 image from microsoft, burn to usb and configure your BIOs to run (preferable) in Legacy mode and secure boot off. Install Windows 10, dont worry , it will self activate (but if asked be sure to select the right version you have, altough the serial nombre of windows 8 / 10 is already written in your motherboard, so usually you are not even asked to select which edition you have, it self detects it). After that now boot the usb ubuntu installation with the proper one selected, the "just plain kingston for legacy, or the "uefi kingston" they are the SAME usb drive, but the bios is letting you choose in which mode you want it to run.
When I install windows 10, it overrides all my EFI entries ( archlinux and efi shell ), and in boot menu I can see only windows. If I reboot to arch iso, go to /boot/EFI/ and remove Microsoft folder from there, it is back to normal.
Parts of your issue sound like different issues to me. It on one hand sounds like windows is removing your Arch boot entry in UEFI and you already know how to replace that entry. You created that entry when you created the entry for Bootctl (systemd boot) using efibootmgr. However I wouldn't think that is the issue because if it were it still wouldn't boot after you delete the windows boot loader directory. The fact that it does boot after you delete that directory tells me the windows boot loader must just be ahead of the Arch bootctl entry in the UEFI boot order. If that is the case you can boot to an Arch iso, follow the instructions for mounting the partitions and arch-chroot and use efibootmgr to change the boot order. The efibootmgr man page or help shows how this is done.
Windows 10 no longer formats the efi partition, so your Arch loader is still there after a Windows install. But it does override the boot sequence, and in some UEFI's you cannot fix this from within the bios (some you can, where you can select from any loader installed right in the bios's boot options). Easiest solution, make a bootable Refind usb and boot from that. It'll be able to boot your Windows boot manager or your already installed Linux bootloader...and if that fails you can direct boot the vmlinuz kernel image right from Refind. Once booted, use efibootmgr to adjust your default boot options.
Annoyingduck: "Windows 10 no longer formats the efi partition" - Yes, the partition is there. everything is there, and the Microsoft folder is there. But I cannot see any uefi bootable device from the bios boot menu, except the windows EFI boot device,
Head_on_a_Stick - By "remove" I mean move away from my EFI partition. When I move away the Microsoft folder, I can see the Arch EFI boot device in boot menu and bios. But if I copy Microsoft folder back to /boot/EFI/, I no longer see arch EFI boot device, just the windows one. So it breaks Windows, for a while.
Don't move anything. Nothing is "gone", just hidden from your UEFI bios. That's what I was saying earlier. Make a Bootable Refind usb and boot from it. It'll see everything that your Bios is not seeing. I use Grub, but I've encountered this a ton of times because I like installing Windows after Linux. Once Windows is installed it takes over booting. Just booting Refind gets you back into Linux, then just adjust the EFI boot from within Linux to set Linux as the default and update your Linux bootloader to include Windows...Done.
Now the fact that you have been moving around Windows boot options leads me to think yo may have some other problems developing that may require a Windows boot repair (which sucks btw), and that "may" actually remove the Linux loader. Not sure on this one.
I am booting from archlinux live CD, and when I mount my /boot i can move/remove items in /boot/EFI/. That is what I am doing to get back my systemd-boot bootloader. I will try to rearrange boot devices with efibootmgr, and see if that helps.
When I move away the Microsoft folder, I can see the Arch EFI boot device in boot menu and bios. But if I copy Microsoft folder back to /boot/EFI/, I no longer see arch EFI boot device, just the windows one. So it breaks Windows, for a while.
Hi all, I've created a Windows 10 VM using the SpaceInvaderOne guide on Youtube. This includes getting the iso file, selecting and installing a VirtIO driver and so on. In all of the videos that I've seen, the VM's go right into the installation of Windows when they start. Mine does not.
I can interact with this screen, but can't get past it. I typed 'exit' and got to a screen where I was able to select a boot device, but none of them ever got to the point of starting the windows install.
So I started the machine, and opened the VNC prompt, then tried a reset. The green 'play' icon briefly changes state, but I don't get any other response. The logs say "Cannot reset device.. no available reset mechanism."
I think that I may indeed have bound the audio device. I'm guessing that i should try un-unbinding this for the initial boot/os install, so I'll give that a try a little later. In fact,, I may as well just start from scratch with a new vm..
Restarting the VM has no effect in my UI or in the UEFI Shell. The line referenced above that showed a PCI device (built-in audio) bound to the VM is no longer in my log file, so that has been corrected. As a side note, I do have a docker container with Plex running on my NAS. I did go through the process of setting up QuickSync to handle transcoding, but I have a hard time thinking that this would prevent UnRaid from booting a VM.
After it was created , i clicked start then VNC and there was the boot from CD promt , i proceeded to windows installation choose virtio driver because windows install did not recognize the disk to install windows to
That didn't do it either, and for some reason i don't have a "bootx64.efi" file in that directory. I do have one called "bootia32.efi" and I tried running that, but it just went to another command prompt and nothing happened
To run bootia32 you need a 32bit uefi firmware; unless you compiled the ovmf firmware yourself and replaced the ovmf files for 32 bit support, and/or you want to emulate a 32 bit windows, your media is wrong.
Woohoo! The 64 bit iso did the trick. It looks like I'm up and running. I'm surprised that wasn't mentioned in the video I watched. Perhaps this could be added in one of the manuals or guides? In any case, thanks everyone!
A VM Guest consists of an image containing an operating system and data files and a configuration file describing the VM Guest's virtual hardware resources. VM Guests are hosted on and controlled by the VM Host Server. This section provides generalized instructions for installing a VM Guest. For a list of supported VM Guests refer to Chapter 7, Virtualization limits and support.
Virtual machines have few if any requirements above those required to run the operating system. If the operating system has not been optimized for the virtual machine host environment, it can only run on hardware-assisted virtualization computer hardware, in full virtualization mode, and requires specific device drivers to be loaded. The hardware that is presented to the VM Guest depends on the configuration of the host.
You should be aware of any licensing issues related to running a single licensed copy of an operating system on multiple virtual machines. Consult the operating system license agreement for more information.
On a VM Host Server running the Xen hypervisor, you can choose whether to install a paravirtualized or a fully virtualized guest. The respective option is available under Architecture Options. Depending on this choice, not all installation options may be available.
c80f0f1006