mgajda83
Critical Signing Issue: PSWindowsUpdate Module Files (PSWindowsUpdate.Format.ps1xml) in AllSigned Environments
Hello,
We are successfully using your PSWindowsUpdate module in enterprise environments, but we are running into a persistent problem due to our strict PowerShell Execution Policy of AllSigned.
The issue is that the module fails to import because the system doesn't trust the signature on internal files, specifically the PSWindowsUpdate.Format.ps1xml file (and potentially others like .psd1, .psm1). The error is: Error en la comprobación de AuthorizationManager.
Although your main script is signed, the certificate used is not recognized as a trusted publisher by default on our managed machines, leading to the failure.
To resolve this for our enterprise environment, we would be extremely grateful if you could do one of the following:
Sign All Module Files with a widely recognized certificate (e.g., a Microsoft trusted root certificate). This is the ideal solution for corporate deployment.
OR
Provide us with the Public Certificate (.cer file) used to sign the files. This would allow us to distribute and install the certificate into our managed machines' "Trusted Publishers" store via Group Policy (GPO), establishing the necessary trust.
Fixing this would ensure smooth, secure deployment of your module across high-security environments.
Thank you for your support.
