- December 28, 2010
- Reaction score
- City, State
- Russell, Ontario (Ottawa area)
- Year, Model & Trim Level
- 2020 Aviator Reserve
Just did my update. Also not able to complete step 4. Web page unavailable.On step 4 I get the error that Owner.ford.com is temporarily unavailable.
"This website will be or currently is being refreshed.
Some content may not be available. Thank you for your patience during this maintenance period."
I'm using Chrome. I didn't have any problems with steps 1-3. It's only step 4 that doesn't work. I though maybe the problem was that I didn't do all steps in one flow. So I started at step 1 again and went through each step, but again step 4 doesn't work. Just tried it again.Which browser? I get errors using Chrome but Firefox seems to work. I'm just now downloading the update, though.
I got the same result in Firefox.
Here is the response I received when contacting Ford:Has anyone tried to contact Ford over the website issue?
Currently owners are not able to confirm SYNC 3 software updates on the owner website. When connected to an available Wi-Fi network, the update will be confirmed once a Key Cycle is completed. A WiFi signal strength of 4 bars (full strength) with reliable internet service will typically allow SYNC 3 to confirm the update. It may take up to a month to confirm the update due to network conditions/connectivity.
Found this in the Ask Ford section of the website.Has anyone tried to contact Ford over the website issue?
I had an issue reporting a successful update prior to the last one and it must have updated my account via WiFi while the Explorer was parked in the garage since my account showed it was updated.Found this in the Ask Ford section of the website.
Issues Confirming Update on the Owner Site
If you update your SYNC 3 software using a USB, you may not be able to confirm the software update on the Ford Owner website. This is a known issue that we are working to resolve. You may have the option to update your SYNC software through Wi-Fi.
Where in your account do you look for that. I'm not finding anything.I had an issue reporting a successful update prior to the last one and it must have updated my account via WiFi while the Explorer was parked in the garage since my account showed it was updated.
Your thread was merged with this one that should answer your question. You have the latest version.Can't seem to find anything from Ford that states what the latest updated version is for my Sync 3. The car shows Version 3.0 Build: 19205 and shows no update available. However, I have run into issues in the past hence my post. What is the current Version and Build?
Have you tried re-downloading the update package again? Different day? A bad download isn't unheard of and can manifest in a few different ways. LST_ERR05 is thrown when it can't find a package in the script.New user, but familiar with legacy Sync update procedures on my 2011 Escape...
This post concerns the 2017 Explorer Sport w/ Nav, Sync 3 v 3.0 build 18093_PRODUCT:
Attempted to update via owner.ford.com and pulled JR3T-14G381-AS.zip
When attempting to extract (using native win10 file explorer or winrar) I'm prompted with errors on JR3T-14G391-CE.tar.gz and JR3T-14G381-AS.tar.gz (unspecified error 0x80004005 from windows, checksum error from Winarar - corrupt archive).
Obviously, these files didn't make it to USB and I'm assuming caused my LST_ERR05 error code.
I've enjoyed all the color commentary on OTA/Wifi updates and foolishly wasted an hour sitting in the car, trying multiple SSID's only to have JR3T-14G391-CE_1557247163000.TAR.GZ barely make it to about 40%...
I read about the migration of binaries to the new server. Perhaps the files were corrupted? Or are these deliberately flagged to prevent install? This experience has been less than thrilling so far
Day 1 of ownership, so just today for attempts - but yes, have tried downloading about a dozen times/ways. Is there an alternative way to download the packages and reassemble?Have you tried re-downloading the update package again? Different day? A bad download isn't unheard of and can manifest in a few different ways. LST_ERR05 is thrown when it can't find a package in the script.