Did you ever find a solution for this issue?
This just started happening to us today after upgrading PCs from Win 10 1511 to 1703. We're using SCCM 2016 1706.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.