Well, there is this. though to be honest I've never seen any evidence of it in action...
I leave that ticked and get Office updates along with Windows ones, doesn't seem to be a problem.If the "Give me updates for other Microsoft products when I update Windows." box is "checked", the updater throws out error codes and Windows Update doesn't search for updates properly. If it does find updates when that box is "checked", their download and install rate is usually a failure.
Good catch. I found out after the start of the thread and was going to post back with my findings later today - you got there first and due credit goes to you for the correction. Thank You for the correct download domain posting.
Yes, I've looked at the running task host processes (I think that is where it would show up) and I haven't experienced any increase or decrease in download times when choosing how updates are delivered.
The problem only persisted on the laptop I got and not my desktop. I'm referring to updates for other Microsoft products in my previous posts. I really do think the upgrade process of the OS went south on the laptop because it uses that UEFI firmware and not the old BIOS technology and the files copied differently or something.
I'm going to use RUFUS to remake the bootable USB and hopefully the install.wim file gets copied correctly, because DISM is reporting an error that points to that file missing or being only partially copied.
I initially used USB installer to make my first bootable copy for my desktop and thought it would be fine for the laptop as well. Turns out I was wrong, because even though the laptop is the same architecture (64 bit), it has a different type of BIOS firmware.
Last edited by EyeInTheSky; 31 May 2017 at 15:20. Reason: Correction
I got the laptop up and running with Version 1703 Build 15063.332 and the Windows Update feature is working perfectly fine as well. My desktop and laptop are now both successfully running the Creators Update. The laptop required having a different boot signature on the bootable USB and RUFUS was able to allow me to get the type of partition management I wanted as well.
I'm going to mark this thread as solved and hope that it helps people running the new type of BIOS firmware UEFI. It is peculiar that I thought this thread was about slow updates and it turns out that it was about finding the correct way to install an OS with a computer running the new type of BIOS firmware. Manufacturers still relate to the new UEFI as "BIOS" even though technically it is different than the old BIOS; but the manufacturers just didn't want to confuse new computer buyers into believing that they had a BIOS that was unable to be upgraded.
The files from a bootable USB containing the ISO of Windows 10 (Creators Update 1703) that is constructed wrong for UEFI will copy wrong to your active partition for windows and result in the install.wim file not being copied over correctly.........well in my particular case anyway, and caused files needed by windows update to be corrupted or partially missing.
Oh, and thanks to all that replied!
Last edited by EyeInTheSky; 01 Jun 2017 at 13:55. Reason: Added Thanks!
Quote