When dual-boot is the right call
Dual-boot is ideal when one app still needs Windows (school lockdown browser quirks, a specific printer tool, a game with no good port) but you want Linux for daily browsing and lighter development. It is a bad call when the disk is tiny, already failing, or you do not have a backup. It is also a bad call if you hate boot menus - you will see one.
Full Linux-only installs are simpler long-term. Dual-boot is a bridge. Treat it with respect.
Prepare Windows first
- Update Windows and reboot until it stops demanding restarts.
- Disable BitLocker or suspend it and keep recovery keys offline if the drive is encrypted - resizing encrypted volumes without a plan locks people out.
- In Disk Management, shrink the Windows volume to free contiguous space (40 GB minimum for comfort; 80+ GB better).
- Turn off Fast Startup so Windows releases the disk cleanly.
- Unplug extra disks and backup drives you do not want as install targets.
If shrink fails because of immovable files, that is a Windows problem to solve first (or a shop imaging job), not a reason to force the Linux installer to guess.
Installer choices that matter
Choose “Install alongside Windows” only when the screen clearly shows Windows detected and free space. If you see “Erase disk,” stop - that option removes Windows. Something went wrong with detection or you selected the wrong drive.
If the installer offers manual partitioning and you are not comfortable with EFI system partitions, swap, and root volumes, do not invent a layout from a forum post at 1 a.m. Use the guided path or book help. Broken EFI partitions are how both systems refuse to boot.
After install: boot menu and updates
You should get a boot menu (often GRUB) offering Linux and Windows. If the machine boots straight to one OS, firmware boot order or EFI entries need a tweak - common and fixable. Update Linux fully, then reboot into Windows once to confirm it still starts. Keep both systems updated; do not ignore Windows Update for six months and blame Linux when the bootloader gets confused after a major Windows feature update.
Windows feature updates sometimes rearrange boot order. Knowing how to enter firmware boot menus keeps panic low. Write the steps for your model on a sticky note in the laptop sleeve.
When to stop DIY
When the stack exceeds DIY - drive failures, dual-boot disasters, locked accounts, or a machine that must be online for work tomorrow - contact CCPCREPAIR in Tahlequah. We do diagnostics with a flat quote after we know what is wrong. Call 918-228-5889 or use the form.
← Linux is easy series · All guides · Book a diagnosticField notes from the shop
At CCPCREPAIR in Tahlequah we see the same pattern repeatedly: people succeed with Linux when they slow down for backups, pick a mainstream distro, and treat the first week as landing the plane - updates, browser, printer - before theming and experimental drivers. They fail when they skip the backup, click through erase-disk options, or paste sudo commands they cannot explain.
Keep a live USB of the same distro in a drawer. It is a recovery tool as much as an installer. When something will not boot, the live session is how you copy files off and read logs without making the problem worse. That habit alone separates calm operators from emergency tickets.
If you share a machine with family, write a one-page note: distro name, username model (not the password), whether the disk is encrypted, and where the backups live. Future you - or a technician - will move faster with that sheet than with a vague memory of a YouTube video from three months ago.
Continue the series in order when you can, but jump ahead if you already know the topic. Every page ends with abort criteria and a path to contact the shop when risk climbs. Linux is easy when honesty about hardware and data comes first.