We did catch this with the Windows 10 1151 update and we updated our KBA’s advance of its general release: https://help.extensis.com
Currently that is the best workaround I have to offer, but we are looking into the root cause to see what we can do to prevent this from happening in the future. I do see this same thing happening in the latest Insider Build (11082) and will have the article updated accordingly. Luckily the workaround is simple and doesn’t put your data at risk.
Realistically, Extensis can’t guarantee any compatibility with these fast-track insider builds. It is simply too big of a moving target to ensure 100% compatibility. These builds are intended for developers and enthusiasts to provide feedback and aren’t considered “daily drivers.” If you require a more predictable working environment, I’d recommend sticking with Microsoft’s general Windows 10 releases.
Thank you for bringing this to my attention,
Ryan C Brown
Extensis Font Management QA