The systems in cars are increasingly computerized. Partly as a result, when one of these systems is misbehaving the fix these days is often a software update, or “reflash.” This is especially true when a model, engine, or transmission is in its first year.

Three months ago the Repair Survey started including such reflashes as a separate outcome. At that time I went back through all previously reported repairs and reclassified their outcomes as reflashes where appropriate. And with this quarter’s results I’m no longer including reflashes in the repair trip frequency analysis.

I made this change for a few reasons.

First of all, as repairs go reflashes are quick and easy. A good dealer will perform one in well under an hour. Second, software is virtually designed to be upgraded, and that in cars is no different in this regard. Every time Windows downloads a software update, do you think of it as a repair? Third, because performance improvements are often possible through software, I wouldn’t want to do anything that might discourage manufacturers from developing and offering them. If upgrading powertrain software would significantly increase reported repair rates, manufacturers would likely avoid doing it.

On the other hand, you don’t have to take your computer into the shop to have its software updated. Instead, you can generally download a patch off the Internet, or one might even download automatically.

Could this also happen in cars? Brendan Moore of AutoSavant recently suggested to me that GM and others would be wise to start performing nav system data updates through OnStar and other such telematics systems. This will become possible as nav systems start storing their data on hard drivers rather than DVDs.

Which made me realize: the same could be done with the various computer systems in the car. If updated software was developed, it could be automatically downloaded and installed whenever the car was not being driven.