Remote IT support fixes a surprisingly wide range of problems. A technician can remove malware, reconfigure a router, repair broken software, recover files, and diagnose performance issues, all without leaving their desk. But the model has real limits. Some faults require physical access to the hardware, and booking a remote session for one of them wastes everyone's time. Knowing those limits upfront helps you choose the right kind of help from the start.
What remote support handles well
Most software-layer problems are fair game. That includes operating system errors, failed updates, driver conflicts, email clients that won't open, and browsers that crash repeatedly. Connectivity issues, like a device that can't reach the internet or a VPN that refuses to connect, are also well within scope. So are account lockouts, permission errors, and cloud-sync failures.
Performance problems are worth mentioning specifically. A remote technician can identify processes hogging CPU, clear junk files, adjust startup programs, and tune power settings. Those steps fix slow machines more often than people expect. If you're unsure whether your problem falls into this category, the article on common computer problems that can be fixed remotely gives a solid overview of what's typically in scope.
The hard limits: what genuinely can't be done remotely
Physical hardware failure is the clearest boundary. If a component has failed, a technician can't replace it through a screen-sharing session. Here are the specific situations where remote support hits a wall.
The computer won't turn on
A machine that won't boot at all can't be accessed remotely. There's nothing for the technician to connect to. The fault might be a dead power supply, a failed motherboard, a loose RAM stick, or a depleted CMOS battery. All of those require hands-on inspection. Take the machine to a repair technician, or arrange an on-site visit.
Display and screen damage
A cracked screen, a backlight that's failed, or display output that simply doesn't work can't be diagnosed or fixed remotely. The technician needs to see the display, test it with an external monitor, and potentially replace the panel. This is especially common with laptops after a drop.
Keyboard, trackpad, and port failures
If the keyboard isn't registering keystrokes or the trackpad has stopped responding, a remote session is a non-starter. The technician can't type commands or navigate the system to fix anything. External USB keyboards sometimes work around the problem temporarily, but the underlying fault still needs physical repair.
Clicking or grinding hard drives
A drive making clicking or grinding noises is failing mechanically. No software fix stops that, and running the drive longer risks total data loss. The right move is to power the machine off, avoid further reads and writes, and get the drive to a data recovery specialist. A remote session at that point could make things worse by spinning the drive further. This is exactly the scenario covered in the guide on what to do when your hard drive starts making clicking noises.
Liquid damage
Water or liquid inside a laptop requires immediate physical intervention: power off, disconnect, dry, and inspect for corrosion. A remote technician can offer advice over the phone, but they can't assess the damage or clean the board. If the machine does power on after a liquid incident, don't assume it's fine. Corrosion develops over days and can cause secondary failures weeks later.
Battery replacement
A battery that no longer holds charge, or one that swells, needs to be physically replaced. Software can confirm the battery's health status, but the fix itself is a hardware job. On most modern laptops the battery is glued or screwed in, requiring tools and sometimes heat guns to remove safely.
The grey area: when remote might partially help
Some situations sit between purely software and purely hardware. A Windows boot loop, for example, might be caused by a corrupted update (fixable remotely using recovery tools) or by a failing SSD (not fixable remotely, but diagnosable). A remote technician can often run diagnostics to tell you which category applies, even if the fix itself requires someone on-site.
Printer problems are similar. Driver issues and queue errors are remote-fixable. A paper jam, a clogged print head, or a broken feed roller are not. A technician can confirm which one you're dealing with before you book the wrong kind of support.
What to do when remote support isn't enough
If the fault is physical, you have two options: take the machine to a repair shop, or book an on-site technician. The right choice depends on how portable the machine is and how urgently you need it back. Desktop towers are awkward to transport; laptops are easier. For small businesses, an on-site visit often makes more sense because the technician can inspect the full setup, not just the one failing machine.
Before either option, do two things. First, back up any data you can access. Even a partial backup beats none. Second, write down the specific symptoms: what the machine does, what error messages appear, and when the problem started. That information cuts diagnostic time regardless of who handles the repair.
Remote IT support solves most problems quickly and cheaply. It's the right first call in the majority of cases. But recognising a hardware fault early, rather than spending an hour on a remote session that can't resolve it, gets you to the right fix faster.