Cumulative Update KB4089848 Windows 10 v1709 Build 16299.334 - Mar. 22

Wynona said:

OK, just checking. Stranger things have happened. :)

Absolutely, my question at this point is if there is a procedure to fix it or if Microsoft, at least, knows about this reinstall loop problem...

EDIT: basically i had the same problem with the infamous KB4054517 update, and then I had to format, no way to fix that! I just don't want to format again

Nandos said:

I'm having problems with this update. Basically I'm in a sort of restart to install loop. I reboot the PC, it installs the update, then WUpdate tells me is waiting to reboot to reinstall it again, and it happens over and over and over . Any fix? At the moment, I uninstalled it just to be sure...

Had the same problem with this update. Winver showed 16299.334 installed but Windows Update showed it as requires restart to finish installing. I uninstalled it and downloaded the MSU from post 1 and reinstalled it using that. Winver shows 16299.334 but Windows Update history now has 2 entries listed for this - first requires restart to finish installing - second shows as successfully installed.

A complete mess from the beginning and has clearly not been thoroughly tested prior to release.

I have a new laptop that is just a couple of days old that is at Build ....309. I haven't been offered the latest update that this thread is about yet through WU. On my last laptop, I had the same issue in that I wasn't offered it and I applied that key registry fix and then the update was made available through WU and I installed it and it seemed to go okay.

With this new laptop everything is perfect and I don't want to mess it up. What would be the safest way to proceed? In general and if the first two options fail?

1. Wait and see if this update is offered in next few days from WU.
2. Wait till next CU and see if it is offered through WU.
3. Use the key reg fix posted by phone guy.
4. Download the update from Windows Update Catalog and install it manually.
5. Some other suggestion.

Main thing is I don't want to run into some looping issue or other issues because I don't think my heart/spirit can take it, lol. Thanks.

WEKJR said:

I had one system that didn't receive the .334 CU and three that did. I downloaded the update from the MS Site and installed it on the one system not receiving it. All went well. This is just my input.


WEK

I gave it a try and it seems to have installed fine. Thanks.

Instead of it showing Cumulative Update in update history for this particular update it just shows "Update for Windows KB4089848" Successfully installed on 3/29/2018. System/About shows build 16299.334. SFC scan finds no errors.

I guess I can now do a backup image.

tomseys said:

I have a new laptop that is just a couple of days old that is at Build ....309. I haven't been offered the latest update that this thread is about yet through WU. On my last laptop, I had the same issue in that I wasn't offered it and I applied that key registry fix and then the update was made available through WU and I installed it and it seemed to go okay.

With this new laptop everything is perfect and I don't want to mess it up. What would be the safest way to proceed? In general and if the first two options fail?

1. Wait and see if this update is offered in next few days from WU.
2. Wait till next CU and see if it is offered through WU.
3. Use the key reg fix posted by phone guy.
4. Download the update from Windows Update Catalog and install it manually.
5. Some other suggestion.

Main thing is I don't want to run into some looping issue or other issues because I don't think my heart/spirit can take it, lol. Thanks.

I used to chase the updates to make sure my systems were up to date. But since the first of the year when MS started the weekly updates, I say enough is enough. I 2 Home systems and 1 Pro system. 1 of the Home systems gets the updates almost immediately. The other Home system I'm not sure about, because I've only had it for about 3 weeks, but the Pro system hasn't received any of these "emergency" weekly updates ? For example both systems were at 192. The Home system received 214, Pro system did not. Finally 248 and both system received it. A week later 251 came out, the Home system got it, the Pro never did. Then came 309 and both systems got it automatically. Now the Home system has 334, not the Pro system.

If I felt that I had a WU problem, then I would do a manual update, but looking at the history that's not a problem. So I just ignore it and see if there is a newer one going to come in.

storageman said:

I used to chase the updates to make sure my systems were up to date. But since the first of the year when MS started the weekly updates, I say enough is enough. I 2 Home systems and 1 Pro system. 1 of the Home systems gets the updates almost immediately. The other Home system I'm not sure about, because I've only had it for about 3 weeks, but the Pro system hasn't received any of these "emergency" weekly updates ? For example both systems were at 192. The Home system received 214, Pro system did not. Finally 248 and both system received it. A week later 251 came out, the Home system got it, the Pro never did. Then came 309 and both systems got it automatically. Now the Home system has 334, not the Pro system.

If I felt that I had a WU problem, then I would do a manual update, but looking at the history that's not a problem. So I just ignore it and see if there is a newer one going to come in.

Thanks Storageman. Now that I've got a baseline of a full update with this laptop and everything looks and is behaving peachy, I think I'm not going to worry too much about the updates going forward. I've also noticed that sometimes a laptop will get an update, another won't, but usually they all end up getting it sooner or later. I guess I just wanted to get this fully updated safely so I can image it and then relax.

Version 1709 Build 16299.334 downloaded, and running fine here.