Hi,
I'm aware that this piece of software is very fringe, but I'm hoping that someone encountered similar issues after the update to 1703.
The Software in Question is IBM Perscomm 6.0.1 (Yes I'm aware that they are at Perscomm 12 now.) wich worked fine with 1607 but after the update, it still starts but once it is connected to our host and should display the text the app becomes unresponsive and
has to be killed via Taskmanager.
Going from what I was able to get out of Processmonitor and Dependencywalker something changed in the way DLLs are handled. In Dependencywalker I can see loops of Kernel32.dll calling api-ms-win-core-sysinfo-l1-2-1.dll and vice versa.
Did anyone experience something similar to this after updating and found a solution?
I would be extremely grateful.
-PhiKro