Honda and Acura cars have been hit by a year 2022 error, aka Y2K22, which resets the navigation system’s clock to January 1, 2002, without being able to change it.
From January 1, the date on the Acura and Honda navigation system automatically changes to January 1, 2002, with the time reset to 12:00, 2:00, 4:00 or other times based on the model or possibly the region the car is located.
Honda and Acura car owners report that the Y2K22 bug affects almost all older cars, including Honda Pilot, Odyssey, CRV, Ridgeline, Odyssey and Acura MDX, RDX, CSX and TL models.
Although it is unclear what is causing the Honda / Acura error, Microsoft Exchange was hit last weekend by a Y2K22 error that froze the delivery of email.
Microsoft’s error was caused by the date being stored in an int32 variable that can only contain a maximum value of 2,147,483,647. Dates in 2022, however, have a minimum value of 2,201,010,001 for January 1, 2022 at midnight, causing the software to crash.
The same flaw may affect Honda and Acura cars, but Honda’s customer service has said it should fix itself in August 2022, indicating that it may be another problem.
“Yes, we are so sad about the problem you are experiencing with your vehicle. We have escalated the NAVI clock problem to our engineering team and they have informed us that you will be experiencing a problem from January 2022 to August 2022, and then it will auto-correct, “Honda’s customer support told a car owner.
Another Honda owner received a similar response that the issue will be automatically fixed in August 2022.
“We are aware of the problem, our engineers are investigating it. They have advised that it has something to do with the navi calendar and that it will resolve itself when the date rolls over in August, but they are looking for a countermeasure to fix it before, “customer support told another owner.
It is doubtful that Acura and Honda will force a car owner to wait seven months for a fix, and an update to the navigation system is likely to be released to resolve the issue.
BleepingComputer has contacted Acura and Honda to learn more about the bug and how they plan to fix it, but has not heard back.
Thanks Aristides for the tip!