Frank Weber

Hi, I ran into this problem with WAsP 11 and also WEng 3.1 the first time in 2023. I am running both programs from within WindPro and, when contacted, the WindPro support advised this: "Open the Windows update history. Please check whether an update with the number KB5011048 has been installed in the LAST category. If so, please uninstall it using the link at the top of the same window. Then restart your computer and see if this has helped. Background: This update causes the described behaviour in some (but not all) users. We do not yet know what is causing this, except that it is probably related to the contact between windPRO and WAsP." --- citation end --- As I found out, the Microsoft .NET Framework updates are indeed the culprit: when I delete these updates, WAsP 11 and also WEng 3.1 again recognise my licence, regardless if I start them individually or WindPro is calling them. That is, alas, not really a proper fix since Windows keeps installing these updates, along with others, like security updates. And after each new update the licence check fails again during start of WAsP 11 and also WEng 3.1. Also in 2023, I have had a call with WAsP support; they said that WAsP 12 and WEng 4 and higher do not have this problem with the Windows Microsoft .NET Framework updates. Can I ask if anybody knows this to be truly the case? Thank you, Frank