Dual-Boot Windows 11 with Linux: Safe, Step-by-Step Guide

If you’re thinking about escaping Windows 11’s telemetry creep or simply want to test a modern Linux desktop without committing, installing Linux alongside Windows — or replacing it entirely — remains the most practical option for most users. This guide walks a careful, practical path through preparing a Windows PC, creating the boot media, partitioning safely, installing a Linux distribution (with Ubuntu-based examples), and recovering from the most common failures. It combines sensible safeguards, real-world tips, and the trade-offs between dual-booting, virtualization, and the Windows Subsystem for Linux so you can choose the route that matches your needs and risk tolerance. elaces two operating systems on the same machine and gives you a boot menu to choose between them at startup. It’s the best way to get native Linux performance while keeping Windows for apps, games, or vendor drivers that you still need. If you want Linux for privacy, speed, or control, testing it in a dual-boot setup is safer than wiping Windows outright. Many distributions are designed to detect existing Windows installations and make dual-boot setup straightforward, but there are important preparatory steps you cannot skip.
Two parallel alternatives exist and dese

• Virtualization (VMs) — Runs Linux inside Windows using VirtualBox, VMware, or Hyper-V. Good for testing and low-risk work, but you lose direct access to some hardware and performance is lower than native.
• WSL (Windows Subsystem for Linux) — Runs Linux userspahout a separate boot. Excellent for command-line tools and dev workflows, but not a replacement for a full Linux desktop environment.

This article focuses on native installation (dual-boot or replacement), but includwhen virtualization or WSL might be preferable.

---

Preparing Your Windows System (Backups, BitLocker, UEFI)​

Why backups and recovery media matter​

Even though installers are usually careful, partitioning and bootloader changes can go wrong and render a system temporarily unbootable. Create a full backup or at least a Windows recovery drive before touching partitions. Use the built-in Recovery Drive tool to write a system recovery image to a spare USB — this provides a rollback path if the bootloader is damaged. Treat the recovery USB as expendable: it will be consumed by the recovery image creation process.

Check BitLocker and firmware settings​

If BitLocker is enabled, decrypt the Windows system drive or or to installing Linux. Installing or modifying partitions while BitLocker is active can lead to Windows refusing to boot or requiring recovery keys. Also confirm you know how to access the UEFI/BIOS and change boot order — you’ll often need to boot from USB to run an installer. Many Windows systems allow entering UEFI via Settings → System → Recovery → Advanced startup → UEFI Firmware Settings.

Decide where to install: same drive vs separate drive​

You don’t need a second physical drive for dual-booting, but Linuxrtition(s). Aim for at least 30–50 GB for a comfortable desktop installation, and more if you plan to store files or install many applications. Different guides list minimums ranging from ~20 GB (very minimal) to 50+ GB; when in doubt, allocate more. If you can, use a second internal or external SSD to isolate systems and reduce risk.

---

Choosing a Distribution and Downloading the ISO​

Which distro to pick​

For first-time switchers, Ubuntu LTS, Linux Mint, and Zorin are popular because they offer familiar desktop experiences and broad hardware support. Specialized distros (Kali, Nitrux, etc.) serve niche needs but are less friendly for general-purpose desktop use. Start with an LTS release (Ubuntu LTS or a Mint release built on LTS) to get longer support windows and stability.

Verify the ISO​

Always download ISOs from official distribution websites and verify checksums (SHA256) to avoid corrupted or tampered images. Many distributions publish a sha256sum file; use CertUtil or a Linux sha256sum check to confirm the downloaded ISO matches the published hash.

---

Creating a Bootable USB (Rufus, balenaEtcher, Etcher)​

• Choose a USB stick with enough capacity for the ISO (4 GB minimum; 8 GB recommended).
• Tools:
  • Rufus (Windows) — widely used, lets you modes and write ISO images.
  • balenaEtcher — cross-platform, very simple and reliable.
  • The installer usually sets the recommended options automatically for modern UEFI systems.

Steps:

1. Launch Rufus or Etcher.
2. Select the downloaded ISO and the target USB.
3. Accept default settings (ensure UEFI (GPT) if your system uses UEFI).
4. Start the flashing process and wait — it may take several minuoning Windows: Freeing Space for Linux

Use Windows Disk Management to shrink Windows partition​

• Right‑click Start → Disk Management → select Windows partition → Shrink Volume.
• Free at least 30–50 GB for a desktop install; larger if you plan to work on Linux daily.
• The shrink operation may be limited by immovable system files; if so, use a third‑party tool.

Third-party partition tools​

If Disk Management can’t free the space you need, use tools like AOMEI Partition Assistant or MiniTool Partition Wizard. These tools can resize NTFS partitions more flexibly and often handle SSD alignment automatically. Note: Windows Disk Management cannot create Linux-formatted volumes; leave the freed space unallocated so the Linux installer can use it.

Recommended partition layout for Linux (basic)​

• Root (/) : 25–50 GB or more — formatted ext4.
• Swap : optional if you have lots of RAM; otherwise 2–4 GB or swap file.
• /home : allocate remaining space if you want to separate userdata (optionrtition (ESP) : reuse the existing ESP created by Windows (no need to create a new one). The Linux installer will detect and install GRUB to the ESP in UEFI systems.

---

Installing Linux — Step-by-Step​

Boot from USB and pick "Try" or "Install"​

1. Reboot and boot from the USB drive you created.
2. On most installers you’ll get a live session first — pick “Try” to verify hardware (Wi‑Fi, graphics, touchpad) before committing.
   options
   • Install alongside Windows: Many distributions offer a guided “Install alongside” option that automatically resizes and creates partitions. This is fine for beginners.
   • “Something else” / custom partitioning: Choose this if you want full control over partitions’s safer if you have a specific layout in mind.

Recommended choices during installer prompts​

• Select to install third-party software for graphics and Wi‑Fi drivers and additional media codecs — e compatibility out of the box.
• Install updates during installation if the installer offers it.
• Confirm the installer will not overwrite your Windows partition — double‑check the target device and partitions before clicking Install.

Bootloader and GRUB​

• On UEFI systems, the installer will write GRUB to the existing EFI System Partition and add entries for both Linux and Windows. After installation, GRUB usually becomes the default bootloader and offers a menu to select Windows or Linux.
• If Windows was installed last or a Windows update overwrote GRUB, you UB using a live USB and running update-grub (or using Boot-Repair).

---

Post-Install: Making Windows the Default or Tuning GRUB​

If you want Windows to boot by default instead of Linux, or adjust boot order and timeout, edit the GRUB configuration on the Linuxminal in Linux.

1. Edit /etc/default/grub and set:
   • GRUB_DEFAULT= (set to the index or saved entry)
   • GRUB_TIMEOUT= (seconds to wait)
2. Run sudo upd-mkconfig -o /boot/grub/grub.cfg depending on distro) to apply changes.

Tip: Some installers set GRUB to hide the menu; if you don’t see the menu at boot, press and hold Shift (legacy BIOS) or Esc (UEFI) to force it to appear.

---

When Things Go Wrong: Common Recovery Steps​

GRUB disappears, system boots straight to Windows​

This usually happens when Windows writes over the EFI entries (for example after a reinstallation or a major update). Two common recovery Linux live USB and re-install/repair GRUB:

1. Mount the root partition and chroot into it, then run update-grub and grub-install.
2. Or use Boot-Repair (a GUI live tool) to automatically detect and restore GRUB.
   • Restore Windows bootloader temporarily using Windows recovery media and then re-add GRUB if you prefer the Windows Boot Manager route. Bootrec commands and bcdboot are tools for repairing Windows boot. If using Windows tools, be careful—replacing GRUB with Windows Boot Manager will remove easy access to Linux until GRUB is restored.

Boot failures due to BitLocker​

If BitLocker was active during partition changes, Windows will likely require the recovery key. Suspend or decrypt BitLocker before partitioning to avoid this. If you end up in recovery, have your BitLocker key (usually tied to your Microsoft account or saved during device setup).

EFI vs Legacy BIOS confusion​

Ensure both OSes use the same boot mode (both UEFI or both Legacy BIOS). Mixing modes complicates bootlften prevents a clean dual-boot. Modern Windows installations on recent hardware almost always use UEFI; match that in the Linux installer.

---

Virtualization and WSL — When They’re Better Choices​

If you don’t need full native performance or direct GPU passthrough, virtualization or WSL might be better:

• **VMg multiple distros, snapshots, and safe experimentation. Use VirtualBox, VMware Workstation Player, or QEMU/KVM (on Linux hosts). They isolate the guest OS from hardware and from Windows, reducing risk to your primary system. Performance for everyday desktop use is lower and some hardware access (e.leration) is limited.
• WSL: Ideal for command-line Linux tools, development environments, and testing Linux packages without rebooting. Note that WSL2 uses a real Linux kernel inside a lightweight VM and excels for development but is not a full desktop replacement.

---

Hardware, Drivers, and Practical Compatibility Notes​

• Graphics: Intel GPUs usually work out of the box. AMD support is good with open-source drivers. NVIDIA often requires installing the proprietary driver for best performance — do this after installation using the distro’s driver manager or package manager.
• Wi‑Fi & peripherals: Test them in the live session before committing. Some Wi‑Fi chipsets require proprietary firmware that can be installed during or after the first boot.
• Steam/Proton gaming: Many games run well but not every title or anti‑cheat system is supported. If gaming is crucial, leave Windows available until you confirm compatibility.

---

Security and Privacy: Why People Move Away from Windows 11​

Many users cite increased telemetry, preinstalled apps, and privacy concerns as reasons to consider Linux. While Linux dily more transparent by default, privacy and security depend on distribution configuration, update practices, and the applications you run. For high assurance, choose an LTS distro,urity updates, and follow best practices for browser and application privacy. Always verify any claims about “complete privacy” — they’re often overstated.

---

Step-by-Step Cheat Sheet (Sequenced)​

or at least critical files + create Windows recovery USB.

1. Disable or suspend BitLocker. Confirm you have the recovery key.
2. Pick a distro (Ubuntu LTS / Mint / Zorin recommended), download ISO, verify SHA256.
3. Create a bootable USB with Rufus or balenaEtcher.
4. Shrink Windows partition in Disk Management or with AOMEI / MiniTool. Leave space unallocated.
5. Boot from USB, use “Try” to verify hardware, then “Install” (choose install third‑party drivers/codecs).
6. Use guided “Install alongside” or manual partitioning as you prefer. Ensure GRUB is installed to EFI.
7. After install, update packages and drivers on Linux. Confirm you can boot into both OSes.
8. If GRUB is missing later, use a le-grub or Boot-Repair.

---

Trade-offs and Final Recommendations​

es native performance and preserves Windows apps, but it requires careful partitioning af bootloaders. It’s the best choice for power users and hardware access (e.g., GPU-accelerated workloads or certain USB devices).

• Virtual machines reducer trying multiple distributions quickly, but they don’t deliver full hardware performance. Choose virtualizatioty and convenience over raw speed.
• WSL is excellent for development workflows that don’t need a full desk the lowest-friction path to Linux tooling inside Windows.

If your main concern is privacy, teot or VM first and only migrate fully after confirming your essential apps, browserherals work or have acceptable alternatives. Use a live USB to test hardware compatibility before any disk changes.

---

Closing Summary​

Installing Linux alongside Windows remains one of the most flexible ways to take control of your computing environment: you get native performance on Linux while keeping Windows available. The process is mature and well documented, but the two most important steps are backing up your Windows system and verifying hardware compatibility in a live session before installing. Choose the installation path that matches your risk tolerance rmance, VM for safety, WSL for convenience — and use the recovery tools and bootloader repair techniques described above if anything goes sideways. This wntime and keeps your data safe while you evaluate whether Linux should become your daily driver.

---

Key resources referenced in this guide include community how‑tos on creating boot media, partitioning Windows safely, GRUB behavior and repair, and options for WSL and virtualization — all practical reference points when planning a migration. Use them to tailor the steps above to your hardware and comfort level before you begin.

---

Source: Guiding Tech How to Install Linux on Windows for Dual Booting or Avoiding Windows 11

 

[ChatGPT]

Dual‑booting Windows 10 and Windows Server on the same PC gives you the flexibility of a desktop OS for daily work and a server OS for testing, lab work, or isolated services — but it also introduces complexity around partitioning, firmware (BIOS vs UEFI), bootloaders and recovery. This guide consolidates a pragmatic, step‑by‑step method to dual boot Windows 10 and Windows Server, explains the technical trade‑offs, highlights common failure points, and provides proven recovery and best‑practice techniques you can use before and after installation.

Background / Overview​

Dual‑boot configurations let one machine host two separate operating systems and choose which to run at startup. For Windows 10 and Windows Server this typically means:

• Installing the primary OS (Windows 10) on one partition or drive.
• Creating a second partition or using a second physical drive for Windows Server.
• Allowing the Windows Boot Manager to present a menu at boot so you can pick an OS.

This approach is appealing when you need native performance for server roles, want an isolated environment for testing Active Directory, or must run services that aren’t suitable for a virtual machine. It is a low‑cost, high‑flexibility solution compared with separate hardware or a VM — but it’s more fragile than virtualization, because partition and bootloader errors can make one or both systems unbootable if you’re not careful. Proper preparation and conservative defaults reduce those risks significantly. Practical installer and diskprep advice is common in community and troubleshooting guides and diskprep via diskpart is a recommended, reliable method for creating exactly the partitions Windows expects during install.

---

Who should consider a dual‑boot Windows 10 and Windows Server setup​

• IT admins and developers needing native Windows Server features (Hyper‑V in a server SKU, Domain Controller testing, IIS and server roles).
• Lab engineers who must test server roles against desktop workflows on the same machine.
• Power users experimenting with server OS features but unwilling to commit separate hardware.

If you need quick snapshots, safe rollbacks, or flexibility to run many server instances simultaneously, virtualization (Hyper‑V, VMware, VirtualBox) or containers may be a better option. Community guides consistently recommend virtualization as the safer, higher‑productivity alternative when native performance is not strictly required.

---

Key prerequisites and decisions (before you touch disks)​

• Back up everything. A full image or at minimum file backups and a Windows recovery drive are mandatory. Many dual‑boot missteps require a recovery USB or image to restore a damaged bootloader.
• Decide whether to use two physical drives or two partitions on one drive. Two drives isolate failure and simplify reinstallation; a single drive requires careful partitioning.
• Choose firmware mode: UEFI/GPT or Legacy/MBR. Modern systems use UEFI/GPT; older machines may require BIOS/MBR. UEFI is preferred for future compatibility but adds complexity around Secure Boot and FAT32 installer limits (see below). Community experience shows diskprep with a clear EFI/MSR/Windows layout reduces installer confusion.
• Check BitLocker: if your current Windows 10 is encrypted, suspend or decrypt before repartitioning. Changing partitions while BitLocker is active can force recovery key prompts or make a partition unbootable.
• Gather ISOs and driver packs: Windows 10 ISO and the Windows Server ISO you plan to install (2012 R2, 2016, 2019, 2022, etc.). Also, save storage/NVMe/RAID drivers if your platform requires them during Setup.

---

How to prepare installation media (USB / ISO)​

• Use the Microsoft Media Creation Tool for Windows 10 if you want an automated, reliable UEFI+BIOS media. The tool usually produces media that works in both UEFI and legacy BIOS modes.
• If you build media manually (Rufus or equivalent): choose the correct partition scheme (GPT for UEFI, MBR for legacy) and be mindful of FAT32’s 4 GB per‑file limit. If an install.wim exceeds 4 GB, tools such as Rufus can split the WIM or use an NTFS+UEFI shim to boot; otherwise UEFI firmware may refuse to boot an NTFS USB stick natively. Practical installer tips recommend letting Rufus or Microsoft’s tool manage these details to avoid boot issues.

---

Step‑by‑step: Dual boot Windows 10 and Windows Server (clean installs)​

The following is the robust workflow used by many community posts and field guides. It assumes you’re starting from scratch or willing to reinstall both systems for the cleanest outcome.

1. Disk prep — create partitions the installer expects​

If you have an empty drive and plan to install both OSes on it, use diskpart during the Windows installer to create the standard partitions (EFI, MSR, Windows). This prevents leftover metadata or mixed partition tables from confusing Setup and ensures both OSes install cleanly.
A recommended diskpart sequence (run Shift+F10 during Setup to open a command prompt) is:

• list disk
• select disk X (verify X carefully)
• clean (erases the disk)
• convert gpt
• create partition efi size=100
• format quick fs=fat32 label=System
• assign letter=S
• create partition msr size=16
• create partition primary
• format quick fs=ntfs label=Windows
• assign letter=C
• exit

After this refresh the installer partition list and select the NTFS partition for installation. This method creates exactly the EFI and MSR partitions Windows expects on a GPT disk and avoids many failure modes seen in the field.

2. Install the primary OS (recommended: Windows 10)​

• Boot the Windows 10 installer USB and perform a Custom install to the Windows partition you prepared.
• Complete installation and update drivers. If you’re using BitLocker, reconfigure it after you finish initial setup.
• Leave the remaining partition(s) or free space for Windows Server.

This order — desktop first, server second — tends to produce a simpler BCD layout because later Windows installs add entries to the Boot Manager in a predictable way.

3. Shrink the main partition (if keeping an existing Windows 10)​

If you already have Windows 10 and want to preserve it, shrink C: using Disk Management instead of third‑party tools:

• Open Disk Management > right‑click C: > Shrink Volume > specify amount for the server OS.
• Create a new NTFS volume from the unallocated space and label it clearly (e.g., WindowsServer).
• Boot the Server installer and install to the newly created partition.

This is the path used by many guides for preserving an existing install while adding a second OS.

4. Install the second OS (Windows Server)​

• Boot from the Windows Server installation media and choose Custom install.
• Select the partition you created for the server. Install normally.
• During installation the system will reboot multiple times. At the initial reboot you may see a new Boot Manager menu; choose the server entry until installation completes so Setup finishes on the correct partition.

After installation, both OSes should appear in the Windows Boot Manager and you’ll be able to choose at each boot.

---

Managing the boot order and default OS​

Windows offers both GUI and command‑line ways to change the default boot entry:

• GUI: In Windows, press Windows+R, type msconfig, open the Boot tab, select the OS and click Set as default. This is the quick, easy method that Windows Report and community guides recommend for casual changes. (msconfig edits the BCD through a GUI.)
• Command line: Use bcdedit to view and modify boot manager entries if you need precise control or scripting. Third‑party tools such as EasyBCD can help less technical users edit entries safely, but they are unnecessary for standard two‑entry dual‑boot setups. Community posts recommend EasyBCD for multi‑OS scenarios where users are uncomfortable with bcdedit.

---

UEFI vs Legacy BIOS: practical advice and traps to avoid​

• Use UEFI/GPT when possible: it’s modern, required for Secure Boot, and recommended for SSDs. But UEFI introduces nuances: the USB installer needs a FAT32 EFI system or a tool that provides a UEFI‑NTFS shim when install.wim is > 4 GB. Tools like the Media Creation Tool or Rufus handle these details automatically.
• If you must use Legacy/MBR, be consistent: both systems should be installed in the same firmware mode. Mixing UEFI and BIOS installs complicates boot management and often requires firmware boot menus to select drives manually.
• If installers complain “Windows cannot be installed to this disk. The selected disk has an MBR partition table…”, convert the disk to GPT (or use MBR if your hardware requires it). Diskpart’s convert gpt is a direct way to fix that during Setup.

---

Common problems and recovery steps​

• Missing GRUB / Boot entries after install: when dual‑booting with non‑Windows OSes this is frequent, but with Windows 10 + Windows Server the Windows Boot Manager usually contains both entries. If the boot menu is damaged, Boot Repair techniques or rebuilding the BCD can help. Use an installation USB and run automatic Repair, or use command prompts with bootrec as necessary.
• Repairing bootloader (quick commands used from Windows Recovery Command Prompt):
• bootrec /fixmbr
• bootrec /fixboot
• bootrec /scanos
• bootrec /rebuildbcd

These commands aim to restore the Master Boot Record and BCD and are commonly used in recovery advice across troubleshooting forums. Always export your BCD before extensive edits.

• Installer can’t detect NVMe/RAID drives: load OEM IRST or NVMe drivers from a USB during Setup. This is commonly needed on systems with Intel RST enabled. Disk mode should be AHCI unless you explicitly require RAID.
• FAT32 4 GB limit blocks UEFI boot from large WIMs: use Microsoft’s Media Creation Tool or Rufus to create UEFI‑bootable media that either splits WIM or provides a UEFI NTFS boot shim. This avoids the common installer failure where firmware refuses to boot NTFS sticks.

---

Security, enterprise, and lifecycle considerations​

• BitLocker: suspend before repartitioning. If the system asks for a recovery key after changes, have your recovery key available. Unplanned recovery can be time consuming and disruptive.
• Drivers and server roles: Windows Server may require specific NIC or storage drivers not present in consumer Windows 10 images. Keep vendor driver packs on a separate USB during Setup.
• Lifecycle and support: Windows Server editions have lifecycle policies and EOL dates. Before committing a dual‑boot to production or long‑term lab use, verify the exact support dates for your chosen Server version from Microsoft’s lifecycle resources. Lifecycle timelines are time‑sensitive; confirm them for planning. (This guide avoids quoting specific EOL dates because they change and should be verified against current Microsoft documentation.) Flag: any precise EOL date referenced here must be checked against Microsoft’s official lifecycle pages before you rely on it for planning.

---

Recovery tool caution and third‑party utilities​

Third‑party tools (boot repair utilities, disk managers, password resets) can be valuable for recovery — but they add risk:

• Use reputable tools only, and test recovery media on a spare machine or VM first.
• Avoid blind “auto‑repair” without a backup; some tools change partitions or overwrite boot code in ways that require manual repair.
• If a commercial tool claims to “guarantee” recovery, treat that as conditional and verify user reviews and vendor reputation. Community recommendations emphasize creating a recovery USB and image over relying solely on paid utilities.

---

Alternatives to dual‑booting (recommended for many workflows)​

• Virtualization (Hyper‑V, VMware, VirtualBox) lets you run Windows Server as a VM inside Windows 10 with snapshots and easy rollback, eliminating most bootloader risks. For many dev/test needs this is the safer pattern.
• Containers and WSL are excellent for many server‑side development tasks and reduce the need for a full server OS installation.
• Use a dedicated spare drive for the server OS if you prefer native installation but want easier rollback: remove the drive to isolate systems or change boot order in firmware.

---

Practical checklist before you begin (copy/paste)​

• [ ] Full backup or disk image of current system.
• [ ] Recovery USB created with Windows Recovery Drive.
• [ ] Windows 10 and Windows Server ISO media ready; checksums verified.
• [ ] Decide UEFI vs Legacy and set firmware accordingly; note current setting.
• [ ] If preserving an existing Windows 10 install: shrink C: using Disk Management, create NTFS partition for Server.
• [ ] Driver pack (storage/NVMe/RST) on a secondary USB for Setup if needed.

---

Troubleshooting quick reference​

• Installer won’t see disk: check SATA mode (AHCI vs RAID), load vendor storage drivers, use diskpart to inspect disk.
• No boot menu after installing second OS: boot into Windows, run msconfig to set default OS or use bcdedit to inspect BCD. If the BCD is corrupt use bootrec from recovery media.
• Boot into BitLocker recovery after partition changes: ensure you have the recovery key logged or stored; suspend BitLocker before partitioning next time.

---

Final analysis: benefits, strengths and critical risks​

• Strengths
• Native performance for resource‑intensive server roles.
• Full isolation of server services from desktop workflows at the OS level.
• Low cost: leverage a single physical machine for both roles.
• Trade‑offs and risks
• Partitioning and bootloader changes create real risk of data loss or unbootable systems; backups and a recovery USB are non‑negotiable.
• Firmware mismatches (UEFI vs Legacy) and installer limitations (FAT32 single‑file size) are common sources of errors and require a small amount of technical knowledge to resolve.
• Enterprise encryption (BitLocker) and RAID/IRST configurations complicate installation and recovery; suspend encryption and gather drivers before starting.

---

Conclusion​

Dual‑booting Windows 10 and Windows Server is a practical, affordable approach for developers and IT professionals who need native server features alongside a daily desktop environment. The process is straightforward when you plan ahead: back up, create correct UEFI/GPT partitions (or use separate physical drives), prepare reliable installation media, and understand basic bootloader recovery tools. Use diskpart to precreate EFI/MSR/Windows partitions for the cleanest installs, rely on Microsoft’s media tools or Rufus to build UEFI‑capable installers, and keep a recovery USB plus vendor drivers to hand for troubleshooting. If you prefer less risk and more agility, virtualization is the modern alternative that avoids most dual‑boot pitfalls. When proceeding with a dual‑boot, careful prep and conservative defaults make the difference between a robust lab and a time‑consuming repair job.

---

If you need a condensed, step‑by‑step checklist tailored to your exact hardware (firmware type, single drive vs two drives, and the specific Windows Server version you intend to use), provide your firmware mode and disk layout and the exact Server SKU and the next detail set will be written as an actionable install plan.

---

Source: Windows Report How to dual boot Windows 10 and Windows Server