Convert a Windows Laptop to elementary OS: Driver Checklist
Replacing Windows with elementary OS can give an older laptop a cleaner interface, fewer background processes, and a focused Linux desktop. The installation itself is usually straightforward, but hardware support deserves careful preparation. A laptop that works perfectly in Windows may depend on proprietary drivers, vendor utilities, or firmware that elementary OS cannot use in the same way.
A driver checklist helps you identify possible problems before changing partitions. It also gives you a practical record of your current hardware, which is useful when searching for Linux compatibility reports or asking for help in the elementary OS community. The goal is not to collect every possible driver manually, but to verify that each important device has a Linux-compatible path.
elementary OS generally benefits from the broad hardware support provided by the Linux kernel and its Ubuntu-based foundations. Still, laptops vary widely. Wireless chipsets, graphics hardware, fingerprint readers, touchscreen controllers, and unusual function keys can require extra attention. A few tests before installation can prevent a frustrating first boot.
Start with a hardware inventory
Before creating an installer, record the laptop’s exact model number and, if possible, its submodel or product code. Manufacturers often sell several machines under one family name, with different Wi-Fi cards, processors, displays, and graphics chips. The information may appear on a label underneath the laptop, in Windows System Information, or in the firmware setup screen.
In Windows, open Device Manager and expand categories such as Display adapters, Network adapters, Bluetooth, Sound, Cameras, and Biometric devices. Save the names of the components or take screenshots. Pay special attention to wireless hardware because a laptop can appear fully compatible while using a Wi-Fi chipset with limited Linux support.
Also record features you actually use. Make a short list of the webcam, microphone, HDMI or USB-C display output, SD card reader, touchscreen, stylus, fingerprint sensor, keyboard shortcuts, sleep mode, and battery charging behavior. A device that appears under Device Manager is not automatically a problem, but knowing what must work helps you test elementary OS methodically.
Prepare firmware, storage, and installation media
Back up personal files before changing the operating system. Copy documents, photographs, browser exports, password-manager backups, and license information to an external drive or trusted cloud service. If the Windows installation may need to be restored later, create Windows recovery media as well. Do not assume that a separate recovery partition is a sufficient backup.
Windows laptops normally use UEFI firmware and a GPT partition layout. Keep the installation method consistent: boot the elementary OS installer in UEFI mode rather than mixing legacy BIOS and UEFI modes. In the firmware menu, check the boot order, confirm that the internal drive is detected, and note whether Secure Boot is enabled. Elementary OS installation support can vary by release and device, so consult the current release documentation if the installer does not boot normally.
Fast Startup in Windows can leave NTFS partitions in a hibernated state. Disable it before attempting to access a Windows partition from Linux, especially if you plan to keep Windows in a dual-boot arrangement. BitLocker encryption also deserves attention: save the recovery key and understand that changing boot settings or partitions can trigger a recovery prompt.
Use a reliable USB drive and verify the elementary OS image before writing it. A damaged download or failing USB stick can look like a driver problem when the actual issue is corrupted installation media. Test the live environment first. Running elementary OS from USB lets you check many devices without committing to a disk change.
Check the drivers that matter most
The live session is the best part of the driver checklist because it exposes hardware support before installation. Connect to Wi-Fi, play audio, open the webcam application, adjust screen brightness, plug in headphones, and test several USB ports. If you have an external monitor, connect it through the port you normally use rather than assuming every display output behaves identically.
Graphics support deserves special care. Intel integrated graphics and most AMD integrated graphics usually work with open-source kernel drivers, while newer or high-performance NVIDIA GPUs may need proprietary driver support for the best performance. A laptop with hybrid graphics can be more complicated because it switches between an integrated GPU and a dedicated GPU. Test display output, suspend, video playback, and application performance before deciding that everything is ready.
The following checklist separates common hardware areas from the signs you should look for during the live session and after installation.
| Hardware area | What to test | Possible warning signs | Useful preparation |
|---|---|---|---|
| Wi-Fi | Connect to a network, reconnect after disabling Wi-Fi, test different bands | Adapter missing, unstable connection, no networks shown | Record the chipset and keep a USB Ethernet or Wi-Fi option available |
| Bluetooth | Pair headphones, mouse, or phone and reconnect them | Device cannot be discovered or audio drops | Test both pairing and automatic reconnection |
| Graphics | Change resolution, connect an external display, play video | Black screen, wrong resolution, flicker, poor performance | Identify Intel, AMD, NVIDIA, or hybrid graphics |
| Audio | Test speakers, microphone, headphones, and volume keys | No output, muted microphone, incorrect device selected | Record the laptop’s audio device and port behavior |
| Touchpad and keyboard | Use gestures, scrolling, function keys, and brightness controls | Erratic pointer, missing gestures, unusable shortcuts | Check firmware options for touchpad modes and hotkey settings |
| Webcam | Open a camera application and test video and microphone | Black image, camera not detected, privacy switch inactive | Check physical shutters and hardware camera toggles |
| Power management | Suspend, resume, charge, unplug, and observe battery use | Failure to wake, overheating, rapid battery drain | Update firmware where appropriate and test sleep before daily use |
| Special hardware | Try fingerprint reader, touchscreen, stylus, card reader, and sensors | Device is visible but has no supported Linux workflow | Decide whether the feature is essential or optional |
If Wi-Fi does not work in the live session, do not immediately assume the installation has failed. Some chipsets require additional firmware packages, and a wired connection or phone USB tethering can provide temporary internet access. Downloading random driver files from a manufacturer’s Windows support page will not solve a Linux driver issue; Linux drivers are normally supplied through the kernel, firmware packages, or distribution repositories.
Verify input, sound, and connectivity
Touchpads often work immediately, but precision varies by model. Test two-finger scrolling, tapping, right-clicking, palm rejection, and the physical click mechanism. Convertible laptops may expose a touchscreen or tablet mode that needs separate testing. If the touchpad behaves poorly in the live session, try an external mouse and record the issue rather than assuming a post-install update will fix it.
Keyboard behavior is equally important on a laptop. Check brightness, volume, microphone mute, airplane mode, keyboard backlight, and display switching keys. Some manufacturer-specific shortcuts depend on firmware interfaces that are not fully supported in Linux. Basic typing should work even when a special key does not, so distinguish between an essential input problem and a missing convenience feature.
Audio can fail in subtle ways. Test the internal speakers, the headphone jack, Bluetooth audio, and the built-in microphone. Open the sound settings and confirm that the expected input and output devices appear. HDMI and USB-C monitors may expose their own audio outputs, so check them separately if you use a docking station or external display.
For wireless troubleshooting, identify the chipset rather than relying only on the laptop brand. Intel wireless adapters are commonly well supported, while some Realtek and MediaTek variants can differ considerably between models. A USB Ethernet adapter is useful during setup, but it should be treated as a fallback rather than proof that the internal adapter will work.
Handle graphics, power, and special hardware
A laptop may boot successfully and still have poor battery life, broken suspend, or excessive heat. After installation, let the system run on battery for a while and test closing and opening the lid. Verify that the screen turns off, the laptop resumes reliably, and the fan does not remain active without a clear reason. Suspend problems can be connected to graphics drivers, firmware, USB devices, or hybrid-GPU configuration.
Firmware updates can improve compatibility, especially for power management, USB-C docks, and newer processors. Check the manufacturer’s Linux or firmware guidance before using a vendor update tool. Some manufacturers provide firmware updates through standard Linux firmware services, while others require a Windows utility or a bootable update image. Keep the recovery key and backups available before changing firmware.
Fingerprint readers and facial recognition deserve realistic expectations. A fingerprint sensor may be physically detected but lack a supported Linux authentication process. The same applies to vendor-specific privacy switches, accelerometers, ambient-light sensors, and proprietary hotkey daemons. Decide which features are essential before installation. If fingerprint login is optional, a strong password and automatic screen locking may be a practical alternative.
For NVIDIA hardware, avoid judging performance from the live USB alone. The live environment may use a basic graphics mode and may not represent the final result after the appropriate driver is installed. On hybrid laptops, test whether the external display is connected to the integrated or dedicated GPU, since the physical port can affect driver behavior.
Test devices after the first boot
Once elementary OS is installed, apply available system updates before diagnosing missing devices. Updates may include kernel changes, firmware packages, graphics improvements, and fixes for laptop-specific behavior. Restart after updates, then repeat the hardware tests from the live session. This gives you a clear comparison between “works in the installer” and “works in the installed system.”
Check the wireless connection after several restarts and from different locations. Pair Bluetooth devices again, test audio input and output, open the webcam, adjust brightness, and connect an external monitor. If a device is missing, inspect the system settings and hardware information before searching for a driver. The exact chipset name is far more useful than a general search for “laptop model Linux driver.”
Applications can also expose hardware issues. Try a browser video call to test the webcam and microphone together, play a local video, connect a removable drive, and print a test page if you rely on a printer. Network printers may require their own setup, while USB printers are often easier to detect. A printer that works in Windows through a manufacturer utility may need a standard Linux printing protocol instead.
For productivity, learn how display workspaces and multitasking behave once the hardware is stable. The multitasking view guide can help you organize open applications while you evaluate the new desktop. This is especially useful on smaller laptop screens where efficient window management matters as much as raw driver support.
Keep a fallback and document the result
Do not erase the Windows installation until you have tested the functions that matter for work, study, or travel. A temporary dual-boot setup, a second drive, or a complete disk image can provide a safety net. If you choose a clean installation immediately, keep the Windows recovery media and exported hardware information somewhere accessible.
Document what works and what does not. Write down the elementary OS release, kernel version, laptop model, wireless chipset, graphics hardware, and any error messages. Save commands or configuration changes that solve a problem, but avoid copying unsupported fixes from unrelated hardware. Community forums are much easier to use when a report includes specific hardware details and clear test results.
A good migration checklist should also include routine maintenance. Keep enough free disk space for updates, install software from trusted sources, and avoid replacing core system packages with unofficial driver bundles. When a future update changes behavior, your original notes will show whether the issue is new or was present from the first boot.
Practical checks before daily use
Use these final checks to decide whether the laptop is ready to become your primary elementary OS machine:
- Confirm that Wi-Fi, Bluetooth, speakers, microphone, webcam, touchpad, keyboard, and charging work after a restart.
- Test suspend and resume several times, including with an external monitor or USB device connected.
- Verify screen brightness, display resolution, HDMI or USB-C output, and graphics performance.
- Check essential special hardware, such as a fingerprint reader, touchscreen, stylus, card reader, or privacy switch.
- Keep backups, recovery media, firmware details, and a record of known limitations.
A Windows laptop does not need a manufacturer-provided Linux driver package for every component to work well with elementary OS. Most support comes from the Linux kernel, firmware, open-source graphics stack, and distribution updates. The important task is to identify exceptions before installation and to test them under realistic conditions afterward.
Once the checklist is complete, use the laptop for ordinary tasks for several days before deleting any fallback system. Browse on battery, attend a video call, connect your usual accessories, suspend it overnight, and test the workflows that matter most. That practical trial turns a promising live session into a dependable elementary OS setup.