2026.3.2 - Favicon functionality broken

A fix for this issue has been implemented in version 2026.3.4.0

2026.3.2 - Favicon functionality broken

avatar

The Favicon functionality is broken.

It only works if specified for an App but not system wide.

More specific, these settings currently do not work:

Thanks for considering to fix that in an upcoming release! 🤗

Best regards,

Don

avatar

Recommended Answer

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of PowerShell Universal (2026.3.4) includes a fix for this problem. You can download it from our website here:

https://devolutions.net/download-center/#psu

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Maxim Robert

All Comments (3)

avatar

@don.lent Thank you for the report! I have opened an issue in our backlog to get this resolved.

Adam Driscoll

PowerShell Expert and Software Architect at Devolutions

avatar

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of PowerShell Universal (2026.3.4) includes a fix for this problem. You can download it from our website here:

https://devolutions.net/download-center/#psu

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Maxim Robert

avatar

Dear @Maxim Robert

Sorry for my late response. Last week I didn't have time to test the new version out. But today I finally managed to give it a try and I'm happy to confirm that the new version correctly fixes the issue!

Thank you very much for you much appreciated help and efforts! 🤗👍🏼

Best regards,

Don

A fix for this issue has been implemented in version 2026.3.4.0