Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
We also have a Microsoft ticket open and we notice that after installing the black screen issue fix (KB5045594 Preview) SSO issues and losing network connectivity between Office apps still happening on our customers.
Microsoft provided us the following workaround/fix (see below screenshot) for the SSO issues regarding the AAD Broker plug-in but we are seeing that the policy is not being applied. Do you guys have the same issue?
Workaround/Fix for SSO Failures
- Install the October 22, 2024 update (KB5045594): http://support.microsoft.com/en-us/topic/october-22-2024-kb5045594-os-build-19045-5073-preview-f307a4b0-f62d-4c28-9062-44207aea55c3
- Reboot the machine.
- Open Group Policy Manager as administrator
4. Navigate to User Configuration > Windows Settings > Scripts (Logon/Logoff) > Logon
5. Click on PowerShell Scripts > Add
6. Type a script name such as “AAD Broker plug-in fix” and on the Script Parameters section add the following command line “Add-AppxPackage -Register -Path "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugincw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode”
Click Ok.
7. Select Run Windows PowerShell scripts first and then Apply:
8. Reboot the machine and ensure the policy is active for all users.
After doing these steps all users should get the fix applied at logon and the issues described on the previously indicated documentation should seize. If you detect a user that experiences the issue, first ensure that the logon script is being applied, if it isn’t, enforce the logon script to the user and ask them to sign out and sign in.
Check your system logs to see if there are logon script failures.
“Add-AppxPackage -Register -Path "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugincw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode” is incorrect for us btw.
There's a missing underscore in the path:
"Add-AppxPackage -Register -Path "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode"
- dit-chrisNov 11, 2024Brass Contributor
mgortonEven with an underscore added I'm still getting those 1130 login script failure errors... logged - but copying and posting the command into a Powershell window seems to run ok logged in as the same user.
- mgortonNov 11, 2024Copper Contributor
I also just created a PS script and put it in our sysvol store to run and used that instead in the GPO. Removed the outer quotes of course