2025 Mercedes-Benz GLC 350 E 4MATIC

I own a 2025 Mercedes-Benz GLC 350e plug-in hybrid. The vehicle experienced a complete loss of both the digital instrument cluster/display in front of the driver and the center MBUX infotainment display. Both screens remained completely black even after the vehicle was started and placed in READY mode. The vehicle was still capable of being driven, but the driver instrument display was completely unavailable. As a result, I could not see critical information normally provided through the instrument cluster, including vehicle speed, warning messages, system status, and other important vehicle information. At the same time, there was recurring static/electrical-type noise coming through the vehicle’s speakers at regular intervals. The vehicle was shut down, locked, and allowed to power down before being restarted, but this did not restore either display. This is a significant safety concern because the vehicle can remain operational and driveable while the entire driver instrument display is unavailable. A driver should not have to operate a vehicle without access to the instrument cluster or critical warnings. I am reporting this issue to NHTSA because I believe a complete loss of the instrument cluster and center display while the vehicle remains driveable presents a potential safety defect. I request that NHTSA investigate whether this is a recurring problem affecting the 2025 Mercedes-Benz GLC 350e and whether a safety-related remedy or recall is warranted.

NHTSA ID

11765412

Incident

Sep 18, 2026

My 2025 Mercedes-Benz GLC 350e displayed a “48V battery malfunction” warning on or about July 1, 2026, while the vehicle was less than one year old. The vehicle was taken to an authorized Mercedes-Benz dealership and remained there until approximately July 20. Mercedes-Benz USA became involved, and the dealership ultimately stated that the malfunction had been corrected through a software update. The 48V battery was not replaced. I have not received documentation clearly identifying the specific software update, campaign, operation number, underlying failure mechanism, or pre- and post-repair diagnostic results establishing that the reported malfunction was caused and resolved by software. I am therefore unable to determine whether the battery or another component of the 48V system was defective, or whether the warning was merely cleared. In late August, I also heard a new and pronounced whirring sound near the left-front area of the vehicle after charging. A different authorized dealership charged the high-voltage battery to 100%, attempted to reproduce the sound, and found no charging-system fault codes or abnormal noise. It characterized the sound as normal post-charge cooling operation and performed no repair. I am submitting this complaint because of the original 48V malfunction, the lack of documentation identifying exactly what failed and what software remedy was performed, and the possible relevance to a previously closed NHTSA investigation involving Mercedes-Benz battery-related concerns. Please associate this complaint with any applicable closed investigation and evaluate whether this incident constitutes additional relevant field evidence.

NHTSA ID

11761658

Incident

Jul 1, 2026

The car went from 20 miles an hour and 35 miles an hour (happened 2 times) to a sudden hault like hitting a wall. The first time I had to restart the car. The second car, I had to return it to drive. A big X came up on the dashboard. I have owned the car 17 months. Both issues happened in the last 30 days. Nothing beefore. The car has 4415 miles on it. The dealer (Fletcher Jones) was unable to replicate). There was no warning. They told us it was our problem and we could report it to Mercedes Benz which we will do today.

NHTSA ID

11759874

Incident

Aug 21, 2026

The contact owns a 2025 Mercedes-Benz GLC 350E 4Matic. The contact stated that while driving 10 MPH and attempting to park the vehicle, the vehicle unintendedly accelerated. The brake pedal was depressed, but the vehicle failed to respond. The vehicle was uncontrollable and crashed into a fence. The driver’s side mirror, bumper, and door were damaged. The contact stated that the air bags did not deploy. The instrument panel had previously gone black before the crash and the vehicle previously failed to accelerate as needed. There were no injuries sustained. A Police report was filed. The vehicle was taken to the local dealer for two prior software updates. The vehicle was towed to the local dealer but was not diagnosed or repaired. The manufacturer was not contacted. The failure mileage was approximately 9,000.

NHTSA ID

11755841

Incident

Aug 9, 2026

Mileage

9,000 mi

The contact owns a 2025 Mercedes-Benz GLC350E 4MATIC. The contact stated that while driving at 68 MPH, the sunroof glass shattered unexpectedly. The contact was able to pull over, and the vehicle was towed to the nearest dealer. The dealer had not yet diagnosed the vehicle. The vehicle was not repaired. The manufacturer was not made aware of the failure. The failure mileage was approximately 17,500.

NHTSA ID

11750300

Incident

Jul 13, 2026

Mileage

17,500 mi

The contact owns a 2025 Mercedes-Benz GLC350E 4MATIC. The contact stated that the vehicle was repaired under NHTSA Campaign Number: 26V281000 (Electrical System); but the recall repair failed to prevent a failure. The contact stated that while starting the vehicle, the instrument panel display was inoperable. The failure was a recurring failure. The dealer was contacted; however, the vehicle was not diagnosed or repaired. The manufacturer was made aware of the failure. The failure mileage was approximately 12,540.

NHTSA ID

11747977

Incident

Apr 30, 2026

Mileage

12,540 mi

Suspension exhibits excessive bounce/instability over road irregularities, unsafe on uneven pavement, affects steering control. Car available for inspection. Checked by two authorized dealerships, both closed as "operating as designed" without resolving it. Also inspected by manufacturer's Field Service Engineer, same result. Issue began after a phantom braking event — vehicle braked suddenly and unexpectedly on its own while changing lanes at highway speed, no obstruction present, no driver error — also damaged the steering column, since replaced.

NHTSA ID

11747605

Incident

Jan 14, 2026

All screens on dash were black and a clicking sound could be heard I side the vehicle. This has happened four times. Towed vehicle to MB dealer and they did a software update but it keeps happening anyway.

NHTSA ID

11738083

Incident

May 4, 2026

Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!

Complaint Frequent rear view camera flap actuations and/or noise associated. NOTE: Rear view camera functions are NOT affected and still perform in accordance with regulatory requirements. Cause Calibration of the reversing camera is in progress. This is not a malfunction, but an intended system behavior. Remedy An optimization has been implemented to reduce the quantity of rearview camera flap actuations for calibration. Open an XSS case requesting addition of the option code "0O1" (Zero, "O", "1"). Once the code has been added, update and SCN code PARK (N62/*) control unit. Prior to releasing the vehicle, please verify the following: • Rear camera flap when calibrating after a key cycle bus sleep will stay open to 29 MPH and then close. Will re‑open, when calibrating, at 9 MPH.

Complaint Tailgate opens unintentionally. Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double‑clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") • an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the “Lock button", then double‑click the “Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Complaint Traffic sign symbol for "Traffic Sign Assist" is blinking in instrument cluster without obvious cause usually with one of the following scenarios: • Flashing without a speed limit ("‑ ‑"). • Flashing when current vehicle speed is under speed limit. • Flashing between US speed limit symbol and European speed limit symbol. NOTE: • Verify that the concern falls under one of the attachment videos. If not, then it is outside of the scope of this LI. • This also does not cover "Traffic Sign Inoperative" messages on the instrument cluster. Cause There are two identified reasons for this concern: 1. Country code information stored incorrectly at a particular geographic latitude range. 2. Incorrect reference data when the vehicle is started and a GPS signal is not immediately available. Remedy Update head unit software to latest version and the re‑check function in the same location. If vehicle is still exhibiting one of the symptoms as described exactly as in the complaint section or as shown in the video attachments, open a TIPS case to the Body/Chassis/Entertainment inbox with the following: • Video of the concern. • Exact location (latitude and longitude is best)

Complaint The following most common complaints may be observed: • Brief connectivity interruptions when using Apple CarPlay over Wi-Fi • Audio cuts out • Device not recognized • No operation possible Cause There are multiple possible causes for an iPhone disconnecting from a vehicle’s head unit while using Apple CarPlay. These include hardware, software, and environmental factors: Environmental Interference External Sources: • Passing under toll bridges, driving near airports, or areas with heavy electronic interference (e.g., as described in LI82.85-P-076157) can cause connection drops. Cellular Networks: • Interference from nearby cell towers operating on similar frequencies (usually 2.4GHz or 5GHz) can disrupt the signal. Storage Location: • Keeping your phone in a handbag or surrounded by other objects inside the vehicle can create physical or electronic interference. Device and Software Issues Head Unit Software/Hardware: • Outdated firmware, bugs, or hardware faults in the vehicle’s head unit can prevent a stable connection. iPhone Software/Hardware: • Similar issues in the iPhone, including buggy iOS updates or hardware problems, may affect performance. Reset or Reboot:• Automatic rebooting or resetting of either the head unit or the iPhone will temporarily disrupt CarPlay. Connection and Settings Wired Connections: • Faulty Cable: A damaged or poor-quality USB cable can cause intermittent or total loss of connection. • USB Port Issues: Dust, debris, or physical damage in the USB port of either the head unit or the iPhone can also lead to disconnects. Wireless Connections: • Intermittent Bluetooth/Wi-Fi: Unstable wireless communication (Bluetooth/Wi-Fi) can frequently break the Car- Play connection. Power Management: • Battery Saver Mode: Enabling low power mode may restrict background processes, affecting CarPlay. • Vehicle’s Electrical System: Unstable power delivery from the car’s battery or electrical interruptions can cause the head unit to malfunction. Phone & App Configuration Phone Settings: • Incorrect or conflicting settings (especially Bluetooth or Wi-Fi) on your iPhone can interfere with the CarPlay link. • Third-Party Apps/Profiles: • Installed apps or configuration profiles may conflict with CarPlay’s operation. • Native apps are apple maps, apple music, audio books, apple news, podcasts, messages and phone. All other apps are considered third party apps. App Conflicts: • Running conflicting apps that require similar system resources as CarPlay can cause instability. Mobile Data Plan: • Streaming from online sources without sufficient mobile data can result in lost connectivity. Other Factors Heat & Overheating: • If either the phone or the head unit overheats, they may disable certain functions to prevent damage, leading to disconnection. User Actions: • Accidentally disconnecting the device in settings, or physically moving or bumping the phone or cable, may disrupt the connection. Remedy FUP6 (E605.8) software has been released for the following chassis: 118, 177, 243,247,206,254,167,294,295,296,223, 297. Flash available software for the head unit and test for function. The LI will be updated once available for the remaining chassis. If the complaint remains after the SW update please continue with the steps below. Guided Diagnostic Path for Apple CarPlay Connection Issues: Please follow the steps below to systematically diagnose and resolve CarPlay concerns:Update Devices: • Ensure the iPhone is updated to the latest available iOS version. • Ensure the vehicle’s head unit is updated to the latest software version available. Isolate the Issue: • Check whether the symptom persists with another iPhone running the latest iOS version. • Test both wireless and wired CarPlay connections: • Does the issue only occur with wireless CarPlay? • Does the wired connection to the phone function correctly? Further Troubleshooting Steps: • Reboot the iPhone. See attachment for further instructions.

Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.