What It Means When a Drone Firmware Update Gets Stuck at 99 Percent
A drone firmware update stuck at 99 percent usually means the device has finished most of the installation process but has not completed the final verification, reboot, or device handoff step.
This can happen on the aircraft, remote controller, battery, or in the companion app, and the cause is often simpler than it looks.
The key is to identify whether the update is truly frozen or just slow, because the wrong recovery step can interrupt the firmware flashing process and create a larger problem.
Why Drone Firmware Updates Freeze Near the End
Most modern drones from DJI, Autel Robotics, Skydio, Parrot, and similar manufacturers use staged update routines.
The system may download files, write firmware to flash memory, validate checksums, restart components, and then synchronize versions across multiple devices.
The final 1 percent can take longer than the first 99 percent because it often includes device reboots and integrity checks.
Common reasons for the stall include:
- Weak or unstable Wi-Fi or mobile data during the download phase
- Low battery on the drone, controller, or phone
- Corrupted firmware package or incomplete cache
- Outdated companion app or incompatible mobile operating system
- Interruption from USB cable issues, Bluetooth handoff problems, or app crashes
- Background processes on the controller or phone preventing the final reboot
- Server-side congestion on the manufacturer’s update service
First Checks Before You Restart Anything
Before forcing a power-off, confirm whether the update is still active.
Some drones keep writing or validating data for several minutes after the progress bar stops moving.
If the app shows a spinning indicator, log file activity, or a changing LED pattern, the process may still be working.
Check battery levels
Make sure the aircraft battery, controller battery, and connected phone or tablet all have enough charge.
Many manufacturers recommend starting firmware updates only when batteries are well above 50 percent, and some require more.
Check the connection path
If the update depends on a phone app, verify that the USB cable is seated properly and that the cable supports data transfer, not just charging.
If the update uses Wi-Fi, move closer to the router and reduce interference from other devices.
Look for app feedback
Some apps display a hidden status such as “verifying,” “restarting,” or “transferring to aircraft.” That status can indicate the update is still progressing even if the percentage is static.
Safe Recovery Steps for a Stuck Firmware Update
If the update remains stuck for 10 to 20 minutes with no visible changes, use a cautious recovery sequence.
The best method depends on whether the aircraft is still responsive and whether the manufacturer provides a dedicated recovery utility.
- Keep the drone and controller powered on for a short period longer to rule out a slow verification stage.
- Close unrelated apps on your phone or tablet and leave the update app open.
- If the manufacturer provides a desktop updater, connect the drone or controller to a computer and check for resume or repair options.
- If the app shows an explicit failure message, follow the recommended retry path instead of hard-resetting immediately.
- Only power-cycle the device if the update is clearly stalled and the manufacturer instructs you to do so.
After a restart, check whether the version number changed.
A partial update may have completed successfully even if the app did not report it correctly.
How to Fix a Drone Firmware Update Stuck at 99 Percent
If you need to retry the update, focus on the most common failure points first.
These fixes solve many cases without requiring professional service.
Use a different cable or port
USB-C and micro-USB cables vary in quality.
A cable that charges a smartphone may still fail during sustained data transfer.
Try a certified data cable and use a direct USB port on the computer rather than a hub.
Re-download the firmware package
Corrupted downloads are common, especially when a connection drops near the end.
Clear the app cache if the platform allows it, then download the firmware again from the official source.
Update the companion app
Manufacturer apps such as DJI Fly, DJI Assistant 2, or vendor-specific desktop tools may need the latest version to communicate correctly with current firmware builds.
Update the app before attempting another installation.
Match the required device sequence
Some systems require the aircraft to be updated before the controller, while others require the reverse order.
Check the manufacturer’s release notes so the devices are synchronized correctly.
Disable power-saving features
Battery saver modes, screen sleep settings, and background app restrictions can interfere with long firmware tasks.
Keep the screen awake and prevent the operating system from suspending the app.
Device-Specific Issues That Can Cause the 99 Percent Problem
Different drone ecosystems fail in different ways.
DJI drones may appear stuck while the aircraft is rebooting internal modules, while controller updates can hang if the app loses permissions or the phone disconnects from the accessory.
Autel Robotics systems may need a clean SD card or a specific desktop utility.
Skydio and Parrot products can be sensitive to connectivity timing and account authentication.
If your drone uses an SD card for offline updates, verify that the card is formatted correctly, has enough free space, and is inserted fully before starting the process.
A damaged card can cause the update to stall late in the installation.
When It Is Safe to Force a Retry
A retry is usually safe when the manufacturer’s support documentation allows repeated attempts after a failed update, and the device still powers on normally.
If the drone is unresponsive, shows boot loops, or refuses to connect after the failure, a repair utility or service center may be safer than repeated resets.
Use caution if the aircraft is mid-flash and the app gives no clear failure signal.
Interrupting internal memory writes at the wrong time can corrupt firmware and prevent the drone from booting.
How to Prevent a Firmware Update From Hanging Again
Good preparation dramatically reduces update failures.
Before future updates, create a checklist and follow it every time.
- Charge the drone, controller, and mobile device fully or at least above the manufacturer’s minimum
- Use the exact app recommended by the manufacturer
- Check that your operating system is compatible with the latest release
- Update in a location with strong network stability or use the recommended offline tool
- Remove unnecessary accessories and disconnect extra USB peripherals
- Read the release notes for order-of-update instructions and known issues
- Back up flight logs and media in case the update forces a reboot or reset
It also helps to avoid updating immediately before a flight.
Schedule firmware changes when you have time to troubleshoot, confirm version numbers, and test basic functions such as GPS lock, camera response, and controller pairing afterward.
When to Contact Manufacturer Support
If a drone firmware update stuck at 99 percent repeats across multiple attempts, or if the aircraft will not power on normally after the failure, contact official support.
Provide the exact model, app version, firmware version, error messages, battery levels, and the step where the update failed.
Screenshots or screen recordings can speed up diagnosis.
Manufacturer support can often tell whether the issue is related to a known firmware bug, a bad update package, or a hardware fault in storage, power delivery, or communications.
Signs the Update Completed Even Though the App Looked Frozen
Sometimes the update succeeded despite the stalled progress bar.
Look for these signs:
- The drone, controller, or app reboots normally
- The reported firmware version matches the latest release
- The app no longer prompts for the same update
- LED indicators return to their standard operating pattern
- Basic functions such as pairing, camera preview, and flight mode selection work as expected
If those checks pass, the freeze may have been only a reporting issue rather than a true installation failure.