Support directory
Windows 11 problems, from quick checks to recovery boundaries.
Begin with the exact device, symptom and connection. These records separate service outages, home-network failures, device software and app sessions before any destructive step.
BitLocker recovery behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · encryptionBitLocker recovery is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · encryptionBitLocker recovery is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · encryptionBitLocker recovery keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · encryptionBitLocker recovery stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · encryptionBitLocker recovery works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates BitLocker recovery through legitimate device ownership/key record versus firmware, account and hardware changes.
Open record Windows · Bluetooth audioBluetooth headphone sound quality drops during calls
Many Bluetooth headsets switch from high-quality stereo playback to a bidirectional hands-free profile when the microphone is used. That behavior is a profile limit, not necessarily interference.
Open record Windows · BluetoothBluetooth is missing or not working in Windows 11
Turn off Airplane mode, toggle Bluetooth, restart the PC and accessory, then run the Bluetooth troubleshooter and update the adapter driver. Remove and re-pair only the affected accessory before reinstalling drivers.
Open record Windows · OneDriveOneDrive file sync behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · OneDriveOneDrive file sync is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · OneDriveOneDrive file sync is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · OneDriveOneDrive file sync keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · OneDriveOneDrive file sync stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · OneDriveOneDrive file sync works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates OneDrive file sync through account/storage quota versus file path, permission, network and Files On-Demand.
Open record Windows · USBUSB device repeatedly connects and disconnects
Repeated USB chimes point to power, cable, port, hub, device or driver instability. Move one component at a time and watch Device Manager.
Open record Windows · AudioWindows 11 has no sound
Unmute Windows and the app, choose the correct output device, run the Audio troubleshooter, then restart audio services or update the sound driver. Test headphones and speakers separately before changing enhancements or drivers.
Open record Windows · Wi-FiWindows 11 Wi-Fi is connected but not working
Check the taskbar connection state, test the same network on another device, toggle Wi-Fi and restart the PC/router, then forget and reconnect. Use Network reset last because it reinstalls network adapters and may require VPN software setup again.
Open record Windows · audioWindows audio device and driver behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record Windows · audioWindows audio device and driver is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record Windows · audioWindows audio device and driver is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record Windows · audioWindows audio device and driver keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record Windows · audioWindows audio device and driver stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record Windows · audioWindows audio device and driver works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows audio device and driver through speaker/headset hardware versus output selection, app mixer and driver.
Open record support · reviewed answerWindows blue screen: what to record before trying fixes
Photograph the exact stop code and any named driver, note the trigger and preserve dump files. Prove whether the crash follows one driver, update, peripheral or workload before reinstalling Windows.
Open record Windows · startupWindows Boot Manager and startup behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · startupWindows Boot Manager and startup is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · startupWindows Boot Manager and startup is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · startupWindows Boot Manager and startup keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · startupWindows Boot Manager and startup stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · startupWindows Boot Manager and startup works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows Boot Manager and startup through firmware drive detection versus boot files, encryption and storage health.
Open record Windows · performanceWindows computer is very slow just after startup
Startup slowness is often driven by login apps, updates, storage pressure or a saturated disk—not by a need to reinstall Windows. Measure Task Manager during the slow window.
Open record Windows · storageWindows external drive behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · storageWindows external drive is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · storageWindows external drive is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · storageWindows external drive keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · storageWindows external drive stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · storageWindows external drive works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows external drive through drive versus cable, enclosure, USB power, filesystem and host port.
Open record Windows · displayWindows external monitor has the wrong resolution
A missing native resolution can come from a bandwidth-limited cable/dock, mirror mode, wrong display selection or graphics driver—not the monitor’s physical size.
Open record Windows · filesWindows File Explorer behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · filesWindows File Explorer is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · filesWindows File Explorer is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · filesWindows File Explorer keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · filesWindows File Explorer stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · filesWindows File Explorer works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.
Open record Windows · graphicsWindows graphics driver behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record Windows · graphicsWindows graphics driver is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record Windows · graphicsWindows graphics driver is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record Windows · graphicsWindows graphics driver keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record Windows · graphicsWindows graphics driver stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record Windows · graphicsWindows graphics driver works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows graphics driver through display/cable versus GPU, driver version, app and power state.
Open record support · reviewed answerWindows keeps asking for the BitLocker recovery key
Enter only the key whose ID matches the screen, then identify the trigger—firmware/TPM change, boot-order change, dock/storage change or policy—before suspending protection. Repeated prompts are not fixed by guessing keys.
Open record Windows laptop · batteryWindows laptop charge limit behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · batteryWindows laptop charge limit is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · batteryWindows laptop charge limit is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · batteryWindows laptop charge limit keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · batteryWindows laptop charge limit stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · batteryWindows laptop charge limit works in one app, account or port but not another
When a computer function works in another app, user account or port, keep the repair inside the failing context. This record isolates Windows laptop charge limit through OEM battery utility versus heat, adapter power and battery condition.
Open record Windows laptop · chargingWindows laptop says plugged in but not charging
Charge thresholds, temperature, an underpowered USB-C adapter, damaged cable/port or battery condition can all pause charging. Verify power rating and firmware status first.
Open record Windows · microphoneWindows microphone input behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Windows microphone input through microphone hardware versus permission, input selection, level and app processing.
Open record Windows · microphoneWindows microphone input is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Windows microphone input through microphone hardware versus permission, input selection, level and app processing.
Open recordStructured depth, not empty permutations
Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.
Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.
See the publication gate