Microsoft .NET Framework and Famic Automation Studio License Manager

Another month and another update for Microsoft .NET Framework (KB5008718). It’s the same sad story again.

Microsoft releases an update for .NET Framework, and naturally ngen.exe and mscorsvw.exe runs after the initial reboot. While this is happening, Famic Automation Studio License Manager is unable to start. I had to reboot the license server twice after the native images had been generated. I did try to start the license service manually after the second reboot, but to no avail. Only after the third reboot did the license service start automatically and I was sort of happy.

I noticed mscorsvw.exe didn’t exactly max out the CPUs while doing its thing. Is there a way of speeding up the process of generating the native images? I know people have complained in the past about ngen.exe and mscorsvw.exe using too many CPU resources. Here I am complaining the exact opposite. I’m in a hurry and so are the students, so I want those native images generated at lightning speed. Why can’t ngen.exe run multiple instances of mscorsvw.exe, spreading the load across the available vCPUs?

Famic, I suggest you make one small alteration to ASNETLM.exe and ASNETLMClient.exe, make them wait until the .NET Framework environment is completely regenerated before proceeding. And Microsoft, rebooting the license server three times in a row should be utterly unnecessary.