I joined this forum so that I could let folks know what fixed my update problem. After trying everything, I just went to Disk Management and set my C: drive where Windows is installed to Active. Update was then successful.
My mistake was installing a boot loader once.
The only reason I can surmise that it would even make a difference setting your C: drive as Active using Disk Management, is because of either one or two things. Firstly, it would only make a difference if you were running more than one physical hard drive or secondly, you have more than one operating system on a primary partitioned hard drive; in other words your C: drive on one physical hard disk.
The MBR (Master Boot Record) is what I'm getting at; so if this made a difference and your computer is not structured as I outlined above in the two scenarios, I would be inclined for further input from you as to why this worked or why you think it worked.
By the way, that Cumulative Update that this thread is about, downloaded successfully for me by the sixth day after its official release. Just like they normally do after so many days of their official Microsoft release date.
This pertains to my rant in post #21 in case anyone missed it. Furthermore, I don't understand why so many feel the need to restructure their computers because of slow updates or updates freezing. Did anyone ever think that maybe Microsoft servers are extremely busy and nothing is wrong with the computer at all?
I added a second drive for a short time but the primary drive did not play nice with it so I removed it again. The reason I know the update process was faulty is that after approximately 17 various occasions having the update install up to 100% and than saying the update failed and waiting for it to uninstall again, I suspected an update problem.
I had tried all of the usual fixes, both automatic and batch files. It wasn't until I set the partition active that the update installed.
I'm still not following the reasoning behind setting the partition active if there is only one drive installed now. You don't have to set a partition active unless you have various partitions on the C: drive and it contains more than one OS on different partitioned sections.
In other words, if you removed your other physical hard drive and you only have one OS installed on the current drive and partition, by default the drive/partition should be active for your system wouldn't boot because it couldn't find the MBR. So since it did boot and you were able to install the update, I'm finding it somewhat difficult to grasp that setting the partition Active was the cure for the failed update and unnecessary being the only OS. I know this, because one cannot get into Disk Management unless the computer actually booted in the first place, unless you selected a boot first device on start-up.
Computers only have problems if two partitions of the same physical hard drive or two hard drives are marked as active because the MBR of different drives or different partitioned Operating Systems would fight each other.
How many days after the Official release of the update did it finally install for you? Just go to the Microsoft Update Catalog and see what day the update was officially released and then tell me how many days out after the release you were able to install the update in question. Then maybe I can get a better understanding if something else was actually the culprit.
Last edited by EyeInTheSky; 21 May 2017 at 12:38. Reason: Additional thoughts.
I registered to this forum for giving big thanks to ZaphodBeeblbrox for his ideea and to pjc123 for his explanations on the ideea and also for telling you what worked for me. So, I noticed that the laptop of my daughter was failing to install the KB4019472 from early april almost daily. After many researches on forums and useless solutions from ms experts like troubleshooter on-line or downloaded and very exotics ideas of other types of experts I saw and tried successfully the procedure indicated below :
EyeInTheSky,
I believe that I have a windows boot-loader somewhere on a partition that loads first and the activates the windows boot-loader. My update KB4016871 finally installed on 5/16/2017.
Windows was booting fine but when I looked at my windows 10 partition with disk management, there was the little yellow triangle and the partition was not active.
My mistake; I was under the impression that you had done away with the boot loader upon getting rid of the conflicting drive.
Also, I thought you were having problems with the Cumulative Update KB4019472; not the KB4016871 that you are mentioning now. What is KB4016871, I can't find that one in my update history?
Never mind, I see why now. That update is for version 1703 - Creators Update right? I currently have version 1607.
Last edited by EyeInTheSky; 21 May 2017 at 19:34. Reason: Just realized something.
Fixed / Solved Installing Windows 10 Update installation problems.
the KB4019472 update,
It took multiple attempts for my fix / solved.
I had tried to net stop the processes, deleted the distribution folder, reboot etc, but install was still completing but failing, not installing successfully. triversion downloading the offline update version, Nope didn't work.
Then ran admin cmd window sfc / scannow which ran but left one unrepaired issue in a boot system file or something. I rebooted and tried again, same thing.
So then I ran the TroubleShooting utility from Control Panel which said it ran fine, but install still didn't work.
Before I planned to try the Creator tool, I thought I Would try the following to see if it might fix and repair the boot file issue since it implied a stronger Repair.
SO..,,
1. ran PowerShell as admin and then
2. typing: Repair-WindowsImage -Online -RestoreHealth
3. Then Stayed in powershell and ran: sfc /scannow
4. Rebooted
5. Installed stand alone update ( kb4019472) since I had downloaded it powershelll6. It rebooted and indicated successful install (confirmed in windows update settings history, and also in Control Panel, windows options / updates, and finally say it in the list there.
7. Rebooted again for good luck, Turned off wifi metered mode to return to normal.
Yeah!Good luck.
-Guy
gschlact
SOLVED!
I was able to bypass the KB4019472 update yesterday by installing the Creators Update using the Media Creation Tool. It allowed me to use a USB flash drive to run the tool, and an external USB hard drive for the 10GB of temporary space needed for the upgrade. After that, running a regular Windows update brought me up to all current updates. I even gained 1GB of space. I will not let inanimate objects beat me.
Quote