At this stage the VM is not connected to our domain, is not activated and has no internet access. Glad I am not the only one having this issue.ĭownloaded WindEnterprise ISO from the Volume Licensing System, installed onto a VM using MDT 2013 and then started working with the VM. We even reset the local security policy to make sure there were no remnants left of any Patch for WSUS? We had temporarily opened all ports from the test computer to WSUS and vice-versa on the main firewall and the Windows firewall is disabled. Does anybody know if the Creator's update is able to be updated via WSUS or am I missing a specific This happens on a brand new computer that is freshly joined to a domain or any computer that has been updated to 1703. We have also limited all GPO's down to just the factory Default Domain Policy and one Windows Update policy that specifies the WSUS We have tried the whole stopping the Windows update service and BITS and then clearing the Software Distribution folders. You can actually see that it starts to initiate the appropriate patches for a brief second and then gets stuck. It will sit there indefinitely mind you, this only happens on the computers updated to 1703. All computers work properly other than the ones updated to Windfrom 1607 which get stuck with: Updates are available.ĭownloading updates 0%. We have WindBuild 15063 computers and other computers getting updates from a Server 2016 WSUS server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |