@MSMG Sorry, I didn't fully understand..!! 9.2 works fine with .379 image though it is refreshed..?? Or just 9.1..??
Only from v9.3 the build is locked to vanilla images, below v9.3 it works for refreshed images but the reported errors or bugs will be present as the Toolkit won't remove the updated file/registry entries present in refreshed images.
lol should just put checks in place so that the toolkit only works with .1 builds this comes up so frequently
Thank you sir. So 17763.379 refuses to work with both 9.2 and 9.3 but the reason is different, for 9.2, its because of Toolkit not removing the updated file/registry entries and for 9.3, it is locked to vanilla images. So the only latest version which is compatible with x.379 is v.9.1. But how to get rid of sfc errors ? If i ignore it will it cause issues in future ? Thank you.
I don't understand you guys. Why trying to use an earlier version of the toolkit that has issues or is not complete just to be able to work with refreshed images? It will create issues anyway. Why can't people just follow the instructions and use the first Windows builds? Cheers.
@MSMG amazing job sir, used 10.0.17763.1 , removed all components, etc....and surprising so sfc errors! amazing fresh install, great work!
No matter what version of the Toolkit you use will generate sfc errors in refreshed images and there is nothing you can do to avoid this. You can no longer remove the components that generate the sfc errors but with a new update may appear new components that break the sfc check.
@MSMG Thanks for this super tool. With version 9.3.1 I was able to edit Windows 10 Pro 1809 (German) as follows: Spoiler 1 / 1 - Index: 5 3 / 2 / 2 3 / 3 / B 3 / 3 / C 4 / 1 / 1 / 8 - [Y]es 4 / 1 / 2 / 1 - [Y]es 4 / 1 / 3 / A, B, C, D, E, G, H, I, J, M, N, P, R, S, V, X, Z, 1, 5, 6, 7 5 / 1 5 / 4 5 / 5 / A, B, C, D, F, I, J, K 6 / 1 6 / 2 6 / 1 Offline installed and SFC scan done, all right. Updates KB4499728, KBkb4494441 and KB4495618 installed offline. Searched for updates online and performed SFC scan, all right again. Is it still possible to remove the following files / folders from OneDrive: Spoiler Code: C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..-onedrive.resources_31bf3856ad364e35_10.0.17763.1_en-us_1e90bb42843e8403.manifest C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-settingsync-onedrive_31bf3856ad364e35_10.0.17763.1_none_c013203a9976dd1c.manifest C:\Windows\WinSxS\Manifests\wow64_microsoft-windows-s..-onedrive.resources_31bf3856ad364e35_10.0.17763.1_en-us_28e56594b89f45fe.manifest C:\Windows\WinSxS\Manifests\wow64_microsoft-windows-settingsync-onedrive_31bf3856ad364e35_10.0.17763.1_none_ca67ca8ccdd79f17.manifest C:\Windows\WinSxS\amd64_microsoft-windows-s..-onedrive.resources_31bf3856ad364e35_10.0.17763.1_en-us_1e90bb42843e8403\OneDriveSettingSyncProvider.dll.mui C:\Windows\WinSxS\amd64_microsoft-windows-settingsync-onedrive_31bf3856ad364e35_10.0.17763.1_none_c013203a9976dd1c\OneDriveSettingSyncProvider.dll C:\Windows\WinSxS\wow64_microsoft-windows-s..-onedrive.resources_31bf3856ad364e35_10.0.17763.1_en-us_28e56594b89f45fe\OneDriveSettingSyncProvider.dll.mui C:\Windows\WinSxS\wow64_microsoft-windows-settingsync-onedrive_31bf3856ad364e35_10.0.17763.1_none_ca67ca8ccdd79f17\OneDriveSettingSyncProvider.dll
Yes it's in my to-do list and will be added when its's ready, that would reduce the size of wim image further.
I have the Language Pack ISO and OnDemand ISO for Windows 10 LTSB 1607. I would like to create language packs for MSMG to integrate into LTSB 1607. How do I rename the language pack files into the name format that MSMG expects? Is there a guide that shows how to create language packs for MSMG? Is there a tool that can rename the files based on their package name?