The workaround works. Publishing the update with the Publishing tool instead of publishing with SCCM. There is a bug with spaces in the deployment name with SCCM publishing.