To download them WITHOUT USING Media Creation Tool, refer to the article:ĭownload Official Windows 10 ISO Images Directly Without Media Toolĭownload the latest version of Windows 10 Media Creation Tool from here Just to double check, I also have fired up a second Windows 10 system, which has been activated via the internet and then had internet access removed.To get the official ISO images, you need to do the following. Eventually the system knew there were updates, and again the download started and got stuck at 0%.Īt the moment I only have one download approved (Adobe Flash Player) and am waiting for the system to attempt to download this update. So in order to test this, I removed the Cumulative Update from the approval list, reset all Windows Update settingsĪnd waited. Windhas an acknowledged problem that if Cumulative Updates were approved, they would stop the downloading of updates. Moved the computer to our testing group where I have the latest W10 1703 Cumulative Update approved, along with Silverlight,Īdobe Flash Player and Visual C++ 2008 SP1 (all updates it reports it needs).Īpprox 1 hour later, the system knows it needs the updates and starts the download 14 hours later the update has not downloaded (same as the OPs screenshot) Make the changes in local group policy and almost immediately the computer shows up on our WSUS server in the Unassigned category. 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 kommentar(er)
