Hook is always the database creation from 3 different files, ISO hashes, SVF hashes and the upload log, then add a readable language abreviation and merge into one database . Needs 3 little helper scripts and some stoizism to not screw any step. Was wondering about hash mismatches with x86 Busiuness SVFs due to wrong file i used along the way . Now it should run as expected...
SVF.ISO Converter Update to v0.51.01 v0.51.01 --added LTSC 2019 (17763.1) to MVS (thanks to Enthousiast) --added 1809 (17763.379) to Techbench (thanks to mkuba50)
Hello everyone, I ask you for a courtesy. How can I extract a single version of Windows 10 (for example Windows 10 Home) starting from the complete ISO 1903 Consumer ISO? I look forward to your answers. Thank you. Alessio
Extract the consumer iso and run this cmd in an elevated cmd: Code: dism /Export-Image /SourceImageFile:"x:\install.wim" /SourceIndex:1 /DestinationImageFile:"y:\install.wim" /Compress:max /checkintegrity Now replace the original wim with the newly exported one.
can someone confirm the latest ltsc build? i have an update for my ltsc 1809 build to 1903 that keeps failing but i dont really see any mention of it here.
How do i see the KB number? Feature update to Windows 10, version 1903 amd64 2019-04 (2) Last failed install attempt on 4/23/2019 - 0x80240034 Not sure if this helps any with the kb number at all updateGuid {2faff704-ac88-4b3f-a3d2-11e6a63f0b67} Spoiler: image
Iirc, we've seen LTSB getting the upgrade to new build compatibility update before too. Any modifications done on that LTSC install?
No, I just used this tool to download and created a usb drive to install it a few months ago. is there a way to install this update or clear it out so it doesnt annoy me with its failed install stuff?