Error codes and messages, explained

Error 4013 during an iPhone restore or update usually points to a connection or hardware problem. Try a different cable and USB port, update your computer software, and restart both devices. If it keeps happening, a failing logic board or storage chip may be the cause.

Error 9 usually means the connection dropped during the restore. Swap the cable, use a port directly on the computer, close security software, and try again. Repeated failures can point to a hardware fault inside the phone.

Error 4005 appears when a restore or update fails, often because of a hardware issue such as storage or logic board trouble. Try a different cable, computer and recovery mode restore. If it still fails, a repair shop can check the board.

Error 14 usually means the update file was corrupted or the USB connection was unstable. Use a different cable and port, restart the computer, and try again. Updating the computer's software can also help.

Error 3194 means the computer could not reach Apple's update server to verify the software. Check your internet connection, turn off VPNs and security software, and make sure the computer's date and time are correct. Then try the restore again.

Error 1671 appears while the computer is downloading software for your iPhone. It usually clears up after a few minutes. Wait, make sure your internet connection is stable, and try again.

Error 4000 is a general restore or update failure that often points to a USB connection problem. Try another cable, another port or another computer. Restart the phone and computer before trying again.

Error 4014 means something went wrong during the restore or update. Restart the iPhone and computer, try a different cable, and run the restore again. If it keeps appearing, it may be a hardware issue.

Error 21 usually means the iPhone stopped responding during a restore, often from a software or hardware problem. Restart both devices, try another cable, and retry. Persistent failures can mean a hardware fault.

Error 56 is a generic restore failure that often points to hardware, such as a damaged component inside the phone. Try another cable and computer first. If it continues, have a repair shop inspect the phone.

Error 1015 usually shows up when you try to restore to an older iOS version that Apple no longer allows. Update to the latest supported iOS instead of downgrading.

Error 17 usually means the computer cannot reach Apple's servers to verify the update. Check your internet connection, turn off firewalls or VPNs, and make sure your date and time are correct.

Error 2002 means the iPhone was disconnected or something interfered with the connection during a restore. Close security software, use a different cable and port, and try again.

Error 3014 means the iPhone could not finish a restore because of a problem reaching Apple's servers or a flaky connection. Check your internet, try a different network and cable, and attempt the restore again.

Error 4010 appears during a restore or update when the connection or software fails. Try a different cable, restart both devices, and update the computer. Persistent errors may point to a hardware fault.

Error 10 often appears when the iPhone has lost its baseband or modem firmware. It usually means a hardware issue, and a shop may need to check the logic board.

Error 1600 appears when updating or restoring in DFU mode and often indicates a connection or hardware issue. Try a different cable and computer, and attempt the restore again.

Error 4016 indicates a restore failure caused by a connection or software problem. Try another cable, update the computer's software and restart both devices.

Error 3004 means the computer could not connect to Apple's update servers. Check your internet connection and security software and try again.

Error 11 usually points to a damaged baseband or hardware issue and can appear during a restore. Try recovery mode, but expect to need repair if it persists.

Error 6 during restore often points to a connection issue or software problem. Try a different cable, update your computer and restart both devices before trying again.

Error 40 signals a hardware problem in the iPhone. Retrying may not help. A repair shop can look at the logic board or storage.

Error 1013 is a restore failure caused by a connection or firmware issue. Use a different cable, restart both devices and try again, using DFU or recovery mode if needed.

Error 2 is a general restore failure often caused by connection trouble. Try another cable, port and computer, and update the computer's software.

Error 9006 is a download failure during an update or restore. Check your internet, security software and cable, and try again.

This message means the iPhone does not recognize the cable or charger, often because it is damaged, not certified, or has debris in the port. Clean the port gently, try another certified cable, and restart the phone.

This usually means the SIM is not compatible with that iPhone or carrier, or the phone is locked to another carrier. Check that the SIM belongs to your carrier and that the phone is unlocked, then contact your carrier.

No SIM usually means the phone cannot read the SIM card. Remove and reseat the SIM, restart the phone, and check for a carrier update. If a different SIM works, your original may need replacing.

Invalid SIM often means the card is not activated, the phone is locked to a different carrier, or the SIM is damaged. Reseat it, restart the phone, and contact your carrier to confirm it is active.

SIM Failure means the iPhone cannot communicate with the SIM. Reseat the card, restart the phone and try another SIM. If it still fails, the carrier can send a new SIM or the SIM tray may be damaged.

The iPhone has sensed moisture in the USB-C port and disables charging to protect it. Unplug it, let it air dry in a well ventilated spot, and try again after a few hours. Wireless charging works in the meantime.

This means the iPhone could not confirm the update with Apple, often from a weak internet connection. Connect to stable Wi-Fi, restart the phone, check that the date and time are set automatically, and try again.

This message usually appears when the date and time are wrong, or a network or profile is interfering. Set date and time automatically, switch networks, and remove old email accounts or profiles that are causing it.

Unable to Activate often means the phone cannot reach Apple's activation server, the SIM is not valid, or the phone is locked. Check Wi-Fi and the SIM, restart, and try again. Contact the carrier or Apple if it continues.

The update needs free space to download and install. Delete unused apps, photos and videos, or offload apps in Settings, then try again. You can also update through a computer to avoid the space problem.

Waiting for Activation usually means a slow or blocked connection to Apple's servers or a SIM issue. Wait a few minutes, check your Wi-Fi, reinsert the SIM and restart. If it persists, your carrier or Apple support can help.

It means the battery has worn down and no longer delivers full performance. Check Battery Health in Settings. A battery replacement at a repair shop is usually $70 to $120, depending on the model.

This message appears when the phone detects a battery, screen or camera it cannot verify, often after a third party repair. The phone usually still works, but some features may be limited.

This usually means the cable, adapter or port has a problem or the accessory is not certified. Try another cable and charger, clean the port gently and restart the phone.

The phone is running out of space. Check Settings, then General, then iPhone Storage to see what is using it. Delete large videos, unused apps and old messages, or use iCloud to free room.

The phone cannot reach Apple's servers. Check Wi-Fi or cellular, confirm the date and time are correct, restart the phone and sign out and back in. Apple's system status page can show whether there is an outage.

The phone cannot set up mobile data, often because of incorrect carrier settings. Toggle Airplane Mode, restart, reset network settings and update carrier settings. If it continues, contact your carrier.

It means a process Windows needs to run was stopped or damaged. Common causes include bad drivers, corrupted system files, or failing storage. Try Safe Mode, run sfc /scannow, and roll back recent driver or update changes.

This stop code means Windows cannot reach the drive it boots from. Common causes are a bad update, a driver problem, a changed storage mode in BIOS or a failing drive. Try Startup Repair, check BIOS settings and test the drive.

Error 0x80070057 means a parameter is incorrect. It appears in Windows Update, backup and drive tools. Try running the Windows Update troubleshooter, run sfc /scannow, and check that the drive has free space.

It means Windows found corrupted data or a driver misbehaving. Common causes are bad drivers, faulty memory or corrupted system files. Update drivers, run sfc /scannow and test your RAM with the Windows Memory Diagnostic.

This blue screen usually points to a driver or system file problem. Update graphics and other drivers, run sfc /scannow, and uninstall any recently added software or hardware. Check Windows Update as well.

Windows tried to read memory that should be available but was not. Causes include faulty RAM, bad drivers or disk errors. Run the Windows Memory Diagnostic, update drivers and check the drive for errors.

It points to a memory problem, either faulty RAM or a driver that mishandles memory. Run Windows Memory Diagnostic, reseat the RAM sticks and update drivers. Replace any RAM that fails the test.

It means a driver or service tried to use memory it should not. Usually a faulty driver or hardware is to blame. Update or roll back recent drivers, check RAM and remove newly added hardware.

It indicates a problem with the storage or memory system. Common causes are a failing drive, bad drivers or antivirus conflicts. Check the drive health, update drivers and run sfc /scannow.

This blue screen means a hardware error was detected that Windows could not fix. Causes include overheating, a failing CPU, RAM or drive, or unstable overclocking. Check temperatures, remove overclocks and test hardware.

It means a processor core stopped responding. Causes include CPU problems, outdated BIOS or drivers, or unstable overclocks. Update the BIOS and drivers, reset any overclock and check cooling.

The system waited too long for a driver or process to finish. It is commonly caused by outdated storage or other drivers or firmware. Update drivers, update SSD firmware and install pending Windows updates.

A system thread hit an error Windows could not handle, often caused by a faulty driver. The file named on screen shows which one. Update, roll back or remove that driver, then restart.

A kernel mode program caused an exception Windows could not fix, usually due to a bad driver or faulty hardware. Update drivers, remove recently installed software and check RAM.

It means the Windows registry or boot configuration is damaged. Try Startup Repair from recovery options, or restore the system using a restore point. Failing hardware or a bad shutdown may be the cause.

It points to problems with the drive's file system, often from a failing drive or disk corruption. Run chkdsk, check drive health, back up your files promptly and replace the drive if errors keep appearing.

The graphics driver stopped responding and could not recover. Update or cleanly reinstall your graphics driver, check temperatures and test the graphics card if it keeps happening.

It usually means a driver damaged memory the system relies on. Update or remove recent drivers and software, run Windows Memory Diagnostic and run sfc /scannow.

Error 0x80070005 means access denied. It appears in updates, installs and app activation when permissions are wrong. Try running as administrator, check folder permissions, and run the Windows Update troubleshooter.

It usually means Windows cannot find a file it needs for the update. Run the Windows Update troubleshooter, clear the update cache, and make sure the date and time are correct.

This error often means the update could not install because of a small System Reserved partition, a network issue or a VPN. Disconnect VPNs, free up space and run the troubleshooter.

It means a file needed for the update is missing or corrupted. Run DISM and sfc /scannow from an admin Command Prompt, then try the update again.

It means Windows could not connect to Microsoft's update servers, often due to proxy, DNS or firewall settings. Check your internet, disable VPNs and proxies and try the update again.

Error 0xc000000f appears at startup when Windows cannot find boot information. A failing drive, loose cable or damaged boot files can cause it. Try Startup Repair and check that the drive is detected in BIOS.

It means Windows could not find or load its boot files. Use Startup Repair from recovery media, check the boot order in BIOS and confirm the drive is detected.

This stop error means a critical system process failed during startup. Causes include corrupted system files or a bad update. Try Startup Repair, uninstall the recent update from recovery, or restore the system.

Error 0x80004005 is an unspecified error that shows up with file sharing, updates and virtual machines. Check permissions, restart, run the Windows Update troubleshooter and make sure network sharing is configured properly.

It means Windows could not find the files needed to install a feature or update. Run the Windows Update troubleshooter and DISM restore health, then try the install again.

It means the data is invalid, often because the update files are corrupted. Clear the Windows Update cache, run the troubleshooter and use DISM to repair system files.

This error means Windows could not reach the activation server. Check your internet connection and the date and time. If you use a work or school license, confirm you are on the network that provides it.

It means a required service, usually Windows Update, is disabled. Open Services, set Windows Update to Automatic, start it and run the update again.

It signals a failed installation, often for a security update or .NET. Restart, run the Windows Update troubleshooter and try again. Repairing .NET or clearing the update cache can also help.

It means the file or directory is corrupted and unreadable. It often appears during installs or file copies. Run chkdsk, check drive health and try a fresh copy of the installer.

This error appears when connecting to a shared printer after a security update. The fix is usually a policy change by the network admin or using a different connection method, such as a local port.

This is INACCESSIBLE_BOOT_DEVICE. Windows cannot reach the drive it boots from, often after a storage mode or driver change. Check BIOS settings, reseat cables and try Startup Repair.

It is IRQL_NOT_LESS_OR_EQUAL, caused by a driver or hardware accessing memory incorrectly. Update or remove recent drivers and software, and test your RAM.

This is SYSTEM_SERVICE_EXCEPTION, usually tied to a driver or system file problem. Update drivers, run sfc /scannow and remove recent software or hardware changes.

It is WHEA_UNCORRECTABLE_ERROR, a hardware error. Check temperatures, remove overclocks, and test the CPU, RAM and drive. Update the BIOS if one is available.

This upgrade error is usually caused by a driver problem. Disconnect extra devices, update drivers, free up space and uninstall third party security software, then retry the upgrade.

It usually means the Store cannot connect to the internet or its cache is damaged. Check your connection and date and time, run wsreset, and run the Store apps troubleshooter.

This is the blue screen message that appears when Windows hits a serious error. It collects info and restarts. Note the stop code on the screen, then check for driver, update or hardware causes.

The computer cannot find a drive to start from. Check that the drive shows up in BIOS, reseat cables or the SSD, and check the boot order. A failed drive may need replacing.

The computer cannot find Windows on the drive. It can be caused by a wrong boot order, damaged boot files or a failing drive. Check BIOS, run Startup Repair and test the drive.

The computer found no drive with a startup system. Remove USB drives, check the boot order in BIOS, and confirm the drive is detected. A failed drive or damaged boot files may be the cause.

It means the computer could not read the drive during startup. Possible causes include a failing drive, a loose cable or damaged boot data. Back up files if you can and test or replace the drive.

The sfc scan found damaged system files. If it says it repaired them, restart. If it could not, run DISM restore health and then run sfc /scannow again.

Windows tried to fix a startup problem and failed. Try Startup Settings, Safe Mode, System Restore or uninstalling recent updates. Check the drive health if the problem continues.

Windows detected a startup failure and keeps trying to repair itself. Try Safe Mode, System Restore, or uninstalling recent updates. If it still loops, the drive or system files may be damaged.

It means the Mac found a startup disk but the macOS on it is not compatible or is damaged. Boot into recovery and reinstall macOS or use Disk Utility to check the drive.

The Mac is trying to start from internet recovery. This happens when it cannot find local recovery or startup files. Make sure you have a stable network connection and follow the prompts.

The Mac is starting up or installing an update. Let it finish, as it can take a long time. If the bar is stuck for hours, try a restart or boot into recovery.

The padlock means a firmware password is set, and you must enter it to continue. If you forgot it, Apple can help after you verify ownership.

It means the Mac had a kernel panic and restarted. Update macOS, disconnect accessories and check for faulty software. Repeated panics can point to hardware problems.

Error -43 means the Mac cannot find a file. This happens when copying or moving items. Check that the file exists, the name is valid, and try again or restart Finder.

Error -36 is an input/output error when copying files. It often comes from a failing drive, a bad cable or hidden dot files. Try another cable or port and copy again.

Error -50 means a parameter was wrong while copying a file. It can happen with special characters in file names or on certain drives. Rename the file and try again.

Error -8003 appears when you try to empty the Trash and a file cannot be deleted. Restart your Mac, close apps using the file, and try emptying the Trash again.

It means the Mac connected to Wi-Fi but has no internet access. Restart the router and Mac, forget and rejoin the network, and check your DNS settings.

The phone's charging port senses moisture or residue and stops charging to prevent damage. Unplug, let the port dry fully, and try again later. Wireless charging may work. Clean the port gently if the alert persists.

The app crashed. Force stop it, clear its cache, update the app, and restart your phone. If it keeps happening, uninstall and reinstall the app.

The System UI crashed. Restart your phone, update Android and apps, and clear the cache of the app named in the message. Booting in Safe Mode can show whether a downloaded app is causing it.

The phone is nearly full. Delete unused apps, photos and videos, or clear app caches. Moving files to the cloud or an SD card can free space.

The system process froze, often from low storage or an app conflict. Restart the phone, free up storage, update software and consider booting in Safe Mode to find a bad app.

The camera app could not start. Restart the phone, clear the camera app's cache and data, free some storage and update the software. Persistent issues may mean a hardware fault.

The phone cannot read the SIM. Restart, reseat the SIM, and clean the contacts gently. Try the SIM in another phone to see whether the card or the phone is the problem.

The phone cannot connect to the carrier network. Toggle Airplane Mode, restart, reseat the SIM and check for outages. Resetting network settings can help.

It means the phone cannot reach your carrier's network but can still call emergency numbers. Restart, reseat the SIM, check coverage and account status, and reset network settings if it continues.

Google Play Services crashed. Update it, clear its cache, and restart. Make sure your date and time are set automatically and Android is up to date.

The phone cannot register with the carrier network. Restart, reseat the SIM, switch network mode, and check for outages. If a different SIM works, your original SIM may need replacing.

The Play Store is waiting to start the download. Check your connection, free up storage, clear the Play Store cache and make sure your date is correct. Restart the phone if it stays stuck.

Error 927 appears when the Play Store is busy updating itself. Wait a few minutes and try again. If it persists, clear the cache of Google Play Store and Google Play Services.

Error 403 usually means a problem with your account or payment setup, or a region or device issue. Check your account and payment method, and clear the Play Store cache.

Error 491 means a Google account issue prevented a download or update. Remove and re-add your Google account, clear the Play Store cache and try again.

Error RH-01 means the Play Store could not retrieve information from the server. Clear the Play Store cache, check your connection, and remove and re-add your Google account.

The Settings app crashed. Restart the phone, clear the cache of Settings, and update Android. If it continues, Safe Mode can help find a conflicting app.

The launcher crashed. Restart, clear the launcher's cache and data, and update it. A third party launcher can be uninstalled if the problem persists.

The phone got too hot and limited features to cool down. Stop using heavy apps, take off the case, move to a cooler spot and unplug the charger. Persistent heat can signal a battery or software issue.

Corrupted system files can cause crashes or boot loops. Try a restart, clear the system cache from recovery and, if needed, factory reset after backing up what you can.

Error 5200 typically indicates a printhead or ink problem on Canon printers. Turn the printer off, reseat the cartridges and printhead, and try again. If it continues, the printhead may need service.

Error B200 indicates a printhead problem on Canon printers. Turn the printer off, unplug it for a few minutes and restart. If it comes back, the printhead likely needs replacing.

Error 6A80 usually points to a fault in the ink absorber or maintenance mechanism. Turn the printer off, remove any obstruction, and try again. Persistent errors usually need professional service.

Error 46 means the ink absorber pad is nearly full. It usually needs service or a replacement part. Contact the manufacturer or a repair shop to have it addressed.

It means Windows cannot communicate with the printer. Check that it is on and connected to the same network, restart it, and set it as the default printer. Uncheck Use Printer Offline if shown.

The E3 code usually means a carriage jam or something blocking the print head. Open the access door, remove any jammed paper and power the printer off and on.

Your device could not reach the DNS server. Restart the router and device, try another browser, and switch DNS to a public server in your network settings.

It means Wi-Fi is connected but there is no internet access. Restart the router and PC, forget and rejoin the network, and run the network troubleshooter. Check the modem lights too.

The device did not get a proper address from the router. Restart the router and device, renew the IP address with ipconfig /release and /renew, or forget and rejoin the network.

The device connected to the router but cannot reach the internet. Restart the router and modem, forget and rejoin the network, and check whether other devices are affected.

The website or server rejected the connection. Check the address, restart your router, clear the browser cache and try a different network. If it happens on one site, the problem may be on their end.

A red internet light usually means the router cannot connect to your internet provider. Restart the modem and router, check cables and look for an outage with your provider.

The browser could not establish a secure connection. Check the date and time, clear the cache and SSL state, disable VPNs or antivirus filtering and try another browser.

The browser could not find the website's address. Check the URL, restart the router and device, and change your DNS settings. Clearing the DNS cache can help.

The website took too long to respond. Check your connection, restart the router, try another network, and disable VPN or proxy settings. If other sites work, the problem may be with that site.

The site's security certificate looks expired, or your device's date is wrong. First check that your date and time are correct. If they are, the website's certificate may be expired.

This browser error means the computer has no internet connection. Check Wi-Fi or Ethernet, restart the router and device and run the network troubleshooter.

Chrome OS could not start. You will need a recovery USB made from another computer to reinstall Chrome OS. Follow Google's recovery steps, and note that local files may be lost.

The watch could not reach Apple's servers. Check Wi-Fi and Bluetooth, restart the watch and iPhone, and try the update again.

This happens when the phone cannot confirm your Apple ID, often from a weak connection or wrong date settings. Switch networks, set date and time automatically, restart and try signing in again.

This message appears when a carrier settings update or software step fails. Restart the phone, toggle Airplane Mode, check for a carrier settings update and make sure you have a signal. Resetting network settings sometimes helps.

It indicates a boot problem, often from damaged system files or a hardware fault like bad memory. Try Startup Repair from recovery media and test the RAM and drive.

It usually means a required module or driver could not be found. This is common with printer, update and driver installs. Run sfc /scannow, and download the correct driver for your device.

It means the device is not ready, often with a drive or backup tool. Check that the drive is connected, working and shows up in File Explorer, and try another port or cable.

It means the RPC server is unavailable, often seen with printing. Make sure the Print Spooler and RPC services are running and the firewall is not blocking printer sharing.

This error usually indicates the Play Store could not retrieve app info. Clear the cache and data of Google Play Store and Services, check your connection and try again.

It means an update did not download properly. Wait and retry, run the Windows Update troubleshooter and clear the update cache if it keeps failing.

It means Windows cannot find the path it needs, often during updates or restores. Run the Windows Update troubleshooter, clear the update cache and check system files with sfc /scannow.