Being as charitable as humanly possible, this all sounds like a company that is really good at cars failing miserably at software engineering, pretty much from top to bottom.
It's pretty clear that, starting at the top, Ford has some significant development, configuration, testing, and revision control issues. They clearly have not mastered the art of software engineering. Moving down the pipe, it's also clear that the dealer network is pretty good at oil changes, replacing air filters, tires and spark plugs, but simply doesn't have the expertise, tools, or mindset necessary to manage what has essentially become a software product. No surprise, really. Imagine if Ford was responsible for updating the OS on your laptop, using the 'geniuses' (mechanics) at its 'genius bar' (dealerships). Doesn't seem like that would go well.

I know this is no help whatsoever to you guys struggling with these crippling issues, I'm really sorry about that. For what it's worth, I would bet my bottom dollar that all other car companies are struggling with the exact same issues albeit with varying degrees of severity (I would guess that Tesla's issues are somewhat less profound, but there nonetheless). The hell of it is that the market is pushing these companies, with inadequate capabilities, to develop and deploy these "features" with inadequate development or testing and without appropriate configuration and revision control mechanisms in place. It makes me crazy, for example, that Tesla is using the public roadways to beta test its self driving cars, at the expense of its customers and every other user of the roads out there. How many dead Tesla customers is considered "acceptable"?

These are lessons that the software companies have (partially) grappled with over the last couple of decades (who hasn't been the victim of a poorly tested s/w "update"?), the difference in this case is that we're talking about a couple of tons of steel moving down the road under the force of 400+hp engines...a lethal combination.
<rant=off>

 

I left my F-150 with dealer for 10 days. They cant get all updates to work. They said some of them worked but I should try to update remaining at home because they were told it works better?? How do I force an update on my WiFi? Any advice appreciated. 1FTFW1EDXMFB61680

 

That's not the update I wanted to hear.
Even though the campaign is ending the fact that you have had your truck into Ford and they have failed to fix it should require them to keep working to get it repaired past the campaign dates.

 

Your OTA dashboard says 2.7.3 failed three times in June on almost the exact dates that my truck failed 2.7.3 back in June. However, your recent trip to the dealership went a lot better than mine. They got you past that and up to 2.8.1. You got an OTA for 2.8.2 yesterday which failed. Go into your update settings and see if it lets you try to install it again.

As soon as they come across the slightest bit of resistance, they want to give up. No tech wants to be tied up for hours and hours doing updates that if they can't complete, they get paid $0 because without getting my truck up to date, they can't bill Ford not even a penny. My truck was there 4 days and they spent maybe 1.5 hours total time working on it. They updated one module, the second update gave them trouble, and they parked it. If I didn't have access to PTS, my truck would still be there sitting and I would not know any better. It's really pathetic.

 

Thank you for the reply. Why does my truck say 2.7.3 is the latest update, but your info is saying 2.8.1?

 

PTS does not tell me what software version you have. I am ASSUMING you are at 2.8.1 because the OTA update that was pushed to your truck is for 2.8.2 which means you should have 2.8.1 already based on the updates your dealer performed in the past few days.

 

understood. Thank you again

 

Anything the dealer does with FDRS will supersede the last OTA. The thing is, when the dealer updates your truck manually, the truck itself will not recognize that and it will still say it is on the latest update it received via OTA. Your dealer must have gotten you to at least 2.8.1 if you're getting 2.8.2 sent to you. If you can get 2.8.2 to go through, I'm sure your truck will say you have 2.8.2 at that point since you got it via an OTA.

 

Think I discovered a new requirement with the latest OTA update.

Use to be you could allow the truck, when using adaptive cruise, to slow down to zero. When traffic started moving, so did the truck.

Now you have to press resume before it moves off again. I'm ok with this. Just a small thing, but proves you are paying attention.

 

There was a GWM software update that appeared this morning in FDRS and after I completed it an APIM update then appeared in FDRS and I did that also so now I have: