EV Software Defects and Over-the-Air Updates: When a Software Car Is a Lemon

A modern electric vehicle is a computer on wheels, and its software runs everything — the touchscreen, the instrument cluster, the driver-assistance systems, the charging logic, even the door handles on some models. When that software fails, the car fails in ways a wrench cannot reach: a black or frozen screen, an instrument panel that won't boot, features that disappear, an over-the-air update that bricks a function instead of fixing it. In California, software defects are covered by the lemon law just like a bad transmission.

The Song-Beverly Consumer Warranty Act does not distinguish between a mechanical defect and a software one. If a software defect substantially impairs your EV's use, value, or safety and the manufacturer cannot repair it after a reasonable number of attempts, you may be entitled to a buyback, a replacement, or a cash settlement, with the manufacturer paying your attorney fees.

The problem with "we'll fix it in an update"

Automakers increasingly promise that software problems will be resolved in a future over-the-air update. Sometimes they are. But an update that never arrives, arrives and doesn't fix the problem, or fixes one thing and breaks another is not a repair — it is a deferral. The lemon law asks whether the manufacturer actually fixed the defect within a reasonable number of attempts, and a string of updates that leave the same problem in place is exactly the failed-repair pattern the law addresses. "It'll be fixed in the next update" is not a defense if the update never delivers.

These are not edge cases. The Chevrolet Blazer EV's launch was so troubled by software failures — frozen screens, resets, charging bugs, disabled functions — that GM issued a stop-sale for weeks while it rewrote the code. Polestar recalled the Polestar 2 rearview camera multiple times over a software synchronization fault, with earlier fixes deemed insufficient. Owners of Rivian, Lucid, and many other software-heavy EVs report screens, driver-assist systems, and controls that fail and return after updates. The pattern is what matters, not the badge.

When a software defect crosses the line

Not every glitch is a lemon — a one-time reboot that never recurs is not a claim. But when a software defect substantially impairs the car and keeps coming back after repeated updates and dealer visits, or when it disables something safety-related like the rearview camera or driver-assistance features, it can absolutely support a claim. The same is true when the car spends significant time out of service waiting on a software fix that keeps slipping.

What to do about a software defect

• Report every occurrence to the dealer and get a repair order — even when the "fix" is just another update.
• Keep a log of which software version you were on when the problem happened, and whether each update helped.
• Screenshot or photograph error messages, frozen screens, and disabled features with dates.
• Note anything safety-related that failed — camera, driver assistance, warnings.
• Get a free case review if updates keep failing to resolve the problem.

And the 18-month / 18,000-mile figure is a presumption period, not a deadline — software defects often persist across many months and updates, and missing that window costs you an automatic shortcut, not your claim.