News for all ENYAQ drivers with software version 4.0 and 4.1
Škoda has launched a new software update – the first one in quite a while and an important step forward. All ENYAQ models running software version 4 will now be updated to version 4.1.2.
While the visible changes are minimal and the infotainment version number remains the same, the update does bring noticeable improvements:
What’s new for ENYAQ models with software version 4.1?
This update is delivered over the air – no workshop visit is required. The rollout campaign starts on April 3, 2025. You can expect the following improvements:
- More stable system performance
- Improved charging reliability
- Technical preparation for future OTA updates
The update is installed in the background and requires no user action. I’ll be receiving the update as well – and I’ll be taking a close look to see whether it makes a difference in daily use.
What’s new for ENYAQ models with software version 4.0?
Drivers of earlier ENYAQ models still running version 4.0 can also look forward to improvements.
Škoda partners are now offering a more comprehensive workshop update to version 4.1:
- Bug fixes for the Intelligent Parking Assistant
- More stable GPS reception (e.g., for vehicle location in the MyŠkoda app)
- Improved 12V battery charging behavior
- Preparation for future OTA updates
The update process takes several hours and can be done during your next service appointment – or sooner, if you request it. Workshop appointments can be scheduled from April 2, 2025. The update is free of charge.
Why an OTA update to a “patch version” like 4.1.2?
Let’s be honest: a real continuation of software 4.x (such as a 4.2 or 4.3) doesn’t make much sense at this point. Version 4 was clearly a transitional generation – an important bridge on the way to software version 5.x.
Let’s recap:
- SW4.0 arrived at the end of 2023, along with the second-generation ENYAQ facelift
- SW4.1 followed just a few months later in early 2024
- And by the model year change in August 2024, SW5 was already shipping
That means software version 4 wasn’t even in production for a full year.
In contrast, we’ve already seen three versions of software 5 on the road:
- SW5.0 for a very short time
- Then SW5.2
- And since early 2025: SW5.4
SW5.4 is now available not only in the ENYAQ Facelift but also for the final batches of pre-facelift models.
This raises an obvious question:
Is VW or Škoda really still actively developing SW4.x – even though SW5.x is already being rolled out? And on top of that, are they still working on SW3? It’s almost certain that they’re already working on version 6. That would mean four major software branches being handled at once.
What we’re seeing on the road is a huge version mess. Even the update rollout for the first-generation ENYAQ is still incomplete. Not all vehicles have been updated to SW3.7 yet.
Based on these observations, I dare say: they are no longer actively working on version 4. The update to 4.1.2 will likely be the last. Anything beyond that would hardly be justifiable from a resource or strategy perspective.
The only logical conclusion: SW5.4 is coming
So I don’t think it’s too far-fetched to say that version 4.1.2 is preparing the ground for a future SW5 update.
Why else would Škoda explicitly mention that this update prepares vehicles with SW4 for upcoming OTA updates?
From everything I’ve read between the lines, it seems unlikely that there will be any further version 4.x releases.
Why do software updates take so long?
This is a topic that comes up again and again in my community – and often with good reason:
“Why do these updates take so long? And why do we get stuck on the same version for ages?”
A quick look back:
- The jump from SW2.0 to SW3.0 took almost two years
- From SW3.0 to SW3.7 took another two years
- SW4.0 arrived in late 2023 – and now, in 2025, we’re seeing the first update
- SW5.0 and 5.2 have been around for a few months, but 5.4 has yet to be officially announced
In the smartphone world, this would be unimaginable – but in the world of automotive software, it’s unfortunately reality.
Why is that?
The reason lies in the domain-based architecture of the MEB platform.
In concrete terms:
- An ENYAQ has dozens of control units, many from different suppliers
- Every update needs approval not only from Škoda, but from each individual supplier
- Sometimes firmware changes are required to enable new functions
- These have to be developed separately – and often weren’t part of the original supplier contracts
- Then everything has to undergo safety checks, compatibility testing, and full end-to-end validation – highly regulated, safety-critical, and complex
Add to that some questionable corporate politics within the VW Group regarding brands – and at times a lack of understanding of what customers really need.
Conclusion
Finally, we’re seeing some movement in the ENYAQ update story. The road ahead is still long – and reliability is still lacking – but this is at least a step in the right direction.
