FYI - Unlock lost after hibernation

[MRedRaider81]

Sharing for FAQ / the benefit of others. I have an 8GB 3070 that unlocks on boot with the USB. Confirmed with the diag tool and I see about a 50% reduction in generation time for videos and images in ComfyUI.
I have my computer set to hibernate when idle for more than 15 minutes. When I wake the machine, the unlock status in diag tool is not_unlocked and generation times are back to original.

This is likely expected based on hibernation; however, it's worth documenting.

[physicsdolphin]

@op Thanks for the report — exactly the kind of user-side confirmation that makes the docs trustworthy. It's recorded in the community-reports table, and it motivated a sharpening of the FAQ sleep section.

What's happening mechanically: S4 hibernation removes power from the whole machine. On wake, the GPU re-runs devinit from scratch — and crucially, the always-on (AON) island that holds the FEAT gate does not survive power loss, so the PLM gate is closed again when Windows comes back. That's why the diag tool shows not_unlocked and generation times revert.

One thing worth knowing before you retry: after an S4 wake, ssdiag --reapply will answer REFUSED: gate closed. That refusal is the correct verdict, not a tool failure — the gate is genuinely shut, and the only recovery is re-running the USB transaction. The --reapply path applies to the other wake shape (S0ix/S3 cases where the rail survives and the gate stays open while only the SS selectors revert) — the FAQ sleep section now states this split explicitly, with your report cited for the S4 side.

Practical options for the 15-minute auto-hibernate:

1. Disable hibernate-on-idle if you'd rather keep the unlock across idle periods: powercfg /change hibernate-timeout-ac 0 (admin). Note plain S3 sleep drops it too on most desktops — see the FAQ sleep table for which state your machine actually uses (powercfg /a).
2. Or embrace the re-run: the armed marker (i_know_what_i_am_doing.txt) makes each USB re-run unattended and fast (read-only prep fills the countdown window), so a re-boot-before-workload habit costs under a minute.
3. If you also game with anti-cheat and toggle Secure Boot, issue [Request] 关闭安全启动后，英雄联盟反作弊系统提示没有开启安全启动，进入不了游戏，有什么解决办法吗？ #145 documents a hibernate-based workflow that's built around exactly this volatility — hibernate preserves your session across the SB toggle, and the unlock is re-applied on whichever boot needs it.

The volatility is by design — the unlock writes no persistent state, which is also why it's fully reversible. 50% generation-time reduction is a solid result for a 3070, by the way.