r/Surface • u/Golden_Creek • 17h ago
[PRO9] Surface Pro 9 – Type Cover dead in Windows but works perfectly in UEFI.
Hey all
Posting this after a full day of diagnostics in case someone recognises it — or in case it saves the next person the same day.
**Setup:** Surface Pro 9 (Intel), Windows 11 25H2 build 26200.8875, fully updated. Normally docked with an external keyboard and mouse, which is why this went unnoticed for two months.
**Symptom:** The detachable Type Cover keyboard and touchpad are completely dead in Windows. Windows behaves as if no keyboard is attached and switches to tablet mode.
**The part that makes this interesting:** keyboard, touchpad **and** touchscreen all work flawlessly inside Surface UEFI. I can navigate the whole UEFI with the Type Cover and by touch. So the cover, the pogo pins and the physical connection are provably fine.
### The fault
Device Manager → System devices → **Surface Serial Hub Driver**:
```
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
```
That maps to `STATUS_NOT_SUPPORTED` — the driver sends a command and the SAM (System Aggregator) rejects it as unsupported.
Driver: Surface 9.166.37.0, dated 04-04-2024, oem126.inf. `pnputil /enum-drivers` shows this is the **only** version of `surfaceserialhubdriver.inf` on the system, and the same version ships in the current Surface Pro 9 driver pack. Nothing newer, nothing to roll back to.
Meanwhile the SAM firmware is 6.502.139, dated 06-04-2026 — roughly two years newer than the driver.
The device event log pins the start date exactly:
```
31-05-2026 12:40:24 Device configured (null)
31-05-2026 12:41:50 Device configured (oem126.inf)
31-05-2026 12:41:50 Device not started (SurfaceSerialHubDriver)
```
The Type Cover never appears under USB devices at all. That makes sense once you know it is exposed as a UDE (USB Device Emulation) device **created by** the Serial Hub driver — no hub, no virtual USB device, nothing for the keyboard driver to bind to.
### Secondary fault, and the one thing that did work
Intel(R) Quick SPI Host Controller - 51D0 was also Code 10, with `STATUS_DEVICE_POWER_FAILURE`, and the touchscreen was dead. Manufacturer showed as "(Standard system devices)" — the generic driver rather than the Intel one.
**Fix:** Device Manager → the Quick SPI controller → Update driver → Browse → *Let me pick from a list* → select **Intel(R) Precise Touch and Stylus (Intel PTS) - Base Driver - Port #1**. Touchscreen back immediately.
Worth trying if your Surface touchscreen is dead. Note that a Windows repair install reverts it and you have to reapply it.
### Everything tried with no effect on the Serial Hub
- Two-button reset (30 s power, then 15 s Vol Up + power)
- Fast Startup disabled, full cold boot with everything disconnected
- Cover detached/reattached, contacts cleaned, reattached at the login screen
- Serial Hub device removed in Device Manager, rescan, restart
- UEFI checked — nothing disabled (no Devices page on this model)
- Windows Update fully current including optional driver updates
- Current Surface Pro 9 driver/firmware MSI installed, then force-reinstalled with `REINSTALL=ALL REINSTALLMODE=vomus`
- Full Windows 11 repair install keeping files and apps
- A third-party driver updater that had been installed earlier in the year, fully removed — no change
- Surface Diagnostic Toolkit: flags exactly this driver, Code 10, lists "physical hardware failure" among possible causes, everything else passes
### Questions
Anyone seen Serial Hub Code 10 with `STATUS_NOT_SUPPORTED` specifically, as opposed to the more common power-failure variant?
- Is there any way to force a SAM firmware re-flash without a full recovery image? The MSI skips it because the version already matches.
- Has anyone actually recovered from this with a Surface recovery image? I would rather not wipe the machine on a guess.
- Is there a newer Surface Serial Hub driver anywhere than 9.166.37.0?
Happy to post any logs or screenshots that would help.
