32 of the Most Infuriating Requests Submitted to IT Workers

If you’ve ever worked an IT help desk, you already know the truth: computers don’t ruin your daypeople do.
Not on purpose, usually. Most end users are just trying to get through their jobs without their laptop turning into a
sad little space heater that refuses to open a spreadsheet.

But some requests? Some requests feel like they were typed with oven mitts, sent from a fax machine, and approved by
a committee that hates joy. The “infuriating” part isn’t that users need helpthat’s literally the point of IT.
It’s the combination of missing details, unrealistic expectations, and “I clicked something… now everything is broken”
energy that turns a simple ticket into a full emotional journey.

Below are 32 of the most maddening (and extremely common) requests submitted to IT workersplus why they happen, what
they cost in time and sanity, and how both IT teams and end users can reduce the support-ticket chaos.

Why These Requests Hit a Nerve

IT teams don’t get annoyed because a problem exists. They get annoyed because the same problems repeat, often with the same
avoidable causes: unclear policies, confusing software prompts, old hardware that should’ve retired three budgets ago, and
training that consists of “good luck out there.”

Also, many requests arrive with one of the following classic ingredients:

• No context: “It’s not working.” (What is “it”? Where is “there”? When did “not” begin?)
• Impossible urgency: “This is critical.” Sent three weeks after the issue started.
• Expectation teleportation: “Can you fix this from your desk even though I’m offline?”
• Human mystery errors: “My keyboard types the wrong letters.” (Spoiler: caps lock, num lock, language settings… pick one.)

The 32 Most Infuriating IT Requests (With Real-World Context)

Category 1: Passwords, Access, and the Endless Loop of Login

1. “I forgot my password. Again.”
   Password resets are a huge share of many support queues, and the frustration comes from repetition. If your organization
   still relies heavily on passwords without a strong self-service option, the help desk becomes a full-time password concierge.
2. “My account is locked.”
   Usually caused by typing the wrong password multiple timesoften after someone confidently insists “I’m typing it right”
   while their keyboard is set to a different language layout.
3. “The system won’t accept my password, so I made it ‘Password123!’ and it still says no.”
   This is the moment IT workers age in real time. Password rules exist because attackers exist. Better guidance today tends to favor
   longer passphrases over short, “complex-looking” passwords that people reuse everywhere.
4. “Can you tell me what my password is?”
   No. And also: please stop asking. The safest systems don’t allow IT to view passwords. That’s not stubbornnessit’s design.
5. “My coworker needs access to my account while I’m out.”
   This is how security incidents are born. If someone needs access, it should be via proper permissionsnot sharing accounts like a streaming service.
6. “I’m not getting the sign-in code.”
   Multifactor authentication (MFA) is greatuntil the user changes phones, loses signal, or accidentally blocks the code number.
   The ticket becomes less “IT issue” and more “life logistics meets security.”
7. “I clicked ‘remember me’ and now it’s asking me to sign in again.”
   Cookies get cleared. Sessions expire. Security policies change. The “remember me” checkbox is not a legally binding contract.
8. “SSO is down so I can’t do anything. Fix it.”
   Single sign-on is convenientand when it breaks, it breaks loudly. One outage can knock out email, chat, HR systems, and half the company’s ability to function.

Category 2: Printers, Peripherals, and Devices That Choose Violence

9. “The printer isn’t printing.”
   The ticket may as well say “I have summoned you.” Offline printers, stuck queues, driver issues, wrong default printerthis is the four-horsemen combo.
10. “It says ‘paper jam’ but I don’t see paper.”
    Sometimes the jam is a tiny shredded corner hiding in a roller like it pays rent. Sometimes the sensor is dirty. Sometimes the printer is just emotionally tired.
11. “My computer doesn’t detect my monitor.”
    Nine times out of ten it’s the cable. The tenth time it’s still the cable, but now it’s on the other end.
12. “My webcam doesn’t work, and my meeting starts in two minutes.”
    This request is always urgent and always last-minute. Privacy shutters, missing permissions, driver updates, wrong camera selectedpick your culprit.
13. “My mouse/keyboard stopped working.”
    Batteries. It’s batteries. Sometimes it’s the USB receiver plugged into a docking station that’s plugged into a hub that’s plugged into a dream.
14. “My headset doesn’t have sound.”
    The device is muted, the wrong output is selected, the meeting app has its own audio settings, or the headset is paired to the user’s phonebecause of course it is.

Category 3: Wi-Fi, VPN, and “The Internet Is Broken”

15. “I can’t connect to Wi-Fi.”
    Is it the right network? Is airplane mode on? Did the password change? Are you in the parking garage trying to get a signal through concrete?
16. “The internet is down.”
    Translation: one website is slow, a browser tab froze, or someone unplugged a cable to charge their phone. (We need a support category called “Cord Crimes.”)
17. “VPN won’t connect.”
    VPN issues can come from outdated clients, expired certificates, blocked ports, conflicts with remote sessions, or MFA hiccups. Users experience it as “I clicked connect and nothing happened,”
    while IT sees a tangled ball of network policy and authentication.
18. “I’m traveling and everything is blocked.”
    Hotel Wi-Fi portals, region restrictions, corporate firewalls, and security rules collide. The user hears: “No.” IT hears: “We’re keeping you safe in a hostile network environment.”
19. “My video calls keep freezing.”
    Could be bandwidth, could be a congested network, could be the user streaming 4K video on the same connection. Diagnosing it remotely is like fixing a car over the phone while it’s still driving.
20. “The network drive is gone.”
    Often it’s mapped differently, permissions changed, the user is off-network, or the drive letter conflicts. The user experiences it as “my files disappeared,” which triggers maximum panic.

Category 4: Software, Updates, and “Can You Install This Random Thing?”

21. “Please install this software I found on the internet.”
    IT hears “please introduce unknown risk.” Good organizations have software catalogs, approval workflows, and application allowlists for a reason.
22. “I need admin rights.”
    Sometimes legitimate, often not. Admin rights can turn a small mistake into a company-wide incident. IT’s job is to enable work without enabling disaster.
23. “My computer is slow.”
    The most vague ticket in history. Causes range from low disk space to too many startup apps to 47 browser tabs doing interpretive dance in the background.
24. “This application suddenly stopped working.”
    “Suddenly” can mean “after the update I ignored for six weeks” or “after I changed settings I don’t remember changing.”
25. “My file won’t open.”
    Wrong file type, corrupted document, missing permissions, or the file lives in an email thread from 2014. The real request is: “Please do digital archaeology.”
26. “Can you recover something I deleted?”
    Sometimes possible, sometimes not, always urgent. The outcome depends on backups, retention policies, and whether the deletion happened five minutes ago or last quarter.

Category 5: Email, Calendars, and Collaboration App Chaos

27. “I’m not receiving emails.”
    Check junk folders, rules, blocked senders, mailbox quotas, and whether the sender typo’d the address. Also: yes, the “internet down” ticket sometimes becomes this one.
28. “My calendar invite disappeared.”
    Time zones, deleted invites, modified series meetings, permission changes, or syncing issues. The user feels gaslit by their own schedule.
29. “This link says I need access.”
    Sharing permissions are confusing. The user clicked a link, hit a wall, and decided the wall is IT’s fault. Sometimes it is! Often it’s the owner’s sharing settings.
30. “My chat app won’t load.”
    Cached data, client updates, SSO issues, or service outages. The frustration level is high because modern workplaces treat chat like oxygen.

Category 6: Security Scares, Suspicious Pop-Ups, and “Is This a Hack?”

31. “A pop-up says my computer is infected and I need to call a number.”
    This is a classic tech-support scam pattern. IT teams hate these tickets because the user is often one click away from handing control of their machine to a stranger.
32. “I clicked a link in an email and now I’m worried.”
    Reporting suspicious messages quickly is good. The issue is that people wait until they’ve clicked everything firstand then say “should I have clicked that?”
    (Answer: no. But thank you for reporting now.)

What These Tickets Really Reveal (And How to Reduce Them)

The best IT teams don’t just fix issuesthey remove the reasons issues happen repeatedly. That means treating support tickets like a feedback system, not just a to-do list.
Here are practical ways organizations reduce “infuriating request” volume without expecting everyone to become a tech wizard.

1) Make Self-Service Actually Useful

If a large chunk of tickets are predictable (password resets, unlocks, basic how-tos), build a self-service portal that’s easy to use and easier to find.
Add short articles with screenshots, not giant manuals. The goal isn’t to push users awayit’s to free IT staff for higher-value work.

2) Use Automation for the Boring, Repeatable Stuff

Chat-based assistants and virtual agents can handle routine requests: resetting passwords, guiding people through Wi-Fi setup, or collecting the right details before a human touches the ticket.
Automation works best when it reduces back-and-forth and forces the ticket to include basics like device type, error message, and what changed.

3) Improve Password and MFA Design

Modern security guidance generally emphasizes long passphrases people can remember, plus MFA to reduce account takeover risk.
When password rules are too complex, users create workarounds: writing them down, reusing them, or choosing predictable patterns.
The more user-friendly the security, the more likely people follow it.

4) Standardize Hardware (Especially Printers)

Printer pain is often a predictable result of mixed models, inconsistent drivers, and unclear “who owns what” responsibility.
Consolidate models where possible, standardize drivers, and document the “first five steps” users should try (power cycle, check the queue, confirm default printer, verify connection, retry).

5) Create Better Ticket Forms (So IT Isn’t Guessing)

A ticket that says “doesn’t work” should bounce back automatically with questions:
What device? What app? What error message? When did it start? What changed?
This isn’t bureaucracyit’s triage. Clear intake saves time for everyone, including the person who wants the problem fixed fast.

500+ Words of Real-World Experiences (Composite Help Desk Moments)

IT workers swap stories the way chefs talk about dinner rushes: half coping mechanism, half professional pride. The details below are composite scenarios
the kind of “I can’t believe this happened” moments that show up across service desks everywhere.

The Phantom Printer: A user submits an urgent ticket: “Printer is broken. Need it for a client meeting.” IT checks the print servereverything looks normal.
They remote in, restart the spooler, reinstall the driver, and send a test page. Nothing. Then the user casually adds, “Also, I moved it this morning.”
Turns out the printer is now plugged into a power strip that’s switched off. The fix takes two seconds, but the ticket already consumed twenty minutes of advanced troubleshooting.
IT closes the request with a polite note and silently adds “power strip check” to the mental checklist… again.

The Keyboard That Betrayed Them: Someone insists their laptop “randomly started typing numbers.”
They’re convinced it’s malware. They’re worried about “hackers.” IT arrives and notices the user’s external keyboard has the numeric keypad enabled, and the cursor is stuck
because the mouse is sitting on a sticky note like it’s sunbathing. The resolution is simple, but the bigger lesson is familiar: people blame invisible villains
because they don’t realize one tiny setting can change everything.

The Two-Minute Meeting Miracle: A message comes in at 9:58 a.m.: “My webcam doesn’t work. I present at 10.”
The user didn’t test it yesterday. Or last week. Or ever. IT asks what changed. “Nothing. It just stopped.” After some quick checks, IT finds the privacy shutter closed.
The user says, “Oh! I didn’t know that was there.” IT fixes it, the user joins the meeting, and everyone moves onexcept IT, who adds “camera shutter” to the growing list of
reasons they drink water and stare at walls after work.

The ‘Fix It From Here’ Paradox: A remote worker submits: “VPN broken. Can you remote in and fix it?”
IT explains that remote access depends on network access. The user replies, “But I can’t access the network.” It’s a classic catch-22:
the user expects IT to “just connect,” like magic. The eventual solution is usually something basican expired password, an MFA change, a client update
but getting there requires phone troubleshooting, patience, and the gentle art of guiding someone to read an error message out loud without skipping the important part.

The Pop-Up Panic: A user reports a scary alert claiming their computer is infected and demanding they call a number immediately.
They almost do. IT praises them for stopping and reporting, then walks them through closing the browser tab and checking for anything suspicious.
The user admits they clicked “Allow notifications” earlier because a website asked them to. IT removes the browser permission, clears the notifications,
and reminds them: legitimate warnings don’t demand gift cards, remote access, or urgent phone calls from random pop-ups. The “infuriating” part isn’t the mistake
it’s how aggressively scammers target everyday users, forcing IT to be both technician and digital safety coach.

In the end, these stories aren’t just funny (or exhausting). They show the real work of IT: translating technology into human-friendly steps, building guardrails,
and keeping businesses moving even when the request arrives as a single sentence with three exclamation points.

Wrapping It Up: The Goal Isn’t Fewer PeopleIt’s Fewer Fires

“Infuriating” tickets usually point to fixable systems problems: unclear processes, confusing tools, inconsistent device setups, and security practices that
unintentionally push users into bad habits. When you improve the environmentself-service, automation, modern authentication, better hardware standards, clearer training
the help desk becomes less of a panic hotline and more of a productivity engine.

And for end users everywhere: IT is not judging you for needing help. They’re judging you for submitting “urgent” tickets without screenshots.
(Kidding. Mostly.)