Windows 10 Uefi Iso

[Mirtha Shikles]

Icurrently have a mini PC with a dead CMOS battery. Its got a built in/emmc install of windows 10, and a Proxmox install on a separate SSD. It'll boot into windows by default (even when I want it going into proxmox), and its kind of annoying to reboot, remember/hit the boot select or UEFI screen fast enough and pick an OS.

In order to get the server to successfully connect to our PXE appliance i had to disable the onboard 1gb connections, and boot in Legacy BIOS. After a successful deployment i changed the server back to UEFI, however now it wont boot into Windows.

When i try to do a one-time boot with UEFI enabled the Windows Bootloader can be seen. But when selected it just loops me back to the one-time boot menu. And if i let the server boot without interruption it just loops saying there are no bootable devices attached.

I don't know about the PXE stuff but the reason for windows 2008 r2 not booting in UEFI mode is the BIOS option UEFI Optimized Boot is probably enabled. To use windows 2008 r2 in UEFI mode on a Gen9 server with UEFI mode enabled you need to disable UEFI Optimized boot.

@Vic384, Thank you for your reply, I very much appreciate your assistance. What I was trying to say is this PC has both a 256SSD (which is currently booting under UEFI), and then a 1TB HDD (that shows up under Legacy Booting Options..). The HDD is blank and I currently only have the SSD connected. Maybe there is a way to submit a video on this discussion board? I have submitted the videos in a couple FB tech support groups, but have had no response yet. Don't know if a link to that post is appropriate here.. What I am trying to say is that when I go into DiskPart, I do as you said... "list disk", "select disk", "list partition", and "clean". It then says that the command was successful. I even redo the "list disk", "select disk", "list partition", and it shows that the disk has been cleaned. I then type "exit" and close the window. But if/when I restart the machine, and I go back into the install tool via USB, when I get to the page where it asks which partition I would like to install to, the partitions are still there, like DiskPart never happened.. It is no longer Unallocated Space as DiskPart was showing. As soon as I restart the computer it's like I didn't do anything.. Any way to submit a video?

Edit: Also, I don't care about / need any info or data on the computer. I am just trying to do a fresh install of Windows 10. I was hoping to use the same Product Key for the new OS, but it isn't that important at this point. I have a fresh Windows 10 USB retail pack with a Key if needed.

@RyGuy I am not sure what you mean by '1 TB HDD (Legacy)'. Did you ever have that OS on the 1 TB HDD? When trying to install Windows you should only have the drive you wish to install Windows on connected, in your case you should disconnect the HDD. I also suggest that you run Disk Management and see what partitions you have on the SSD and HDD. A successful execution of DiskPart is not temporary; you should review the DiskPart commands like 'list disk', 'select disk', 'list partition', and 'clean' which removes all volumes and partitions from the selected disk. I assume the 1 TB HDD is your data storage drive so be careful when using DiskPart, it is probably better to disconnect this drive while you are doing your fresh install.

@redxps630 Thank you very much for your assistance. I have also tried via Microsoft's Media Creation Tool, via USB. This method also failed. I have sent you a private message with a link to videos of what I am encountering during the install..

if i understand you correctly you put a windows.iso on a bootable usb. if so that would be a common misunderstanding of Win 10 install. you should use Windows media creation tool to prepare a bootable usb media. -us/software-download/windows10

@RyGuy I have seen other users link to videos, but there is no way attach a video to your post. I am not sure what to say about DiskPart, but I have used DiskPart to clean and partition a drive and never encounter your problem. In my case, I used Macrium Reflect Free Edition to create Rescue Media on a USB drive. I then booted the Rescue Media and from the command prompt ran DiskPart.

I reviewed the video. it is strange. never seen this before. it does not let you successfully delete all old partitions. the 1 tb hdd is listed. I thought you planned to clean install on the ssd which is 256 gb.

based on your video, both ssd and hdd are connected to pc. this would be my guess. somehow your ssd and hdd are linked via RAID mode (Dell default). so as soon as you delete one partition it automatically creates another one (as if you did not delete anything). to solve this issue, go inside bios > SATA and change to AHCI. then remove hdd. only keep the ssd in system. then try the clean install using Microsoft media usb again.

Legacy MBR booting is NOT ALLOWED for ANY internal drive on an 8930. You MUST choose SATA OPERATION AHCI not RAID and secure boot must be off. DISKPART MUST SELECT THE SSD and CLEAN THE DRIVE. Any other drives MUST BE REMOVED.

@RyGuy I agree with everything @redxps630 wrote. The could not view the videos because I do not have a Facebook account and while clicking on the video makes it play, the video does not expand to a point that I can make out anything. If the HDD is still connected you definitely need to disconnect it; at least the SATA cable to the HDD. Here is a link to the use of DiskPart: -magic-manager/initialize-disk-gpt-mbr-from-cmd-diskpart.html

And then there's a video which I will send to each of you in private message (just in case you're interested..). If I try to create the new partition through the install tool, After I have just cleaned in DiskPart, I get the following error and the cleaned disk partitions reappear once I hit "Refresh", like what I just did in DiskPart never took place..

@RyGuy I think Secure Boot should be Enabled and Load Legacy Option Rom should be Disabled, but I don't think that is the problem with DiskPart. With regards to the DiskPart problem, the issue may be the DiskPart on your USB drive which I assume is your Windows installation media. I recommend trying Rescue Media created with Macrium Reflect Free Edition like I previously mentioned.

Sometime last week, I decided to move my entire ESP folder into a dedicated boot partition mounted at /boot. (I did this because I liked the idea of having everything boot-related in a partition for easy access when I dual boot or need any file from there). Unfortunately, I didn't attempt to reboot in order to check if anything was broken...until today

Using the steps outlined in the arch wiki for rEFInd, I was able to get my hands on an EFI shell. Using some of the commands from the arch wiki, I was able to discover that the windows boot EFI file didn't exist anymore in the boot partition.

It may seem odd, but to install a windows os, with UEFI mode enabled, you must have the flash drive hosting the installer files formatted with FAT32, if you are going to install it as legacy, aka UEFI off, it must be nfts.

If anyone is still interested I have found the solution for audio on MBP 2011 Windows 10 UEFI installs - it has taken me 4 years to figure out. I was given the answer from a tutorial only adjacently related -here:

"A Windows system's DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgeted to be large enough to host the notebook's PCIe devices. A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it. macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space"

As someone who also deals in hackintoshes I am very aware of DSDT's and how editing them can help get OSX running on home brew PC hardware- I had played around with installing Clover (the UEFI bootloader almost synonymous with Hackintoshes) on USB thumb drives and putting the DSDT from my MBP 2011 in the /Clover/ACPI/Windows folder - still nothing-- I thought that pointing windows to a DSDT would be enough.......

After booting into windows the sound card was immediately working (this was because I had installed the cirrus logic drivers from bootcamp 4) - the display audio driver in device manager had an exclamation point but I was able to install the display audio driver from intel's driver support for the i7 2470m CPU in this machine-

*NOTE: when I tested the registry method I skipped the first few steps since I already had a modified DSDT- I did need to create the 'C:\dsdt folder and extract the windows binaries to that folder - but I did not use their acpi dump nor compiler (I check for errors and compiled my dsdt in Maciasl in OSX)

I would gladly go more in depth but I doubt there are many more who need this information- just glad to have figured it out without the BIOS emulation of bootcamp- going to test this method on other 'pre 2013' Macs with non complient UEFI bios'

TGIK provided the full Mac/Clover bootloader version of creating a executing the DSDT patch, and gave a solution to the issue, itayemi provided a Windows alternative of creating and executing the DSDT patch. I'm the guy who took the two and made a script for Windows and added other needed and useful tools that is needed to make Windows 10 ver 1903 and higher to be compatible. This is the safest way without mistakenly bricking your Macbook and ruining your firmware. This is only targeted to MacBook Pro Early 2011 "13" inch models aka MacBookPro8,1.

1.) This is a script that will install a DSDT file to make your audio drivers work for your MacBook Pro Early 2011 in EFI mode. This is means if you want to install multiple Windows Partitions you can in EFI and you are no longer dependent on the DVD Rom.

3a8082e126