@MSMG found a bug in the latest 13.7.7 toolkit. When use it against 11 22H2 22621.2283 then install, windows updates are broken, while trying to install any update I get error. But when using toolkit 13.6.7 no windows update errors.
Please, fix error dism /online /cleanup-image /scanhealth (after removing Edge and some other components from the image)
Don't think it can be fixed it's an old error that affects every win 11 ver. Either don't ever use dism reset base or dism++ etc to clean sxs folders Or after patching win 11 with toolkit and installing it install next kb update that will fix scanhealth error then uninstall update
I have never understood MSMG Toolkit's varying behaviors with the DISM command. For example, I just recently used MSMG v.13.6 on Windows 11, version 23H2, Image Version, 10.0.22631. Of the DISM RemovePkgstList.txt items selected for removal, MGMG nuked everything except System Retore and Edge. Fortunately, Edge can be removed after setup from Windows' programs list, although the program subdirectory "C:\Program Files\Microsoft\EdgeUpdater" remains as well as the C:\Program Files (x86)\Microsoft subfolders for Edge. The crazy thing is I have used this exact same RemovePkgstList.txt on Windows Windows 10 build 19041 and Windows 11 22H2 and gotten different results: Edge was removed in 22H2 with WebView2 remaining intact but not in Windows 10 build 19041, which I could only remove using MSMG menu custom removal choices. Otherwise, for those who are curious, MSMG removes quite a bit from Windows 11, version 23H2, including Media Player , Photo Viewer, Face Recognition and a bunch of other half-baked applications. One other issue, though. 23H2 does a terrible job of handling the SetupComplete.cmd in $OEM$. Half the applications would not auto-install, including most critically the program AutoIt, which I use to script unattended installs of most of my apps. I think it was a permissions issue since the scripts would display in Notepad rather than execute the scripted commends.
i said 13.7.7 breaks wu on win 11 22h2 22621.2283, 13.7.7 was upgraded to support 11 23h2 and most likely doesnt break wu on 23h2
@dabour & @Jingzin. I don't use Windows Update. I toggle it on and off with Windows Update Blocker v1.8 and can confirm that it does work when making an ISO of 23H2 with MSMG v13.6.
I'm not fixing with resetbase. I use a 3rd party program and reimage the OS if a bad driver or app screws up my OS. As they say, if it ain't broke, don't fix it. MS updates often have bugs so I wait a month or two when it is all sorted out and do a clean install. I've gotten those down to about two hours now. Well worth the time I would otherwise spend doing MS's job of trouble shooting why an update screwed up my system or deprecated a function I really liked. But I may be about to follow @Jingzin back to 22H2. 23H2 is slow as molasses.
When you patch win 11 with toolkit then install windows and run dism resetbase, you will get error, are you normally fixing that error in somway or aren't ever running resetbase or leaving that error without fixing it?
I'm glad to hear that the project has received an update and that the community is active. I wish you all success.
what you need update for ? toolkit works against 22 and 23h2. also you dont even need toolkit to strip down 22 and 23h2 and even 24h2 all you need is uup dump config to mark what you need in your iso then after install used dark dinosaur script to disable telemetry make few more task scheduler tweaks few regedit tweaks and youre done. 24h2 pro sucks really badly comparing to 22h2
MSMG had a problem on his farm and the project was not updated for a long time. I don't use Windows 11, only Windows 10 22H2.
Can someone tell me what my mistake is with this unattend file? I tried many things, but I can’t get the windows of: language, license, and Internet skip in auto... UPD: if anyone will search I solved the problem. the file in the root of the flash drive must be AUTOunattend, for work fully in auto mode. I take the unattend file from Rufus created, but it was in the windows folder, so I didn't know that a different name was needed for the root directory.