Windows 10 Hotfix Repository

Look, i only told parsix that the dynamic setupupdate is not meant for integrating in install.wim/boot.wim/winre.wim, but only for updating the installmedia itself.

Your reply about the uselessness of integrating any updates in boot.wim/winre.wim was based on you not really knowing on what or how.

Since windows installs have the inbuilt recovery/reset option it's better to keep the winre.wim uptodate at time of installation.

You state that updating the winre.wim and boot.wim only increases their size, but if you once had tried it, you would have found out it is very minor.

Boot.wim (x86) updated with servicing stack and current CU: size increased appr. 4MB
Winre.wim (x86) updated with servicing stack and current CU: size increased appr. 2MB

So there is nothing to loose and all to gain, better safe than sorrow

 

i have not any problem with kb3201845
my base iso: en_windows_10_enterprise_version_1607_updated_jul_2016 (VL-original)
my answer file is ok.

Test 1: kb3201845 integrated to boot.wim index 2 (Original boot.wim on iso jul_2016 ) and worked fine
Test 2: kb3206632 integrated to boot.wim index 2 (Original boot.wim on iso jul_2016 ) and show ProductKey Error in answer file (windows installation-boot.wim intex 2).


kb3201845 and kb3206632 integrated by dism (Report):
test 1:

Code:

Dism /Image:"Z:\Windows_Develop\Temps\Mounted-Boot" /Add-Package /PackagePath:"Z:\Windows_Develop\00-WHD-Updates\Downloaded-Updates\Updates\Windows10-x64\General\14393\Windows10.0-kb3201845-x64.msu" /ScratchDir:"R:\UpdateScratch"

[==========================100.0%==========================] 
The operation completed successfully.

test 2:

Code:

Dism /Image:"Z:\Windows_Develop\Temps\Mounted-Boot" /Add-Package  /PackagePath:"Z:\Windows_Develop\00-WHD-Updates\Downloaded-Updates\Updates\Windows10-x64\General\14393\Windows10.0-KB3206632-x64.msu"  /ScratchDir:"R:\UpdateScratch"

[==========================100.0%==========================] 
The operation completed successfully.

error only in KB3206632 (test 2)

 

What answer file are we talking about, can you show us?

I don't see you mentioning you've integrated the servicing stack first, did you?

What error do you exactly get and when do you get it?

And last but not least, did you try to integrate the non integrateble dynamic setupupdate in these scenarios?

 

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.

 

I just received this: Cumulative Update for Windows 10 Version 1703 for x64-based Systems (14986) (KB3206309) Anyone know anything about it?

 

You need to login to view this posts content.

 

I updated a clean msdn enterprise windows image by using abbodi1406's W10UI_1.8 script and used your autounattend.xml and i didn't encounter any error during setup in vmware.

 

You need to login to view this posts content.

 

Cumulative brings system to 14986.1001. Lack of further details, though.

 

You need to login to view this posts content.

 

i install from usb disks, i put anwserfile in root folder in boot.wim index 2. i try new test
my app and abbodi1406's W10UI_1.8 script have same algoritm, my app is GUI and abbodi1406's W10UI_1.8 script is command line base

my apps is smart, detect correct ms Updates for windows

 

Whether the app you use is smart or not has nothing to do with your errors.

The autounattend.xml file has to be in the root of the iso, not inside the boot.wim.

 

You need to login to view this posts content.

 

my app have 3 mode for answer file (answer file can be exist in Root boot.wim index 2 or System folder or root of the iso), when put in Root boot.wim index 2 you don't need handle usb errors. in all 3 mode it read and work fine.

refrence is microsoft site, i test this mod on 2200+ pc and laptop, very usefull in usb boot
Test it

 

You need to login to view this posts content.

 

I have ADK installed on Windows 10. However W10UI_1.8 does not recognize it when running. Another thing is that it does not create Windows ISO when finalizing.