All ISP issues cleared for now (or appears to be), so... Started updating Review (Updated 1703 to include Latest IP CU KB4034450) ....... Links can be found at foot of post, under Spoiler TESTING, TESTING... Some bits and bobs still to be added, also ... Adopting a format that will make lists easier to manage in future.. All other OS versions will be addressed as soon as.... but will be up to date by next PATCH day
You could just set the script to enable dotnetfx3 and no resetbase on the windows indexes will be performed, on winre and boot.wim it's better to do a resetbase anyway..
just tried enabling dotnetfx3 (set net35=1) and got this: Spoiler ============================================================ Adding .NET Framework 3.5 feature ============================================================ Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 An error occurred trying to open - 1 Error: 0x80070003 An error occurred trying to open - C:\cab\1 Error: 0x80070003 Error: 3 An error occurred trying to open - C:\cab\1 Error: 0x80070003 The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Do I need to add something to the repo-dir to enable dotnetfx3 ?
You should just let the script run on the extracted iso not directly to the install.wim. Of you only care about integrating the updates into the wim use this 3 line script: Code: Dism /mount-wim /wimfile:x:\install.wim /index:1 /mountdir:y:\mount Dism /Image:y:\Mount /Add-Package /PackagePath:z:\updatesfolder dism /unmount-wim /mountdir:y:\mount /commit
I'm a bit confused right now. Where do I specify the target folder to enable .NET 3.5 in the W10UI.cmd? " # Enable .NET Framework 3.5 if available source detected locations to be checked: mounted iso, inserted dvd/usb, sxs folder for distribution target so provide one of these if you want to auto-enable it"
Regarding the ResetBase issue, it seems this registry value prevent the removal of superseded components in offline operation (maybe online too, but i didn't check) Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Configuration] "DisableResetbase"=dword:00000001 it basically makes the /Resetbase parameter not effective and DISM perform the standard ComponentCleanup operation by delta-compressing superseded components, which makes the process takes longer setting the value to 0 solves that on a side note, i see that in build 15063 and later, "%windir%\Logs\CBS" directory is now protected by TrustedInstaller they don't want us to delete the big logs?
its possible they locked logs\cbs the whole OS cauze is online and when you make first log in account without e-mail or with e-mail automatically "trusted Installed" get the whole Permission Rights?
No, that's has nothing to do with login or account, it's for servicing (updates, features, SFC, DISM)
Thanks Microsoft for disabling features and taking good care of my OS Edit: Thanks @abbodi1406 It works ResetBase much faster (around 4 min with Win10 LTSB 2016 x64).
W10UI 3.1 - Added option to skip Resetbase operation - Added visible menu options for .NET 3.5 and Resetbase - Implemented auto fix/change for registry value DisableResetbase (to allow Resetbase) - Enabling .NET 3.5 now occurs after installing updates (to allow Resetbase), and cumulative update will be reinstalled afterwards - Few improvement to handle "All applicable updates are found installed" situation - Windows 10 ADK DISM will be used if detected, even if Host OS is Windows 10 Edit: v3.1: Added option for custom path to .NET 3.5 cab source
abbodi1406, since I update my wims directly, is enabling .NET 3.5 supported if microsoft-windows-netfx3-ondemand-package.cab is put in the updates directory with the rest? The readme states you only check three locations.
Updating 1607 LTSB x64 install.wim with June updates took only half an hour to complete on my system with W10UI v3.0. I haven't decided yet whether to enable .NET 3.5 in my target wim (if supported as mentioned in my previous post) or do it with SetupComplete.cmd using dotNetFx35_WX_3_x86_x64.exe Spoiler =========================================================== 1. Target (x64): "x:\$W0\$0_WUI\x64\LTSB+06.wim" 2. Updates: "x:\$W0\$0_WUI\x64\Repo-Dir" 3. DISM: "x:\$W0\ADK_6\amd64\DISM\dism.exe" 4. Enable .NET 3.5: NO 5. Reset Image Base: YES =========================================================== 0. Start the process =========================================================== Change a menu option, press 0 to start, or 9 to exit: . . =========================================================== Extracting/Copying .cab files to temp folder =========================================================== 12:30 1/4: windows10.0-kb4022715-x64.msu 2/4: windows10.0-kb4022730-x64.msu 3/4: windows10.0-kb4023834-x64.msu 4/4: windows10.0-kb4025632-x64.msu . . . =========================================================== Finished =========================================================== Press any key to exit. 12:58
When you really want dotnetfx3 pre-enabled why don't you just run the script with the extracted iso path as target, then all will be integrated in the correct order and the install wil be much faster compared to using the setupcomplete.cmd stage to do it (looks unprofessional too). When you enable it after integrating the CU, there is a chance that there will be a (partially) re-download of the CU after install is finished, to update dotnetfx3. Maybe @abbodi1406 can code the option to set the path to the sxs folder manually when the target is the install.wim.
Setting the target to the iso source updates the install.wim etc.. I don't want to extract the iso every time to get a fresh wim each time I build a new one. I'd rather use the vanilla install.wim as a starting point and export from that wim and go from there. What looks unprofessional - using SetupComplete.cmd, or using it to enable .NET 3.5? SetupComplete.cmd is very useful in my case such as installing non-integratable fixes, assigning drive letters, system activation, etc.
I extract the iso once and use it for 100's of new uptodate builds, just put in the sxs folder and the base boot + install.wim every time you want to do a new project. The base wims i use are pre produced: Murphy78's Diskpart and image apply script 1.2.8 in boot.wim index 2 MS DaRT 10 in boot.wim index 2 MS DaRT 10 in winre.wim from the first index (W10UI will update it and copy it over to all other indexes) The 15063 en-US base install. wim's contain all 13 x86 and 13 x64 en-US indexes The 15063 nl-NL base install.wim's contain all 10 x86 and 10 x64 dutch indexes