I have not seen this mentioned, but towing season is around the corner for many of us (if not started already) and this recall has to do with losing lights and brakes on your trailer due to loss of truck and trailer connectivity. It’s a software update, dealers have it. Don’t wait until you are headed out. Safe travels!

 

If Ford doesn't have the OTA ready to push by then, FDRS is ready but not OTA, I'm going to have them do it when they finally allow us to schedule to have the driveshaft inspected. First tow with the new truck is slated for April.

 

After reading these two posts, I called my local Ford dealer to schedule a visit to get this taken care of. He is sending a mobile truck to my house this Monday to take care of it. I don't even have to drive to the dealership.

 

My truck is going in tomorrow for an unrelated brake warning light in the cluster. Apparently this trailer module recall will be done while it's there.
I did get a notice for the recall on FordPass.

 

Had my 2023 F350 reprogrammed 3/24/26 via mobile tech. You may want to hold off on this reprogramming. Took the truck over to my 5th wheel today to check out any changes post reprogramming, Prior info: I never had any problems connecting or towing either my previous 33ft travel trailer or my new 5th wheel trailer. Now back to the issue at hand. I backed the truck up far enough to connect the 7 pin and the Ford rear camera connector. The truck gave me the usual "Blind Spot and Cross-Traffic deactivated Trailer attached" message. Now, after the reprogram I also get this: "Trailer Blind Spot AUX sensor fault Blind Spot deactivated See Trailer Blind Spot aux manual". I no longer have the camera picture on the touch screen when I activate either turn signals. All of my custom screen settings were gone, warning chimes are loud and different and all my Diesel gauges are missing.
Also a couple times shortly after starting the truck, an incredibly LOUD screech/pop/crackle sound emitted from the audio system (speakers). I grabbed the volume **** and turned down the volume, only to discover it showed "0" for volume status. I turned the **** either way and it didn't change the volume number, always zero "0". I changed stations, powered off the radio, shut off the truck, restarted the truck. 3 out of 4 times the same sound happened. I disconnected, re-connected the plugs from the trailer with no change of problems. I even deleted my 5th wheel configuration and recreated it. I even created an new travel trailer profile (bumper pull). I adjusted trailer parameters (Type, width, length, weight, height) and still no change. My side mirror cameras work when I select the button to view all the different camera angles (hitch, bed, front both sides etc) but not using the turn signal. The option to activate it under settings is grayed out. I called my Ford dealer who dispatched the original tech. They are digging for answers and will call me back on what needs to be done. Either dispatching another field service tech or me bringing the truck in for an investigation. I never had any problems towing, disconnect messages or any sensor failures.

 

I had the recall done yesterday while the truck was in for a brake issue. The brake issue ended up being a vacuum booster sensor. Fortunately they had one in stock and took care of it.
I never had any module communication problems when towing trailer so I don't know if that software update fixed anything or not. However, somewhere in the forum I saw a post about a TSB that somehow restored the black box in the center of the screen when rearview cameras are accessed via the dash button. I specifically told them not to perform that TSB if it came up. I checked the cameras this morning and sure enough, the black box is there. So I'll be getting into FORScan today to remove it again.

 

mine was done today as got first oil change on my 26 xl, dealer knew about it without having to say anything and they just said it will be done while it's in getting oil change, when i got it back the drivers door window didn't one touch up and it would power down to half way point when it hit the top so i turned around and they had to do some more stuff to correct whatever door module stuff they didn't finalize properly, all tickity boo now though...

 

I had this recall done a couple of weeks ago and towed the 5th wheel a couple of days afterwards. I noticed no changes or issues by those mentioned by others.

 

Every now and then my "smart" windows will do as yours did. No reason why that I can see. There's a relearn procedure and that puts them right again.

 

I'm about to install a brake controller in my 25 STX. Can I get the dealer to enable the controller while doing the reprograming? Hope so, I don't have Forscan and that would kill two birds with one stone.

 

I experienced the same after the update but with the passenger window. Never had an issue before, but that afternoon after the mobile tech did the recalls I had an issue with bounce back of the front passenger window. Followed the reset procedure to recalibrate and no problems after that. Something in the reprogramming must cause this glitch.

 

I’m driving my ‘26 F450 KR out of state sans trailer. A couple days ago the screen popped up indicating the OTA had taken place. So far, not seeing any issues. A bit antsy wanting to hook up to my 5th wheel.

Side gripe - my wife has a 2023 LR Defender. It warns you about a pending OTA update. I prefer not to be surprised, Ford.

 

Are you sure it was for the trailer brake module and not the TCU-telematics control unit? There has been a recent TCU update taking place. If it was actually the TCM trailer brake control module, this would be the first OTA for it I’ve heard of.

 

I was also somehow under the impression that this trailer module update had to be dealer performed, not OTA.
I received notice for it in the mail a few days ago. But I tossed it without reading very closely because I had the update performed before the notice arrived.

 

Mine gets done tomorrow at the dealer, I will be sure to check the window bounce back afterwards. For those that had that issue was it constant or just once in a while?