VW Crafter Start Failure: Bad Switch vs. Hidden Culprits

Had almost the exact same issue with my 2015 VW Transporter TDI. I would turn the key and get inconsistent starting behavior, very similar to what you describe. As someone with basic car maintenance experience, I first thought it was the ignition coil or something more complex. Took it to my regular workshop and turns out it was just a blown fuse related to the ignition system. The whole repair including diagnosis was 52€, which was a relief since I was expecting much worse. The symptoms can point to various issues though, could be the ignition switch, electrical connections, or even fuel system problems. To help diagnose this better, could you share: Does the dashboard light up normally when you turn the key? Are there any warning lights showing? Have you noticed any changes in fuel consumption? Do you get any error codes when scanning? Before spending money on major parts, definitely have the fuses and car electronics checked. In my case, replacing that single fuse solved all the starting problems and rough running issues.

I have 104952KM on the clock. Thanks for your detailed response about the ignition key problems. You raised good points about the dashboard behavior. When I turn the key, all lights come on normally and I dont see any warning indicators. Fuel consumption seems normal and I have not scanned for codes yet. The starter motor seems to crank fine when it does turn over, but the inconsistent starting is really concerning. Its been serviced regularly with the last maintenance done 3 months ago. Looking at the symptoms you described with your vehicle, I should probably get those fuses checked first before replacing more expensive parts. Do you remember which specific fuse was related to your ignition system issues? The engine start problems seem very similar to what you experienced.

Thanks for providing those additional details. In my Transporter, it was fuse 32 (20A) in the main fuse box that controlled the ignition circuit. However, while a blown fuse fixed my issue, your symptoms now sound a bit different from what I experienced. Since your starter motor cranks normally and all dashboard lights work properly when turning the ignition key, this points less toward a simple fuse issue and more toward potential problems with: Faulty ignition coil(s), Worn ignition switch contacts, Loose wiring connections at the ignition switch, Fuel system problems The fact that the engine runs rough when it does start suggests looking at the ignition coils first. A failing ignition coil can cause exactly these symptoms, inconsistent starting and rough running. I would recommend getting a proper diagnostic scan done. When my ignition system acted up later (different issue from the fuse), the scan revealed a failing ignition coil that was causing similar problems. The repair cost was around 180€ for parts and labor. While checking fuses is still a good first step since its quick and cheap, be prepared that you might be dealing with a different underlying issue than what I had initially.

Thanks for your feedback on the potential ignition system problems. The regular servicing should have caught any obvious issues, but these intermittent starting problems can be tricky to diagnose. I will definitely start by checking all the fuses related to the ignition circuit, including fuse 32 that fixed your vehicle. Good point about the ignition coils possibly being the culprit since the engine runs rough after starting. The starter motor does crank normally when I turn the key, which at least eliminates that as a problem. Planning to get a diagnostic scan done this week to check for any error codes before replacing parts. The 180€ repair cost for your ignition coil replacement doesnt sound too bad if that ends up being my issue too. Much better than continuing to drive with unreliable starting and rough running that could leave me stranded. Will update once I know more after the diagnostics. Really helpful to hear about your similar experience, gives me a good starting point for getting this fixed properly.