Skip to content
Lower risk Medical device recall · FDA · Published July 17, 2020

Medtronic Restore Clinician Programmer Software Recall: Inability to Communicate

Medtronic recalls version 1.0.4232 of the Restore Clinician Programmer Application Software (model A71100) due to compatibility issues with some legacy software, preventing communication with implanted neurostimulators.

Take action

Contact the company

Recalling firmMedtronic Neuromodulation7000 Central Ave Ne · Minneapolis, MN 55432-3568
✎ GovInfoNow plain-language explainer

Medtronic is recalling version 1.0.4232 of the Restore Clinician Programmer Application Software (model A71100) because it has compatibility issues with some legacy software. This prevents the programmer from communicating with implanted neurostimulators, which could lead to improper device function. Read more at govinfonow.com/recall/64692-medtronic-restore-clinician-programmer-software-recall-inability-to-communicate-with.

Source Summary by GovInfoNow · govinfonow.com/recall/64692-medtronic-restore-clinician-programmer-software-recall-inability-to-communicate-with · Updated August 19, 2026 · FDA enforcement record: FDA #Z-2657-2023

Cite this page

“Medtronic Restore Clinician Programmer Software Recall: Inability to Communicate.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/64692-medtronic-restore-clinician-programmer-software-recall-inability-to-communicate-with. Based on FDA recall #Z-2657-2023 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2657-2023%22&limit=1).

The FDA announced on July 17, 2020, that Medtronic Neuromodulation is recalling Restore Clinician Programmer Application Software, model number A71100, due to a compatibility issue preventing communication with implanted neurostimulators. The agency classified the recall as Class II.

How to tell if you have it

  • Brand: Medtronic
  • Product: Restore Clinician Programmer Application Software
  • Model number: A71100
  • Version: 1.0.4232
  • UDI-DI: 00763000273668
  • Quantity: 2,408 devices

The hazard

The original version of the A71100 Restore Clinician Programmer Application has a compatibility issue with some legacy clinician programmer software. This results in the programmer being unable to establish communication with the implanted neurostimulators.

Context

GovInfoNow's records show Medtronic Neuromodulation has 45 other recalls on record since August 9, 2017. Other recent recalls of similar products include Medtronic SynchroMed Flex Infusion Software Issue (April 8, 2026) and Medtronic Vanta CP App Software Recall (December 3, 2025). Other recent recalls of similar products include Elekta MOSAIQ Oncology System Software Recall (May 21, 2026), Elekta Leksell GammaPlan 11.1 Software Recall (December 12, 2025), and B. Braun Medical CESK Riverside Health System Software Recall (January 29, 2026).

How to tell if you have this one

Check if you have the Restore Clinician Programmer Application Software version 1.0.4232 (model A71100) used with Restore Neurostimulators. The software was sold with the device and has a UDI-DI number 00763000273668.

  • Brand
    Medtr: a short, human brand name for headings (e.g. "Trsmima")
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Verify the software version by checking the device's settings or documentation for version 1.0.4232 (model A71100).

Where it went and when

Where it was distributed

Distributed nationwide, and outside the U.S.

Alaska: yesAKMaine: yesMEVermont: yesVTNew Hampshire: yesNHWashington: yesWAIdaho: yesIDMontana: yesMTNorth Dakota: yesNDMinnesota: yesMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: yesRIMassachusetts: yesMAOregon: yesORNevada: yesNVWyoming: yesWYSouth Dakota: yesSDIowa: yesIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: yesCTCalifornia: yesCAUtah: yesUTColorado: yesCONebraska: yesNEMissouri: yesMOKentucky: yesKYWest Virginia: yesWVVirginia: yesVAMaryland: yesMDDelaware: yesDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

FDA distribution: “Worldwide distribution - US Nationwide (there was government and military distribution) and the countries of Australia and Singapore.” States read from FDA’s own wording; “not listed” means the notice does not name it.

Distributed nationwide, and outside the U.S.

Recall timeline

FDA terminated this recall 4.2 years after the firm started it.

1. Firm started the recall: Jul 17, 202012. FDA classified it Class II: Sep 29, 202323. Published in FDA’s Enforcement Report: Oct 11, 202334. FDA terminated the recall: Sep 27, 2024420202024
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report
  4. FDA terminated the recall

Dates from the agency record only; steps without a date are left out.

Similar recalls

Latest medical device recalls

Keep exploring

Where this comes from

The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.

  • Official source: FDA Recall #Z-2657-2023 (July 17, 2020) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2657-2023 to see it in context.
  • Plain-language summary written by qwen3:4b on August 19, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
  • GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.
GovInfoNow is an independent guide. We are not FDA or any government agency. Always confirm details with the official recall.Data: CPSC · FDA · NHTSA · USDA