Browse
Log in / Register
Share
(Updated February 18, 2026)
A Texas driver says a fast-food stop turned into an hour-long wait in a McDonald's drive-thru line after her Tesla began a software update without warning. The car locked itself in Park for the entire installation, refusing to shift into Drive or Reverse while the new firmware was written. There was no cancel option, no pause, and no override. It's the latest example of a quirk that Tesla's own documentation quietly confirms: once an over-the-air (OTA) update is in motion, the car runs on its own timeline.
The Texas account joins a long line of similar reports. Over the years, Tesla owners have described being temporarily stranded by software updates in parking garages, at Supercharger stations, in hotel lots, and even in their own driveways. The common thread is simple: a Tesla cannot be driven while an update is installing. The process typically takes 30 to 60 minutes — easily long enough to turn a quick errand into a roadside wait.
The driver said she was waiting in the drive-thru lane when the center display changed to an update progress screen. The car would not shift out of Park. The screen rebooted several times over the next hour while the new software was written to the vehicle's controllers. When the installation completed, the car restarted and normal driving controls returned. There was no option to cancel or delay the install at any point during the process.
Tesla's software update logic requires only one thing: the gear selector must be in Park. If a pending update reaches its scheduled time — or a countdown timer expires — while the car is parked, the installation starts. The system does not check whether the car is at home, plugged in, connected to Wi-Fi, or parked in a McDonald's lane. Park is Park. That's the entire qualification.
Tesla's support documentation tells owners to install updates at home, connected to Wi-Fi, when they can leave the car parked and unoccupied. It also states, plainly, that the vehicle "will not be drivable" during the installation and warns against interrupting the flash. The owner's manual goes further, cautioning that stopping an update midway can leave the car in a condition that requires a service visit. Nothing in the documentation tells drivers where they can or cannot park before an install begins. The only requirement is Park — and a drive-thru lane technically satisfies that.
Most owners don't trigger updates by accident. They trigger them through scheduling. When a new version is available, the Tesla app offers "Install Now" and "Schedule." Drivers who choose a time window often assume the car will wait until they're home, asleep, with the garage door closed. It won't. The timer simply starts the update at the chosen time, regardless of where the car is. A drive-thru at 2 p.m. is just as eligible as a garage at 2 a.m.
Recent Tesla software versions introduced a visible countdown that warns "Software Update Starts in 10 Minutes" and lets the driver tap "Remind Me Later." That's a genuine improvement. But the warning only helps if the driver is in the car when the timer runs out. If the car is parked and locked, the countdown continues and the installation begins without a human confirmation. The Texas incident fits this pattern: an unattended timer converting a parked car into a captive vehicle.
Tesla is not alone in disabling vehicles during OTA updates. Rivian, Ford, and General Motors also require Park before flashing new firmware. But Tesla pushes updates far more frequently than most automakers and lets drivers schedule a time rather than requiring a fresh confirmation at the moment of installation. That combination creates more opportunities for an update to fire in the wrong place at the wrong time.
The National Highway Traffic Safety Administration's complaint database includes multiple Tesla entries involving software updates that made vehicles temporarily undrivable. Some owners report cars that would not shift out of Park, screens frozen on update messages, and in a few cases vehicles that needed a tow because the installation failed or left the car in a boot-loop state. NHTSA has not opened a formal investigation into update-related lockouts, and most complaints end with the car recovering. But the filings show that the Texas drive-thru episode is not an isolated event — and that the frustration is often less about the update itself than about being caught by surprise.
The deeper issue is expectation mismatch. A driver who taps "Schedule" once may forget about the update entirely until the car locks itself down at the worst possible moment. A driver who ignores a "Remind Me Later" prompt may run out of postponements. And a driver who never engaged with the update at all may be caught by a countdown they didn't know existed. Tesla's documentation covers the mechanical rules, but the real-world experience leaves owners surprised — and waiting.
The McDonald's drive-thru incident shows what happens when a software-defined vehicle follows a software-defined schedule. Tesla's updates are frequent, feature-rich, and generally smooth — but they come with a hard rule: once the installation starts, the car is unavailable until it finishes. Until Tesla changes that rule, owners are better off handling every update at home, at night, in Park, with the charger plugged in and nowhere to be. The alternative is sitting in a drive-thru watching a progress bar instead of eating lunch.
