Windows 10: Reporting successful install of 1-2018 Cumulative Update KB4056892

Just wanted to report that I just received the lastest 1-2018 Cumulative update KB4056892
and it installed without any issues, for reference it took just over 8 minutes and
there were some odd screens which I haven't seen before, one of which was
a blank screen using MS basic video graphics for about 2 minutes all you see is the spinning dots
with low res graphics .....At first I thought I had a problem but then it moved onto the more typical blue working on updates screen and the %.

Confirmed with winver I'm on version 16299.192

This is the first PC I have tried this update on which is from 2014 and upgraded from 7 to 10 just a week ago!
Next is the PC from 2009, which I also upgraded from 7 to 10 last week. I'll post an update tomorrow.


Aside comment, the number of updates on 10 is dizzying and annoying as well.
What I really DISlike intensely is that the updates download WITHOUT my permission even during
active hours! I have a very slow connection and it kills my ability to do anything on the internet except the update.
MS needs to change this for low speed connections soon. It's driving users away. There are still MANY users with glacially slow connections speeds and we simply can't deal with this kind of behavior .

:)

 

Cumulative Updates Windows 10 version 1709 multiple fails then success - what does this really mean?

I have been trying to get Windows 10 version 1709 to accept Cumulative updates since January. Here is the history of attempts:

Cumulative update 2018-01 (KB4056892) 134 failures, over many days, with most common error code 0x8024200d and last failed attempt on February 5, 2018. This update never successfully installs despite trying several official suggestions except a complete
reinstall.

Cumulative update 2018-02 (KB4074588) 27 failures, over several days, with most common error code 0x8024200d and last failed attempt on March 16, 2018. This update never successfully installs despite trying several official suggestions except a complete
reinstall.

Cumulative update 2018-03 (KB4088776) March 16 1 failure with error code 0x8024200d

Cumulative update 2018-03 (KB4088776) March 16 update installs

My question is: Does the successful installation of Cumulative Update 2018-03 mean that all the changes included in updates 2018-01 and 2018-02 are now on this machine and I no longer need to be concerned about the failures of the two earlier updates to
install?

Thanks for any insight into this issue.

 

Jan 2018 update failed to install

Hello Michelle,

I downloaded KB4056892 from the Catalog and successfully installed it. The only anomaly that I now observe is, on my "Update History List"; there are now two KB4056892
entries.

The first listed entry reads:

Security Update for Windows (KB4056892)

Successfully installed on 1/19/2018

The second listed entry reads:

2018-01 Cumulative Update for Windows 10 Version1709 for x64 based Systems (KB4056892)

Failed to install on 1/4/2018 - 0x80070643

NOTE: The ID numbers for the two updates are identical, however, the titles of the Updates vary significantly. The Update with the successfully installation status is the one that I manually downloaded and installed, I suppose that I should
simply ignore the "Failed To Install" entry. I'm confused.

 

I think you'll be noticing this 'cos you've just upgraded. Things should then quieten down.

Otherwise you could upgrade to Pro where you have more control via Group Policy. The initial upgrade will be followed by another large update, then you get an update about once a month, with possible driver updates.

Or disable windows updates for a couple of weeks, then catch up...

Please see the News section for a thread per update per build.

Every 6 months, there's a new major build (where all system files are replaced). This is very unlike '7 (no SP1,2,3, hundreds of updates if you reinstall thankfully!) and
- advantage- applying new build can sometimes solve bugs in a corrupted system
- disadvantage- new build can introduce new bugs and incompatibilities
- advantage- reinstalling is usually - reinstall + 1 big update + 1 cumulative update.
- advantage- in place repair install is typically last major build + 1 big update + 1 cumulative update.

That's a very very rough guide.

 

Update:

Just updated my 2009 HP Pavilion p6680t (upgraded from Win 7 to Win 10 last week) with KB4056892 today.
It did install successfully, however after downloading it appears to download a partial additional payload and appeared to install and
fail initially with a error code of 0x8024200d.

Took about 10 minutes and showed some of the same odd screens that occurred on my Acer Aspire AXC-605.

 

Did Microsoft fix the update?

 

I don't see anything that "clearly" indicates this. from my research on the net. It could be that MS will send out a revised version of this update in the weeks to come that remedies the issue.

I've been a Windows user since 3.1 way back in the early 90s and I' very disappointed in the direction MS is moving since Windows 8 arrived.
With the forced updates, garbage apps being forced on users as well and advertising.....I might be moving to Linux Mint for good soon.
I wish MS would invite Paul Allen back to the company as a consultant. He was the real brains and innovator behind Windows OS and maybe he can persuade the company to start listening to their customers again.

 

This update caused one of my old AMD based PCs to fail to boot after the update so I've had to block the update for now.

 

Yes, I've been over on the MS Community Forums and it seems like MANY AMD chips are affected.

I wish that MS Community Forums and / or tenforums would set up a specific forum section for users to post threads of their experiences
with a specific update . Where you must use the KB number and then introduce the thread with any issues and or characteristics encountered.

 

There is a thread per update per build in the News section.

 

Thanks for that....I didn't realize that it would not only focus on new builds but cumulative updates as well.

 

You're welcome - the one on the most recent update 4056892 related to chip security risks is rather lengthy. The links to the updates for manual download are posted in each thread too.