Device and power
- Power and visible indicators
- Loose or disconnected cables
- Expected keyboard, mouse, headset, or device
Safe first checks · IT support knowledge
Windows checks before contacting IT support
Identify the failed task, protect your work, record useful symptoms, and know when to stop. These checks are reversible and require no administrator access.
Do not continue when risk or authority is unclear
Contact the approved support or security channel when the device may be unsafe, files appear damaged or encrypted, an unexpected prompt requests a password, payment, remote access, or security code, or the next action needs administrator access.
- Do not open equipment, change firmware, bypass security, or use an administrator account.
- Do not call a telephone number displayed in an alarming pop-up.
- Do not share sensitive organizational information when you are unsure what is permitted.
If an unexpected pop-up, caller, or message asks for remote access, credentials, a security code, or payment, follow the suspicious tech-support contact safety guide.
Eight safe preparation steps
Work from the visible symptom toward a concise record. Do not change protected settings or assume the cause.
Describe the task that failed
Record what you tried to do, the application or device involved, the expected result, what happened instead, when it started, and whether another person or device is affected.
At 09:20, I tried to print a two-page PDF. The document stayed in the queue. Printing worked yesterday, and another user can print to the same device.
Protect open work
Save responsive documents, note open files and applications, and avoid forcing a shutdown during a save or update. If an application is frozen, record its name and your last completed action.
Check visible conditions
Confirm power, expected connections, device indicators, the Windows network status, available storage, and the exact application or browser tab affected. Do not open hardware or reconnect damaged components. If Windows reports low storage, use the safe Windows storage checks before deleting anything. If Wi-Fi is connected but internet tasks fail, follow the safe connectivity checks before changing network settings.
Consider a normal restart
If work is saved, the device responds, and local policy permits it, use Start → Power → Restart. Repeat the original safe task once and record whether the result changes.
Record recent changes
Note updates, restarts, power interruptions, new applications or peripherals, account changes, relocation, or no known change. Timing is evidence to investigate, not proof of cause.
Capture information safely
Record the exact error wording. Review screenshots before sharing and remove passwords, security codes, private messages, confidential content, and unnecessary identifiers.
Classify the symptom area
Choose the closest task area—startup, application, network, printing, peripheral, or performance—without treating the label as a final diagnosis.
Prepare the support request
Summarize the task and impact, timing, exact symptom, recent changes, and checks completed. Use only the organization’s approved support channel.
Useful observations, not repairs
These comparisons help narrow the scope while keeping the final diagnosis open.
Network
- Windows network indicator
- Secure Ethernet connection
- Another permitted service or device
Application or website
- Exact application or browser tab
- One safe file versus every permitted file
- Full message before dismissal
Privacy
- No passwords or security codes
- No unnecessary private content
- Approved support channel only
Classify the visible symptom
Use the closest description to route the request. This is not a root-cause diagnosis.
| Symptom area | Useful observation |
|---|---|
| Startup or sign-in | Where the process stops and the exact message shown. |
| One application | Application name, affected task, and whether another safe file works. |
| Network or website | Network indicator, affected service, and whether another approved service works. |
| Printing | Printer selected, queue state, and whether another user is affected. |
| Sound or peripheral | Device connection, visible state, and whether Windows detects it. |
| Performance | Slow task, time first noticed, and whether the slowdown is constant. |
Build a useful support request
Keep it concise, factual, and free of passwords or unrelated personal information.
Task and impact
What cannot be completed, and who or what work is affected?
Time and frequency
When did it start, and is it constant or intermittent?
Exact symptom
What appears on screen or on the device after private information is removed?
Recent change
What changed shortly before the issue, or is there no known change?
Checks completed
What did you actually check, and what was the result?
Availability
How can approved support reach you, and when can the device be examined?
Privacy check: Never send a password in a ticket, email, chat, or screenshot. Share only what the approved support process requires.
Continue with the right resource
Use the printable intake record, review the technician’s method, or discuss an appropriate IT support opportunity.
General preparation guidance only. Organizational policy, authorized support, security-response procedures, and manufacturer instructions take priority.