Build a Resolve-Ready Multiboot SSD

Preserve Windows while adding Ubuntu, Rocky Linux, shared files, and Resolve.

Introduction

30 Second Summary

Your laptop already holds the files you rely on every day. Making room for more operating systems puts that familiar Windows setup at risk unless every disk change is deliberate.

In this project, you will preserve Windows 11 while installing Ubuntu 24.04 and Rocky Linux 8 on one internal SSD. You will configure Rocky for DaVinci Resolve 21.1, then finish with a tested UEFI boot menu and two-way file access between the Linux systems.

What You'll Build

At startup, your Dell lets you choose Windows, Ubuntu, or Rocky Linux, then opens DaVinci Resolve with the NVIDIA GPU active and both Linux file trees within reach.

By the end of this project, you'll have:

A three-system UEFI boot flow that opens Windows 11, Ubuntu 24.04, or Rocky Linux 8 from the Dell one-time boot menu.
A DaVinci Resolve workstation on Rocky Linux 8.10 with the NVIDIA driver verified before launch.
Automatic two-way Linux file access through UUID-based mounts, with read-write tests from both operating systems.
Secret Mission: Build a multiboot recovery pack containing your disk map, filesystem UUIDs, boot entries, and first-response repair notes.

Are there any prerequisites?

You need the Dell G7 17 7700 on mains power, Windows administrator access, internet access, an 8 GB or larger USB drive, 32 GB of system memory, and a modern discrete NVIDIA GPU. Back up personal files and save the Windows BitLocker recovery key before changing firmware or partitions.

Before We Start

Before We Start...

Before the hands-on work begins, lock in the complete build and the safeguards that protect Windows 11. You are creating a three-system SSD with Ubuntu, Rocky Linux, DaVinci Resolve, and shared Linux files while keeping the sensitive Mac drive disconnected.

Create the Verified Ubuntu USB

The existing USB is ordinary storage. It needs a verified Ubuntu installer image before the Dell can boot it.

Windows hibernation can preserve an NTFS session that a Linux live system could misread. This step disables hibernation before Rufus rewrites the USB.

In this step, get ready to:

Prepare Windows for a safe Ubuntu live session.
Verify the downloaded Ubuntu image against its official SHA256 checksum.
Write the verified image to the existing USB with Rufus.

Protect the storage before writing

Rufus erases whichever USB you select. A capacity check identifies the correct drive before any destructive action begins.

Keep the sensitive Mac drive physically disconnected.
Connect the Dell to power.
Sign in to Windows with your administrator account.
Insert the existing USB drive.
Right-click Start.
Select Disk Management.
Locate the existing USB in the lower disk list by matching its removable-drive size.
Confirm that the USB has at least 8 GB of capacity.

Good. You now have one clearly identified USB target while the sensitive Mac drive stays outside the process.

Copy every file you want to keep from the USB to a folder on the internal C: drive using File Explorer.

Hibernation preserves the Windows NTFS session across shutdowns. Disabling it gives the later Ubuntu live environment a clean view of the volume.

Press the Windows key to open search.
Type Command Prompt into the search box.
Select Run as administrator for Command Prompt.
Approve User Account Control by selecting Yes.
Disable Windows hibernation by running this command:

powercfg.exe /hibernate off

What does this command do?

The powercfg.exe utility manages Windows power settings.
The /hibernate off option makes hibernation unavailable.
Administrator access allows the command to change this system-level setting.

Confirm that Command Prompt returns without reporting an error.

That safety setting is now in place. Windows no longer leaves a hibernated NTFS session for the live environment to encounter.

Command rejected?

Close Command Prompt if it was opened without administrator access.
Repeat the search steps using Run as administrator.
Still stuck? Help me disable Windows hibernation safely.

Download and verify the installer files

A checksum is a fingerprint calculated from a file's contents. Matching the official SHA256 value proves that your downloaded ISO has the expected contents.

The Ubuntu ISO is much larger than the Rufus executable. A quiet download bar for several minutes is normal on a slower connection.

Open the Ubuntu 24.04 release page in your web browser.
Select ubuntu-24.04.5.1-desktop-amd64.iso to download the desktop image.
Open the Rufus download page in your web browser.
Select rufus-4.15.exe to download the executable.
Wait for both downloads to finish.

You now have ubuntu-24.04.5.1-desktop-amd64.iso and rufus-4.15.exe in your Downloads folder.

PowerShell can calculate the ISO's SHA256 value directly. You can compare that result with Ubuntu's published value before trusting the image.

Press the Windows key to open search.
Type PowerShell into the search box.
Select Windows PowerShell.
Calculate the ISO's SHA256 value by running this command:

Get-FileHash -Path "$HOME\Downloads\ubuntu-24.04.5.1-desktop-amd64.iso" -Algorithm SHA256

What does this command do?

The Get-FileHash command calculates a fingerprint for the downloaded file.
The -Path parameter points to ubuntu-24.04.5.1-desktop-amd64.iso in your Downloads folder.
The -Algorithm SHA256 parameter selects the same algorithm used for Ubuntu's published checksum.

Compare the Hash value in the PowerShell output with 4da4a0c9035da8e68a59a838674f403f0a54472c78a83b4fb7f78d03588f85a7.

The two values should match character for character. That match confirms that the ISO is ready to write to the USB.

Checksum does not match?

Stop before opening Rufus because the downloaded ISO cannot be trusted.
Delete the mismatched ISO from your Downloads folder.
Download ubuntu-24.04.5.1-desktop-amd64.iso again from the Ubuntu 24.04 release page.
Still seeing different values? Help me troubleshoot the Ubuntu ISO checksum mismatch.

Write Ubuntu to the USB

Rufus writes the ISO image as bootable installation media. Its Device selection determines which drive gets erased.

This is the riskiest click in the step. Matching the Device capacity to your earlier check protects the internal SSD.

Press Windows+E to open File Explorer.
Select Downloads in the File Explorer sidebar.
Double-click rufus-4.15.exe.
Select the existing USB in the Device list.
Confirm that the displayed Device capacity matches the USB you checked earlier.
Click SELECT.
Choose ubuntu-24.04.5.1-desktop-amd64.iso from your Downloads folder.
Keep the remaining Rufus values at their defaults.

Before you start the write, which Rufus status do you expect to prove that the installer USB is complete?

Click START.
Select Write in ISO Image mode when Rufus asks how to write the image.
Approve the warning that the selected USB will be erased.

A few quiet minutes are normal while Rufus rewrites the drive.

Wait until the Rufus Status bar says READY.

That is the media preparation complete. Your internal SSD remains in its original Windows-only layout.

Rufus does not reach READY?

Confirm that Device still shows the existing USB.
Confirm that the selected image is ubuntu-24.04.5.1-desktop-amd64.iso.
Still stuck? Help me troubleshoot the Rufus USB write.

Your checksum-verified Ubuntu installer USB is ready. Next, you'll boot it through the Dell's one-time boot menu and prove that Ubuntu can see the internal SSD.

Boot Ubuntu and Check the SSD

Your verified Ubuntu installer is ready. Now the Dell must prove it can start Ubuntu through UEFI.

A live desktop gives you the first visible Linux result. GParted then reveals whether Ubuntu can access the internal SSD through its current storage-controller configuration.

In this step, get ready to:

Start Ubuntu from the verified USB.
Check the laptop hardware in the live desktop.
Confirm GParted can see the internal SSD.

Boot the live Ubuntu desktop

The Dell one-time boot menu starts the USB for this session without changing the saved boot order. Choosing Try Ubuntu runs Ubuntu 24.04.5.1 LTS without installing it.

Leave the sensitive Mac drive disconnected.
Leave the verified Ubuntu USB connected.
Restart Windows normally.
Tap F12 repeatedly when the Dell logo appears.
Select the UEFI boot entry that matches your USB device.
Choose Try Ubuntu when the Ubuntu screen loads.

You have reached your first visible Linux win. Ubuntu is running from the USB while the internal SSD remains untouched.

What is a live session?

A live session runs Ubuntu directly from the USB. It lets you test the laptop before committing an installation.

If you did not reach the live desktop, use the recovery path below before continuing.

USB missing from the boot menu?

Restarting the USB creation erases that USB again. Keeping the sensitive Mac drive disconnected limits the risk to the device selected in Rufus.

Restart the Dell if the Windows logo appeared before the boot menu.
Tap F12 earlier during the next startup.
Return to Windows if the USB still does not appear.
Run the Rufus 4.15 executable from earlier.
Select the correct USB under Device.
Set Partition scheme to GPT.
Confirm Target system shows UEFI (non CSM).
Write the Ubuntu ISO in ISO Image mode again.

Wait until Rufus reports READY. Boot the rewritten USB through F12.

Still stuck? Help me troubleshoot why my Dell cannot boot the Ubuntu USB.

Check the live-session hardware

The live session is a hardware compatibility gate. Stop before disk work if any listed component does not work reliably.

Inspect the full desktop for a clear picture.
Move the pointer across the desktop with the touchpad.
Open the live desktop application search.
Type Ubuntu hardware check into the search field.
Open the Wi-Fi network list from the top bar.
Connect to your Wi-Fi network.
Open a web browser from the desktop dock.
Play a short audio clip from a trusted website.

What should I see?

Your display shows a stable desktop at a usable resolution.
The pointer follows your touchpad movements.
The search field shows Ubuntu hardware check exactly.
Wi-Fi reports that the laptop is connected.
The browser loads a web page.
The speakers play the audio clip.

Confirm Ubuntu can see the internal SSD

GParted 1.5.0 can modify partition tables. This check uses its disk map without creating or applying any operation.

Disk tools can feel risky here. Keeping the pending-operations list empty preserves the original Windows-only layout.

Before you compare the device sizes, which entry do you expect to belong to the internal SSD?

Open the live desktop application search.
Enter GParted in the search field.
Start GParted from the search results.
Wait for GParted to finish scanning the connected storage devices.
Compare the device sizes in the GParted device selector.

✔️ I see the approximately 1 TB SSD

Ubuntu can access the SSD through the Dell's current storage-controller configuration. The larger device is the internal SSD.

Select the approximately 1 TB internal SSD.
Confirm its map contains the approximately 952.53 GB Windows NTFS volume.
Confirm the existing EFI partition remains visible.
Confirm the existing recovery or OEM partitions remain visible.
Confirm the smaller device is the Ubuntu USB.
Confirm GParted shows no pending partition operation.

The internal SSD should still show its original Windows-only GPT layout. No UBUNTU or ROCKY partition should exist.

ⓧ The SSD is absent or Intel RST appears

An Intel RST configuration can prevent Ubuntu from accessing the internal SSD. Switching to AHCI can also prevent Windows from starting when Windows is not prepared first.

This controller change is the fiddliest part of the check. Follow Canonical's Windows-to-AHCI workflow in the order shown below.

Shut down the live Ubuntu session.
Remove the USB when Ubuntu prompts you.
Start Windows normally.
Open Device Manager.
Expand IDE ATA/ATAPI controllers.
Check whether the listed mode reads Standard SATA AHCI Controller.

Already using the standard AHCI controller?

Stop before changing the registry or firmware if Device Manager already shows Standard SATA AHCI Controller. The missing SSD has a different cause.

Use help me diagnose why Ubuntu cannot see my SSD.

Start Registry Editor with administrator approval when the controller mode differs.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorV\.
Double-click the Start key.
Set the Start value to 0.
Expand the iaStorV entry.
Select the StartOverride entry.
Set the key named 0 to the value 0.
Repeat those changes under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\ if that path exists.

What do these registry changes prepare?

The registry values enable the Windows storage drivers needed for AHCI. Safe boot gives Windows one controlled startup to configure those drivers after the firmware change.

Search Windows for msconfig.
Open the System Configuration app.
Select the Boot tab.
Enable Safe boot under the boot options.
Select OK to confirm the setting.

Prepare Windows before changing firmware

Changing SATA Operation before completing the registry and Safe boot preparation can stop Windows from starting. You have now completed the required preparation.

Restart the Dell.
Tap F2 repeatedly when the Dell logo appears.
Select SATA Operation in the firmware storage settings.
Change the controller mode to AHCI.
Save the firmware changes.
Let Windows start in Safe Mode.
Open System Configuration again.
Disable Safe boot.

What did Safe Mode accomplish?

Windows has now configured the AHCI storage path while using a minimal startup environment. The next normal restart proves Windows can use that controller mode.

Restart Windows normally.
Return to Device Manager.
Confirm the controller now reads Standard SATA AHCI Controller.
Shut down Windows.
Reconnect the verified Ubuntu USB.
Boot the USB through F12.
Choose Try Ubuntu.
Start GParted again.

Windows now starts normally with AHCI active, and GParted is open in the new Ubuntu session. Confirm that the internal SSD remains visible through the new controller mode.

Select the approximately 1 TB internal SSD.
Confirm the approximately 952.53 GB Windows NTFS volume remains visible.
Confirm the smaller Ubuntu USB remains a separate device.
Confirm GParted shows no pending partition operation.

Windows not starting normally?

Stop making firmware changes if Windows does not start after the controller switch. Use Canonical's recovery section from the linked workflow before continuing.

Need help? Help me recover Windows after changing the storage controller to AHCI.

You should see the approximately 1 TB internal SSD selected with its original Windows-only partition map. The smaller Ubuntu USB remains a separate device.

No partition operation should be pending. The approximately 952.53 GB Windows NTFS volume remains unchanged.

That is the storage compatibility check complete. Next, you'll document the untouched disk map before making room for Linux.

Inspect the Current Disk Layout

Your Ubuntu live desktop can read the internal SSD. Before changing any partition, you need a baseline that separates Windows data from the boot and recovery areas.

This step compares the SSD through GParted and Windows Disk Management. The comparison reveals whether the current layout already has enough room for both Linux targets.

In this step, get ready to:

Identify every partition on the internal SSD.
Capture a baseline photo before making any disk changes.
Confirm the current layout in Windows Disk Management.

Inspect the SSD in GParted

Disk tools can feel high stakes. This inspection leaves the disk layout untouched.

The sensitive Mac drive remains disconnected. The Dell remains connected to power.

Before you inspect the map, do you think the SSD already has enough unallocated space for separate Ubuntu and Rocky Linux targets? Hold that prediction while you read the layout.

Check that GParted still shows the approximately 1 TB internal SSD as the selected device.
Locate the approximately 952.53 GB partition that uses the NTFS filesystem.
Identify that partition as the Windows C: volume by its filesystem and size.
Locate the existing EFI System Partition by its small size and boot role.
Identify every visible recovery or OEM partition by its size, filesystem, label, or flags.
Avoid every create, resize, format, delete, queue, or apply control.

You should see the Windows volume consuming almost all usable space. You should see no Linux-sized unallocated region.

That shortage is the intended obstacle. The current layout has no distinct target for Ubuntu or Rocky Linux.

What Are These Partitions?

The Windows NTFS volume holds the operating system and files stored on C:.
The EFI System Partition stores the boot files used by UEFI firmware.
Recovery and OEM partitions support repair tools or manufacturer recovery features.

Take a clear photo of the full GParted window using your phone or camera.
Review the photo to confirm that the Windows NTFS volume, EFI System Partition, and every visible recovery or OEM partition are readable.
Confirm that GParted lists no pending partition operation.

You now have a trustworthy before picture. That photo records the untouched Windows-only layout before any repartitioning begins.

Cannot Identify a Partition?

Use each partition's filesystem and size to distinguish it from the Windows NTFS volume.
Leave any uncertain partition untouched because boot and recovery partitions can be small.
Still unsure? Help me identify the partitions in my GParted disk map.

Confirm the disk map in Windows

GParted exposed the space shortage from the live desktop. Disk Management lets you confirm the same layout from the operating system that owns the NTFS volume.

Use the system menu in the top-right corner of the Ubuntu desktop to shut down the live session.
Remove the Ubuntu USB when prompted.
Press Enter to complete the shutdown after removing the USB.
Press the Dell's power button to start the laptop.

You should reach the normal Windows sign-in screen. This confirms the untouched Windows installation still starts from the internal SSD.

Before you open Disk Management, do you expect Windows to reveal a Linux-sized unallocated region that GParted missed? Hold that prediction while you compare the second view.

Right-click the Start button in the taskbar.
Select Disk Management.
Find the C: volume on the approximately 1 TB internal disk.
Read the displayed capacity of the C: volume.
Inspect the disk map immediately after the C: volume.
Confirm that no partition operation or progress task is active.

You should see the C: volume at approximately 952.53 GB. You should see no Linux-sized unallocated region.

The existing EFI, recovery, and OEM partitions remain unchanged. No partition operation is pending.

Disk Management Looks Different?

Check that you are reading the approximately 1 TB internal disk instead of a smaller removable device.
Maximize Disk Management if partition labels or capacities are cut off.
Avoid changing any partition while comparing the two disk maps.
Still stuck? Help me compare my Windows Disk Management layout with my GParted photo.

Your original disk layout is documented in both tools. Next up, you will create Linux space while preserving the Windows, EFI, recovery, and OEM partitions.

Shrink Windows for Linux Space

Your baseline disk map proved that Windows currently occupies almost the entire internal SSD. Neither Ubuntu nor Rocky Linux has a safe target yet.

Windows Disk Management can shrink the NTFS volume while preserving its files. This step leaves C: at 204800 MB, which is approximately 200 GiB.

In this step, get ready to:

Calculate the shrink amount that leaves C: at 204800 MB.
Shrink C: to approximately 200 GiB.
Confirm Windows starts normally from the resized volume.

Calculate the shrink amount

The shrink dialog expects the amount Windows should remove from C:. Your target keeps 204800 MB on the volume.

In Windows Disk Management from earlier, right-click the approximately 952.53 GB C: volume.
Select Shrink Volume.
Read the value beside Total size before shrink in MB.
Subtract 204800 from the displayed value.
Record the result here: your calculated shrink amount in MB.

Why Subtract 204800?

The calculated result is the amount removed from C:. Keeping 204800 MB produces the planned Windows target of approximately 200 GiB.

The released capacity becomes unallocated space for the two Linux targets. Small differences in the displayed totals can come from storage unit presentation.

Windows Offers Too Little Space?

Cancel the dialog if the available shrink space is smaller than your calculated shrink amount in MB.
Follow Microsoft's guidance on unmovable files to identify what is limiting the shrink.
Avoid forcing the resize with GParted or another partition tool.
Still blocked? Help me diagnose why Windows cannot shrink C: enough.

Shrink the Windows volume

Changing a partition boundary can feel risky. Your baseline photo gives you a reference for every partition you must preserve.

The Dell remains connected to power. The sensitive Mac drive remains disconnected.

Enter your calculated shrink amount in MB as the amount to shrink.
Verify that the dialog calculates a final volume size of 204800 MB.
Select Shrink to commit the resize.

When the operation finishes, you should see C: at approximately 200 GB followed immediately by approximately 752 GB marked Unallocated.

Leave the released region marked Unallocated untouched.
Avoid creating a New Simple Volume in the released region.
Compare the existing EFI System Partition against your baseline photo.
Compare every recovery or OEM partition against your baseline photo.

Does the Layout Look Different?

Stop before creating or formatting another partition.
Compare each visible partition with your baseline photo.
Confirm that only the size of C: changed.
Need another set of eyes? Help me compare my resized Windows disk map with the baseline.

Restart and verify Windows

A successful restart proves that Windows can still boot from the resized volume. Opening an application plus a file checks that C: remains usable.

Before you restart, which results would prove that the resize succeeded without harming Windows?

Restart the Dell from Windows.

You should reach the Windows sign-in screen normally.

Sign in with your administrator account.
Open one Windows application installed on C:.
Open one file stored on C:.

The application plus the file should open normally. This confirms the resized Windows volume remains usable.

Right-click Start.
Select Disk Management.

You should see C: at approximately 200 GB followed immediately by approximately 752 GB marked Unallocated.

The existing EFI System Partition, recovery partitions, plus OEM partitions should match your baseline photo. No UBUNTU or ROCKY partition exists yet.

That's the delicate resize complete. Next, you'll turn the unallocated region into separate targets for Ubuntu plus Rocky Linux.

Create Ubuntu and Rocky Targets

You have proved that Windows can release enough SSD space without moving or deleting its system partitions. That unallocated region is now ready to become three clearly identified Linux targets.

In this step, you will use GParted to create Ubuntu’s main partition plus Rocky Linux boot and root partitions. The small Rocky boot partition keeps its boot files separate, while the larger Rocky root partition becomes the Resolve environment.

In this step, get ready to:

Confirm the unallocated space is on the internal SSD.
Create the Ubuntu and Rocky Linux targets.
Apply the queued operations and verify the final disk map.

Open the internal SSD in GParted

Press the Windows key.
Type GParted.
Open GParted Partition Editor.
Enter the live-session password if Ubuntu requests authentication.
Open the device selector in the top-right corner.
Select the approximately 1 TB internal NVMe SSD.

Confirm the disk before editing

The risky part is choosing the correct device. Confirm that you can see the roughly 200 GiB Windows NTFS partition plus approximately 752 GB of unallocated space before continuing.

Stop if the layout does not match. Keep every external drive disconnected so only the USB installer and internal SSD are available.

Create the Ubuntu target

Right-click the large unallocated region.
Select New.
Enter 614400 in New size (MiB).
Select ext4 as the file system.
Enter UBUNTU in the Label field.
Click Add.

You will see a queued 600 GiB partition named UBUNTU plus unallocated space for Rocky Linux.

Create the Rocky targets

Right-click the remaining unallocated region.
Select New.
Enter 2048 in New size (MiB).
Select ext4 as the file system.
Enter ROCKY_BOOT in the Label field.
Click Add.
Right-click the final unallocated region.
Select New.

You will now see a queued 2 GiB partition named ROCKY_BOOT. The remaining unallocated region becomes Rocky’s root target.

Use all remaining space for the new partition.
Select ext4 as the temporary file system.
Enter ROCKY in the Label field.
Click Add.
Confirm the queued map contains UBUNTU, ROCKY_BOOT, and ROCKY.
Click the green checkmark in the toolbar.
Click Apply in the confirmation window.

The temporary ext4 format makes the ROCKY target easy to identify in the installer. Rocky reformats this partition as xfs before writing its system files.

This operation can take several minutes while GParted formats the large filesystems. Leave the laptop connected to power until the completion message appears.

Click Close after GParted reports that every operation completed successfully.
Confirm the disk map shows the Windows NTFS partition, UBUNTU, ROCKY_BOOT, and ROCKY without warning icons.

Did an operation fail?

Stop before retrying or formatting another partition. Help me interpret the failed GParted operation without changing any other partition.

Your SSD now has dedicated targets for both Linux systems without touching Windows. Next, you will install Ubuntu 24.04 into its 600 GiB partition.

Install Ubuntu 24.04

The SSD now presents separate Ubuntu and Rocky Linux targets while Windows remains intact. The next goal is to turn the 600 GiB Ubuntu target into a working Ubuntu 24.04 desktop.

The installer can see every partition on the drive, so manual storage selection matters here. You will format only UBUNTU and reuse the existing EFI System Partition without erasing it.

In this step, get ready to:

Start the Ubuntu installer in manual mode.
Assign only the Ubuntu and EFI partitions.
Boot the installed Ubuntu 24.04 desktop.

Start the manual installation

Double-click Install Ubuntu 24.04.5.1 LTS on the live desktop.
Choose your language.
Choose your keyboard layout.
Connect to your network if the installer offers the option.
Select Interactive installation.
Select the default software selection.
Enable third-party software for graphics and Wi-Fi hardware.
Select Manual installation on the disk setup screen.

Why use manual installation?

Manual installation exposes the full partition table. That control keeps Windows and the future Rocky Linux environment outside Ubuntu’s format operation.

Assign the Ubuntu and EFI partitions

Select the approximately 600 GiB partition labelled UBUNTU.
Set its filesystem to ext4.
Set its mount point to /.
Enable formatting for the UBUNTU partition.
Select the existing small FAT32 EFI System Partition.
Set its mount point to /boot/efi.
Leave formatting disabled for the EFI System Partition.
Leave ROCKY_BOOT and ROCKY unused.

Check the format summary

The confirmation screen is your final safety check. It should show one format operation for UBUNTU and no format operation for Windows, EFI, recovery, OEM, ROCKY_BOOT, or ROCKY.

Continue only when the storage summary matches the intended layout.
Choose your time zone.
Enter your display name.
Enter your Linux username as the account username.
Create your account password.
Start the installation.

Expect the installation to take about 15 to 30 minutes. The progress screen can pause while packages and boot files are copied, so leave the laptop connected to power.

Boot and verify Ubuntu 24.04

Click Restart Now when the installer finishes.
Remove the Ubuntu USB when the installer requests it.
Press Enter to continue the restart.
Select Ubuntu from the boot menu if the Dell does not choose it automatically.
Sign in with your new Linux account.

Before you check the system, do you expect the root filesystem to come from the 600 GiB UBUNTU partition?

Verify the installed release and root filesystem by running these commands:

cat /etc/os-release
findmnt -no SOURCE,FSTYPE /

You will see Ubuntu 24.04 in the release details. The second line will identify an ext4 filesystem mounted at /.

Ubuntu does not appear?

Use the Dell F12 menu to select the Ubuntu boot entry. If Ubuntu still does not start, help me check the EFI and Ubuntu boot entries without formatting any partition.

Ubuntu 24.04 now runs from its dedicated partition. Next, you will prove that both Ubuntu and Windows still boot before replacing the USB with Rocky Linux media.

Verify Windows and Ubuntu

Ubuntu now boots from the partition you prepared. Before introducing another installer, you need proof that the current Windows and Ubuntu boot paths both work.

This checkpoint creates a known-good baseline. It also captures Ubuntu’s filesystem UUID, which Rocky Linux will use to mount Ubuntu’s data later.

In this step, get ready to:

Boot Windows through the Dell one-time boot menu.
Return to Ubuntu and record its filesystem UUID.
Confirm both operating systems expose your files normally.

Test the Windows boot path

Before you restart, do you expect Windows to open from the unchanged 200 GiB NTFS partition?

Shut down Ubuntu.
Start the Dell.
Press F12 at the Dell logo.
Select Windows Boot Manager.
Sign in to Windows 11.
Open one familiar file stored on C:.

The file should open normally. That confirms Windows still boots from its own partition after the Ubuntu installation.

Windows does not start?

Do not launch Startup Repair or make another partition change. Use F12 to retry Windows Boot Manager, then help me inspect the boot entries without formatting the SSD.

Record Ubuntu’s filesystem UUID

Restart the Dell from Windows.
Press F12 at the Dell logo.
Select the Ubuntu boot entry.
Sign in to Ubuntu.
Read the UUID of Ubuntu’s active root filesystem by running:

findmnt -no UUID /

You will see one UUID on its own line. Record it here: your Ubuntu filesystem UUID.

Why record the UUID?

A filesystem UUID identifies the partition even if Linux assigns it a different device name on another boot. That makes UUID-based mount entries safer than paths such as /dev/nvme0n1p5.

Confirm both entries remain available

Restart the Dell from Ubuntu.
Press F12 at the Dell logo.
Confirm the menu lists Windows Boot Manager.
Confirm the menu lists Ubuntu.
Select Ubuntu to return to the installed desktop.

You have now booted both installed systems and confirmed their files are readable. That baseline makes the Rocky Linux installation easier to diagnose if its boot entry changes the default order.

Windows and Ubuntu are both healthy, and Ubuntu’s UUID is recorded. Next, you will check the Resolve hardware requirements and replace the USB with Blackmagic’s Rocky Linux environment.

Prepare the Resolve Environment

Windows and Ubuntu now provide a stable baseline, and Ubuntu’s UUID is saved. Rocky Linux has one job in this build: provide Blackmagic Design’s tested environment for DaVinci Resolve.

Blackmagic formally tests Resolve on Rocky Linux 8.6 with a modern discrete NVIDIA GPU. The current Linux minimums include 32 GB of system memory, at least 2 GB of VRAM, and support for OpenCL 1.2 or CUDA 11.

In this step, get ready to:

Confirm the Dell meets Resolve’s Linux requirements.
Download Blackmagic’s current Rocky Linux environment.
Write and boot the Rocky Linux USB safely.

Check the Resolve hardware baseline

Boot Windows through Windows Boot Manager.
Press Ctrl+Shift+Esc to open Task Manager.
Select Performance in the left sidebar.
Select Memory.
Record the installed amount: your installed system memory.
Select the NVIDIA GPU entry.
Record the model: your NVIDIA GPU model.
Record the dedicated GPU memory shown in the panel.

Does the Dell meet the minimums?

Resolve on Linux expects 32 GB of system memory and a discrete GPU with at least 2 GB of VRAM. Blackmagic’s formally tested path uses a modern NVIDIA GPU with the manufacturer driver.

If the Dell has less than 32 GB of RAM or no NVIDIA GPU, continue only with the operating-system installation. Upgrade the missing hardware before treating Rocky as a supported Resolve workstation.

Download the Blackmagic environment

Open the official DaVinci Resolve download page in your browser.
Choose the Linux download for DaVinci Resolve or DaVinci Resolve Studio.
Complete Blackmagic’s download form.
Save the Linux package in your Windows Downloads folder.
Extract the downloaded package.
Open the included Linux installation instructions PDF.
Open the standardized Rocky Linux environment link in that PDF.
Download the ISO and its accompanying checksum file.

Use the current installer PDF

Use the link inside the current Resolve package instead of an old bookmarked ISO. Blackmagic updates the standardized image independently from the Resolve application.

Open Windows PowerShell through the Start menu.
Calculate the ISO’s SHA256 value by running:

Get-FileHash -Algorithm SHA256 "[[ROCKY_ISO_PATH="C:\Users\your-name\Downloads\your Rocky Linux ISO.iso"]]"

Compare the displayed hash with the value in Blackmagic’s checksum file.
Delete the ISO if the two values differ.

Matching values confirm that the large installer image reached your computer unchanged.

Write the USB and disable Secure Boot

Download Fedora Media Writer for Windows from its official release page.
Run the downloaded installer.
Complete the setup wizard.
Press the Windows key.
Type Fedora Media Writer.
Press Enter to open the app.
Choose Custom image.
Select the verified Rocky Linux ISO.

Writing the image erases the USB that currently holds Ubuntu. The installed Ubuntu system remains on the SSD, so only the removable drive is replaced.

Select the removable USB by its capacity and model.
Click Write to disk.
Approve the Windows administrator prompt.
Wait for Fedora Media Writer to finish writing and checking the image.
Shut down Windows after the success message appears.
Start the Dell.
Press F2 when the Dell logo appears.
Open Boot Configuration.

Set Enable Secure Boot to off.
Leave Boot Mode set to UEFI only.
Apply the changes.
Exit the firmware setup.
Press F12 at the next Dell logo.
Select the Rocky Linux USB.

You will reach Blackmagic’s Rocky Linux installation menu. Stop at the menu without choosing Automatic installation.

Never choose Automatic installation

Automatic installation can erase every drive visible to the installer. Your Windows and Ubuntu partitions share this SSD, so the next step uses manual configuration only.

The installer menu is now the success signal. If the USB never reaches this screen, use the checks below.

USB missing from F12?

Confirm that Secure Boot is off and that Fedora Media Writer completed its checking phase. If the USB still does not appear, help me check the USB and UEFI settings without changing the SSD.

The Resolve hardware baseline is checked, and Blackmagic’s Rocky environment now boots from USB. Next, you will install it manually without touching Windows or Ubuntu.

Install Rocky Linux for Resolve

Blackmagic’s installer now starts from USB, and the Dell’s Resolve hardware has been checked. The remaining challenge is putting Rocky Linux into its two reserved targets without letting the installer take over the SSD.

Manual configuration keeps the format list explicit. Rocky will use ROCKY_BOOT for /boot, ROCKY for /, and the existing EFI System Partition for shared UEFI boot files.

In this step, get ready to:

Choose manual storage configuration.
Assign only the Rocky Linux targets and existing EFI partition.
Boot Rocky Linux and record its root filesystem UUID.

Open manual storage configuration

Select Manual configuration from Blackmagic’s installer menu.
Choose your language.
Choose your keyboard layout.
Open Installation Destination.
Select the approximately 1 TB internal NVMe SSD.
Choose custom storage configuration.
Confirm the partition list contains UBUNTU, ROCKY_BOOT, and ROCKY.

Confirm the internal SSD

Stop if the selected drive does not show the 200 GiB Windows partition and 600 GiB UBUNTU partition. Those two landmarks distinguish the internal SSD from the installer USB.

Assign the Rocky Linux filesystems

Select the 2 GiB partition labelled ROCKY_BOOT.
Set its mount point to /boot.
Set its filesystem to ext4.
Enable formatting for ROCKY_BOOT.
Select the large partition labelled ROCKY.
Set its mount point to /.
Set its filesystem to xfs.
Enable formatting for ROCKY.

The storage table should now show ROCKY_BOOT at /boot and ROCKY at /. Next, attach the existing EFI partition without formatting it.

Select the existing FAT32 EFI System Partition.
Set its mount point to /boot/efi.
Leave formatting disabled for the EFI System Partition.
Leave the 600 GiB UBUNTU partition unchanged.
Leave every Windows, recovery, and OEM partition unchanged.
Open the pending storage summary.

Read every pending format operation

This is the destructive checkpoint. The summary must contain format operations only for ROCKY_BOOT and ROCKY.

Return to storage configuration if the summary mentions Windows, EFI, recovery, OEM, or UBUNTU.

Accept the storage changes after the summary matches the intended layout.
Open User Creation.
Enter your Linux username as the username.
Create the account password.
Grant the account administrator access.
Start the installation.

The installation normally takes 15 to 30 minutes while Rocky Linux, NVIDIA components, and Blackmagic packages are copied. Leave the laptop connected to power until the installer reports completion.

Boot Rocky Linux and record its UUID

Reboot when the installer finishes.
Remove the Rocky Linux USB when the system restarts.
Press F12 at the Dell logo.
Select the Rocky Linux boot entry.
Sign in with your Linux account.

Before you inspect the system, do you expect Rocky’s root filesystem to use xfs on the partition labelled ROCKY?

Verify the installed release and root filesystem by running:

cat /etc/rocky-release
findmnt -no SOURCE,FSTYPE,UUID /

You will see Rocky Linux 8.6 in the release output. The second line will show the active xfs root filesystem and its UUID.

Record the final value from that line: your Rocky filesystem UUID.

Rocky Linux does not boot?

Use F12 to select the Rocky boot entry again. If it remains missing, help me inspect the UEFI installation without reformatting any partition.

Rocky Linux now occupies only its reserved partitions, and its filesystem UUID is recorded. Next, you will verify the NVIDIA stack and install the current DaVinci Resolve release.

Validate Rocky for DaVinci Resolve

Rocky Linux now boots from its own XFS partition with Blackmagic’s dependencies and NVIDIA components. The next goal is to bring Rocky 8 onto its supported minor release, prove that GPU acceleration survived, and launch DaVinci Resolve.

Rocky Linux supports only the latest minor release in each major line, which is Rocky 8.10 through May 2029. Blackmagic’s formal test baseline remains Rocky 8.6, so the NVIDIA check after the update is the gate before Resolve installation.

In this step, get ready to:

Update Rocky Linux 8 to its supported minor release.
Verify the NVIDIA driver and GPU.
Install and open DaVinci Resolve.

Update within Rocky Linux 8

Connect Rocky Linux to the internet.
Open Terminal from the applications menu.
Upgrade Rocky Linux 8 by running:

sudo dnf -y upgrade

The upgrade can take 10 to 30 minutes because it replaces the Rocky 8.6 kernel and base packages. Keep the laptop on power while the package transaction runs.

Restart Rocky Linux after the command completes.
Confirm the supported Rocky release by running:

cat /etc/rocky-release

You will see Rocky Linux 8.10. This is the supported Rocky 8 minor release with security maintenance through May 2029.

Did the upgrade fail?

Do not install Resolve after an interrupted package transaction. Reconnect the network, then help me complete the Rocky 8 upgrade without removing Blackmagic or NVIDIA packages.

Verify the NVIDIA stack

Read the active NVIDIA driver and GPU state by running:

nvidia-smi

You will see your NVIDIA GPU model, the NVIDIA driver version, total VRAM, and no driver communication error.

NVIDIA driver unavailable?

Stop before installing Resolve if nvidia-smi cannot communicate with the driver. Reboot once more, then use the driver instructions inside Blackmagic’s Linux installation PDF.

Help me restore the NVIDIA driver without replacing the Rocky installation.

With the NVIDIA stack confirmed, review your camera codecs before choosing the Resolve edition.

Check your media codecs

The free Linux edition has narrower delivery codec support than Windows. Blackmagic’s codec list marks H.264 and H.265 decode and encode as Studio features on supported NVIDIA hardware.

AAC audio support can also differ on Linux. Check the source codecs from your cameras before moving an active project away from Windows.

Install and open DaVinci Resolve

Open a web browser from Rocky’s applications menu.
Open the official DaVinci Resolve download page.
Choose the Linux download for the Resolve edition you selected earlier.
Complete Blackmagic’s download form.
Save the Linux package in Rocky’s Downloads folder.
Open Files from the applications menu.
Open the Downloads folder.
Extract the downloaded package.

The current Linux package is now available inside Rocky. The next actions make Blackmagic’s installer executable and start it.

Open the extracted DaVinci Resolve Linux folder.
Right-click the file whose name ends in .run.
Open the file’s properties.
Enable permission to run the file as a program.
Close the properties window.
Double-click the .run file as your normal user.
Accept the licence terms.
Complete the installation wizard.

The installation can take several minutes while it registers the application and checks its libraries. A brief pause does not mean the installer has stopped.

Press the Super key after installation.
Type DaVinci Resolve.
Open DaVinci Resolve.
Activate Resolve Studio if you installed the Studio edition.
Create an empty test project named Multiboot GPU Test.

You will reach the Edit page without a GPU initialization error. That proves the Rocky, NVIDIA, and Resolve layers can work together.

Resolve does not open?

Confirm that nvidia-smi succeeds before troubleshooting Resolve itself. If the driver works, help me interpret the Resolve startup error using Blackmagic’s Linux requirements.

DaVinci Resolve now opens on a current Rocky 8 system with the NVIDIA driver active. Next, you will give Ubuntu and Rocky automatic read-write access to each other’s files.

Share Files Between Linux Systems

Rocky now launches DaVinci Resolve with the NVIDIA driver active. The two Linux systems still keep their files behind separate root filesystems, so the next goal is to make each one mount the other automatically.

A filesystem UUID keeps each mount stable across boots. Using the same Linux username also makes ownership predictable when both first-user accounts use numeric user ID 1000.

In this step, get ready to:

Mount Rocky’s filesystem automatically in Ubuntu.
Mount Ubuntu’s filesystem automatically in Rocky.
Read and write test files across both Linux systems.

Mount Rocky in Ubuntu

Boot Ubuntu through the F12 menu.
Open Terminal.
Check Ubuntu’s numeric user ID by running:

id -u

You should see 1000.

Create the Rocky mount point, back up Ubuntu’s mount table, and add the automatic mount by running:

sudo mkdir -p /mnt/rocky
sudo cp /etc/fstab /etc/fstab.before-multiboot
echo 'UUID=[[ROCKY_UUID="your Rocky filesystem UUID"]] /mnt/rocky xfs defaults,nofail,x-systemd.device-timeout=10s 0 2' | sudo tee -a /etc/fstab
sudo mount -a

What do these commands do?

The first command creates a stable folder for Rocky’s filesystem.
The backup provides a clean rollback if the new line contains a typo.
The UUID line tells Ubuntu where to mount Rocky on every boot.
The final command tests every mount entry immediately.

Confirm the Rocky mount by running:

findmnt /mnt/rocky

You will see the Rocky UUID mounted at /mnt/rocky with the xfs filesystem.

Did mount -a report an error?

Do not reboot with an untested mount entry. Restore Ubuntu’s backup before retrying:

sudo cp /etc/fstab.before-multiboot /etc/fstab

Help me correct the UUID or fstab fields before I reboot.

Create an Ubuntu test file by running:

printf 'Created in Ubuntu\n' > ~/Documents/ubuntu-share-test.txt

Confirm the file content by running:

cat ~/Documents/ubuntu-share-test.txt

You will see Created in Ubuntu.

Mount Ubuntu in Rocky

Restart the Dell.
Boot Rocky Linux through the F12 menu.
Open Terminal.
Check Rocky’s numeric user ID by running:

id -u

You should also see 1000. Stop and resolve the account IDs before sharing writable files if the number differs.

User IDs do not match?

Do not create or modify files through /mnt/rocky while the IDs differ. Align the two accounts before adding Rocky’s mount entry or performing the cross-system file tests.

Help me compare the account IDs before I continue.

Create the Ubuntu mount point, back up Rocky’s mount table, and add the automatic mount by running:

sudo mkdir -p /mnt/ubuntu
sudo cp /etc/fstab /etc/fstab.before-multiboot
echo 'UUID=[[UBUNTU_UUID="your Ubuntu filesystem UUID"]] /mnt/ubuntu ext4 defaults,nofail,x-systemd.device-timeout=10s 0 2' | sudo tee -a /etc/fstab
sudo mount -a

Confirm the Ubuntu mount by running:

findmnt /mnt/ubuntu

You will see the Ubuntu UUID mounted at /mnt/ubuntu with the ext4 filesystem.

Ubuntu mount failed?

Restore Rocky’s backup before retrying:

sudo cp /etc/fstab.before-multiboot /etc/fstab

Help me correct the mount entry before I reboot.

Exchange a test file

Read the Ubuntu test file from Rocky by running:

cat /mnt/ubuntu/home/[[LINUX_USERNAME="your Linux username"]]/Documents/ubuntu-share-test.txt

You will see Created in Ubuntu.

Create a Rocky test file by running:

printf 'Created in Rocky\n' > ~/Documents/rocky-share-test.txt

Restart the Dell.
Boot Ubuntu through the F12 menu.
Read the Rocky test file by running:

cat /mnt/rocky/home/[[LINUX_USERNAME="your Linux username"]]/Documents/rocky-share-test.txt

You will see Created in Rocky. Both automatic mounts now support two-way file access.

Ubuntu and Rocky can now read and write each other’s files through stable UUID-based mounts. Next, you will run one final boot and storage test across Windows, Ubuntu, and Rocky Linux.

Complete the Multiboot Test

The two Linux systems now exchange files through automatic mounts. The final step proves that all three operating systems still boot independently and retain the storage roles you designed.

Windows 11 must open its files. Ubuntu must mount Rocky Linux, while Rocky must mount Ubuntu and keep the NVIDIA driver and DaVinci Resolve available.

In this step, get ready to:

Boot and check Windows 11.
Boot and check Ubuntu 24.04.
Boot and check Rocky Linux with DaVinci Resolve.

Verify Windows 11

Before you start the test, do you expect all three installed systems to appear in the Dell one-time boot menu?

Restart the Dell.
Press F12 at the Dell logo.
Confirm the menu lists Windows Boot Manager.
Confirm the menu lists Ubuntu.
Confirm the menu lists Rocky Linux.
Select Windows Boot Manager.
Sign in to Windows 11.
Open one familiar file on C:.

The file will open normally. Windows remains independent from both Linux filesystems.

Verify Ubuntu and the Rocky mount

Restart the Dell.
Press F12 at the Dell logo.
Select Ubuntu.
Sign in to Ubuntu.
Verify Ubuntu’s root and Rocky’s automatic mount by running:

findmnt /
findmnt /mnt/rocky

You will see Ubuntu’s ext4 root plus Rocky’s xfs filesystem at /mnt/rocky.

Read Rocky’s test file by running:

cat /mnt/rocky/home/[[LINUX_USERNAME="your Linux username"]]/Documents/rocky-share-test.txt

You will see Created in Rocky.

Verify Rocky, Ubuntu, and Resolve

Restart the Dell.
Press F12 at the Dell logo.
Select Rocky Linux.
Sign in to Rocky Linux.
Verify Rocky’s root, Ubuntu’s mount, and the NVIDIA driver by running:

findmnt /
findmnt /mnt/ubuntu
nvidia-smi

You will see Rocky’s xfs root, Ubuntu’s ext4 filesystem at /mnt/ubuntu, and your NVIDIA GPU model in the NVIDIA status table.

Read Ubuntu’s test file by running:

cat /mnt/ubuntu/home/[[LINUX_USERNAME="your Linux username"]]/Documents/ubuntu-share-test.txt

You will see Created in Ubuntu. Rocky can read the file through its automatic Ubuntu mount.

Open DaVinci Resolve from the applications menu.
Open the Multiboot GPU Test project.

DaVinci Resolve will reach the Edit page without a GPU error. Your three-system boot, storage, and Resolve checks are complete.

Did one check fail?

Retry the affected system through F12 before changing firmware or partitions. Help me isolate the failed boot, mount, or NVIDIA check without changing the disk layout.

Secret mission

Build a Multiboot Recovery Pack

Build a multiboot recovery pack with your partition map, filesystem UUIDs, UEFI entries, mount tables, and first-response repair notes. Store the archive away from the internal SSD so a future boot failure starts with evidence.

Clean Up Your Resources

Your finished layout lives entirely on hardware you already own, so it creates no ongoing cloud costs. Choose the cleanup option that matches what you want to do next.

Resources you used:

The removable USB containing Blackmagic’s Rocky Linux installer.
The installed Ubuntu 24.04 system on UBUNTU.
The installed Rocky Linux system on ROCKY_BOOT and ROCKY, including DaVinci Resolve.
The Ubuntu and Rocky UEFI boot entries on the shared EFI System Partition.
The Windows C: volume reduced to approximately 200 GiB.

Keep everything running

No action is needed. Choose this if you want to keep using the finished Windows, Ubuntu, Rocky Linux, and DaVinci Resolve setup.

Keep Secure Boot off while using Blackmagic’s Rocky Linux environment.
Keep the recovery pack stored away from the internal SSD.
Run nvidia-smi after Rocky kernel or driver updates.
Keep Windows, Ubuntu, and Rocky backups current.

Pause - I'll come back to this later

Shut down running systems to free their active resources. The installed operating systems, mounts, and Resolve environment remain ready for your return.

Close DaVinci Resolve.
Shut down the current operating system normally.
Remove the Rocky Linux installer USB after the Dell powers off.
Store the USB with the checksum and recovery pack.
Leave Secure Boot off so Rocky can return to the same NVIDIA environment.

Delete - I don't want to use this again

This permanently removes Ubuntu, Rocky Linux, DaVinci Resolve, their UEFI files, and their automatic mounts. Back up every Linux file before starting.

Protect Windows during cleanup

The deletion is irreversible. Compare every partition and EFI path with your recovery pack before committing a change.

Copy the multiboot recovery pack to external storage.
Copy every personal Linux file to external storage.
Boot Windows through Windows Boot Manager.
Open Fedora Media Writer from the Start menu.
Choose Custom image.
Select the checksum-verified Ubuntu 24.04 ISO.
Select the removable USB by its capacity and model.
Click Write to disk.

Wait for Fedora Media Writer to finish writing and checking the image. The verified Ubuntu USB provides the live tools for removing the Linux partitions.

Restart the Dell.
Press F12 at the Dell logo.
Boot the Ubuntu USB.
Choose Try Ubuntu.
Open GParted through the application search.
Select the approximately 1 TB internal NVMe SSD.
Compare the disk with your saved recovery map.

Queue only the three Linux labels created in this project. Leave the EFI, Windows, recovery, and OEM partitions untouched.

Queue UBUNTU for deletion.
Queue ROCKY_BOOT for deletion.
Queue ROCKY for deletion.
Confirm the pending list contains only those three deletions.
Apply the pending operations.
Wait for GParted to report completion.
Shut down the live session.
Remove the Ubuntu USB.

The former Linux region is now unallocated and immediately follows Windows. Windows can reclaim that adjacent space through Disk Management.

Start Windows.
Right-click Start.
Select Disk Management.
Confirm the unallocated region sits immediately after C:.
Right-click C:.
Select Extend Volume.
Use the full available amount.
Finish the wizard.

Disk Management will show C: using the reclaimed space. The EFI, recovery, and OEM partitions will retain their original sizes.

Press the Windows key to open search.
Type Command Prompt.
Select Run as administrator.
Back up the Windows boot configuration by running:

bcdedit /export C:\BCD-before-linux-cleanup.bak

List the full firmware entries by running:

bcdedit /enum firmware /v

Record the Ubuntu identifier: your Ubuntu firmware identifier.
Record the Rocky identifier: your Rocky firmware identifier.
Record Ubuntu’s full parent directory under Y:\EFI after removing the executable filename from its path field: your Ubuntu EFI directory path.
Record Rocky’s full parent directory under Y:\EFI after removing the executable filename from its path field: your Rocky EFI directory path.
Delete only the two recorded Linux firmware entries by running:

bcdedit /delete [[UBUNTU_BOOT_ID="your Ubuntu firmware identifier"]]
bcdedit /delete [[ROCKY_BOOT_ID="your Rocky firmware identifier"]]

List the firmware entries again by running:

bcdedit /enum firmware /v

You should still see Windows Boot Manager. Ubuntu and Rocky Linux should no longer appear.

The final cleanup touches the shared EFI partition. Delete only the two parent directories you recorded from the former Linux firmware paths.

Mount the EFI System Partition as Y: by running:

mountvol Y: /s

Review the EFI directories by running:

dir Y:\EFI

Confirm both recorded Linux directories exist under Y:\EFI.
Delete only those verified directories by running:

rmdir /s "[[UBUNTU_EFI_DIR="your Ubuntu EFI directory path"]]"
rmdir /s "[[ROCKY_EFI_DIR="your Rocky EFI directory path"]]"

Approve each directory deletion only after checking its path.
Unmount the EFI System Partition by running:

mountvol Y: /d

Re-enable Windows hibernation by running:

powercfg.exe /hibernate on

Restart the Dell.
Press F12 at the Dell logo.
Confirm Windows Boot Manager is the only project operating-system entry.
Start Windows.
Open File Explorer from the taskbar.
Right-click the removable USB after identifying it by capacity.
Select Format.
Start the format with the default capacity settings.

File Explorer should show the USB as empty removable storage. The next restart should offer Windows Boot Manager without Ubuntu or Rocky entries.

Cleanup verification failed?

Stop if Windows Boot Manager is missing or a recorded EFI path does not clearly belong to Ubuntu or Rocky Linux. Help me verify the cleanup before I make another change.

Nice Work!

You did it! Your Dell now boots Windows 11, Ubuntu 24.04, and Rocky Linux 8 from one SSD, with DaVinci Resolve running on the NVIDIA-powered Rocky environment.

You've learned how to:

Build and test a three-system UEFI multiboot SSD while preserving Windows recovery and OEM partitions.
Create a Resolve-ready Rocky workstation by updating Rocky 8, validating the NVIDIA driver, and opening a GPU-backed Resolve project.
Configure two-way Linux file access with filesystem UUIDs, automatic mounts, and read-write tests from Ubuntu and Rocky.
Complete the optional Secret Mission by building a recovery pack with the disk map, UUIDs, UEFI entries, mount tables, and first-response notes.

Ready to quiz yourself?