Windows Hello: issues with Phone Pairing and Dynamic Lock

I have the same problem. I have removed my Windows 10 PC from my iPhone Bluetooth devices, removed my iPhone from my Windows 10 Bluetooth devices, and have re-paired the two devices multiple times. The iPhone and the Windows 10 PC will not (usually) reconnect automatically--I have to reconnect them manually (from my iPhone Bluetooth device list).

I use this feature a lot (working from home & have kids) and I love not having to manually lock the screen when I walk away ... if only it kept working and the control panel didn't lie about it.

I get the same symptoms (Lenovo P52 + Win10 + Samsung S8) except I find that going into the control panel, turning off dynamic lock and then turning it back on again seems to fix the issue (temporarily). I've not had to un-pair/remove devices from bluetooth, all I need to do is "turn it off and on again" in the control panel.

i.e. the control panel is telling me that dynamic lock is on (when Windows has actually turned it off; it'll even notify me on the desktop that it's done so ... but the control panel still shows it as "on"), and if I "scan for device" it tells me that it can't find it (even though it can, and in fact already has, found it).

I think we've actually got two problems here, which is why it's hard to resolve.

(1) The "Dynamic lock" control panel page lies about the actual state of the OS's underlying functionality.
It seems to me that the Win10 control panel is correctly controlling the real underlying functionality but it's reporting false information based on "what it asked for last" instead of actually reporting the live status from the real underlying functionality ... AND because the real underlying functionality is failure-prone (causing it to switch itself off for "no apparent reason", without the control panel knowing) we can end up in a state where it's really "off" but the control panel is showing it as "on" (because that's the last state that the control panel set).
IME turning it off and on again re-aligns the underlying "on/off"ness with the control-panel's displayed state.

I've found that I can reproduce the "the control panel lies" issue just by turning bluetooth off on my phone while my PC is locked and then unlocking the PC; Windows (correctly) complains that it can't see my phone and notifies me that it's turned dynamic lock off (which is true, it really has turned it off, and that's really useful to know) ... but the control panel will still show that it's switched on (when it isn't). Turning my phone's bluetooth back on allows Windows to reconnect, but the Dynamic lock control panel will still insist that my phone is nowhere to be found. Turning dynamic lock off and on again in the control panel makes it reconnect and work again.

(2) Dynamic lock will spontaneously turn itself off but won't spontaneously recover without user intervention; there's a numerous folks reporting this all over the place and the problem isn't new.

My guess is that it's probably an in-the-background windows update or similar not-triggered-by-the-user configuration change causing the underlying functionality to disconnect AND that the underlying functionality fails to automatically reconnect when this "normal operation for Windows" stuff happens.
i.e. it's just not robust enough for "real world" usage.

So, unless we can figure out some other way of seeing "what's really happening" (event log maybe?), we really need a fix for (1) before we're going to stand any chance of fixing (2).