Features Stopped Working After a Module Was Replaced
A module was replaced, the car drives, and something else has quietly stopped working - the mirrors no longer fold, the tyre pressure display is blank, the trailer lights are dead, a warning light appeared that was never there before. The part is almost certainly fine. What is missing is configuration: the option content that tells a replacement module what equipment this particular car actually has.
As of September 2026 in Dallas-Fort Worth, finishing that configuration runs $250-$400 for a body module written to your VIN, $350-$550 where component protection or similar manufacturer coding is involved, and $150-$300 where the fix is a software update rather than a full configuration. The diagnostic read that tells you which one you need is $90-$150, and it is waived when you book the work.
This page is about how to tell an unfinished job from a broken part - a distinction worth several hundred dollars, and one that a surprising number of shops never explain.
What "configuration" actually means
A module leaving a factory is a generic piece of hardware. It becomes your car's module when three things are written into it.
The VIN. The vehicle identification number ties the module to this car. Many modules will operate without a matching VIN and then fail a later check, or refuse to communicate correctly with a module that does check.
Option content, or variant coding. This is the list of what your car has: heated seats or not, folding mirrors or not, a tow package, rain sensing wipers, tyre pressure monitoring, memory seats, auto headlights. The module cannot detect these. It has to be told.
The security relationship. On any module that touches the immobilizer chain, the key table and the pairing with other modules have to be re-established. On Audi and Volkswagen this appears as component protection; on other makes it has other names and the same effect.
Skip the first and the car may run fine for months and then throw a fault. Skip the second and features disappear one by one, exactly as described above. Skip the third and the car will not start at all - which is at least an honest failure, and the subject of car will not start after an ECU swap.
The four distinct operations behind all this are set out in flash, clone, code and adapt: module programming explained. The distinction matters because a shop that only performs one of them will honestly tell you the module was "programmed" and still leave you here.
The symptom pattern that says configuration, not hardware
Configuration faults have a fingerprint. Look for these:
- The missing features are all optional equipment. Base-model functions work; the extras do not. That is option content, almost every time.
- It has been wrong since the module went in. Nothing degraded. It simply never worked from the moment the part was fitted.
- The dead features have nothing mechanically in common. Folding mirrors and tyre pressure monitoring share no wiring, no fuse and no motor. They share a module that does not know they exist.
- No fault codes point at the dead features themselves. Instead you may see codes about mismatched configuration, an implausible VIN, or a module reporting a variant it should not have.
- Something works only partly. Windows go up but not one-touch; the sunroof runs but has no pinch protection; the remote locks but does not fold the mirrors.
By contrast, a genuinely faulty module tends to fail visibly and completely, set codes that name its own circuits, and behave inconsistently rather than uniformly. That distinction is also the whole subject of BCM symptoms misdiagnosed as key problems.
Where used modules go wrong
A used module is not a blank module. It arrives carrying the donor vehicle's VIN and the donor vehicle's option list. Fitted without configuration, it will confidently run your car as though it were the other one - which is why the classic used-module symptom is not silence but wrong behaviour: features enabled that your car does not have, features missing that it does, and occasionally a warning light for equipment that was never fitted.
Three outcomes are possible, and which one you get is decided by the platform rather than by effort:
- The module accepts a full rewrite. VIN, option content and security relationship all take. This is the good case and it is common on a lot of platforms.
- The module is locked to its donor. Some modules can never be rewritten once they have been married to a vehicle. No amount of equipment changes that, and the honest answer is a different part.
- It appears to work and then does not. A VIN rewrite that takes, followed by a security handshake that fails weeks later, is the worst of the three because the connection to the original work is no longer obvious.
Asking which of these applies before the part is bought is the single highest-value question in this whole process. Our when a used ECU or module genuinely works page covers how that question gets answered.
Make-specific notes worth knowing
GM. Body module configuration is done by VIN, and option content matters more here than most owners expect - a correctly fitted module with the wrong build list produces exactly the missing-features complaint. The related key-side procedures are in our GMC key fob programming guide.
Ford. The smart junction box on many years shares immobilizer duty, so a configuration gap can present as a security symptom rather than a comfort one.
Audi and Volkswagen. Component protection is the whole story. An uncoded module throws a fault the owner then pays twice to clear - once for the module, once for the coding that should have accompanied it.
BMW and Mercedes. Both use coding that is expected as part of any module change rather than as an optional extra. On BMW the footwell module is the common candidate; on Mercedes the signal acquisition modules are.
FCA and 2018-onward vehicles generally. A security gateway sits between a scan tool and any module that accepts writes. It does not prevent the work; it adds an authentication step and time. See security gateway module and key programming.
Land Rover and Jaguar. Coding follows essentially every module change on these platforms, because the body module and the KVM hold the key table between them. Pricing sits in Land Rover and Jaguar key replacement cost.
What a proper finish-the-job visit looks like
- Read what is actually in the module. Stored VIN, coding index, variant, software level. That single read usually explains the whole complaint in a minute or two.
- Compare against the vehicle's own build data. What the car should have, versus what the module believes it has.
- Write the correct configuration. VIN, option content, and any manufacturer coding the platform requires.
- Re-establish the security relationship where the module touches the immobilizer chain, including key registration if applicable.
- Verify each dead feature individually, not just "no faults present". A clean scan is not the same thing as working mirrors.
Steps one and two are the reason we ask you not to authorise another part before someone has read the module you already have.
What it costs in DFW as of September 2026
| Job | Mobile (DFW) | Note |
|---|---|---|
| Diagnostic read of module configuration | $90-$150 | Waived when you book the work |
| Module software flash or update | $150-$300 | Where the fix is software, not configuration |
| Replacement programming, configure to VIN | $250-$400 | The usual answer to missing option content |
| Component protection or equivalent coding only | $350-$550 | Audi and Volkswagen, after a dealer-supplied part |
| Module work including key registration | $200-$450 | When the immobilizer chain is involved |
| ECU reflash or firmware update | $300-$500 | Engine controller, no hardware change |
When it is genuinely not configuration
Be fair to the shop that did the work. Some post-replacement faults are real:
- A connector left unseated or a pin pushed back. Common, quick to find, and nobody's fault but gravity's.
- A fuse pulled during the job and never replaced.
- A pre-existing fault that the old module was masking. Replacing a module sometimes reveals a wiring problem that was always there.
- A genuinely defective replacement part. Rare with new parts, less rare with used ones.
- Work that simply cannot be completed independently on that platform. The honest list is in which car modules need the dealer and which do not.
A read tells you which of these you have in a few minutes, and it is cheaper than any of the guesses.
What to have ready when you call
- Year, make, model and trim, plus the option packages if you know them
- Which module was replaced, and whether the part was new, used, or dealer-supplied
- Exactly which features stopped working, and whether they ever worked after the swap
- Who did the work and whether they said any coding was performed
- Any fault codes you already have, and which module reported them
If you are choosing a shop for the follow-up work rather than going back to the first one, finding local car module programming services sets out what to ask before anyone opens a laptop.
Frequently Asked Questions
Why did my mirrors and tyre pressure display stop working after a module was replaced?
Because the replacement module does not know your car has them. Option content - the list of optional equipment fitted to your specific vehicle - has to be written into the module during configuration. Skip that step and the optional features silently disappear while the basic ones keep working.
Does a replacement module need to be programmed even if it is brand new?
Yes, on almost every modern vehicle. A new module is generic hardware until the VIN, the option content and any security relationship are written into it. "New" and "configured" are two different things, and only the second one makes it your car's module.
Can a used module from the same model work?
Sometimes. It depends entirely on whether that platform allows the donor VIN and option content to be rewritten. Some accept it cleanly, some are permanently locked to the first vehicle they were married to, and some accept the rewrite and then fail a security check later. Ask before the part is bought.
How much does it cost to finish the configuration in DFW?
As of September 2026: $250-$400 to configure a body module to your VIN, $350-$550 where component protection or comparable manufacturer coding is involved, and $150-$300 where a software update is the actual fix. The diagnostic read is $90-$150 and is waived when you book the work.
The shop says the module was programmed. Why are features still missing?
Because "programmed" covers several different operations. A module can be flashed with software and still carry no option content, or be configured for a different equipment list entirely. Ask specifically whether the VIN and the option content were written, and whether the coding was verified against the vehicle's build data afterwards.
Will a scan tool that shows no fault codes prove the job was done right?
No. Missing option content frequently produces no fault codes at all - the module is doing exactly what it was told, which happens to be wrong. Verification means testing each affected feature, not reading a clean scan.
Can this be fixed without going back to the shop that did the work?
Yes. Finishing someone else's configuration is routine work and does not require the original shop's involvement. Bring the details of what was replaced and the read will tell the rest of the story.
Is a warning light that appeared after the swap related?
Very likely. A module configured for equipment the car does not have will look for that equipment and report it missing. That is a configuration symptom rather than a hardware fault, and it usually clears with the correct coding rather than another part.
Get the module read before you buy another part
We read what is actually written in the module you already have, compare it against what your car should be, and finish the job properly - with the diagnostic waived when you book the work. Arlington shop or mobile across Dallas-Fort Worth, seven days a week: (682) 344-1957.
