So, I am also working with the W8 ECU (07D 906 018 AP) and have created a fairly stout file that makes quite an impact on the way these "luxury" engines put down their power. Live-tuning with WinOLS and my UCM100 is flawless, but, when trying to hand over the file to the flash EEPROM the ECU bricks. Checksums are all valid across MPPS, KESS V2, and WinOLS. I even sent the file to a friend across the pond and he has also verified with multiple tools that the checksums are fine. He said I may need to have a manual correction done for this to be flashable. When flashing the file to the ECU has completed, the serial EEPROM (5P08C3) corrupts in response. I can flash the original serial EEPROM data back successfully, and it reads back fine, but once I connect the ECU to a power source the flash communicates with the serial EEPROM and slaps all of the data around... I would really like to be able to drive my car with the file in the ECU instead of only being able to use it over real-time export. I imagine someone will know what wonky trick is needed for yet another odd ME7.1.1 ECU variant giving me trouble.

With the UCM100 I can real-time export a file.

Yes you can real time export the file, and then what? That just writes the file to your HDD.
You still need an emulator for the ECU.

There is no "real time tuning" going on. The UCM100 does not do anything to the ECU.
You have not changed anything at all in the car.

You can not do that with the UCM100.
So are you using an emulator or not?

If not, then all you have "felt" is placebo. That can happen if you don't log anything.

UCM100 does not upload any changes to the ECU or allow you to real time tune anything.
I have developed parts of the UCM100 integration logic together with EVC, so I know exactly what I am talking about.

Your post only makes sense if you mixed up the names of the UCM100 and the OLS300, because what you are describing is OLS300 behaviour.