OBD-II fault code

U0100: Lost Communication With Engine Control Module

Safe to drive?

Drive with care — fix it soon

If it runs: minimal, gentle trips only — communication faults are intermittent by nature and can escalate to a stall or no-start without notice. If it already won't start, that decision has made itself.

U0100: Lost Communication With Engine Control Module — illustration

What U0100 means

The car's modules talk constantly over a shared network (CAN bus); U0100 means other modules stopped hearing from the engine computer. It's a network fault, not an engine fault — although what it disables can be dramatic, up to a car that cranks and won't start.

What you’ll notice

  • Multiple warning lights at once
  • No-start or stalling in worse cases
  • Gauges dropping dead or misbehaving
  • Symptoms that flicker with bumps or damp weather

Likely causes and repair cost

Broad US independent-shop bands, parts and labour.

Power or ground fault at the engine module — fuses, corroded grounds
$20–$250
CAN bus wiring damage — chafe, water in a connector, rodents
$100–$500 (mostly diagnosis time)
The engine module itself failing (the least common, most quoted)
$500–$1,500

Can you drive with U0100?

If it runs: minimal, gentle trips only — communication faults are intermittent by nature and can escalate to a stall or no-start without notice. If it already won't start, that decision has made itself.

The misdiagnosis to avoid

Where the money goes wrong

Buying a module for a wiring fault. U-codes tempt the biggest-part diagnosis, but the module is the last suspect, not the first: its power feeds, grounds, and the bus wiring cause the majority of these — often at a corroded connector a methodical hour finds. Module replacement also usually needs programming; that quote deserves the full rule-out list behind it.

Not sure this matches your car?

Describe what it’s doing in your own words and the symptom checker gives you a safe-to-drive verdict, ranked causes with costs, and notes to take to the shop — free, no sign-up.

Advertisement

Read the code yourself

Affiliate links — we may earn a commission at no extra cost to you. How this works.

Diagnostics~$25

ANCEL AD310 Classic OBD2 Scanner

The glovebox tool. Wired, no app, no pairing, no batteries — plug it in and it reads and clears engine codes. This is the one that saves you a diagnostic fee the first time the check engine light comes on. Its limits are honest: engine codes only, no ABS or airbag, no live graphing.

Best for: Anyone who just wants to know what the light means

Check price on Amazon
Diagnostics~$100

BlueDriver Bluetooth Pro OBD2 Scanner

Pairs with your phone and reads far more than engine codes — ABS, airbag, transmission and HVAC on most vehicles — plus live data. The real feature is the repair reports, which map a code to the fixes that most often resolved it on your specific year, make, model and engine. No subscription.

Best for: Owners keeping a car past warranty, or checking used cars

Check price on Amazon
Diagnostics~$130

OBDLink MX+ Bluetooth OBD2 Adapter

The enthusiast pick. Faster live data than most dongles and it works with a wide range of third-party apps, which matters if you want custom dashboards or logging. Well regarded for connection stability and for not draining the battery when left plugged in.

Best for: People who want live data and app flexibility

Check price on Amazon

Questions people ask

Why do these faults come and go with weather and bumps?

Because their usual cause is physical: a chafed wire touching at some suspension positions, moisture bridging a connector when humid. The fault moves with the flaw. That intermittency — infuriating to experience — is itself diagnostic: it says 'connection,' not 'component.'

Multiple U-codes at once — is everything broken?

The opposite, usually: when the shared bus itself is damaged, every module logs a lost-comms code about the others simultaneously. A wall of U-codes is a strong signature of one network-level fault — a single wiring or power issue — rather than mass module death.