New Year Service Overdue Bug

[MileHigh]

Anybody check this against the Mayan calendar?

 

[Krabby]

Anybody check this against the Mayan calendar?

If that's the case, we're all f*cked!

 

[Bayford]

My service is at 2,162 days overdue - last reset on Feb 3rd 2025.

Quite nostalgic to get the adult offspring of the Millennium Bug a quarter of a century later.

 

[WanderingSniper]

Just had it serviced a month ago, only a year old. I know we will have to drive to them again, but it would nice if they could fix this without the visit.

 

[Tx246]

1872 days

 

[Jean Mercier]

My build number is 9848, and I still have no service reminder, so I still feel like I am missing out.
What is your build number Jean, I know it is a lot earlier than mine, and if I remember yours is petrol, mine is diesel, you are in Belgium I am in Australia, or are we just special, or has Ineos forgot that we exist.

Steve.

My build number is 1312 and is petrol and the bug forgot me

 

[FlyersFan76]

I am at 1917d as of Thursday. I forgot to check what it said this morning when drove it for the first time this year.

My inspection is due this month and I might as well get an oil change at the same time. Wonder what will happen on Thursday after it is done.

 

[Guy]

2023 Diesel: 1890 days in the morning and 1891 days in the evening (CET)…

 

[Mazeman]

This guy came out on FaceBook and states that Ineos will be coming out with an over-the-air patch to fix the Y2K issue.
Hopefully true.
Facebook Link

 

[Dlucky]

Thank you to the moron software developer at whatever software company that Ineos uses for my new annoying feature after a new year has rolled over /s

service overdue 1899 days

I get it serviced every 5,000km.
View attachment 7917840

Mine is showing 1851 overdue

Thank you to the moron software developer at whatever software company that Ineos uses for my new annoying feature after a new year has rolled over /s

service overdue 1899 days

I get it serviced every 5,000km.
View attachment 7917840

1851 on mine

 

[IslandFalconer]

This guy came out on FaceBook and states that Ineos will be coming out with an over-the-air patch to fix the Y2K issue.
Hopefully true.
Facebook Link

Over the Wi-Fi my ass

 

[Deon]

I got the same thing today, except 1968 days as I clicked over 32,700km.

Looks like it is only affecting AU firmware so far.

Let's have a competition on who gets the highest number.

TALLY (Updated)
Krabby 1492 days
ResponsiblyReckless 1625 days
Chook 1840 days
anti 1841 days
Itsdchz 1841 days, first US car with the pox
BrandonADV 1852 days
TahoeGren 1852 days
Rocky 1856 days
Bjoern 1864 days
Znarfgh 1864 days
PB60 1865 days
Pat-Ard 1868 days
Rok Dr 1869 days
Malkay 1875 days
Sonoranrover 1875 days
linksk9rig 1877 day
BluDawg 1879 days
Shopkeep 1879 days
rabia 1879 days
mji111 1880 days
mji111 1880 days
PNW IG 1881 days
Michael H 1889 days
Robt 1890 days
Chem409 1890 days
Blackwolf 1891 days
Duncan McDonald 1892 days
joejet 1894 days
grnamin 1897 days
TimeosYoc 1899 days
TimeosYoc 1899 days
Korg 1899 days
LPT FSJ 1900 days
GrenADV 1901 days
Green Gren 1903 days
stefan.schaefer.de 1906 days
Grumpy 1906 days
HeavyFoot 1915 days
pedrogb 1915 days
Tom Ireland 1916 days
Jax F1 Dave 1917 days
Old Salt 1919 days
Woody 1919 days
UncleBuck 1924 days
Force Pro 1924 days
Voader O 1925 days
OGrid 1927 days
singlefin 1927 days
Green 1928 days
DrahthaarGuide 1929 days
WhiteBear 1931 days, first car outside ANZ
ecohen2 1932 days
oilpresuure 1933 days
Forefun 1933 days
Happyoldgit 1933 days
DaveB 1935 days
OkGo 1937 days
prezioson 1940 days
NixGrenadier 1940 days
Peterr's neighour 1944 days
ddv 1945 days (Aug 2023)
Tergosa 1946 days
Rudilf 1948 days
Johnb 1950 days
Fred 1950 days
Antgil 1953 days
TheBMcCann 1953 days
Camilondo 1953 days
nr002 1954 days
Knoe 1955 days
rickydoc 1961 days
Peterr 1961 days
Jeremy966 1967 days
Ex-defender driver 1968 days
TheDocAUS 1968 days (Feb 2024)
shekesc 1969 days
SilverNZ 1971 days
Joe B 1971 days
Denis M 1975 days
Augustin 1979 days
Telliottaus 1980 days
rwhitinger's better half 1981 days
OZZA 1987 days
joejet 1989 days
Mohs9 1989 days
MattG 1989 days
Jonnieblaze 1950 days
TJD 1985 days
Phred 1994 days
douggie 1995 days
Isle of Wight Paul 1996 days
Phud 1996 days
Des Mattes 2003 days
Glen 2007 days
Badger4x4 2007 days
Adam 2007 days
Baron van T 2009 days
Tomdoc 2016 days
gratefuldiver 2021 days
Silverjay 2022 days
theox 2024 days
Chris Hilton 2024 days
Tony H 2025 days
SaudiGR 2026 days
Sylvan 2032 days
Landmannn 2044 days
Oscar786 2045 days
acky 2048 days
n545ca 2050 days
Logsplitter 2051 days
Commodore 2057 days
NeoGTi 2057 days
HelgeL 2059 days
Greasemonkey 2059 days
SD Jeff 2063 days
Keato 2069 days
Lollo050968 2074 days
HessenHUnter 2081 days
Citori21 2081 days
bakepl 2082 days
MurphyMurph 2085 days
McPharmerII 2088 days
Barney 2091 days
Wile E Coyote 2095 days
DrewB 2096 days
Dschubba 2097 days
Stu Barnes 2097 days
Manuel4x4 2106 days
Mazeman 2107 days
Jork 2113 days
KlasN 2123 days
Wueste 2123 days
Brock63 2124 days
Tazzieman 2137 days
skinny tom 2139 days
Tenac loaner 2139 days
Phobiac 2141 days
archerwolf 2146 days
pipo 2149 days
Skymark 2156 days
ADVAW8S 2159 days
Ever Pragmatic 2141 days
StKesseler 2171
slukell 2175 days
Emil 2190 days
emax 2233 days
bigleonski 2250 days
Ron50 2253 days
Torc Steel 2277 days
Clark Kent 2367 days
C-Mack 2458 days
Jorda 2503 days
DeepCJ7 2651 days
mirwantandyo 2668 days
rwhitinger 6410 days

Deon 1893 days

Steve B, baders and Jean Mercier no alert.

INEOS has acknowledged the issue here.

The numbers seem very random. The only thing I can see, is the date is before each car was even made - over 5 years ago. EDIT: every number is 4 digits and all are above 1800.

 

[Jean Mercier]

My build number is 1312 and is petrol and the bug forgot me

In fact, perhaps one interesting thing: I got a "head unit" update about one year ago. I don't really know what it is. Somebody on the forum mentioned this too, but I don't remember if he had the bug or not. But this is possibly also a possible difference.

I had also during more than one year the service warning on, even after reset, and it only stopped after the head unit update.

Not sure, but perhaps related

 

[Jean Mercier]

Over the Wi-Fi my ass

I agree with you, most improbable

 

[Eric]

In fact, perhaps one interesting thing: I got a "head unit" update about one year ago. I don't really know what it is. Somebody on the forum mentioned this too, but I don't remember if he had the bug or not. But this is possibly also a possible difference.

I had also during more than one year the service warning on, even after reset, and it only stopped after the head unit update.

Not sure, but perhaps related

I had the head unit update @jean as well, but I have the 2026 bug

 

[Blackwolf]

This guy came out on FaceBook and states that Ineos will be coming out with an over-the-air patch to fix the Y2K issue.
Hopefully true.
Facebook Link

They'll have to deliver an over-the-air capability first, and it would be hard to do that over-the-air.

 

[Tazzieman]

I got a "head unit" update about one year ago

I probably need one too. I post a lot of rubbish here

 

[[ Adam ]]

This guy came out on FaceBook and states that Ineos will be coming out with an over-the-air patch to fix the Y2K issue.
Hopefully true.
Facebook Link

Considering there is no OTA capability in the grenadier, I find this unlikely.

 

[globalgregors]

Kind of nice that we have this to bring us all together for the New Year (1966 Days here).
If this can be fixed in the carpark of an Argentinian winery I’m all set.

 

[bakepl]

On an aside. What I find somewhat amusing is if Ineos had empowered/enabled an owner, DIYér, or other service provider to reset the service reminder - aligning with the advertised DIY philosophy, none of this would likely be an issue. Now I guess it will cost Ineos considerable $$ for a dealer reset/fix and perhaps software update. Hopefully any software writing in process will allow for an owner to reset.