Battery Report Summary – Surface Laptop 7 (Snapdragon X Elite)
Report Date: November 27, 2025 Device: Microsoft Surface Laptop 7, Snapdragon X Elite Charge Cycles: 9 1. Key Data Battery Name: SurfaceBattery Manufacturer: SWD Design Capacity: 52,330 mWh Full Charge Capacity: 53,850 mWh Cycle Count: 9 2. Usage Observations Despite the battery being new (only 9 cycles), the report shows abnormally fast discharge. Examples from the report: On November 25, the battery dropped from 30% (16,340 mWh) to 23% (12,520 mWh) in ~20 minutes of use. On November 27, during “connected standby,” the battery fell from 77% (41,200 mWh) to 55% (29,440 mWh) within about one hour. These behaviors are inconsistent with expectations for a new device with full capacity. . Technical Analysis Battery authenticity: The data indicates the battery is original (manufacturer SWD, capacity matches design). Primary issue: The discharge rate is unusually fast and unstable, which is not normal for a battery with so few cycles. Possible causes: Defect in the Battery Management System (BMS). Internal cell imbalance. Firmware/driver issue affecting power management. 4. Conclusion and Request The Surface Laptop 7 is showing abnormal battery behavior despite being new and original. Any idea where this problem comes from? Any solution? Thanks in advance!
Trouble Activating Ultimate Performance Plan on My Surface Laptop
Hi everyone, I’m trying to enable the Ultimate Performance power plan on my Surface device. I’ve already used the command powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61, and it shows up in my system. However, when I try to activate it using powercfg /setactive [GUID], I get an “Invalid Parameters” error—even though the GUID matches exactly what was listed under powercfg /list. My current active plan is “High performance” (custom-made). Has anyone else encountered this issue on a Surface laptop? Is this plan blocked or incompatible with certain Surface models, or am I missing a step? Would appreciate any insights or tips! Thank you so much for your attention and participation.
Overheating problems with Surfaces
Since the temperatures have risen, we already have four devices(Surface Laptop & Pro) that are constantly throttling to the point of crashing due to overheating. Surface Support only allows us to replace the entire device, so I'll try it here. Are you also experiencing these problems? Did Microsoft provide a bad firmware update in this case?
Surface Laptop 7, will not boot after system restore
Brand new Surface 7 13.8", just received the package yesterday. I've set it up for my wife, but shortly after network just started timing out querying the router's DNS server (Router is fine, multiple other phones, windows 10 & 11, linux, mac machines work without a hitch). Tried some fixes to no avail, and decided on a system restore just in case I've messed something up during setup. System restore looked like it worked, but laptop restarted and ended up with a bluescreen (something kernel something). System restore is there just fir that, right? Well, I've started it nine hours ago. Now it's just boot looping with the "preparing" bit and then shuts back down. It's been like that the whole day. I've even tried to get a USB stick to have the requisite livecd/recovery media, but it doesn't the new Surface ARM-based processor. What can we even do at this point?
Surface laptop 7th & Thunderbolt 3 external display issue
Hello, I have a surface laptop 7th under Windows 7 with the snapdragon processor offering 2 USB 4 ports. I don't manage to get my external display working through thunderbolt 3 connection. When I go to the device controller panel, I see the serial bus constantly refreshing. Otherwise, Windows 11 and the graphic card drivers are up to date. Would really appreciate if someone can help me. Thanks
Various multiple monitor issues on Surface Laptop Studio (1) since driver updates.
Issues started directly after NVIDIA - Display - 32.0.15.7344 or Surface - Extension - 14.54.139.0 both installed on 2025-10-21 Issues occur when a second monitor is attached, and either extend or duplicate screens is selected. Using only one screen has no issue. Checked with different cables, bypassing HUB and different monitors. All show the same issues. Issues are (but not limited to) 3D (Vulkan) applications in non full-screen mode glitch with a triangle like tearing between the frames. This is a screenshot from a derivate of the Vulkan tutorial. To illustrate the tearing I alternate the clear colour to black and green. With only one monitor selected (either one) the green flashes as expected. With two monitors, even with duplicate display(!), this tearing which seems to be the presentation not waiting for the chain to finish rendering. Again this was all fine before the update. In borderless full window mode it is okay, as the NVIDIA driver doesn't use the INTEL integrated swap chain. Clear type tech is not working, and text is chroma distorted. Happens in all apps, including Microsoft ones. I can literally have an app like visual studio running on the second monitor and the text has serve chroma distortion, and then I change monitor setting to just that monitor and the text is correct. and back and forth. General glitches on apps when resizing, frames of windows appear for a second.Leveraging the power of NPU to run Gen AI tasks on Copilot+ PCs
Thanks to their massive scale and impressive technical evolution, large language models (LLMs) have become the public face of Generative AI innovation. However, bigger isn’t always better. While LLMs like the ones behind Microsoft Copilot are incredibly capable at a wide range of tasks, less-discussed small language models (SLMs) expand the utility of Gen AI for real-time and edge applications. SLMs can run efficiently on a local device with low power consumption and fast performance, enabling new scenarios and cost models. SLMs can run on universally available chips like CPUs and GPUs, but their potential really comes alive running on Neural Processing Units (NPUs), such as the ones found in Microsoft Surface Copilot+ PCs. NPUs are specifically designed for processing machine learning workloads, leading to high performance per watt and thermal efficiency compared to CPUs or GPUs [1]. SLMs and NPUs together support running quite powerful Gen AI workloads efficiently on a laptop, even when running on battery power or multitasking. In this blog, we focus on running SLMs on Snapdragon® X Plus processors on the recently launched Surface Laptop 13-inch, using the Qualcomm® AI Hub, leading to efficient local inference, increased hardware utilization and minimal setup complexity. This is only one of many methods available - before diving into this specific use case, let’s first provide an overview of the possibilities for deploying small language models on Copilot+ PC NPUs. Qualcomm AI Engine Direct (QNN) SDK: This process requires converting SLMs into QNN binaries that can be executed through the NPU. The Qualcomm AI Hub provides a convenient way to compile any PyTorch, TensorFlow, or ONNX-converted models into QNN binaries executable by the Qualcomm AI Engine Direct SDK. Various precompiled models are directly available in the Qualcomm AI Hub, their collection of over 175 pre-optimized models, ready for download and integration into your application. ONNX Runtime: ONNX Runtime is an open-source inference engine from Microsoft designed to run models in the ONNX format. The QNN Execution Provider (EP) by Qualcomm Technologies optimizes inference on Snapdragon processors using AI acceleration hardware, mainly for mobile and embedded use. ONNX Runtime Gen AI is a specialized version optimized for generative AI tasks, including transformer-based models, aiming for high-performance inference in applications like large language models. Although ONNX Runtime with QNN EP can run models on Copilot+ PCs, some operator support is missing for Gen AI workloads. ONNX Runtime Gen AI is not yet publicly available for NPU; a private beta is currently out with an unclear ETA on public release at the time of releasing this blog. Here is the link to the Git repo for more info on upcoming releases microsoft/onnxruntime-genai: Generative AI extensions for onnxruntime Windows AI Foundry: Windows AI Foundry provides AI-supported features and APIs for Copilot+ PCs. It includes pre-built models such as Phi-Silica that can be inferred using Windows AI APIs. Additionally, it offers the capability to download models from the cloud for local inference on the device using Foundry Local. This feature is still in preview. You can learn more about Windows AI Foundry here: Windows AI Foundry | Microsoft Developer AI Toolkit for VS Code: The AI Toolkit for Visual Studio Code (VS Code) is a VS Code extension that simplifies generative AI app development by bringing together cutting-edge AI development tools and models from the Azure AI Foundry catalog and other catalogs like Hugging Face. This platform allows users to download multiple models either from the cloud or locally. It currently houses several models optimized to run on CPU, with support for NPU-based models forthcoming, starting with Deepseek R1. Comparison between different approaches Feature Qualcomm AI Hub ONNX Runtime (ORT) Windows AI Foundry AI Toolkit for VS code Availability of Models Wide set of AI models (vision, Gen AI, object detection, and audio). Any models can be integrated. NPU support for Gen AI tasks and ONNX Gen AI Runtime are not yet generally available. Phi Silica model is available through Windows AI APIs, additional AI models from cloud can be downloaded for local inference using Foundry Local Access to models from sources such as Azure AI Foundry and Hugging Face. Currently only supports Deepseek R1 and Phi 4 Mini models for NPU inference. Ease of development The API is user-friendly once the initial setup and end-to-end replication are complete. Simple setup, developer-friendly; however, limited support for custom operators means not all models deploy through ORT. Easiest framework to adopt—developers familiar with Windows App SDK face no learning curve. Intuitive interface for testing models via prompt-response, enabling quick experimentation and performance validation. Is processor or SoC independent No. Supports Qualcomm Technologies processors only. Models must be compiled and optimized for the specific SOC on the device. A list of supported chipsets is provided, and the resulting .bin files are SOC-specific. Limitations exist with QNN EP’s HTP backend: only quantized models and those with static shapes are currently supported. Yes. The tool can operate independently of SoC. It is part of the broader Windows Copilot Runtime framework, now rebranded as the Windows AI Foundry. Model-dependent. Easily deployable on-device; model download and inference are straightforward. As of writing this article and based on our team's research, we found Qualcomm AI Hub to be the most user-friendly and well-supported solution available at this time. In contrast, most other frameworks are still under development and not yet generally available. Before we dive into how to use Qualcomm AI Hub to run Small Language Models (SLMs), let’s first understand what Qualcomm AI Hub is. What is Qualcomm AI Hub? Qualcomm AI Hub is a platform designed to simplify the deployment of AI models for vision, audio, speech, and text applications on edge devices. It allows users to upload, optimize, and validate their models for specific target hardware—such as CPU, GPU, or NPU—within minutes. Models developed in PyTorch or ONNX are automatically converted for efficient on-device execution using frameworks like TensorFlow Lite, ONNX Runtime, or Qualcomm AI Engine Direct. The Qualcomm AI Hub offers access to a collection of over 100 pre-optimized models, with open-source deployment recipes available on GitHub and Hugging Face. Users can also test and profile these models on real devices with Snapdragon and Qualcomm platforms hosted in the cloud. In this blog we will be showing how you can use Qualcomm AI Hub to get a QNN context binary for models and use Qualcomm AI Engine to run those context binaries. The context binary is a SoC-specific deployment mechanism. When compiled for a device, it is expected that the model will be deployed to the same device. The format is operating system agnostic so the same model can be deployed on Android, Linux, or Windows. The context binary is designed only for the NPU. For more details on how to compile models in other formats, please visit the documentation here Overview of Qualcomm AI Hub — qai-hub documentation. The following case study details the efficient execution of the Phi-3.5 model using optimized, hardware-specific binaries on a Surface Laptop 13-inch powered by the Qualcomm Snapdragon X Plus processor, Hexagon™ NPU, and Qualcomm Al Hub. Microsoft Surface Engineering Case Study: Running Phi-3.5 Model Locally on Snapdragon X Plus on Surface Laptop 13-inch This case study details how the Phi-3.5 model was deployed on a Surface Laptop 13-inch powered by the Snapdragon X Plus processor. The study was developed and documented by the Surface DASH team, which specializes in delivering AI/ML solutions to Surface devices and generating data-driven insights through advanced telemetry. Using Qualcomm AI Hub, we obtained precompiled QNN context binaries tailored to the target SoC, enabling efficient local inference. This method maximizes hardware utilization and minimizes setup complexity. We used a Surface Laptop 13-inch with the Snapdragon X Plus processor as our test device. The steps below apply to the Snapdragon X Plus processor; however, the process remains similar for other Snapdragon X Series processors and devices as well. For the other processors, you may need to download different model variants of the desired models from Qualcomm AI Hub. Before you begin to follow along, please check the make and models of your NPU by navigating to Device Manager --> Neural Processors. We also used Visual Studio Code and Python (3.10.3.11, 3.12). We used the 3.11 version to run these steps below and recommend using the same, although there should be no difference in using a higher Python version. Before starting, let's create a new virtual environment in Python as a best practice. Follow the steps to create a new virtual environment here: https://code.visualstudio.com/docs/python/environments?from=20423#_creating-environments Create a folder named ‘genie_bundle’ store config and bin files. Download the QNN context binaries specific to your NPU and place the config files into the genie_bundle folder. Copy the .dll files from QNN SDK into the genie_bundle folder. Finally, execute the test prompt through genie-sdk in the required format for Phi-3.5. Setup steps in details Step 1: Setup local development environment Download QNN SDK: Go to the Qualcomm Software Center Qualcomm Neural Processing SDK | Qualcomm Developer and download the QNN SDK by clicking on Get Software (by default latest version of SDK gets downloaded). For the purpose of this demo, we used latest version available (2.34) . You may need to make an account on the Qualcomm website to access it. Step 2: Download QNN Context Binaries from Qualcomm AI Hub Models Download Binaries: Download the context binaries (.bin files) for the Phi-3.5-mini-instruct model from (Link to Download Phi-3.5 context binaries). Clone AI Hub Apps repo: Use the Genie SDK (Generative Runtime built on top of Qualcomm AI Direct Engine), and leverage the sample provided in https://github.com/quic/ai-hub-apps Setup folder structure to follow along the code: Create a folder named "genie_bundle" outside of the folder where AI Hub Apps repo was cloned. Selectively copy configuration files from AI Hub sample repo to 'genie_bundle' Step 3: Copy config files and edit files Copy config files to genie_bundle folder from ai-hub-apps. You will need two config files. You can use the PowerShell script below to copy the config files from repo to local genie folder created in previous steps. You also need to copy HTP backend config file as well as the genie config file from the repo # Define the source paths $sourceFile1 = "ai-hub-apps/tutorials/llm_on_genie/configs/htp/htp_backend_ext_config.json.template" $sourceFile2 = "ai-hub-apps/tutorials/llm_on_genie/configs/genie/phi_3_5_mini_instruct.json" # Define the local folder path $localFolder = "genie_bundle" # Define the destination file paths using the local folder $destinationFile1 = Join-Path -Path $localFolder -ChildPath "htp_backend_ext_config.json" $destinationFile2 = Join-Path -Path $localFolder -ChildPath "genie_config.json" # Create the local folder if it doesn't exist if (-not (Test-Path -Path $localFolder)) { New-Item -ItemType Directory -Path $localFolder } # Copy the files to the local folder Copy-Item -Path $sourceFile1 -Destination $destinationFile1 -Force Copy-Item -Path $sourceFile2 -Destination $destinationFile2 -Force Write-Host "Files have been successfully copied to the genie_bundle folder with updated names." After copying the files, you will need to make sure to change the default values of the parameters provided with template files copied. Edit HTP backend file in the newly pasted location - Change dsp_arch and soc_model to match with your configuration pdate soc model and dsp arch in HTP backend config files Edit genie_config file to include the downloaded binaries for Phi 3 models in previous steps Step 4: Download the tokenizer file from Hugging Face Visit the Hugging Face Website: Open your web browser and go to https://huggingface.co/microsoft/Phi-3.5-mini-instruct/tree/main Locate the Tokenizer File: On the Hugging Face page, find the tokenizer file for the Phi-3.5-mini-instruct model Download the File: Click on the download button to save the tokenizer file to your computer Save the File: Navigate to your genie_bundle folder and save the downloaded tokenizer file there. Note: There is an issue with the tokenizer.json file for the Phi 3.5 mini instruct model, where the output does not break words using spaces. To resolve this, you need to delete lines #192-197 in the tokenizer.json file. Download tokenizer files from the hugging face repo (Image Source - Hugging Face) Step 5: Copy files from QNN SDK Locate the QNN SDK Folder: Open the folder where you have installed the QNN SDK in step 1 and identify the required files. You need to copy the files from the below mentioned folder. Exact folder naming may change based on SDK version <QNN-SDK ROOT FOLDER>/qairt/2.34.0.250424/lib/hexagon-v75/unsigned <QNN-SDK ROOT FOLDER> /qairt/2.34.0.250424/lib/aarch64-windows-msvc <QNN-SDK ROOT FOLDER> /qairt/2.34.0.250424/bin/aarch64-windows-msvc Navigate to your genie_bundle folder and paste the copied files there. Step 6: Execute the Test Prompt Open Your Terminal: Navigate to your genie_bundle folder using your terminal or command prompt. Run the Command: Copy and paste the following command into your terminal: ./genie-t2t-run.exe -c genie_config.json -p "<|system|>\nYou are an assistant. Provide helpful and brief responses.\n<|user|>What is an NPU? \n<|end|>\n<|assistant|>\n" Check the Output: After running the command, you should see the response from the assistant in your terminal. This case study demonstrates the process of deploying a small language model (SLM) like Phi-3.5 on a Copilot+ PC using the Hexagon NPU and Qualcomm AI Hub. It outlines the setup steps, tooling, and configuration required for local inference using hardware-specific binaries. As deployment methods mature, this approach highlights a viable path toward efficient, scalable Gen AI execution directly on edge devices. Snapdragon® and Qualcomm® branded products are products of Qualcomm Technologies, Inc. and/or its subsidiaries. Qualcomm, Snapdragon and Hexagon™ are trademarks or registered trademarks of Qualcomm Incorporated.Display problems with Surface 1872
Hi, I hope someone can help me here. I was given a Surface 1872 with a broken screen to fix. The picture was viewable but yes, the screen needed replacing. I cleaned out the broken screen and bought a brand new one (that was a mistake that I won't make again !!), I then attached the new screen in place of the broken one (not in the lid, just laying above it) and attached it using the 4 cables. The laptop booted up, but there was nothing showing on the screen. I attached a USBC cable and plugged it onto my Monitor's HDMI port and that screen was fine. I then, by accident, touched the laptop screen and bizarrely, the touchscreen was working, just only visible on my monitor, not the new laptop screen. Googling this told me that it was probably a faulty screen. I then bought a second hand replacement screen, apparently tested and fully working, but as part of the whole top, i.e. in and attached to the lid. I replaced the laptop screen again and this time there was still nothing on it, but my monitor showed some flickering & some lines. I therefore disconnected the screen re-attached all of the cable again and rebooted. I hear the laptop boot up, but now I am getting nothing on either screen !!! What on earth could have caused this ? Why, at least, do I not have video on my Monitor when I did before ?!? I have tried CTRL-Win Key-Shift-B & numerous other suggestions but nothing has so far made a difference 😢 ... Any help or advice would be a Godsend !!!
Surface Laptop 5 abysmally horrible battery life
I bought this laptop 2 years ago for $1.4k. I expect it to have a battery life that lasts more than 3.75 hours. The charger it came with is also incredibly finnicky and this webcam makes everything look like it was recorded on a D-list smart fridge. The only think this crapshoot is good for is the aesthetic. Functionally it's useless. I really expected better from a reputed company like Microsoft.
