Installing KB4056892 causes DCM to report errors:
Failed to get installed families(s)
Access is denied
Failed to get the system mode
Yes, we are aware of the issue as of this morning since Microsoft released it yesterday for the "meltdown and spectre" issues at the intel chip level.
The issue not only seen on windows 10, but other KBs in the microsoft catalog (expected to be pushed next week) also exposed the same in 2012, 2016 as well. Looks like some permissions issue changed with the update.
We are working diligently to triage and determine root cause in order to find a fix.
Just posting technote posted for this topic.
Are there any updates on this? Will Dialogic be fixing the DCM? We have multiple D/480JCT-2T1 in use and the DCM is important for us.
See the following technote link above:
Overall, underlying API for at Microsoft level was changed and broke backward compatibility in their update. In meantime you can following one of the recommendations in the article written until Microsoft decides to correct/fix the issue.
Just an update that Microsoft has released fixes for the issues that were affecting HMP software.
Here is list of original problematic KBs and fix noted below:
Also see following article to locate you applicable OS variant KB and then applicable KB fixes within that article for subsequent KB fixes.
KB4073291 is only for Windows 10 32bit systems and cannot be installed on 64bit systems and therefore doesn't resolve the issue.
Ok, I guess thee main point overall is to run the updates check on you own server in order to get the latest fixes from Microsoft in this case. As noted in the main article for the meltdown/spectre topic they have multiple OS streams going and the affected change has been addressed in the ones that I checked.
All my systems are 64-bit (2012, 2016, win 10), but there a mix of core variants (1607, 1703, or 1709). I was able to confirm the KB fix provided on those systems to correct the DCM issues.
I think the one for Win 10 was actually this one, from what I can tell
Does this issue occur with Windows 7 Pro or Windows Server 2008R2?
I can only state that on 2008 R2, applying the KB4056897 (in my case) it worked just fine with no issues as I had seen reports of the same from others. I suspect since that KB is also applicable to certain win 7 setups, that it would also work.
I've confirmed on my Windows 10 x64 system that KB4074588 released on 2018/02/13 resolved the issue with DCM.