Search results

I don't know if this IPMA problem was why they updated FDRS only two days after the previous revision was released. But if you initially tried updating with 39.6.2 you may want to try it again after updating to 39.6.3.

I noticed this when I saw the little alert thing in the top right corner this morning. I guess I need to install the newer one now. I did the IPMA on my Lightning and Mach-E using the 38.5.7 revision of FDRS about a month ago and had no problems on either of those. This is the IPMA update that...

The application manifest for that IPMA update in your available list shows different values for software and strategy than what FDRS says you have now. So I don't think the update took.

Well going from 38.5.7 straight to 39.6.2 is a clue that they've been riding the strugglebus. And a day later we're now at 39.6.3? Yeah..not good.

Is this the fix for the one that made the speakers pop everytime you opened one of the doors or the tailgate after unlocking? Mine still does that.

Strange that they jumped to not only a new major rev (38 to 39) but then all the way to 39.6.2 One can only imagine all the reasons all those other minor revisions in between were scrapped :unsure: FDRS code team hard at work!

I didn't know "Win10 mode" was a thing. I remember "XP mode" on Win7 but didn't know they were still doing compatibility modes on Win11.

Wow..so that's interesting...so other posters on the Lightning and MME sites reported that FDRS worked fine on their Win11 laptops prior to the R38 release (as recently as two months ago). So with the release of R38 trying to run it on Win11 is now a hard "No" I guess? I'm still on Win10...

I'm in FDRS right now. Works fine. And as far as installing an older version...alternatively you can install the newest version just make sure you tick the box to delete user data during the install and it will all start working again.

Well it was wrong for both of my vehicles too...it was out of date the week after it came out when we both got our APIMs updated...but it was probably accurate the day it was released (on the 19th).

GSB 23-7146 was posted to the MME forum thread today by one of our outstanding smart folks and it concerns how to determine what the most current version of Sync 4 is for various platforms. Here's the link. And here's a link to bookmark so you can keep track of the chart and view the changes...

And I thought it was just me.

No, but "Clear and Retest" will usually.

There have been instances that I'm aware of where the gateway update and the PCM updates had/have a dependency relationship such that if they are not updated in a certain sequence then it can cause problems. There's a recent case that come to mind, the first being at the beginning of this year...

And this showed up this morning on the FDRS login/message page:

Mine does the "pop" everytime I open a door or tailgate after it's been locked. Wish I'd never done that DSP update at all now.

Yeah it's working for me now this morning as well. Maybe this is all over with now. (y)

Let us know if pulling a session history from a previous session works for you.

FDRS is experiencing a server issue that's been going on for more than 24hrs. I can log in and do a VIN search to find available software updates but the vehicle history section is broke hard. Here's what you get when you try to view history on any VIN: I'm told by another forum member that...

Anytime you do a PCM update (powertrain in general) it resets the learned values, or so I'm told. So things like shift points etc. would all have to be relearned.