As of October 2026, three BMW engine computers have an instant EWS-delete path here, each at $150 and each pinned to one verified software: Siemens MS43 on software ca430064, Siemens MS45 on DME part 6577365, and Bosch ME7.2 on part 7506366. Anything else — a different software version, a different part number, a family we do not list — is refused before payment and routed to mail-in at $250 or to the specialist network.
Our MS43 guide covers the six-cylinder M54 computer in detail. This post is about the two that joined it, why each is locked as tightly as it is, and how to tell which computer you are holding before you order anything.
What EWS is, and why a delete exists
EWS is BMW's immobiliser — the initials stand for the German for electronic drive-away protection. In the generations these computers belong to, a separate EWS module reads the transponder in the key and, if it recognises it, releases the starter and exchanges a code with the engine computer, which BMW calls the DME. The DME will crank the engine all day without that exchange. It will not fire it.
That design is sound, and on an original car in good order nobody should want to remove it. The delete exists for the cases where the pairing between the EWS module and the DME can no longer be honoured:
- An engine and its DME have been moved into a chassis that never had the matching EWS module — the classic transplant.
- The EWS module, the key or the ring antenna has failed on an older car and the matched set is no longer obtainable.
- A replacement DME has been fitted and the alignment that would marry it to the car cannot be completed with the tooling available.
In each of those the DME is healthy and the immobiliser is the obstacle. The delete changes the DME so it no longer waits for the release.
The three instant families, side by side
| DME | Part / software | Read size | Checksum handling | Instant price |
|---|---|---|---|---|
| Siemens MS43 | Software ca430064 | 512 KB (524,288 bytes) | None needed | $150 |
| Siemens MS45 | DME part 6577365 (Siemens 5WK93012) | 1 MB (1,048,576 bytes) | None needed | $150 |
| Bosch ME7.2 | Part 7506366 | 512 KB (524,288 bytes) | All ROM checksums corrected for you | $150 |
| Other MS43 software (430037, 430056, 430066, 430069) | — | 512 KB | Correction required, not yet automated | Mail-in $250 |
| MS41 (M52) | — | — | — | Not an immobiliser product yet |
| MS42 | — | — | — | Not in our catalog |
Read the first three rows as three separate products rather than one product with three options. Each was derived and verified independently, and each has its own fingerprint.
ME7.2: the V8 one
Bosch ME7.2 is the engine computer on the later M62 V8, and the instant path is pinned to part 7506366 as fitted to the E39 540i. The upload is a 512 KB read of the external flash.
Two things distinguish it from the others.
First, the returned file has its ROM checksums corrected. ME7.2 verifies its own program against stored checksum values, and a file in which the immobiliser has been patched but the checksums have not been brought into line is a file the computer will reject. The correction is part of the product, not a second step you have to buy or perform.
Second, it carries the strongest evidence of the three. The recipe was validated against a stock read from a second, physically different 540i — a file the recipe was not derived from — and processed it cleanly. That is the test that separates “it worked on one car” from “it works on this software”, and it is why we are comfortable describing ME7.2 as proven independent of the individual car.
MS45: the later six-cylinder one
MS45 is the Siemens generation that followed MS43 on later six-cylinder cars. The instant path is pinned to DME part 6577365 — the label also carries the Siemens number 5WK93012 — and the upload is a 1 MB read of the external flash.
It needs no checksum correction: the file that comes back is ready to write. That is a property of where the change sits in this software, confirmed on a car that ran on the result.
The honest caveat is the evidence tier. MS45 was derived from a single verified pair of files — one car's stock read and the same car running on the processed file. We have not yet validated it against a second car's read the way we have for ME7.2. The fingerprint lock is what makes that acceptable to sell: the calculator will only process a file whose software matches the one we verified, byte for byte in the region that matters. If your MS45 is a different part number or a different software, it is refused, not attempted.
Why every one of these is locked to a fingerprint
The question we get most often about this page is some form of “my DME is the same family, why won't you just try it?”
Because a patch is not a setting. It is a specific change at a specific place in a specific program. The same family name covers many software versions, and in a different version that same place holds something else entirely. Writing the change there does not disable the immobiliser — it corrupts whatever was at that address, and the result can be a computer that no longer runs.
So each calculator takes a fingerprint of the uploaded file before it offers anything. If the fingerprint matches the software we verified, you see a price. If it does not, you see a refusal and the reason, and nothing is charged. Our signed bootloader post deals with a different limit — controllers that verify a cryptographic signature — but the commercial principle is the same one: a service that accepts any upload and takes the money has told you nothing about whether it can do the job.
“We could widen the net tomorrow by removing the fingerprint check, and we would get more orders. We would also get more dead computers. The check is the product.” — File-service desk, ECU Flash Cartel
This is also why MS43 appears in the table twice. Software ca430064 was derived from a verified pair of files and needs no checksum work, so it is instant. Versions 430037, 430056, 430066 and 430069 have a known patch route but need a checksum correction that we have not finished verifying. Until it is, those go through mail-in, where a person does the work and checks the result on the bench.
Telling which DME you have
Do not order by model year. The same body ran different engine computers across markets and build dates, and the label is the only thing that settles it.
Read the label. Photograph the whole thing rather than transcribing it. The BMW part number and the supplier number are both there, and on these families the part number is what the instant path is pinned to. Our M52 and M54 DME identification post walks through the six-cylinder labels, and the general method is in our Bosch label guide.
Check the file size. A 512 KB read is 524,288 bytes; a 1 MB read is 1,048,576. An MS45 read that comes out at half the expected size is a partial read, not a small file.
Let the calculator tell you. Upload is free and the verdict arrives before any payment step. On MS43 the software version is visible in the file itself, which is how the calculator distinguishes ca430064 from its siblings. Our free identifier does the same job if you only want to know what you have.
Getting the read
All three are external-flash reads: the full contents of the flash chip, not a calibration-only read through the diagnostic port. Which access level produces that depends on your tool and the family, and our bench, boot and OBD read methods guide sets out what each level reaches.
The practical rules are the ones that apply to every file we accept. Read on a stable supply. Read twice and confirm the two files are identical. Keep the original somewhere safe before you do anything else with it — it is the only thing that will put the computer back exactly as it was, and our return ECU to stock post explains why that file matters more than the processed one.
If you cannot read it, mail-in is $250 and removes the tooling question entirely.
What a delete does not do
It does not make a replacement DME a matched one. A used computer from another car carries that car's data, and removing the immobiliser check does not rewrite the rest. Our swapped ECU won't start post lists the other reasons a transplanted computer refuses to run, and several of them have nothing to do with EWS.
It does not touch the EWS module. On a car that still has one, the module continues to control the starter through its own circuit. A delete in the DME addresses fuel and spark, not the crank signal.
It is not a tune. Nothing in the fuelling or ignition calibration changes.
And it is not something we can do as a remote session. BMW is not on our session platform list — the eight platforms there are GM, Ford and Lincoln, Nissan and Infiniti, Mazda, Volvo, Toyota and Lexus, VW and Audi, and Chrysler, Dodge, Jeep and Ram. Our brands not covered post sets out what that means for BMW in practice.
If your computer is not on the list
There are three honest routes.
Mail-in bench work, $250. A technician reads the computer, does the work by hand and verifies it. This is the route for the other MS43 software versions and for any DME where the automatic path refuses the file.
The specialist network. Posting a job to our network costs nothing. Operators with different tooling see it and bid, and you pay only if you accept a bid. For a family we do not list at all, this is the fastest way to find out whether anyone credible does.
Keep the matched set. If the EWS module, key and DME from the donor are all available, moving the three together and leaving the immobiliser intact is frequently the better engineering answer. Our engine swap immobiliser guide compares the two approaches.
A worked example
A builder is fitting a later M62 V8 and its ME7.2 computer into an older chassis. The donor car was parted out long ago, so there is no EWS module and no key to move across. The engine cranks and will not fire.
The label on the computer reads 7506366. The builder takes a full external-flash read, checks that it is 524,288 bytes, takes a second read and confirms the two match, and uploads one. The calculator fingerprints the file, recognises the software and offers the product at $150. The returned file has the immobiliser check removed and its ROM checksums corrected, and the builder writes it back with the same tool that took the read.
Now change one detail: the label reads a different part number. The same upload is refused, with the reason given and nothing charged. That builder's next step is mail-in at $250 or a posting on the network, and knowing that before paying is the point of the check.
Ownership and the legal position
We require proof of ownership for any operation that touches an immobiliser chain, on every make, and we decline when it is not provided. Independent repairers have a recognised right of access to security-related procedures — in North America that access is administered through the registry run by NASTF — and the same framework that grants access expects the people using it to know whose car they are working on.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
An immobiliser delete is not an emissions change, and nothing in these files alters what the engine does once it is running. The federal Clean Air Act continues to govern the rest of the calibration and the hardware on the engine, and a transplant brings state registration and inspection rules of its own.
The short version
Three BMW computers have an instant EWS delete at $150: MS43 on software ca430064, MS45 on part 6577365, and ME7.2 on part 7506366. ME7.2 comes back checksum-corrected and has been validated on a second car; MS45 and MS43 need no checksum work. Every one is fingerprint-locked, so an unrecognised file is refused before payment rather than attempted. Other MS43 versions are mail-in at $250, MS42 is not in our catalog, and there is no BMW remote session. Photograph the label, upload the read at the unlock calculators, and take the verdict at face value.