This might be it...
I first encountered the MEM_ERR03 popup when I tried to install v2.2.17011 over v2.2.16280. I think somebody somewhere didn't see how anyone could attempt to install v2.2.x twice and it creates some unhandled exceptions.

 

I'm imagining there's a Ford programmer somewhere (India? Dearborn?) reading this thread, thinking "Nope", "Ooo, good!", "Not even close", "Good luck with THAT, pal!"



Same with the tribiology engineers who read the threads on 3000 mile oil changes and whether/not the OLM can be believed.

 

Either way, there are a lot of people out there smarter than me. I give you all credit for the reverse-engineering work.

 

I always take that one as a challenge.
Ford engineers (yes I got a response from Michigan) told me there was no way to enable Remote Keyless Entry on my '08 F250 XL if it didn't have the option from the factory.

Enter ForSCAN, and about an hour of looking up 3+ VINs for every option combo I could find... I narrowed the RKE bits down to about 8 possibilities... and it was the first one I tried.

 

2016 XLT Supercrew. Started with Sync 3 version 1.0. Updated using the unofficial files to 2.2 on build 16280_PRODUCT in December. Now trying to updated to 2.3 with the files from Ford. Getting MEM_ERR03 error code. At Ford's request tied a module reset and a master reset. Neither of which corrected the issues.
Everything still seems to be ok, with version 2.2 apart from that I no longer have an Gracenote version.

 

LOL! Right?!

Anyway, a lot of dev is in fact in-house @ Ford in the Dearborn area. They also contract out some infotainment dev. stuffs to local Detroit & Dearborn tech firms, as well as P3 Group out of Germany.

 

Did you have Gracenote before attempting to go from 2.2 to 2.3, or did you lose it during an earlier update?

 

Lost it trying to do the update to 2.3

 

The issue causing MEM_003 errors has been narrowed down to the huge voice control/recognition/prompt software package; not enough space on the 8GB ramdisk on non-nav systems to install it. So you're still running the one that came with 2.2. Some of us are working on a fix for that.

GN can be fixed. Head over here, download v2.2_17011, and follow my HOWTO (assuming you have non-nav):

https://www.f150forum.com/f118/howto...7011-a-398097/

 

So @TexasRebel05 and @ljworcs both had v2.2.16280 installed. But@TexasRebel05 was your v2.2.16280 an unofficial build (I am not familiar with the 2.2 unofficial build, does 16280 essentially indicate an unofficial build)?

@Cuch and @jlworcs 's common link is an unofficial version previously installed, although doesn't look like @Cuch had 2.2.16280..