Distinct consumer questions
Computer troubleshooting
Browse computers by the symptom the customer actually sees. Each record has its own observation, isolation test, correction, verification and stop condition; manufacturer names are not swapped into generic copy.
Browse by platform
949 complete records in this directoryAirDrop is not working between a Mac and iPhone
Enable Wi-Fi and Bluetooth on both devices, put them nearby, open AirDrop on the Mac and make the receiver discoverable, then restart both devices. Confirm Contacts Only has matching Apple Account contact details.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Chromebook · Android appsAndroid apps on Chromebook 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 Android apps on Chromebook through app compatibility versus Play Store availability, storage and managed restrictions.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Mac · ContinuityApple Handoff and Continuity 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 Apple Handoff and Continuity through Apple Account and feature eligibility versus Bluetooth, Wi-Fi and app support.
Open record Windows · encryptionBitLocker 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 Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · accountChromebook account and settings 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 Chromebook account and settings sync through local profile versus Google Account sync, policy and network.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · displayChromebook external monitor 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 Chromebook external monitor through port video capability versus adapter, cable, display input and mirrored mode.
Open record Chromebook · sessionChromebook keeps signing out or returning to the login screen
Unexpected sign-outs can be a crash, storage pressure, managed-session policy, account token problem or power interruption. Determine whether the whole device restarts.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · LinuxChromebook Linux development environment 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 Chromebook Linux development environment through device/policy eligibility versus container disk, update and configuration.
Open record Chromebook · startupChromebook will not turn on but the charge light is on
A charge light proves some adapter power, not that the battery, display or system completed startup. Remove accessories and try the model’s hardware reset before recovery.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Chromebook · updatesChromeOS update 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 ChromeOS update through Google update service versus storage, network, managed policy and support lifetime.
Open record Computers · touchpadLaptop cursor jumps while typing
Cursor jumps often come from palm contact, touchpad sensitivity, moisture, charger noise or a swollen battery pressing the pad. External-mouse testing separates software from hardware.
Open record Mac · window placementMac app window opens off screen
A window can remain positioned for a disconnected monitor. macOS window commands, display arrangement and temporarily changing resolution can bring it back without deleting app preferences.
Open record Mac · PrinterMac cannot find a Wi-Fi printer
Confirm the printer and Mac are on the same Wi-Fi, resolve any printer display error, then add it from System Settings › Printers & Scanners. Prefer AirPrint when the printer supports it; reset the Mac printing system only as a last resort.
Open record Mac · DisplayMac does not detect an external display
Verify how many displays the exact Mac supports, reconnect power and the cable, choose the correct display input, then use Displays settings to detect or arrange it. Test a direct compatible cable before a dock or adapter.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · iCloud DriveMac iCloud Drive 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 Mac iCloud Drive sync through cloud capacity/account versus local storage, network and optimization state.
Open record Mac · Wi-FiMac is connected to Wi-Fi but the internet does not work
Check the same network on another device, turn Wi-Fi off and on, restart the Mac and router, then run Wireless Diagnostics. Forget the network or change TCP/IP/DNS settings only after recording the current configuration.
Open record Mac · searchMac Spotlight search index 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 Mac Spotlight search index through indexing progress versus excluded locations, external drives and filesystem health.
Open record Mac · searchMac Spotlight search index 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 Mac Spotlight search index through indexing progress versus excluded locations, external drives and filesystem health.
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