Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125

Bree said:

Sounds like you have tried all you are comfortable with doing. The next cumulative update is a week away, due out on Tuesday 9th January, and will include all the fixes from this one. I'd wait and see if that installs OK, there's a good chance that it will.

Thanks Bree. I sure hope the next cumulative update works. Very frustrating for me, when I don't understand a lot of things discussed in this form, and these updates want install.

Sonjstar said:

I did a Restart last night and went to bed with it attempting to download or install,, and when I got up this morning it had failed again. I don't understand this either. It's showing that my computer has only 2 failed attempts, "KB4054517" to install last one on 12/13/17, but actually it has tried many, times. I tried to insert an image to show you what I see on my computer "view installed update history" but I can't post an image. Why would it say last attempt was 12/13/17, when I did a Restart last night and it attempted again. I have had another Win Update since this failure KB4058043, but I still only have Build 16299.98. I was told this should have brought my build up to 16299.125, but it didn't happen. I'm still showing 16299.98. I'm showing an error code "0x800705b4".

I just to add that you are NOT alone in having problems installing KB4054517, it's a widely known issue and MS has even acknowledged this too. My own experience was a small problem. In my particular case it DID install, but the software distribution folder didn't recognize it as installed even though it was confirmed by running winver 16299.125 and the update said it successfully too, then WU tried to attempt to install it ANOTHER FIVE TIMES before that ceased. (My guess is that MS sent a stealth update to cancel the repeated attempts. Also my system has been functioning perfectly since that too. Very odd. I agree with Bree the next Cumulative update is a week away and I would wait it out. Also there is always a well-hidden troubleshooter package, KB3073930 which you can download from the ms catalog which allows you to manually check off and block specific updates too.

AntJac said:

Strange. There's another definition update that installed on my Dad's pc fine so I checked and there is one ending .218 I think. That won't install either. Anybody else having that?

HI,
Are you sure the Os build belong to 1709? because the . 218 it was for =>

10586.218 - check the link

Windows 10 release information - current branch, build history

Thanks
MAMC

legacy7955 said:

I just to add that you are NOT alone in having problems installing KB4054517, it's a widely known issue and MS has even acknowledged this too. My own experience was a small problem. In my particular case it DID install, but the software distribution folder didn't recognize it as installed even though it was confirmed by running winver 16299.125 and the update said it successfully too, then WU tried to attempt to install it ANOTHER FIVE TIMES before that ceased. (My guess is that MS sent a stealth update to cancel the repeated attempts. Also my system has been functioning perfectly since that too. Very odd. I agree with Bree the next Cumulative update is a week away and I would wait it out. Also there is always a well-hidden troubleshooter package, KB3073930 which you can download from the ms catalog which allows you to manually check off and block specific updates too.

Thanks Legacy7955 for the info.

Thanks legacy7955

I followed your reply and downloaded MS KB3073930 and it stopped my laptop constantly trying to download this problem update KB4054517, when restarting, I`ll now hopefully wait for MS to put out its reworked update on Tuesday.

I for one appreciate all the comments but some are just to deep to understand and are not for the ordinary folk like myself LOL!!

Regards

Rich

@vidanova & Sonjstar:

You're most welcome! I'm glad I could be of some help.

Fact is Windows 10 Home users shouldn't have to be "power users" to keep their systems running
consistently, nor should the solution for common problems be a "fresh install" of 10, or editing the registry.
Yet this is what things have come to many times.

MS needs to strongly reconsider forcing major feature updates and cumulative updates onto ALL
Windows 10 users. Fact is that the WU system is just not proven reliable enough to do so. There should be an EASILY
found and implemented method to delay such updates for up to 5 months. I do agree that Windows Defender updates should be implemented at least weekly, but even then the user should be able to delay them as well for up to 7 days...
This way if any issues or bugs are found users have at least some chance to prevent major issues on their systems.

Update Done! :)

My issue with KB4054517 is that I have manually installed it and OS updates keeps trying to update it again and fails every time.
My WINVER IS 1709 BUILD 16299.98.
It happens every time i restart and fails causing an uninstall of update so I have chosen to hibernate Laptop to get around to time delay.