A firmware update rolled out in early August 2025 for Snapdragon-powered Surface devices is causing a severe battery charging regression for a subset of Surface Pro 11 owners. The bug removes the UEFI toggle for Battery Limit while leaving the 50 percent charge cap enforced, effectively halving real-world battery runtime on what is otherwise a highly mobile device. Microsoft has acknowledged the issue and is actively investigating through its support channels.
Surface devices have long included a Battery Limit feature accessible via UEFI, intended for kiosks and always-plugged scenarios. Microsoft’s official documentation describes it as a firmware setting that limits the battery to a 50 percent maximum charge to prolong longevity. The same documentation details how to enable or disable it, and lists supported models including the Surface Pro 7 and later. Alongside this, Microsoft offers Smart Charging—an OS-level mechanism that typically holds the battery at 80 percent when the device is plugged in for extended periods. The Surface app recently gained a direct 80 percent charge limit option and a temporary 100 percent override for Snapdragon Surface Pro 11 and other Snapdragon models, eliminating the need to reboot into UEFI for many users.
The August firmware wave that introduced those convenient in-app controls appears to have also introduced a dangerous regression. Multiple users began reporting around August 9, 2025, that the UEFI “Enable Battery Limit” toggle had vanished from their devices. Simultaneously, their batteries would not charge beyond roughly 50 percent. For a Surface Pro 11 lauded for its all-day battery endurance—often exceeding 10 hours under mixed workloads—the result is a runtime drop to about five hours. This transforms a device built for portability into one that demands frequent tethering to power.
Community threads on Microsoft Q&A and social platforms show that the issue is not isolated to one model. Reports mention Surface Laptop 7 and other Snapdragon Surface devices experiencing the same symptoms. One user noted that after installing the August firmware on July 30, the Battery Limit option disappeared from UEFI, and the battery refused to charge past 50 percent. Another described the Surface app’s 80 percent option being missing, leaving no way to override the cap. Microsoft support staff in those threads have guided users to open tickets and provide detailed firmware version strings, Windows Update package IDs, and timelines to aid escalation.
The practical impact is harsh. A professional who counts on the Surface Pro 11 for a full day of meetings or travel suddenly confronts a device that runs out of power by lunchtime. Fleet managers face unpredictable charging behavior that undermines productivity. The regression strikes at the core promise of a premium portable PC.
Microsoft’s official Battery Limit documentation explains that the setting is meant for devices continuously connected to power and that enabling it when the battery is above 50 percent will not immediately drain it but will stop charging until it drops below that threshold. That page, along with a Surface support article on charging issues, forms the basis of Microsoft’s public guidance. Yet neither document addresses the scenario where the toggle simply disappears while the cap remains enforced. Support agents have acknowledged the gap and are collecting diagnostic data.
Affected owners should first update the Surface app via the Microsoft Store and run Windows Update to ensure all pending firmware and driver packages are installed. After a reboot, they should check the Surface app’s Battery & charging section for the 80 percent or 100 percent options. If those are absent, the next step is to enter UEFI (Power + Volume Up at startup) and look under Boot configuration > Advanced Options for the Enable Battery Limit toggle. If the toggle is missing, the device is likely one of those hit by the regression. Users should then gather firmware versions (UEFI, EC, SAM/SMF) and the exact Windows Update KB or driver package IDs visible in Update history. Opening a support ticket with this information is the recommended path, as Microsoft has indicated it helps trace the root cause.
Microsoft warns that on ARM-based Surface models like the Pro 11, uninstalling battery drivers can lead to a full system reset. Users should avoid such steps unless explicitly instructed by support. A temporary workaround documented in community threads involves toggling kiosk or Battery Limit states when UEFI is still accessible, but for those whose toggle is gone, the only reliable recourse is the support ticket.
For IT administrators managing fleets, the regression is a cautionary tale. The August firmware package that added the 80 percent controls should not be broadly deployed without a pilot. Staged rollouts mean that only a fraction of devices receive updates at a time, and the bug’s appearance in a small group can be enough to disrupt operations. Administrators who rely on UEFI Battery Limit for kiosks should treat firmware updates as high-risk and prepare rollback procedures.
Root cause analysis points to a UEFI layout change that removed or renamed the Battery Limit control path while leaving the underlying enforcement policy active. Another possibility is a mismatch between the new Surface app and older firmware components, creating a state where the app lacks authority to override the firmware cap. An Embedded Controller firmware regression could also be permanently setting a battery profile that requires an updated EC image to clear. Each scenario explains why the toggle disappears and why a simple UEFI tweak cannot fix it.
The incident reveals both strengths and weaknesses in Microsoft’s approach. The drive to bring user-friendly battery controls into the Surface app is sound and aligns with modern battery stewardship. Documentation on Battery Limit and Smart Charging is thorough. However, firmware rollouts that touch UEFI and EC layers demand exceptional QA across Snapdragon and Intel SKUs. The current regression shows that a quality-of-life improvement can unleash a severe usability regression when firmware, app, and UEFI components interact. Microsoft’s telemetry and diagnostic tooling could be stronger: community members have noted that an on-device firmware state diagnostic would speed triage.
Lessons for Microsoft are clear. Prioritize cross-SKU testing that verifies UEFI toggle visibility and charging behavior. Build safeguards that automatically revert or unblock devices if a critical control path vanishes. Consider a Surface app diagnostic module that surfaces firmware flags and allows a logged override, giving support a quicker path to repair without full reimaging.
The path forward should include a public advisory listing affected models and mitigation steps. A firmware hotfix that either restores the UEFI toggle or clears the erroneously set 50 percent enforcement flags is essential. An enterprise advisory with rollback guidance would help fleet managers. The faster Microsoft communicates and delivers a fix, the sooner trust can be restored.
Prospective buyers who need guaranteed full-day battery life may want to wait for a confirmed resolution. Current owners should verify firmware and app status after every major update and keep a record of firmware versions. The underlying architecture—combining durable firmware controls with convenient app toggles—remains sound. But execution matters, and this regression has turned an optional longevity feature into a disabling user experience. A timely, transparent fix will show that Microsoft can still get the details right.