Release date: October 12th 2022
Welcome to my VMware Horizon series. Recently I ran into a somewhat strange issue at a customer of mine. The case was that they wanted to use Windows Defender in their Horizon Desktops, but the error message below was shown whenever they tried to open Windows Security in Windows 10.
As they are using MDT to create their Horizon Golden templates, I started out by checking if they could open Windows Security during the task sequence, and thereby validating if this was a problem that VMware OSOT caused. I tried opening Windows Security several times during the MDT Deployment, lastly during the OSOT Finalize-phase, but had no problems. The problem occurred when the Horizon Template was deployed to the Desktop Pool.
The solution to the problem was to create a small script that re-registers the SecHealthUI App Package, which I set to run at User Logon, as shown below.
Add-AppxPackage -Register -DisableDevelopmentMode "C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\AppXManifest.xml"
When I log in and test, I can now open the Windows Security page and validate status.
I hope this little nugget of info can be helpful to others who run into the same issue with their VMware Horizon Desktops when using MS Defender.
VMware Horizon planning, deployment etc.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.