It turns out that Honda and Acura are facing a 2022 problem bug, commonly known as “Y2K22,” which resets the clocks in their navigation systems to January 1, 2002, with no way to change them.
After January 1, the date in the Acura and Honda navigation systems will automatically change to January 1, 2002 and the time will reset to 12:00, 2:00, 4:00, etc. depending on the model and the region where the car is located.
According to Honda and Acura owners, the Y2K22 bug affects almost all older vehicles, including the Honda Pilot, Odyssey, CRV, Ridgeline, Odyssey, and Acura MDX, RDX, CSX, and TL models.
The cause of the Honda/Acura bug is unknown, but Microsoft Exchange has been hit by the Y2K22 bug, which has frozen email delivery.
The Microsoft bug was caused by the date being stored in an int32 variable that can only hold a maximum value of 2,147,483,647.
But the date 2022 will cause the software to crash because the minimum value at midnight on January 1, 2022 is 2,201,010,001.
The same bug could also affect Honda and Acura vehicles, but Honda customer service says it should be resolved by August 2022, indicating that it could be a different issue.
We are very sorry to hear about the issues you are experiencing with your vehicle.
We have escalated the NAVI clock issue to our engineering team and they have told us that the issue will occur from January 2022 to August 2022, after which it will be fixed automatically
Another owner has also responded in the same way, saying that the problem will be fixed automatically in August 2022.
We are aware of this issue and our engineers are looking into it.
The problem is related to the navigation calendar and will be resolved once the date is in August, but we are looking into measures to fix it faster
It is doubtful that Acura and Honda will force car owners to wait seven months for a fix, and an update to the navigation system is likely to be released to resolve the issue.