Windows 10 Hotfix Repository

No it's not, this is my current project:

Integrating kb's into 10586.0 win image (offline, manually, one by one in the red marked order)

With dotnetfx pre-enabled:

Code:

1.
Package Identity : Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~x86~~10.0.10586.0
State : Install Pending
Release Type : OnDemand Pack
Install Time : 12/7/2015 10:21 PM

Integrated kb's:

Code:

2.
Package Identity : Package_for_KB3116278~31bf3856ad364e35~x86~~10.0.1.0
State : Install Pending
Release Type : Update
Install Time : 7/15/2016 12:35 AM

3.
Package Identity : Package_for_KB3173428~31bf3856ad364e35~x86~~10.0.1.0
State : Install Pending
Release Type : Update
Install Time : 7/15/2016 12:36 AM

4.
Package Identity : Package_for_KB3174060~31bf3856ad364e35~x86~~10.0.1.0
State : Install Pending
Release Type : Security Update
Install Time : 7/15/2016 12:36 AM

5.
Package Identity : Package_for_RollupFix~31bf3856ad364e35~x86~~10586.499.1.0
State : Install Pending
Release Type : Update
Install Time : 7/15/2016 12:49 AM

No problem, manually.

ps, they get state: "pending" because i've pre-enabled dotnetfx before integrating the other kb's.

EDIT:

Now this happens when I do exactly the same on an offline 10586.0 image without dotnetfx3 pre-enabled (so all updates should get state: "installed":

Integrating the current CU after doing step 2 > 4:

Code:

An error occurred trying to open - e:\WIM.Kaal.x86_NL\4.CU Error: 0x80070003
An error occurred trying to open - e:\WIM.Kaal.x86_NL\4.CU Error: 0x80070003

Error: 3

An error occurred trying to open - e:\WIM.Kaal.x86_NL\4.CU Error: 0x80070003

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Getpackages after:

Code:

Package Identity : Package_for_KB3116278~31bf3856ad364e35~x86~~10.0.1.0
State : Installed
Release Type : Update
Install Time : 7/15/2016 1:03 AM

Package Identity : Package_for_KB3173428~31bf3856ad364e35~x86~~10.0.1.0
State : Installed
Release Type : Update
Install Time : 7/15/2016 1:05 AM

Package Identity : Package_for_KB3174060~31bf3856ad364e35~x86~~10.0.1.0
State : Installed
Release Type : Security Update
Install Time : 7/15/2016 1:05 AM

 

You need to login to view this posts content.

 

That must be the reason they released a new CU so fast after the previous one.

On 14388 RS1 preview it never showed up.

 

Interesting.
BTW updates for version 1607 started to appear Microsoft Update Catalog... I see KB3176476 and KB3176479 dated on July 14.
What's going on...

 

You need to login to view this posts content.

 

Gosh, really?
RS1 update doesn't released yet, but they already make tons of KBs?
Sorry, but i hate to integrate patches in winre.wim & boot.wim
Also, catalog.update.microsoft.com doesn't work for me now.

 

Compared, to .494, the new build only features new lddmcore (the graphics subsystem)

 

Same Here....
Need Help with Links to these Updates for 10240 in order to update Review - KBs 3163912 CU, 3173427 SS, 3174060 FP, 3172983 DU
... TIA

 

It's working for me here. Tried to download kb3172988 and it's working.
BTW how to grab download links on Windows 10? Sorry for the stupid question...

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

So? where is the question?

Nevertheless, servicing stack goes first
it's mainly affect running os

 

The question is: Why this:

When offline pre-enabled dotnetfx3 the integration of all needed updates goes fine and also without the servicing stack integrated first.

 

servicing stack is actively used when you boot the image to install it
integration don't matter much

 

I know but there is something about it.

For me personally it's not a biggy (i always first offline enable dotnetfx3 so the CU gets "install pending" and will install after it and update it, if needed).

 

It is not useful to integrate this update to ISO? and install it afterwards ?