Windows 10: Cumulative Update KB4093105 Windows 10 v1709 Build 16299.402 - Apr. 23

That was 5 days ago! *Shock

 

Me too. I'm just waiting for it to show up on hide/show so I can block the thing.

 

You say that like it was 3 weeks ago and didn't include a weekend.

 

This is off-topic -- as this is what you see when you install build 17134.1.

I have installed the KB that is the topic of this thread -- and NOT seen this screen.

Please don't take this thread off-topic into other issues.

 

lol...ppl on the net have become so addicted to 0day news and such that 5 days (including a weekend) may actually seem like an eternity to someone

 

This didn't show up in WU until this morning for some odd reason or another. Must've come out later than my morning checks yesterday, looking at various timestamps. So far, so good, though.
--Ed--

 

I had to click check for updates on my 2nd PC for it to get it. Installed super fast for an old dino pc though.

 

Didn't find update upon startup this AM. Asked to Check for Updates this PM & it's now downloading it.

 

Dang! I was writing about today's update failure, whereupon Firefox killed that tab and would not retrieve it.

On to KB failure. Just as happened earlier this month, it downloaded, then appeared to stall at 70% installation; the next thing I saw was a Retry button, but I needed first to restart to update Malwarebytes. That showed me a restart of the KB installed around the usual 30%, but the next time I went to the computer, it asked me to log on.

Totally unsurprisingly, today's KB is marked as failure; as there was no retry button, which I am sure was removed by my restarting the machine, I started a new update search; after an hour or so, it stated that my computer is up-to-date; I tried twice more, each time taking less that a minute to report that there is nothing to be updated.

Malwarebytes proceeded to finish installing the update.

The KB install earlier this month failed in much the same way on both computers, which I reported it the relevant thread, but no one else commented on having the same problem. As my computer is working okay (except for that weird Firefox problem,) I am going to try to update my wife's computer.

===
Before starting the update on the other computer, I looked at Uninstall Updates, which shows that KB4093105 was installed today, even though the update history only shows that it failed. I am on Version 1709, OS Build 16299.402., which is the OS Build associated with KB4093105.

I would say "strange," but as this is Windows 10....

===
Wife's computer stalled at 70% (at least that is the last figure that I saw,) offered to retry. As my machine installed the supposedly-failed first install step, I decided to ignore the retry button and reboot. Machine is now running the latest KB with its relevant OS Build, but states that the install failed---another echo of my computer.

Only a few minor differences: After logging in after the update, it twice popped up a message to check the internet connection, which did not need checking, and when I went to the Windows update page, the retry button was still there. However, that button disappeared after I had checked the system data to determine that the update had installed, and a search for new updates proceeded, which found a Windows Defender to install.

Perhaps the strangest part of this is that this is the second Windows 10 update this month that demonstrated identical problems. Both machines are Dells, but of different models and years, with her computer having much less software than mine, and no software that I don't have. She has on-line access to a few school-related programs that i don't use, as I don't need to enter grades nor update a blog, but those are not installed locally.

 

Updated two office systems to 16299.402 and both are running fine. My two other systems are at 17133.73 waiting for the April final because I didn't wait for the final/final.

 

Installation has been stuck at 87% for some time now. Any ideas anyone?

Fortuunately this has now finished thanks to a hard-reboot.

 

Actually, Malwarebytes didn't finish installing the update; it was already installed. It's listed in Known Issues.

Known issues in this update

Symptom Workaround Windows Update History reports that KB4054517 failed to install because of error 0x80070643. Even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. To verify the installation and that there are no additional updates available, select Check for Updates.

You can also type About your PC in the search box on the taskbar to verify that your device is using the expected OS build.

Microsoft is working on a resolution and will provide an update in an upcoming release.

 

I wonder if a 3rd party AV is causing these issues. My 2nd PC had zero issues with the last few updates. It runs only Windows Defender. I am running 1803 on here so I cannot install this update with my Malwarebytes premium running to test it.

And because I am not a Macrium pro yet, I forgot that it was set to only retain 2 images. When my 2x weekly ran this morning at 5am, it wiped my backup of 1709 before I went Insider 1803 *Banghead

 

That's odd. I use the free edition of Macrium Reflect and I can keep as many images as I choose. How come you have a restriction?

 

It is set to run 3x a week so I can go back in time easily after testing something. I have it set to two, so I don't fill up my backup drive with images of my C drive. I have Macrium set on a schedule and rarely look at the backup drive. It is easier to have it run automatically and verify when making the image. Set it and forget it, so to say.