In both Specify and Get-Specs, the WMI call for HotFixes was getting jammed up either indefinitely or for a very long period of time. This was discovered after both Jim and I looked into where the problem was occurring. Below is the original log where it got caught. Jim made a dev build that tracked the WMI calls and found that to be taking a massive amount of time on hot fixes.
Something we should work towards is having a time out on any loops running so that the program doesn't hang in unexpected areas. Basically if the calls time out, add it as an issue and make note of it on Specified.
This issue was brought to my attention when a user tried running Specify when their system was infected with a virus that incapacitated Windows Update in an unknown way: https://discord.com/channels/749314018837135390/750395566307016814/1114330300823109643
In both Specify and Get-Specs, the WMI call for HotFixes was getting jammed up either indefinitely or for a very long period of time. This was discovered after both Jim and I looked into where the problem was occurring. Below is the original log where it got caught. Jim made a dev build that tracked the WMI calls and found that to be taking a massive amount of time on hot fixes.
Something we should work towards is having a time out on any loops running so that the program doesn't hang in unexpected areas. Basically if the calls time out, add it as an issue and make note of it on Specified.
message (10).txt