It looks like you are running SofTrack. Integrity Software has published an update that fixes this problem. I downloaded the latest version and updated my server. I had to update the client interactively, but it seems to work.
KB5013942 May 2022 Windows 10 update prevents .NET applications from launching
Noting ahead of time: I can reproduce this issue easily by uninstalling and reinstalling KB5013942 on the affected computers.
We have 48 lab computers, all Dell Precision Tower 3420's, and since the May 2022 cumulative update, we have this problem with several applications. They never launch their UI's, just sit in the task manager, consuming 10-15% CPU.
As I said at the top of this post, if I uninstall the KB in question and reboot, everything launches perfectly. I also tried installing the out-of-band update (KB5015020) and this does not fix the problem either.
I noticed that both Microsoft Endpoint Configuration Manager's scclient.exe seems be built using .NET, and also the Dell Command Update program does too. The fact they have that in common seems suspect.
I tried following the instructions here for Windows 11 machines that , running those 3 commands:
dism /online /enable-feature /featurename:netfx3 /all
dism /online /enable-feature /featurename:WCF-HTTP-Activation
dism /online /enable-feature /featurename:WCF-NonHTTP-Activation
To see if that would fix the issue - unsurprisingly, it did not.
This does not affect ALL of our domain's computers - some are working fine. But it is affecting 100% of this make/model of computer.
8 additional answers
Sort by: Most helpful
-
Rita Hu -MSFT 9,641 Reputation points
2022-06-02T02:37:09.07+00:00 Thanks for your posting on Q&A.
What is the windows version of the affected devices? I found the following tips in the following link:
https://support.microsoft.com/en-gb/topic/may-10-2022-kb5013942-os-builds-19042-1706-19043-1706-and-19044-1706-60b51119-85be-4a34-9e21-8954f6749504According to the description, After installing this update, Windows devices that use certain GPUs might cause apps to close unexpectedly or cause intermittent issues that affect some apps that use Direct3D 9. It seems that this issue occurred on the devices which used the Direct3D 9. Please try to confirm whether it is ture in your environment.
Hope the above will be helpful. Please let me know if there are any questions or updates of the case.
Best regards,
Rita
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. -
MD5Hash 151 Reputation points
2022-06-02T15:19:31.867+00:00 Good morning @Rita Hu -MSFT - the lab computers are all 21H2 machines. They were originally imaged with a 20H2 wim, then used the enablement package to upgrade them to 21H2.
They are using integrated and discrete graphics - Intel HD Graphics 630 and NVIDIA Quadro K420.
I did see that Known Issue already. However, it seemed unlikely to me that Software Center, used to install software from Microsoft Endpoint Configuration Manager, and Dell Command Update, use to patch Dell computers, would be using DirectX at all, much less a version of Directx - nine - that is so old.
Furthermore, I didn't see any error messages in my Application event viewer log.
However, as requested, I installed the KIR on one of my lab machines, set its status to "Disabled" per the instructions, and rebooted the machine.
Unfortunately, the issue with the 'hung' applications stuck at a consistent low CPU percentage continues.
Anything else we can try?
-
MD5Hash 151 Reputation points
2022-06-02T21:47:14.33+00:00 Imaged a new HyperV VM with the original 21H2 WIM (no updates), and then updated it to the May 2022 patch level. No issues with programs not launching, it really seems this bug has something to do with certain configurations of physical hardware.
-
MD5Hash 151 Reputation points
2022-06-03T18:27:20.797+00:00 I just tried installing the June Preview Update on one of the lab machines to see if that would fix the issue. Unfortunately it does not.