Honda and Acura drivers complained that on January 1, 2022, the on-board clocks of standard navigators or multimedia systems of ten-year-old or older cars reset the date and time to January 1, 2002 2:00 (4:00 or 12:00) without the possibility of changing back. Reconfiguration manually does not help - the clock is reset to incorrect parameters again.
Advanced users said that in some cases they were helped by rolling back the media firmware update to an older version.
The watch has gone astray on many older Honda, including the Pilot, Odyssey, CRV, Ridgeline, Odyssey, as well as Acura MDX, RDX, CSX, TL and other models.
Acura technical support said that the problem affected many cars from 2008 to 2013. The manufacturer is aware of the incident, but will release an update to fix the bug, at best, only in August.
Honda proposed, as a temporary measure, to disconnect the negative terminal of the battery 15 minutes before the current default time and then turn on the power back as close to the current clock as possible, so that at least the time was correct in the car. Later, this instruction was updated: disconnect the battery at about 12:40 for about 15 minutes, then reconnect the battery a few minutes before 13:00, at exactly 13:00, you must turn on the ignition for the first click of the key (then the radio will be energized). Honda promises that then the time should be correctly set through the data from the GPS, but this may take some time during which the ignition cannot be turned off.
Some drivers were sympathetic to the situation and are waiting for the manufacturers to update the firmware against this bug for their cars. One Acura owner even explained that after the new year he had to explain to his 18-year-old son about hysteria for fear of Y2K errors that happened before he was born, as he now faced a similar situation in his car.
Previously, Microsoft released a temporary fix in the form of the Reset-ScanEngineVersion.ps1 script to fix an antivirus error on Exchange 2013, 2016 and 2019 servers, due to which, from January 1, 2022, receiving or sending letters was blocked. The reason for the bug is the storage of the current date in the FIP-FS anti-virus scanner in int32, and the value "2 201 010 001" (YYMMDDhhmm) is greater than "2 147 483 647".
bbabo.Net