MBUX 2.6 not arriving for my car
Thread Starter
Junior Member
Joined: May 2024
Posts: 18
Likes: 1
MB C300e S206
MBUX 2.6 not arriving for my car
Hi,
I do not understand why I do not receive the MBUX 2.6 update? I have a c300e (estate, year 2023) with NTG7 and no news about the new update. My friends got it a week ago (2023 petrol GLE and an EQA) both running NTG 6 system, yet they got the update. The phone app also indicates that no new version is available. Anyone have any idea what the problem might be? Maybe 2.6 is not coming for the PHEVs?
I do not understand why I do not receive the MBUX 2.6 update? I have a c300e (estate, year 2023) with NTG7 and no news about the new update. My friends got it a week ago (2023 petrol GLE and an EQA) both running NTG 6 system, yet they got the update. The phone app also indicates that no new version is available. Anyone have any idea what the problem might be? Maybe 2.6 is not coming for the PHEVs?
MBWorld God!
Joined: Dec 2019
Posts: 32,222
Likes: 6,281
Hi,
I do not understand why I do not receive the MBUX 2.6 update? I have a c300e (estate, year 2023) with NTG7 and no news about the new update. My friends got it a week ago (2023 petrol GLE and an EQA) both running NTG 6 system, yet they got the update. The phone app also indicates that no new version is available. Anyone have any idea what the problem might be? Maybe 2.6 is not coming for the PHEVs?
I do not understand why I do not receive the MBUX 2.6 update? I have a c300e (estate, year 2023) with NTG7 and no news about the new update. My friends got it a week ago (2023 petrol GLE and an EQA) both running NTG 6 system, yet they got the update. The phone app also indicates that no new version is available. Anyone have any idea what the problem might be? Maybe 2.6 is not coming for the PHEVs?
Last edited by W205C43PFL; Apr 28, 2025 at 08:11 PM.
Thread Starter
Junior Member
Joined: May 2024
Posts: 18
Likes: 1
MB C300e S206
Member
Joined: Nov 2018
Posts: 85
Likes: 13
From: United Kingdom
W206 C300e AMG Line Premium Plus with driver assistance package
My c300e in the uk got it. It took a couple of weeks until it attempted to install and even then it failed and I had to get the dealer to install it last week.
The deployment is staggered and I doubt a dealer will install it manually as it takes 1 or 2 days to do.
The deployment is staggered and I doubt a dealer will install it manually as it takes 1 or 2 days to do.
Trending Topics
MBWorld God!
Joined: Dec 2019
Posts: 32,222
Likes: 6,281
MB World Stories
The Best of Mercedes & AMG
Manual Mercedes? 6 Times Sindelfingen Let Drivers Have All The Fun
Verdad Gallardo
Mercedes SLR McLaren 722 S Is Extremely Rare Example Modified by McLaren
Verdad Gallardo
8 Classic Boxy Mercedes Designs That Have Aged Like Fine Wine
Verdad Gallardo
Flawlessly Restored Mercedes 190E Evo II Heads to Auction
Verdad Gallardo
Electric Mercedes C-Class Unveiled: 11 Things You Need to Know
Verdad Gallardo
Mercedes EQS Gets A Major Update: Everything You Need to Know
Verdad Gallardo
5 Underrated Mercedes-Benz Models That Don't Get the Love They Deserve
Verdad Gallardo
Mercedes 300D Has Pushed Well Past 1 Million Miles and It Ain't Stopping
Verdad Gallardo
10 Most Reliable Mercedes-Benz Models You Can Buy Used
Verdad Gallardo
Junior Member
Joined: Dec 2024
Posts: 58
Likes: 9
W206 C200 4Matic
Looks this is "premium" customer care
MBWorld God!
Joined: Dec 2019
Posts: 32,222
Likes: 6,281
MBWorld God!
Joined: Dec 2019
Posts: 32,222
Likes: 6,281
MBWorld God!
Joined: Dec 2019
Posts: 32,222
Likes: 6,281
I wouldn't say it is the same as how a phone software works but the idea with phone software for example is:
Phase 1, the phone manufacturer decides to release a new software version.
Phase 2. Development of the software
Phase 3. Testing
Phase 4. Bug fixes
Phase 5. Closed Alpha testing
Phase 6. More bug fixes
Phase 7. Public Alpha testing
Phase 8. Even more bug fixing
Phase 9. Closed beta testing
Phase 10. You know the drill
Phase 11. Open beta testing
Phase 12. You know the drill already {
Phase 13. Release candidate
Phase 14. Send to carrier for further testing on their network (android specifically)
Phase 15. Carrier makes changes to software
Phase 16. Sent back to OEM for testing and bug fixes
Phase 17. Give the greenlight to carriers.
Phase 18. Carriers do final testing.
Phase 19. Carriers release the update.
Phase 20. Consumer release is staggered (android specifically) so not every region gets it yet
Phase 21. If no bugs then release to more regions, if bugs are present jump to phase 22.
Phase 22. If there are bugs, pull the update, fix bugs and test again
Phase 23. Send to carrier (android specifically) to test
Phase 24. Carrier send it back to oem
Phase 25. Oem gives green light
Phase 26. Carrier releases update and again staggered, if there are bugs again, repeat phase 20-26 again.
Phase 1, the phone manufacturer decides to release a new software version.
Phase 2. Development of the software
Phase 3. Testing
Phase 4. Bug fixes
Phase 5. Closed Alpha testing
Phase 6. More bug fixes
Phase 7. Public Alpha testing
Phase 8. Even more bug fixing
Phase 9. Closed beta testing
Phase 10. You know the drill
Phase 11. Open beta testing
Phase 12. You know the drill already {
Phase 13. Release candidate
Phase 14. Send to carrier for further testing on their network (android specifically)
Phase 15. Carrier makes changes to software
Phase 16. Sent back to OEM for testing and bug fixes
Phase 17. Give the greenlight to carriers.
Phase 18. Carriers do final testing.
Phase 19. Carriers release the update.
Phase 20. Consumer release is staggered (android specifically) so not every region gets it yet
Phase 21. If no bugs then release to more regions, if bugs are present jump to phase 22.
Phase 22. If there are bugs, pull the update, fix bugs and test again
Phase 23. Send to carrier (android specifically) to test
Phase 24. Carrier send it back to oem
Phase 25. Oem gives green light
Phase 26. Carrier releases update and again staggered, if there are bugs again, repeat phase 20-26 again.
