Software Updates
Senior Member
Joined: Sep 2010
Posts: 3,534
Likes: 2,586
From: Livonia, MI
I found a way to resolve pesky configuration not complete DTC's with ForScan. It is known to appear after software updates for those of us who have modified our as built data. This applies to the ForScan and software update threads, so you might see this as a duplicate post around the web.
If your as built data has been altered and you are seemingly stuck with a persistent U-2100 or similar DTC after an OTA or FRDS update which states: initial configuration not complete, it can be cleared but it takes a few more steps than usual. As built configurations do not need to be returned to default to clear this error.
In ForScan go to > Configuration and programing > Module X Module Configuration (As Built) > Restore All (nothing changes) > Write All > Yes Force Rewrite all current values > Follow on screen steps.
After successful forced as built rewrite > back out of module configuration tab > go to service functions tab > under service procedures select the module(s) you rewrote > perform a module reset action > follow on screen steps.
When done > select the GWM > perform a module reset action > follow on screen steps.
This accomplishes is a forced rewrite of the custom as built data and forced reboot of the module with undesirable DTCs. Rebooting the GWM is simply to ensure the in-vehicle handshake is re-established before final steps.
In ForScan > back out of the service functions tab > go to DTC Tab > Reset DTC's > follow on screen steps.
Initial configuration not complete DTCs for the target ECU will now disappear.
Note uncleared DTC's should prevent future OTA's from completing in target modules as per the WSM. Therefore, it is important to try to clear / resolve DTC's when any are present so that future updates can complete.
If your as built data has been altered and you are seemingly stuck with a persistent U-2100 or similar DTC after an OTA or FRDS update which states: initial configuration not complete, it can be cleared but it takes a few more steps than usual. As built configurations do not need to be returned to default to clear this error.
In ForScan go to > Configuration and programing > Module X Module Configuration (As Built) > Restore All (nothing changes) > Write All > Yes Force Rewrite all current values > Follow on screen steps.
After successful forced as built rewrite > back out of module configuration tab > go to service functions tab > under service procedures select the module(s) you rewrote > perform a module reset action > follow on screen steps.
When done > select the GWM > perform a module reset action > follow on screen steps.
This accomplishes is a forced rewrite of the custom as built data and forced reboot of the module with undesirable DTCs. Rebooting the GWM is simply to ensure the in-vehicle handshake is re-established before final steps.
In ForScan > back out of the service functions tab > go to DTC Tab > Reset DTC's > follow on screen steps.
Initial configuration not complete DTCs for the target ECU will now disappear.
Note uncleared DTC's should prevent future OTA's from completing in target modules as per the WSM. Therefore, it is important to try to clear / resolve DTC's when any are present so that future updates can complete.
Senior Member
Joined: Sep 2010
Posts: 3,534
Likes: 2,586
From: Livonia, MI
So I got 2.8.2 last Thursday and today had to get on the expressway and set cruise and was surprised to see my BlueCruise is now fully active. So can mark me down as another Job 1 2021 truck that got BC from OTA updates. Overall went pretty smooth.
Senior Member
Joined: Mar 2021
Posts: 108
Likes: 45
congrats. 2.82 is next for me. Really hope i get it next few days for road trip coming up.
Senior Member
Joined: Feb 2012
Posts: 3,770
Likes: 2,178
From: SE Michigan
2.8.2 is the last of 6 Power-Up updates required to enable BlueCruise hands-free driving on trucks so equipped.
Senior Member
Joined: Sep 2010
Posts: 3,534
Likes: 2,586
From: Livonia, MI
So as long as you get 2.8.2 2-3 days before your trip you should be set.
I did notice that right after getting 2.8.2 though I could go to connected services and it now said BlueCruise was "Available", but when you clicked to Activate it took you to the site to pay $600 for 3 years. So... don't do that. Just wait for the year to activate.
Junior Member
Joined: Jun 2022
Posts: 10
Likes: 3
First. Thanks to everybody on this thread, especially the folks looking up VINs. It's helping to add clarity to the OTA process.
I'm trying to figure out what software version my truck is on. When I view System Updates > Update Details in my 2021, it says my system is up to date, and that's it. There is no software update version. Is there another way to tell what version I'm on? I was one of the stuck 1.7.1 victims but that has been resolved.
I'm trying to figure out what software version my truck is on. When I view System Updates > Update Details in my 2021, it says my system is up to date, and that's it. There is no software update version. Is there another way to tell what version I'm on? I was one of the stuck 1.7.1 victims but that has been resolved.
Senior Member
Joined: Sep 2010
Posts: 3,534
Likes: 2,586
From: Livonia, MI
If you got 2.8.2 as your first, then you likely already had the others from the factory. There haven't been many OTA updates this year since Ford has been spending most of their efforts on getting existing trucks up to date.
