There is no way to provide a time for the APIM since so many are having issues, mine didn't complete until the following morning after sitting all night with the USB stick still in. The others however, have been fine. Here's an updated doc you can print to keep at your side when doing the...
The APIM may give you issues like a few of us had... just post back here if it happens and we'll help through it.
Edit: After the APIM update you may get a GWM update.
Not too bad... set your battery charger/maintainer to 10amps. Leave the APIM last. Note, the GSM will be there even after the update so don't be concerned.
Parsing my JSON file this caught my attention for the APIM:
code 6005
source "ORFIN"
details "Hardware found but no matching Strategy found for the following dids and softwarePartNumbers [F188 : MU54-AA T-14G676-EG]. "
nodeAddress "7D0"
That just means they are disregarding the last failed OTA but the corruption issue may affect the OTA's and until someone with the corrupted data gets an OTA it's a wait and see game.
Nothing yet and I did my updates after the 2.3.0 OTA failed so I'm not sure if Ford saw that failed OTA and may not be pushing 2.4.1 to my truck or if the corrupted data or even both is stopping it. I'm hoping to see another FDRS update within the next few days and if it happens, I'll be jumping...
I don't think it's affecting the modules but, the AsBuilt shows the same issues and would probably prevent any OTA's being pushed to us due to the corruption.