NFC driver doesn't go into low power state (D3) on system going to Modern standby

[HariomKesh]

Need Win10 Desktop PC with connected standby support.
Issue seen in CLX based NFC Client driver.

Steps to repro:

• put system into modern standby & resume from Modern standby
  Expected results:
• NFC driver shown be in D3 when system is in standby & resumes back to D0 when system resumes from connected standby.
  Actual results:
• NFC driver remains in D0.

Initial Analysis :-
On Modern standby proximity service sends NFP_DISABLE for all open handles.
But ScardSvr handle still remains open as there is no disable for that.
This causes CLX driver to remain in D0 state so do NFC Client driver also remain in D0.

If we stop ScardSvr manually, CLX driver is able to go into low power mode so do NFC Client driver is able to go into low power mode when system goes into Modern standby.

scardsrv_Disabled_Success_ETL.zip
scardsrv_running_Failed_ETL.zip

Logs are attached for success (scardsrv disbaled) & failed (scardsrv running) cases.

[icherniukh]

Is it still reproducible?