What Switchboard Checks Before Recommending Linux in Kirksville

A Kirksville computer should not be moved to Linux simply because Windows has become annoying.

The useful local service decision is more mechanical:

Is the computer healthy, does the owner's real workflow fit Linux, and is migration better than repairing or replacing the existing Windows setup?

That requires an assessment, not a sales pitch.

First: is the hardware itself healthy?

Before discussing operating systems, check the machine.

Look at:

• storage health;
• RAM stability and capacity;
• battery condition on laptops;
• cooling;
• obvious physical damage;
• network reliability;
• age and upgradeability.

Linux is not a repair for failing hardware.

A dying SSD remains a dying SSD after installation.

Second: what is Windows actually objecting to?

Windows 10 standard support ended in October 2025.

Microsoft currently provides a temporary Consumer Extended Security Updates path for eligible Windows 10 systems, but that does not restore ordinary full support indefinitely.

Windows 11 also has hardware requirements involving CPU support, TPM 2.0, UEFI/Secure Boot capability, memory and storage.

A machine can therefore be physically healthy while falling outside Microsoft's supported Windows 11 path.

That is different from a computer being worn out.

Third: inventory the real software

Ask what the owner actually uses.

Not what is installed.

Not what came with the computer.

Actual tasks might include:

• browser and email;
• Microsoft 365;
• accounting;
• photo editing;
• games;
• school software;
• VPN tools;
• specialty business applications.

Classify each dependency as:

• available natively;
• browser-based;
• replaceable;
• testable through compatibility software;
• remotely accessible;
• Windows-required.

One Windows-only application can matter more than twenty compatible ones.

Fourth: inventory peripherals

List the exact:

• printer;
• scanner;
• webcam;
• Bluetooth devices;
• external displays;
• docks;
• specialty USB hardware.

Printer and scanner support should be checked by model, not brand.

A multifunction device may print while a required scanning function does not work.

Fifth: test Linux before erasing anything

Boot a current live Linux environment.

Test:

• Wi-Fi;
• Ethernet;
• audio;
• microphone;
• webcam;
• displays;
• suspend/resume;
• Bluetooth;
• external storage;
• required peripherals where feasible.

Then perform a normal sample workflow.

A machine that merely reaches a Linux desktop has not passed.

Sixth: back up before deciding

The migration decision should never depend on "I think everything important is in the cloud."

Verify the data.

Back up documents, photos, browser data and any local application files that matter.

Confirm the backup can actually be read.

The result can be "stay on Windows"

A good assessment has more than one acceptable answer.

Possible outcomes include:

• repair the existing Windows installation;
• use the temporary supported Windows path;
• upgrade hardware;
• replace the computer;
• dual boot;
• migrate fully to Linux;
• keep Windows because one critical workflow requires it.

Recommending Linux when it is the wrong fit is not a successful Linux service.

Local service value is in the decision process

The useful distinction for Switchboard is not "Linux is better."

It is the ability to put a specific Kirksville computer and a specific owner's workflow through a repeatable decision process.

If the hardware is healthy, the workflow fits and the live test passes, Linux can be a sensible outcome.

If one of those fails, the recommendation should change with the evidence.