The problem device: _SB.UR15 is a UART bus, not a standalone peripheral — it's almost certainly carrying the Bluetooth radio's UART transport (or possibly GNSS/a sensor). The "Problem Device: TRUE" flag means Microsoft's own tooling has pinned it as what's blocking DRIPS. Airplane Mode/Disconnected Standby didn't help because those control network connectivity, not whether the UART driver is holding a power reference open.
Suggestions:
Device Manager → View → Devices by connection → expand _SB.UR15 to confirm what's actually attached to it.
Test: fully disable Bluetooth in Device Manager, then re-run powercfg /sleepstudy overnight. If UR15 clears up, Bluetooth's UART stack is confirmed as the cause.
Look for an updated Bluetooth UART Transport Driver or Qualcomm Bus Device package via Windows Update/Surface app.
Until fixed: leave Bluetooth off overnight or rely on Hibernate instead of Modern Standby.
File feedback via the Feedback specifically referencing the June 25, 2026, update and the System Manager Device/SCM version — these routes to the Surface engineering team faster than forum posts.
Watch for the next Surface Laptop 7 firmware release — regressions like this in the System Manager layer are usually caught and patched within one or two cycles once enough sleep-study reports come in.
In the meantime, using Hibernate instead of relying on Modern Standby is your most reliable workaround, since it sidesteps the DRIPS/power-state issue entirely.