Cumulative Update KB4016871 Windows 10 v1703 Build 15063.296

IronZorg89 · 10 May 2017

@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.

Faith · 10 May 2017

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

pbcopter · 10 May 2017

Yes it is cumulative and contains the updates from earlier.

Superfly · 10 May 2017

Fafhrd said:

I see this and I think "If it ain't broke, what do you think you are trying to fix?"

SFC reports no problems, so why run DISM with the /restorehealth switch without running /checkhealth first?

What's more, do you have any failed processes which flag up component store corruption in the first place?

By all means upvote the Feedback Hub, but otherwise unless you really need to fix the component store, you are just spoiling for a fight!

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 ..

JSheridan · 10 May 2017

CWGilley said:

CU update and install yesterday with minimum trouble. Just ran WU and got this:

Attachment 134315

This has caused me to tense up! What do I do now?

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

Windows Update error 0x8024402f Solved - Windows 10 Forums

IronZorg89 · 10 May 2017

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.

Superfly · 10 May 2017

IronZorg89 said:

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 .. :)

EdTittel · 10 May 2017

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--

eLPuSHeR · 11 May 2017

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).

Bree · 11 May 2017

eLPuSHeR said:

Can anyone check if the autochk issue (chkdsk not triggering at bootup time) is really fixed?

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