Interesting, I wonder if anyone else had to do this? I just had the GWM and OBCC update I never did. I never saw my old PCM update pop back up. I did the GWM and APIM and got the 2nd GWM after that. All went well with no issues.So now that we're all getting the ball rolling....It was a naughty PCM update that was keeping the GWM from showing up. I'm told that in addition to whatever dependency issue was created by doing the PCM update (at the time I did it there was no GWM in my list) the PCM was not completely 'reporting' as well, which could have compounded the problem.
I asked somebody on another forum to check something out for me and the result was a 'reset' of my PCM reported version to a previous iteration.
Which made the GWM....and the PCM (again) show up as updates in my list.
![]()
I was advised to do an offline download of the GWM software (no network scan), and then only plug it in afterward...and to do a PMI (and answer "No" to the question about if the original module is installed).
That worked like a charm and after the completion of the GWM update (GWM "-LAD" revision) and the network scan I was bestowed with the precious Sync 640 APIM update, and the naughty PCM update had disappeared from the list (because it was actually already installed).
![]()
Afterward, another GWM showed up and all the packages in that update still showed as "-LAD" except the F188 which flipped over to "-LAE".
All good...another Sync crisis put to rest.
Well I did all of this earlier this morning and apparently after I had done my usual daily VIN check and found nothing, I reached out to the module whisperer on the F-150 forum. That's how I ended up going down this road to get there. I get the first gateway done, come back in to check the forum and find out that the US floodGWM have opened and updates are flowing like mud in CA.Interesting, I wonder if anyone else had to do this? I just had the GWM and OBCC update I never did. I never saw my old PCM update pop back up. I did the GWM and APIM and got the 2nd GWM after that. All went well with no issues.
Consider doing a sync reboot before starting the FDRS process. I had trouble with the car recognizing my USB during an update earlier this year. Forced reboot sync before starting and then USB was good to go.Thanks for all of the responses, it's probably me here, not the software.
I've done USB updates before no problem -- I am trying a different USB drive that I know has worked for me in the past, I'm going to leave my door open this time, and I will be doing an incantation while burning incense bowing to my car for 20 minutes this time.
This method has worked 100% of the time for meWow, I just opened my door to turn the car fully off. Waited my usual minute, watching when the headlight switch turns to off, and then turned the car fully back on, "engine" too. About 3 minutes later, pop up that update has completed.
It's a result of FORScan changes you madeIs this a new setting in the new UI? What does it mean?![]()
Haven’t touched ForscanIt's a result of FORScan changes you made
So there is hope.....my license expires in 90 minutes, but ill keep a close watch on fdrsMy GWM update has just shown up as well - obviously there’s a bit of a satellite delay across the pond this evening ?
Did you do a fresh network scan after the GWM to try and get it to trigger the APIM?GWM module updated to LJ8T-14H021-LAD
But no more modules offered after that, so i guess ill wait a few days