It's really surprising that this feature was implemented in this way. Not only is it incomplete, but this method is extremely inefficient and messy. It's slow and fills the event log with "Windows Installer reconfigured the product.". This can be seen from the screenshots here:
Unfortunately the suggestion they give is not valid any more. It doesn't work on 64-bit machines.
The better alternative is usually to query the registry. I have a PowerShell script written that does a pretty good job and I could have swore I had it integrated in to ConnectWise Control Access to return the output in a custom tab, but recent updates seem to have broke it and I can't seem to find the custom code I had written to do it.
It's really surprising that this feature was implemented in this way. Not only is it incomplete, but this method is extremely inefficient and messy. It's slow and fills the event log with "Windows Installer reconfigured the product.". This can be seen from the screenshots here:
https://docs.connectwise.com/ConnectWise_Control_Documentation/Supported_extensions/Productivity/Remote_Diagnostic_Toolkit?psa=1
Microsoft KB supporting this:
https://support.microsoft.com/en-us/help/974524/event-log-message-indicates-that-the-windows-installer-reconfigured-al
Unfortunately the suggestion they give is not valid any more. It doesn't work on 64-bit machines.
The better alternative is usually to query the registry. I have a PowerShell script written that does a pretty good job and I could have swore I had it integrated in to ConnectWise Control Access to return the output in a custom tab, but recent updates seem to have broke it and I can't seem to find the custom code I had written to do it.
Some references on how to do this properly:
https://devblogs.microsoft.com/scripting/use-powershell-to-find-installed-software/
http://jeffwouters.nl/index.php/2014/01/a-powershell-function-to-get-the-installed-software/