100% Free

No Scanner Needed

Carly logo

samuelkrause1

Golf Hybrid Dead After Service Software Update

My hybrid Golf from 2017 wont start at all after getting it back from service last week. The engine light is flashing and engine fault message appears on the display. No strange noises, it just does not turn over. Could be an ECU issue since they updated the engine software during service. Car only has 50000km on it. Anyone had similar problems after service? Looking for recommendations on what to check before going back to the shop.

4 comment(s)

samuelhartmann9

Had a similar situation with my 2014 Golf GTE hybrid last month. When the engine light started flashing with an engine fault message, it turned out the battery cables were not properly secured after routine service work. The ECU was actually fine, the loose connections were causing inconsistent power delivery to the hybrid system. This triggered the safety protocols, preventing engine start. The symptoms match exactly what you describe, no turnover, just warning lights. The fix required proper cleaning of the battery terminals and correct torque application on the cable connections. Though not a major repair, incorrect battery connections can seriously damage the hybrid system over time due to voltage fluctuations. Before returning to the shop, check: 1. Battery cable connections for tightness 2. Battery terminals for corrosion 3. Check engine codes with a scanner if possible Since your issue started right after service, its likely related to reassembly rather than an actual ECU failure. The computer update they performed should not cause these symptoms if done correctly. Would recommend getting it checked immediately to prevent potential damage to the hybrid components.

samuelkrause1 (Author)

Thanks for sharing that experience. I had a nearly identical issue with my VW after software updates, including the flashing engine light and engine fault warnings. The dealer had apparently not completed the ECU programming sequence properly, leading to fuel injection system errors. After taking it back, they redid the software update and checked all connections. Everything has worked perfectly since then. Very similar to what you described with the battery terminals, it seemed more like a reassembly oversight than a serious mechanical problem. How much did the fix end up costing you? Have you had any recurring issues since they sorted it out? Good to know about these experiences for future reference.

samuelhartmann9

The battery cable repair came to 155€ total and completely resolved my engine fault warnings. No engine control malfunction messages or other issues since they properly secured and cleaned all the connections. The fuel injection and entire electrical system have been working flawlessly for several months now. The engine light problem never returned, confirming it was just those loose battery connections causing the weird behavior. Really glad it was such a straightforward fix rather than a more complex ECU issue. These hybrid systems are quite sensitive to proper electrical connections. Best to have a thorough technician who double-checks all connections after any service work. Getting it fixed promptly definitely prevented any potential long-term damage to the electronics.

samuelkrause1 (Author)

After getting the initial engine fault warnings, I took the car back to the dealer right away. The diagnostic check was free since it was their mistake with the software update. They found the incomplete ECU programming and fixed it under warranty in about 2 hours. The service manager explained that during software updates, the programming sequence needs to complete fully or it can cause engine surge and starting issues. Since fixing the programming glitch, the check engine light has stayed off and the car runs perfectly. No additional charges since it was their error. I learned to always check that all warning lights are clear before leaving the shop after any software work. Also made sure to get documentation of the fix in case any related issues pop up later. Really glad it was just a programming oversight rather than actual mechanical problems.

Join the discussion now: