Windows fixes organized by the problem you can actually see.
Each guide states its scope, starts with lower-risk checks, and keeps broad resets or repair commands later in the sequence.
Wi-Fi not working in Windows 11: a safe troubleshooting order
Diagnose a Windows 11 Wi-Fi problem from the least disruptive checks to network reset.
Bluetooth not connecting in Windows 11: diagnose pairing before drivers
Work through pairing mode, saved device state, updates and driver checks in a low-risk order.
No sound in Windows 11: check output, enhancements, services and drivers
A safe sequence for silent speakers or wired headphones when Windows appears to be running normally.
Black screen in Windows 11: identify the stage before changing anything
Separate display-output, login, update and boot-device symptoms before using recovery steps.
Printer offline in Windows 11: reconnect it without unnecessary resets
Check power, network, queue state and the print spooler before reinstalling the printer.
Windows 11 update not installing: troubleshoot from simple checks to repair tools
A conservative sequence for Windows Update failures before resetting update components.
Windows 11 won’t start: when to use Startup Repair
Use Windows Recovery Environment and Startup Repair for genuine startup failures, not ordinary app crashes.
Repair Windows system files with DISM and SFC: correct order and scope
Use DISM first, then System File Checker, when Windows components or protected system files may be damaged.
Windows 11 keeps blue-screening: isolate the stop code before broad repair
A safe-first route for repeated Windows 11 stop-code crashes that separates recent hardware, drivers and recovery options.
Screen flickering in Windows 11: distinguish a display driver from an app
Use the Task Manager flicker test and graphics-driver reset before changing the wrong part of Windows.
Camera not working in Windows 11: check privacy, app scope and driver state
Separate a disabled camera, permission problem, app-only failure and driver issue before reinstalling anything.
Microsoft Store not opening in Windows 11: reset the cache before deeper repair
Start with wsreset, Windows updates and time/region checks when Microsoft Store will not launch.
Driver problem after Windows Update: update, roll back or reinstall the right device
Use timing and Device Manager status to choose between a newer driver, rollback and device-specific reinstall.
Windows Update component-store corruption: DISM and SFC repair path
Use this path for servicing errors such as 0x800F081F, 0x800F0831 and 0x80073712 when component-store repair is relevant.
Reinstall the current Windows 11 version to repair system problems without removing apps
Use Windows 11’s supported “Fix problems using Windows Update” recovery option only after narrower repair paths are exhausted.
Windows 11 stuck in a restart loop: use recovery options in the least disruptive order
Move from Windows Recovery Environment and startup checks toward restore or reinstall only when the loop persists.
USB device not recognized in Windows 11: separate the port, device and driver
Use another port and a direct connection first, then check Device Manager before reinstalling drivers.
No audio output device detected in Windows 11: restore detection before changing sound settings
If speakers or headphones do not appear under Output, check Device Manager and driver detection before tuning audio settings.
Microphone not working in Windows 11: permissions, input selection, then drivers
Check microphone privacy access and the selected input device before reinstalling audio drivers.
App not working in Windows 11: repair before reset or reinstall
For supported apps, use Repair first; Reset and reinstall are more disruptive and belong later.
Microsoft Store app not installing in Windows 11: update, account and cache checks
Separate a Store/app problem from regional availability or a broader Windows problem before reinstalling anything.
Display driver problem in Windows 11: update, roll back or reinstall based on timing
Choose update versus rollback from the failure timeline instead of cycling graphics drivers blindly.
Microsoft Edge not opening in Windows 11: close, update, isolate, then repair
Use Edge-specific repair after restart and process checks instead of treating a browser launch problem as a Windows reinstall problem.
Chrome not opening in Windows 11: end stuck processes before reinstalling
Treat Chrome as an application problem first: close background processes, isolate extensions and reinstall only after narrower checks.
Crackling or distorted audio in Windows 11: enhancements, format, driver, services
Test reversible sound settings before replacing drivers or changing hardware.
USB mouse or keyboard not working in Windows 11: test the hardware path first
Reconnect, change ports and bypass hubs before changing Windows drivers.
Bluetooth disappeared in Windows 11: check detection before reinstalling drivers
When the Bluetooth toggle or icon disappears, confirm the adapter and Windows detection path before treating it as a pairing problem.
Ethernet not working in Windows 11: isolate cable, router, adapter and Windows
Separate a physical Ethernet path failure from a PC-only network-stack or driver problem before using network reset.
External monitor not detected in Windows 11: test the display path before driver replacement
Check cable, input, dock and display topology first; use graphics-driver rollback or reinstall only when the timeline supports it.
Drive not showing in File Explorer: check Disk Management before formatting anything
Determine whether Windows sees the disk, whether a volume exists, and whether the problem is only a missing drive letter before destructive changes.
169.254 IP address in Windows 11: diagnose DHCP before resetting the network
A 169.254.x.x IPv4 address is a strong clue that Windows did not receive a usable DHCP address from the router or DHCP server.
DNS not resolving in Windows 11: prove name resolution before changing DNS settings
Use IP configuration, nslookup and a browser comparison to separate DNS failure from general connectivity or one-site failure.
Connected but no Internet in Windows 11: identify IP, DNS or upstream failure
A connected Wi-Fi/Ethernet icon does not prove usable Internet; check addressing, gateway, DNS and another device before resetting Windows.
Proxy blocking Internet in Windows 11: verify whether the proxy is intentional first
A manual proxy or setup script can be required by work/school networks, so distinguish stale configuration from managed policy before disabling it.
VPN connected but no Internet in Windows 11: separate tunnel policy from Windows networking
Compare the connection with and without the VPN, preserve organization policy, and avoid network reset until the failure is proven to be Windows-wide.
Network adapter missing in Windows 11: prove device detection before TCP/IP repair
If Windows cannot enumerate the Wi-Fi/Ethernet adapter, DNS flushes and browser resets are the wrong layer; focus on Device Manager, hardware detection and the correct driver.
Chrome page-loading network errors on Windows: separate browser, DNS and network layers
Use Chrome’s exact error code and a cross-browser comparison before clearing data, disabling security tools or resetting Windows networking.
Microsoft Edge pages not loading in Windows 11: separate site/network failure from browser repair
Compare another browser and another site first; repair Edge only after the failure remains Edge-specific.
Unexpected restart in Windows 11: use Event ID 41 as a timeline clue, not the diagnosis
Kernel-Power Event ID 41 confirms Windows detected an unclean restart; correlate its fields with bugcheck, power and recent-change evidence before deciding why.
Find repeated app crashes with Reliability Monitor before reinstalling everything
Use the Windows reliability timeline to identify when failures began and whether they line up with a specific app, driver, update or installation.
Windows Memory Diagnostic: when to run it and how to read the result
Use the built-in memory test when repeated stop errors or instability make RAM plausible, then read the recorded result instead of assuming a clean test proves all hardware is healthy.
Check storage health in Windows before running repair commands
Separate physical-disk health evidence from volume/file-system repair by checking what Windows Storage reports before using CHKDSK repair switches.
File-system errors in Windows 11: start with CHKDSK scan before repair switches
Use CHKDSK for a volume/file-system integrity problem—not as a generic slow-PC command—and distinguish a scan from /f or /r repair operations.
Drive randomly disconnects in Windows 11: separate cable, power, device detection and disk health
Repeated storage disconnects are not a reason to format the drive; preserve detection and health evidence before changing the file system.
Windows service won’t start: identify state, dependency and Service Control Manager evidence first
Troubleshoot a Windows service that refuses to start without blindly changing startup types or registry service entries.
Use a clean boot to isolate a background service or startup-app conflict in Windows 11
A controlled clean boot can prove whether a non-Microsoft service or startup app is involved without turning permanent service changes into the diagnosis.
Application keeps crashing in Windows 11: correlate Event ID 1000 with WER and the faulting module
Use repeated Application Error/WER records to identify the failing process, module and exception before reinstalling Windows or unrelated drivers.
Find Windows crash dump files: Minidump vs MEMORY.DMP and what each tells you
Locate the dump that matches a Windows stop error and verify dump configuration before assuming Windows failed to capture the crash.
Driver install failed or changed unexpectedly: inspect SetupAPI.dev.log before reinstalling everything
Use Windows’ device-installation log to verify what driver package Windows tried to install, when it happened and whether signing/install errors were recorded.
Storage Event ID 129 or 153 in Windows: treat timeouts and retries as storage-path evidence
Repeated Storport resets/retries can point to a stressed or unreliable storage path; correlate them with the affected disk, driver/controller, cabling and device health before file-system repair.
Application not responding in Windows 11: inspect the wait chain before forcing repairs
A hung app may be waiting on another process, service or resource. Preserve the process and dependency evidence before reinstalling Windows or killing unrelated tasks.
Capture a user-mode app dump with Task Manager in Windows 11
Preserve a crashing or hung application state for vendor or debugger analysis without crashing the whole PC.
No memory dump after a Windows blue screen: verify capture settings before blaming the crash
A missing MEMORY.DMP or Minidump can reflect dump configuration, paging-file requirements, disk space or an incomplete write—not proof that no bugcheck occurred.
Use Windows Error Reporting evidence to separate app crashes from app hangs
WER can preserve report identifiers and crash/hang context that help connect an incident to the correct process without turning every report into a root-cause claim.
Windows 11 starts slowly: build a startup evidence timeline before disabling services
Separate boot delay, sign-in delay and post-desktop startup load, then correlate recent changes and startup items before broad service changes.
Driver problem or hardware failure? Build the evidence before replacing parts or reinstalling Windows
Use device state, driver chronology, repeatability and vendor diagnostics to decide when Windows troubleshooting should hand off to hardware support.
Desktop program will not install, update or uninstall in Windows 11
Separate a desktop installer problem from Microsoft Store/MSIX deployment, then use repair, uninstall and installer evidence in the least disruptive order.
Microsoft Store app will not install or update in Windows 11
Check account/device availability, restart state, Windows/Store updates and app-specific deployment evidence before broad package repair.
Repair vs Reset vs reinstall an app in Windows 11: use the least disruptive option first
Repair can preserve app data/settings; Reset is broader; reinstall is a later step when the problem remains isolated to that app.
Older app stopped working after a Windows 11 upgrade: check compatibility before reinstalling Windows
Update the app, confirm Windows compatibility, and use Program Compatibility Troubleshooter before broad OS recovery.
MSI installer failed in Windows 11: create one verbose Windows Installer log before guessing
Use the exact MSI code first; when the cause is still unclear, a controlled /L*V log can preserve the Windows Installer sequence for support.
Use WinGet to identify, repair or update an installed app without guessing the package
List the installed package first, verify its exact ID, then use repair or upgrade only when the package supports that operation.