New
#11
I would typically do updates off peak hours.
Failing updates on a fresh install are rarely the fault of the update itself. It is because the Windows Update process tried to install the updates out of order.
That said, there are some buggy updates. Please write an operating system and updates for us that does not have this issue.
I'll send a mail to Bill. If you want to, you can join, here's his email : b.gates@microsoft.com
Usually, he has nothing to do other than reading mails and saving the planet, so I think our issue will be solved very quickly.
I don't know how to write an operating system. I was hoping that you would write one for us that did not have these buggy updates
If you really want to build on operating system from scratch
One way is here
https://help.ubuntu.com/community/Li...ionFromScratch
Another way is here
https://help.ubuntu.com/community/In...tion/MinimalCD (Others distros might also have a MinimalCD)
Note: While the minimal iso image is handy, it isn't useful for installing on UEFI-based systems that you want to run in UEFI mode. The mini iso lacks the proper files for booting the computer in UEFI mode. Thus, the computer will boot in BIOS compatibility mode, and the installation will be in BIOS mode.
"If we only knew why some computers are not having these problems, then maybe we could help those that are." I cannot remember reinstalling any Windows 7 in the last few months that did NOT have these problems. It does not seem to matter if it was a clean install or just returning to factory conditions.
"Load only Important updates and forget Recommended and Optional ones will help a lot." I agree completely with this comment and that is what I always do.
"For me it takes all day but that because I have slow high speed connection." As for me I have a fast download speed, but you have realize that you can only download as fast the server sending to you can provide. I also agree with another statement that Microsoft downloads have always been slow.
I have Virtual Machines that have only SP1 installed. I watched Wireshark from the time that I requested updates to the time that I was given a list of ~200 items to be installed. I saw some interesting connections, but that is another story. I did this three times this past weekend - testing different DNS configurations. It only took ~20 minutes to get the initial list of updates. For all three tests, I manually installed the September Windows Update Client patch before asking for the initial list of updates.
When I exit the particular Virtual Machine that I use for this testing, I do not save any changes. This means that the next time that I want to test how long it takes to get that first list - I am starting from the exact same point. I have tested this "time to list" dozens of times over the past few years*. I have seen it take several hours or less than an hour.
*It is not that I have been interested in the WU update time all of these years, it is the way that I use these VMs that has given me lots of empirical data on this point. I only recently decided to keep/save one VM all patched up. In the past, if I wanted to test software conflicts with recent patches, I had to take the time to fully patch a VM.
Very little data flows while gathering this first list, so download speed is not an issue for that part. When I opt to install all updates, the biggest variation in timing is the media. It takes more than 5 hours to fully patch the Virtual Machine when it was on a 7200 RPM spinner. It takes much less time when the VM was on an SSD. I have tested this using two different ISPs. Downloading the files does not seem to be an issue for me. They come in pretty fast.
The problem is: it is taking much longer for some people to get that initial list and much longer to get the files downloaded/installed.