PSdZData doesn't update itself, and E-Sys won't tell you when yours is too old. You find out when a module throws CAFD not found after a dealer visit, or when an option you want to VO code needs newer files. The update takes ten minutes, as long as you follow the one rule people keep breaking.
Based on the F30post threads PSdZData Full vs. Lite and Coding cable and ESYS, psdzdata.
Do You Need to Update?
Not if everything works. Asked whether to update with no error in sight, Almaretto's answer was no: newer E-Sys and PSdZData give you nothing if you can already read and code what you want. E-Sys Launcher is the one thing worth keeping current.
Update when one of these happens:
- E-Sys says CAFD not found, usually after the dealer has programmed the car.
- You want to VO code an option that needs newer files. An owner who wanted Sport Automatic and anti-dazzle high beams asked whether that took newer data, and Frogman's answer was yes.
- You're flashing a module to a newer I-Step. That needs the Full package.
shawnsheridan's rule for all three: your PSdZData has to be the same as or newer than the software in the module.
Is Yours New Enough?
Compare two I-Steps. The car's is in E-Sys under Expert Mode → VCM, Master tab, Read: I-Step (current) is what the car runs now. Our iDrive software guide shows that screen.
Your data's I-Steps are in the Target list of the connection window. Each entry names a chassis and an I-Step, for example F025_17_07_504. If the car's current I-Step is newer than anything in your list, your PSdZData is too old for it.
Delete and Replace, Never Merge
shawnsheridan has said it in reply after reply: delete the existing psdzdata folder in C:\Data and put the new one in its place. Don't merge them. In one owner's case, copying a new version over the old one was exactly what had corrupted the data.
The routine mih222001 used, and it worked first time:
- Close E-Sys and unpack the new PSdZData. Lite is enough for coding (see PSdZData Full vs Lite).
- Delete C:\Data\psdzdata. Want a way back? Move it somewhere outside C:\Data instead.
- Copy the new psdzdata folder to C:\Data, so the path is C:\Data\psdzdata again.
- Start E-Sys and check Options → Settings → Directories: the Data path must be C:\Data.
- Open the connection window. The Target list should now show the newer I-Steps.
Smaller update packs that come out between full releases have their own rules, and the Full vs Lite guide covers those too.
Match E-Sys to the Data
New PSdZData often needs a newer E-Sys. These are the pairings shawnsheridan and atzebmw gave over the years:
| PSdZData | E-Sys | When they said it |
|---|---|---|
| 54.x | 3.24.3 (3.26.1 was already too new) | 2016 |
| 58.x and the later two-digit versions | 3.27.1 | 2016 |
| 4.17.20 and newer | 3.30.0 or newer for CAFD injection and flashing | 2020 |
E-Sys 3.27.1 kept working with newer data for FDL and VO coding. Only CAFD injection and flashing needed 3.30.0, so some owners keep two copies of E-Sys in separate folders. shawnsheridan's advice to one of them: code with 3.27.1, flash and inject with 3.30.0.
Newer isn't automatically better here either. In mih222001's case, Detect CAF for SWE stayed greyed out with E-Sys 3.33.0 and worked as soon as 3.30.0 was installed.
Dots Instead of Names in the FDL Editor
If the FDL editor shows dots or bare numbers like 3000 and 3001 instead of names, new PSdZData won't help. shawnsheridan's explanation: every CAFD in PSdZData has had its descriptions trimmed out, and E-Sys Launcher is what puts them back. So check that you start E-Sys through the Launcher, that the Launcher is up to date, and that it's set to the right car series.
You don't need the Launcher at all for VO coding (atzebmw). For FDL coding the very newest CAFDs, shawnsheridan's options in 2026 were BimmerUtility, E-Sys Ultra or a phone app like BimmerCode.
If the Target List Goes Blank
shawnsheridan's three checks:
- The folder at C:\Data\psdzdata is the psdzdata folder from the PSdZData download.
- Every chassis folder has an empty dist folder, for example C:\Data\psdzdata\mainseries\F020\F020_xx_xx_xxx\odx\dist. Create any that are missing.
- The Data path under Options → Settings → Directories is C:\Data.
Going Back to an Older Version
Same routine in reverse: delete the folder and unpack the older version in its place, as TrickyT put it. Older data may need an older E-Sys too. shawnsheridan's pick for 54.x data was E-Sys 3.24.3.
FAQ
Does updating PSdZData change anything in the car?
No. It only replaces files on the laptop. The car changes when you code or flash, not before.
Lite or Full?
Lite for coding, Full for flashing. The Full vs Lite guide has the details.
The attached one-page PDF has the routine, the version table and the three checks. Or we can update it for you in a remote session.
Credits 
This comes from the F30post threads PSdZData Full vs. Lite, started by benoa in 2013, and Coding cable and ESYS, psdzdata, both still active in 2026. Almost every answer is shawnsheridan's. Thanks also to atzebmw, Almaretto, TrickyT and Frogman, and to mih222001 for writing down the routine that worked.