One more additional question. Having the current updated 17763.168 AIO ISO x64 & x86 with W10UI and it apply to UUP2ISO multi_arch_iso.cmd to create option 1 or 2, Created CD Name is 17763.1 ISO. Do I need to modify inside script or it is normal and manually change to CD Name from 17763.1 to 17763.168? Or Do I must using UUPs with convert_uup.cmd to make ISO first and go to multi_arch? Pls.. Thank you.
When you've used UUP>ISO with the updates in the UUP folder, it creates the iso with 17763.168 in the filename.
Yes, I knew. My question is Only those ISO to apply to multi_arch to get same CD name or Updated W10UI ISO can not apply to multi_arch (I mean even updated build number)? Let say UUP ISO 17763.168 -> Cd 17763.168 W10UI 17763.168 -> 17763.1 (not 17763.168) why? Than you.
BUG Report : W7 UI v4.7 when integrated offline update , Package_RollupFix won't process with boot.wim and imagebasedsetup-media source wont copy to the installation source , for W7 UI v4.6 is all working fine on offline .
MSEdgeUpdater v3 Added support for offline updating either mounted directory (e.g. C:\Mount), or offline image drive (e.g. F:\) the support is basic: - you have to manually mount install.wim - make sure MS Edge is already integrated/installed - edit MSEU.cmd and set the correct mount directory path, or offline image driver letter - example: set "target=C:\Mount" - Run MSEU.cmd as administrator - manually unmount install.wim and commit changes
Just a thought, what about using LTSC's NTUSER.DAT Searching for onedrive in LTSC's NTUSER.DAT returns nothing. I am just a bit worry about messing with that file because of its à/ÿ/¨ characters. Thanks!
It will not make a difference, you won't get OneDrive, but you still get unworking shortcut in Start Menu the actual file and path is plain english, it's only localized virtually in Explorer you can delete the shorcut in specialize phase in unattend.xml Code: del /f /q "%systemdrive%\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\OneDrive.lnk"
Hello, Update used for 1809. KB4465065 (Intel Microcode Update. KB4470502 (DotnetCU) KB4470788 (SSU) KB4471331 (FlashPlayerUpdate) KB4471332 (WindowsCU) (I removed uneeded lines) Installing updates... Processing 1 of 3 - Adding package Package_for_KB4465065~31bf3856ad364e35~amd64~~10.0.1.2 Processing 2 of 3 - Adding package Package_for_KB4470502~31bf3856ad364e35~amd64~~10.0.1.2273 Processing 3 of 3 - Adding package Package_for_KB4471331~31bf3856ad364e35~amd64~~10.0.1.0 The operation completed successfully. Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.194.1.5 The operation completed successfully. Resetting OS image base The operation completed successfully. The operation completed successfully. Adding .NET Framework 3.5 feature Enabling feature(s) Reinstalling .NET cumulative update... Processing 1 of 1 - Adding package Package_for_KB4470502~31bf3856ad364e35~amd64~~10.0.1.2273 The operation completed successfully. Is W10UI working right? So no need to re-install Windows CU KB4471332 after resetting the image base? Thanks.
I am going to test this, because on my previous test i also needed to manually reinstall the standard CU after W10UI_5.6 was finished, so WU didn't offer the standard CU when the iso was installed.
I have verified that reintegrating normal CU does not affect or add anything to .NET 3.5 in ver 1809 but it may need to be reintegrated to be the last in servicing chain, to satisfy WU
Well, Thanks for testing, do you even have to reboot at the end as well? Hopefully no Maybe UUP side effect?
It was only a test to confirm, the standard CU needed a re-integration after this integration: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-357#post-1489692