Windows 10: Cumulative Update KB4016871 Windows 10 v1703 Build 15063.296

Actually, it's "the other THREE updates". The same security/bug fixes are released as cumulative updates for each of the four versions - 1703, 1607, 1511 and original release (1507) although after this one Windows 10 version 1507 will no longer receive security updates. They are all listed here:

Windows 10 update history

 

@Fafhrd,


I Know sfc /scannow didn't show any integrity violations. One more reason why the DISM comand line should have completed to 100% because there is nothing to fix. It used to be that way before the advent of the Creators Update.

 

Heyhey! Being absence of the 15063.250 update, my machine finally got this one. *Smile My question now is; does this contain previous fixes from the .250 version? I assume so since it's "cumulative" right?

 

Yes it is cumulative and contains the updates from earlier.

 

Yip, that's a minor issue if components are OK..(but it should be fixed in updates...it's basic functionality )

I think online chkdsk initialization is more important ..

 

Here's a thread about this problem. Hope it helps. Good luck.

Windows Update error 0x8024402f Solved - Windows 10 Forums

 

Yip, that's a minor issue if components are OK..(but it should be fixed in updates...it's basic functionality )

I think online chkdsk initiation is more important .
@Superfly,

Thanks for seeing it the same way I do. It's a matter of basic functionality...Whether or not sfc /scannow finds or doesn't find any integrity violations, the DISM command line will give the same error message: 0x800f081f.

 

That will be a... Yep.... from me .. *Smile

 

All CB machines came through without issue. My Insider Preview PC (Surface Pro 3) showed the "update problems" message after the Cumulative was installed, but I cleared it with a combination of the Update Troubleshooter and the "turn off options" item in this TenForums post: Windows Update error 0x8024402f Solved - Windows 10 Forums. Once again, it appeared related to Windows Defender updates, FWIW...
So far, so good!
--Ed--

 

Can anyone check if the autochk issue (chkdsk not triggering at bootup time) is really fixed? I forced one today and, when booting, it did it just for two seconds and 100% completed was already on screen. There was no chkdsk file on root folder either (I don't remember the file name sorry).

 

It was the second thing I checked after updating to 15063.296. It worked as expected.
(The first thing was DISM, which didn't.)

 

I had this problem too with chkdsk at bootup. It was fixed after the last cumulative update.

 

Thanks for checking it out. *Cool

 

Very good afternoon, group of users of our multicolored window. I write in this post because lately the last 2 updates have not been installed on my operating system (Creator update 1703, built 15063.138), which before it officially , I manually installed This OS ( Creator Update ) (Although they remember there were 3 Versions before the official version, which was released in April.) , In that Order.

Those update are the KB4016871 and the kb4016240

I install the March version (the manual version released on 15 or 20 of the writing month , not the final version ).

The problem is that every time I install it via windows update, it downloads and installs it normally, but when it reboots it says the majestic words: "We could not complete updates undoing changes".

I tried everything (Install via Cab files., Via MSU and running the update troubleshooter) and happened the same trouble.

I have also tried the sfc / scannow and found no problems and remember that the DISM does not work yet.

I would like someone to help me since I am not in the mood to reinstall the operating system again (I already do the restoration and nothing), I do not think it is some service that will disable it.

Thank you so much.

 

downloaded and installed on my desktop
had no problems did a sfc /scannow said no problems but an hr later the computer just shut down. started it up again and so far not happened again in last few days