Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125

Problem persists, perhaps even worse than what I saw yesterday: KB Update still won't install, of course, but I just spent a few hours running an ISO in-place update, which also failed. While there was a notification about that, it did nothing other than to take me to the Windows Update module, where I found a failure note, and yet another KB waiting for a restart; that restart, of course did nothing.

I have only had one attempt at an actual install of the update, and that was the first time that I restarted yesterday; computer went into the "don't turn me off, I am working on this," which failed. Now, every time I try again, the machine just totally skips any attempt at installing the update; it simply goes to a normal restart.

MartinDL asked, "How about this? Reset Windows Update in Windows 10 Windows Update Activation Tutorials
would that fix the issue?" I tried that twice, and each time I get "Background Intelligent Transfer Service failed to stop." I could certain stand to receive the transfer of something intelligent. I am going to force a stop after posting this, try the batch file again.

I do have a Macrium Reflect full backup and the accompanying rescue disk. The backup is from Monday of last wee, as this wee's Monday full backup failed twice, and I have not had the to follow the instructions tech support sent me to try to fix this. I don't remember how to run the full backup restore, having only done it one or possibly twice, and definitely in not more than year. I am tempted to do this, but am also hesitant, as I have no guarantee that the time required will actually restore my Windows 10 backup capability: Given what happened during my first attempt yesterday, I suspect that problem arose then, so that restoring to 4December2017 ought to fix matters--but I sure wish I had some way of knowing that in advance, but I don't have a forward-looking time machine machine.

===
Stopped Background Intelligent Services, ran the batch file, which complained that the service was not running; hit Enter, service started, batch complained that the service did not stop, and quit. Given the amount of time I have spent, to no avail, over the past twenty-two or so hours, I may just quit....

Not Myself said:

Problem persists, perhaps even worse than what I saw yesterday: KB Update still won't install, of course, but I just spent a few hours running an ISO in-place update, which also failed. While there was a notification about that, it did nothing other than to take me to the Windows Update module, where I found a failure note, and yet another KB waiting for a restart; that restart, of course did nothing.

I have only had one attempt at an actual install of the update, and that was the first time that I restarted yesterday; computer went into the "don't turn me off, I am working on this," which failed. Now, every time I try again, the machine just totally skips any attempt at installing the update; it simply goes to a normal restart.

MartinDL asked, "How about this? Reset Windows Update in Windows 10 Windows Update Activation Tutorials
would that fix the issue?" I tried that twice, and each time I get "Background Intelligent Transfer Service failed to stop." I could certain stand to receive the transfer of something intelligent. I am going to force a stop after posting this, try the batch file again.

I do have a Macrium Reflect full backup and the accompanying rescue disk. The backup is from Monday of last wee, as this wee's Monday full backup failed twice, and I have not had the to follow the instructions tech support sent me to try to fix this. I don't remember how to run the full backup restore, having only done it one or possibly twice, and definitely in not more than year. I am tempted to do this, but am also hesitant, as I have no guarantee that the time required will actually restore my Windows 10 backup capability: Given what happened during my first attempt yesterday, I suspect that problem arose then, so that restoring to 4December2017 ought to fix matters--but I sure wish I had some way of knowing that in advance, but I don't have a forward-looking time machine machine.

===
Stopped Background Intelligent Services, ran the batch file, which complained that the service was not running; hit Enter, service started, batch complained that the service did not stop, and quit. Given the amount of time I have spent, to no avail, over the past twenty-two or so hours, I may just quit....

Have you tried Update troubleshooter. I know Brink's tutorial should do this better, but you never know

andreten said:

have you tried update troubleshooter. I know brink's tutorial should do this better, but you never know

I thought (well, perhaps there is a better word than insinuating that I did actually think) that I had put that into my previous reply, especially as I have an almost-readable copy of the error that the troubleshooter provided:

"Potential Windows Update Database Error detected, not fixed."

I don't know what that actually is, but am rather sure that it is the proximate cause of the update failures, and wonder if, somehow, it also caused the ISO failure.

I also suspect that I ran at least one other MS troubleshooter about this, or at least found and tried some possible update solutions which referred to that database, earlier today, but all of the various approaches I have tried starting yesterday afternoon, are now just a jumble of vague recollections.

Not Myself said:

I thought (well, perhaps there is a better word than insinuating that I did actually think) that I had put that into my previous reply, especially as I have an almost-readable copy of the error that the troubleshooter provided:

"Potential Windows Update Database Error detected, not fixed."

I don't know what that actually is, but am rather sure that it is the proximate cause of the update failures, and wonder if, somehow, it also caused the ISO failure.

I also suspect that I ran at least one other MS troubleshooter about this, or at least found and tried some possible update solutions which referred to that database, earlier today, but all of the various approaches I have tried starting yesterday afternoon, are now just a jumble of vague recollections.

Sorry, but looks like I've missed that part of the post. Sometimes simple tasks can achieve better results than complex one...
I did have some similar experience with one update, nothing helped till MS released a fix ... (or was it workaround?)
Hope you'll resolve this

f14tomcat said:

Defender Updates, along with other updates, can also be viewed in Reliability History.

Thanks for the tip. Really appreciate it :)

View Reliability History in Windows 10 Performance Maintenance Tutorials

Not Myself said:

I thought (well, perhaps there is a better word than insinuating that I did actually think) that I had put that into my previous reply, especially as I have an almost-readable copy of the error that the troubleshooter provided:

"Potential Windows Update Database Error detected, not fixed."

I don't know what that actually is, but am rather sure that it is the proximate cause of the update failures, and wonder if, somehow, it also caused the ISO failure.

I also suspect that I ran at least one other MS troubleshooter about this, or at least found and tried some possible update solutions which referred to that database, earlier today, but all of the various approaches I have tried starting yesterday afternoon, are now just a jumble of vague recollections.

First off, let me say that I don't really know how to fix your issue. Everything that I am going to say here is just suggestions. In your case, I think that the Occam's razor principle (law of parsimony) applies here. In layman's term, that means going from the simplest to the more complicated.
Now, having said that, I would suggest the following:
- Run sfc /scannow
- Run chkdsk /R C:
- Run dism.exe /online /cleanup-image /restorehealth ( even if you didn't find any integrity violations with sfc /scannow)
- Run Windows Updates troubleshooter one more time
- Check the following tutorial on how to fix Stuck Win 10 Updates. It has a similar link to Shawn's (Reset windows updates in Win 10) tutorial using a .bat file

https://www.addictivetips.com/window...ow-10-updates/

If all else fails, I am afraid unfortunately, you will have to go nuclear by reinstalling Windows 10 with a "Refresh" instead of a "Reset".

I really hope that helps you in resolving your issue.

IronZorg: Thanks, greatly appreciated. I shall get to it tomorrow, today is just too late, I'm too frustrated, etc.

Meanwhile, some progress. I found a suggestion to run sfc /scannow, which I ought to have thought of. For the first time ever for me, it found and replaced some files. It gave a location for the log, which I opened and quickly closed. I can read some medieval manuscripts, I can write and edit fire service training manuals, among my other weird capabilities, but reading that log does not fit into my skill set.

Having done that, I again ran the Windows Update troubleshooters, and knew immediately that something had changed, as it went into an apparently serious rebuilding of the Windows Update Database. It said to restart, but first it finished another part of its procedure, and gave some now-forgotten error message.

Rebooted, which of course failed. Reran troubleshooter, with again a forgotten error message, but I told it to skip the step about finding and starting pending updates. Not sure now just what I did next, but at some time I did a search for how to remove pending updates. Went to the folder, nothing there except an empty subfolder. I have no idea where the pending update file is located, as it is not where I was told it could be found

I forgot this, so here I shall add that I ran sfc /scannow a second time, which did not report any action taken.

Tried another restart, failed. Just before logging on here, after I had removed the empty subfolder, in Windows software distribution\ downloads, I reran the troubleshooter, and for the first time, it shows Potential Windows Update Database fixed and Windows Update Components Must Be Repaired, also fixed. Checked Windows folder, the subfolder I removed had be recreated, which might be what that second 'fixed' referred to.

Again, thanks, and having looked up "Zorg," I shall Groz....