If the Windows Settings app feels like a maze, you're not alone. For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.6, you're expected to move through it quickly and explain what each control changes. That skill matters on the exam, and it also shows up in day-to-day support work.
This part focuses on five Settings areas you'll use most often: System, Devices, Network and Internet, Gaming, and Accounts. Each section ties settings to real outcomes, such as display and power behavior, printer and Bluetooth issues, Wi-Fi and VPN problems, game overlays that interfere with apps, and sign-in choices that affect access.
By the end, you'll know where to find each setting, what it does, and when to use it for troubleshooting. You'll also learn common "symptom to setting" links, so you can act fast when a user reports slow performance, missing devices, dropped connections, or login errors.
System Settings Fixes
In CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.6, you need to know which System settings address common user complaints. In practice, these same controls often resolve "slow and blurry" reports without touching drivers or reinstalling apps. Start here because Settings changes are reversible, quick to test, and easy to document.
Display, Night light, and scaling, when text is too small or blurry
Blurry text and awkward sizing usually come from mixing up resolution and scaling. Think of resolution as how many pixels the screen can show, and scaling as how big Windows draws text and buttons on those pixels. If the resolution is wrong, the image can look soft because the monitor has to stretch it. If scaling is wrong, text may look huge, tiny, or slightly fuzzy in older apps.
First, confirm the basics in Settings > System > Display. Set Display resolution to the monitor's recommended value when possible. Next, adjust Scale to a comfortable level (common values are 100%, 125%, or 150%). As a quick rule, keep the resolution at the recommended setting, then use scaling for readability. Changing both at once makes results harder to judge.
Multi-monitor setups add another layer. Windows can apply different scaling per screen, which is helpful, but it can also create "one screen looks right, the other looks wrong" situations. In Display settings, use these steps to reduce confusion:
- Select Identify to label monitors with numbers.
- Drag the monitor boxes to rearrange them so the layout matches the desk.
- Choose the primary screen and select Make this my main display (this controls where the taskbar and sign-in prompts prefer to appear).
Night light is another common surprise. It shifts colors warmer to reduce blue light, which can help at night. However, it can be a problem for photo work, color checks, and some display tests. If whites look yellow or colors seem "off," turn Night light off and recheck the issue.
If a user reports "flicker" instead of blur, check Advanced display at a high level. A mismatched refresh rate can cause visible flicker on some panels.
Power and sleep settings that stop random shutdowns and battery drain
Power complaints often sound dramatic ("it shuts off randomly"), yet the cause is sometimes a normal timeout. Screen timeout only turns off the display, while sleep pauses the system state to save power. In other words, a black screen might be a display timeout, not a shutdown. Because of that, always confirm the exact symptom: does the PC power off, go to sleep, or only blank the screen?
Open Settings > System > Power & battery (or Power & sleep on some versions). Check the timers for Screen and Sleep on both battery and plugged-in modes. On laptops, short sleep timers can look like instability, especially during reading or meetings. Increase the sleep timer for testing, then adjust to policy later.
Laptop lid behavior also matters. Many "random shutdown" reports are really lid close actions. In Control Panel > Power Options > Choose what closing the lid does, set expectations clearly:
- Sleep: Saves battery and resumes quickly, but some devices fail to wake due to driver or firmware issues.
- Hibernate: Saves more power and is more stable for travel, but resume takes longer.
- Do nothing: Useful on docks or external monitors, but it can overheat a bagged laptop if users forget.
If a device won't wake, treat it as a clue, not a mystery. Fast checks help before deeper work: confirm the power button works, test with AC power, unplug external USB devices, and try an external keyboard or mouse. Also confirm the user did not enable an aggressive power plan that sleeps too quickly.
Battery tools can reduce drain without changing hardware. Battery saver limits background activity and dims the display, which often fixes "battery drops fast overnight" complaints when an app keeps running. Also review Power mode (Best power efficiency, Balanced, Best performance). On a laptop, selecting Best performance can increase heat and drain, so use it only when needed.
When troubleshooting, change one power setting at a time. Otherwise, you won't know which adjustment fixed the behavior.
Storage and temporary files, freeing space the safe way
Low disk space causes more than "can't save a file." Windows updates may slow down, apps may crash, and the system can feel sluggish because it has less room for caches and temporary work files. Before you delete anything, confirm what is actually consuming space.
Go to Settings > System > Storage to see a clear breakdown by category (such as Apps, System, Temporary files, Desktop, Documents, and Downloads). This view helps you avoid guesswork. For example, a large Apps category points to installed programs and games, while a large System category may reflect update files, restore points, or reserved storage.
Windows can clean safely when you use built-in tools. Storage Sense automatically removes temporary items and manages recycle bin content on a schedule. Turn it on when a user repeatedly runs out of space, then set a reasonable cadence (weekly works well for many PCs). Storage Sense focuses on low-risk items, yet it still deserves a careful first run so you understand what it will remove.
The Temporary files section is the manual option. It often includes cache files, old update remnants, and app temp data. These are usually safe to remove, especially when troubleshooting update failures. Still, two areas require extra care:
- Downloads: Users often treat it like a filing cabinet, even though it is meant as a drop zone.
- Recycle Bin: It may contain files the user expects to restore.
Review those categories before deleting. A quick scan avoids accidental data loss and saves time later. After cleanup, restart the PC and try the failed update or the crashing app again. If the system stabilizes, document how much space you freed and which categories were cleared.
About and Remote Desktop, what to check before you escalate
Before you escalate a case, capture the key facts from Settings > System > About. This page answers the "what am I working on?" questions that drive correct choices for drivers, updates, and app versions. It also reduces back-and-forth with a senior tech because you provide a baseline upfront.
Focus on these items:
- Device name: Helps identify the correct PC in management tools and on the network.
- Processor (CPU): Guides performance expectations and compatibility for some software.
- Installed RAM: Explains slowdowns when users run many browser tabs or VMs.
- Windows edition: Important for feature support, including Remote Desktop hosting.
- System type (32-bit vs 64-bit): Critical for choosing the right app installer and some drivers.
That last point prevents a common mistake. A 64-bit system can run many 32-bit apps, but a 32-bit system cannot run 64-bit apps. If an installer fails with a vague message, system type is often the reason.
Remote access issues also benefit from quick checks. Remote Desktop requires the right Windows edition on the host PC, and it must be enabled in Settings > System > Remote Desktop. After you enable it, confirm three practical items before blaming the network:
- Network reachability: The client must be able to reach the host (same network, VPN, or approved route).
- User permissions: The user must be allowed to sign in via Remote Desktop (local admins work by default, others may need to be added).
- Device awake: Sleep settings can block access if the host sleeps and does not support wake reliably.
When these basics check out, you have strong notes for escalation, including edition, system type, and whether Remote Desktop was enabled and tested.
Peripheral Settings
For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.6, you need to know how Windows Devices settings affect real hardware. In support work, this is where small toggles fix big frustrations, a headset that "connects" but stays silent, a printer that "prints" but never outputs paper, or a touchpad that makes the cursor jump. The goal is simple: confirm Windows sees the device, confirm it uses the right mode, then reset the connection path when symptoms persist.
Bluetooth and pairing mode, why devices connect but do not work
Bluetooth problems often start with a misunderstanding: pairing is the long-term trust step, while connecting is the moment-to-moment link. Pairing creates saved keys, so Windows remembers the device. Connecting uses that relationship to pass audio, input, or data. Because of this, a device can show as "Connected" but still fail at its actual job.
Discoverable mode matters first. Many devices only broadcast their identity for a short time (often after you hold a button). If the device is not discoverable, Windows can't complete pairing. In Settings > Bluetooth & devices, Bluetooth must also be on, and the device should appear during Add device.
When a device connects but doesn't work, the cause is usually one of these:
- Wrong Bluetooth profile: For example, a headset may connect for calls (hands-free) but not switch to high-quality audio (stereo), or a keyboard may connect but not register due to a mismatch in input support.
- Low battery: Bluetooth may stay connected, yet the device drops packets and acts "dead."
- Distance and interference: Walls, USB 3.0 hubs, and crowded Wi-Fi bands can cause stutter and missed input.
- Competing connections: Many earbuds auto-connect to the last phone, so Windows connects second and loses audio control.
If things still fail, reset the relationship by removing and re-pairing:
- Go to Settings > Bluetooth & devices > Devices.
- Select the device, then choose Remove device.
- Turn the device off, then back on, and re-enter pairing mode.
- Select Add device, then complete pairing again.
- Test the app (music player, Teams, Zoom) after the connection is stable.
If audio or input still breaks after a clean re-pair, check for a basic driver or firmware update from Windows Update or the device vendor. Keep it simple, you are confirming support, not rebuilding the system.
Printers and scanners, setting default printers and clearing stuck jobs
Printer issues often come down to three questions: did Windows add the right printer, is it the default, and is the queue blocked. Windows can "see" a printer yet send jobs to the wrong place, such as a stale network share or a virtual PDF printer.
Start in Settings > Bluetooth & devices > Printers & scanners. Use Add device to let Windows find nearby printers. If the printer is not detected, confirm it is on, connected to the same Wi-Fi (for wireless), or plugged in (for USB). For shared printers, you may need the exact network path from the organization.
After the printer appears, set expectations by making it the default when appropriate:
- Open the printer entry, then choose Set as default.
- If Windows keeps changing it, turn off Let Windows manage my default printer (in the same area). This prevents Windows from switching defaults based on the last printer used.
Next, validate the path with a test page. A test page proves the driver can render output, and it proves the connection can deliver the job. If the test page fails, the problem is not the document, it is the setup.
When printing "hangs," open the print queue from the printer's page. The queue is a waiting room. If one job gets corrupted, it can block every job behind it. Common causes include the printer going offline mid-job, a bad document, or a connection drop to a print server.
To recover quickly:
- In the queue, try Cancel on the stuck job.
- If many jobs pile up, use Cancel all documents.
- If the queue shows "Paused," select Resume printing.
Windows also includes a built-in printer troubleshooter, which can clear common spooler issues and fix basic configuration errors. Use it when the symptoms are unclear or repeat across users.
A driver reinstall becomes reasonable when the printer consistently fails test pages, prints gibberish, or disappears after reboots.