Windows client v3 stopped working, I assume after a Win11 update.
Same error as in this post “Xibo v3 support for Windows 11 ”
There didn’t seem to be a resolution there.
I upgraded the client to the current version 406. Getting a similar error as follows:
Anything I should try?
Thanks
dan
April 21, 2026, 10:20am
2
This happens on systems with tightened code-integrity policies (Windows 11 Smart App Control, WDAC, AppLocker, some AV products). You could try to add a white list or turn off that feature if you can work out which of them is causing it.
I’ve reported a bug for it here to see if we can improve it how its handled:
opened 10:09AM - 21 Apr 26 UTC
OP: https://community.xibo.org.uk/t/win11-24h2-client-406-error/37784
A user re… ported the player crashes at startup with a "Fatal Error" popup showing a System.Runtime.InteropServices.COMException (HRESULT 0xD0000003) thrown from System.CodeDom.Compiler.FileIntegrity.MarkAsTrusted via System.Xml.Serialization.XmlSerializer.GetSerializersFromCache, triggered when new xmds.xmds() is constructed inside RequiredFiles..ctor (the first time the SOAP client is created on startup).
<img width="911" height="563" alt="Image" src="https://github.com/user-attachments/assets/2016cbe6-5204-4ccf-a32f-9f8b3f2ce2c6" />
dan
April 23, 2026, 9:34am
3
There is a beta release available for you to try: https://xibo-firmware.fra1.cdn.digitaloceanspaces.com/Windows-Test-MSI/xibo-client-v4-R407.1-win32-x86.msi
It prebuilds the DLL that is being blocked by windows and ships it in the MSI as a signed DLL.
Full disclaimer, I am not sure if it will work as I wasn’t able to reproduce the issue locally, so it is a theoretical fix.
Please let me know if it solves the issue for you.