Windows collect a lot on users and what users commonly install on their machines. For this specific situation a simple script pulling from chocolatey and a warn

Windows collect a lot on users and what users commonly install on their machines. For this specific situation a simple script pulling from chocolatey and a warning based on a threshold (and additional warning factors based on history) would have given them a failing test for fairly low amount of effort. This kind of issue should be mostly automated rather than being manually added by QA.