“Drive Mode not available”

[MacherAWD]

I actually haven't seen this error in a very long time.

Happened to me 4 times yesterday. Hadnt happened in weeks prior. Who knows.

Sponsored

 

[mkhuffman]

I actually haven't seen this error in a very long time.

Same here. And I can only remember getting it two times, ever.

 

[phil]

It was interesting, on my 21 GT with all updates applied, I was getting it all the time, at least twice a day. But now on my 22 GTPE with NO software updates, I haven't gotten it at all. I go into the dealership next week for them to update everything, it will be interesting to see if I start getting it once everything is up to date.

Are you sure you want the updates? I know I don't.

 

[RKinWA]

Are you sure you want the updates? I know I don't.

They are new things I do want though I belive my current Verdon is 4.0.22

 

[phil]

They are new things I do want though I belive my current Verdon is 4.0.22

I am on 3.5.2. The only new thing I want is the new control to turn on the backup camera. But it's not worth the risk of phone-key problems, settings getting wiped out, drive mode not available, and whatever other hiccups sometimes happen with the power ups.

I'm quitting while I'm ahead.

 

[OH2AZ2OH]

Happened to me 4 times yesterday. Hadnt happened in weeks prior. Who knows.

Happened to me 4 times today on my outbound trip and once on my return trip. I don't recall this happening to me ever before.

This was my longest drive after getting Priority Update 23-PU0314-CM-LAT on Jul 5.

 

[Calgary MACH E]

We are seeing this issue on ours every so often. Happened today.

 

[dml105]

I'm strting to see "Drive mode not available" on any drive over say 30 miles. Has anyone figured out what this is? The dealer says the car is not providing any codes.

 

[macchiaz-o]

I'm strting to see "Drive mode not available" on any drive over say 30 miles. Has anyone figured out what this is? The dealer says the car is not providing any codes.

It's a software glitch and the corrective software hasn't been released to us yet.

 

[tomterky]

I have the same thing. I noticed this started when the Alexa update was first put into Sync. I am not saying it is Alexa related, but it started right around when that downloaded to the car. I have a job 1 AWD/STD, 01/09/2021 build date.

 

[Ford Motor Company]

I have the same thing. I noticed this started when the Alexa update was first put into Sync. I am not saying it is Alexa related, but it started right around when that downloaded to the car. I have a job 1 AWD/STD, 01/09/2021 build date.

Hi there! Will you send us a message with your VIN and your local Ford dealer? I can look into things on my end.

 

[Logal727]

I have the same thing. I noticed this started when the Alexa update was first put into Sync. I am not saying it is Alexa related, but it started right around when that downloaded to the car. I have a job 1 AWD/STD, 01/09/2021 build date.

please read the rest of the thread, it's a known issue and we're waiting on a software fix, no need to take it to dealer.

 

[mkhuffman]

I have the same thing. I noticed this started when the Alexa update was first put into Sync. I am not saying it is Alexa related, but it started right around when that downloaded to the car. I have a job 1 AWD/STD, 01/09/2021 build date.

Alexa is definitely the cause.

 

[Muse]

I came here to find answers, alas. I've only started seeing the drive mode error this yr, and it has happened only a handful (<10) of times on seemingly random occasions, hot weather, cold weather, from garage, from parking, going slow, going fast. Happened just yesterday. No idea what triggers it. Switching car off and on clears it up.

 

[mkhuffman]

I came here to find answers, alas. I've only started seeing the drive mode error this yr, and it has happened only a handful (<10) of times on seemingly random occasions, hot weather, cold weather, from garage, from parking, going slow, going fast. Happened just yesterday. No idea what triggers it. Switching car off and on clears it up.

I believe it was reported earlier in this thread that it is a known software bug. So it will eventually be fixed via an OTA update.

Sponsored