Since multiple organizations were involved (us, Microsoft, our digital certificate provider, Dun and Bradstreet, etc.), we couldn't even communicate a realistic time estimate for this fix. Only device drivers signed by Microsoft are allowed to be loaded. Why it took so long to fix this issue? Latest posts 07 Nov 2016 » DU Meter issues on Windows 10 Anniversary Update have been resolved 02 Aug 2016 » How to solve DU Meter issues after Windows 10 update have a peek at this web-site
We all here at Hagel Technologies are very upset it took so long, and will take steps to ensure that critical updates will be issued at a much faster pace in DU Meter 7.20 contains device drivers properly signed by Microsoft, and it works correctly on all supported versions of Windows now. Related Posts 02 Aug 2016 » How to solve DU Meter issues after Windows 10 update 07 Feb 2012 » Base Filtering Engine (BFE) service is missing: why did it happen Getting Microsoft to sign our drivers involves getting an Extended Validation Code-Signing Certificate, and it all happened at a worst possible time for us: we were in the middle of corporate https://www.tenforums.com/browsers-email/62566-problem-digital-certificates-since-anniversary-update.html
This change in Windows caused DU Meter driver not to load, and therefore DU Meter stopped working. The reason this relatively simple change took so long is bureaucratic and not technical. Getting an EV certificate involves stringent corporate identity checks, and we couldn't pass these till our move is complete.