So I was looking through the script and I noticed that for the "Xbox" component removal, you're making registry changes but not mounting the registry and unmounting it afterwards. Is this a bug? I presume so, since I notice other things appear to mount and then unmount the registry.
If I may politely say, just release it and let people do the testing for you Or otherwise let people build the code together alongside you.
well troubles to integrade Language Pack into build 15063.hmmm anyone can help out? thanks EDIT: got it working all fine i just put the lip file into the LangPacks folder not in w8.1 or w10 etc
Sadly it doesnt works. The tool gave me the feedback the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana had to be installed correctly. Plus there is a registry error. I'm asking me why sfc generated this mini collapse *g*.
I wonder one thing. Since the Toolkit comes with independent DISM and libraries, why can't we service Win 10 images under Windows 7? Is it that the built-in DISM in Windows 7 is intervening or complicating the process? Eventually, we are working on an offline image.
Hi! Using v6.9 and 15063. Removed all metro apps expect Store and Xbox, but Xbox app is not working (nothing happens when i try to launch it) Thanks.
you still have not solved the problem of integrating cumulative updates for Windows 10 enterprise LTSB x64bit v1607?
I have successfully integrated latest CU and SS into LTSB 1607 iso file using MSMG Toolkit 6.9 and before. No errors. The only drawback is the size of the Wim file growing up from 3,2 to 4,6 GB. Final size is around 5GB.
Another offer to beta test ... There are many signs that the newly released Windows 10 Build 15063 will become--after a Day 1 patch-- the final Creators Update. I'm sure many of us would love to help you knock out any "ToolKit GUI version" glitches using the latest Windows 10 build. In any event, thanks again for all your effort, the ToolKit in any form is magiical!
Actually it's called a Zero Day Patch, an update that fixes some last buggies on releaseday of a new windows edition.
As far as I understand, the 'zero day' patch fixes a few more bugs, but also 'flips a few bits' to change what winver shows for the version of Windows you're running. Meaning you don't have to download and 'upgrade to' the next windows version. Build 15063 already is the next windows version and will show that in winver (About Windows) after the 'zero day' patch.
It will install during OOBE (OOBE ZDP). When you install windows after the patch is released, of-course
How to do ? After integrating updates then remove stuff I don't need, The only choice is Apply, then Target to make iso file. When applying, messages show "rebuilding with maximum compression" for Boot.wim and Winre.wim. Can you elaborate the way to go for "rebuild Install.wim" ? Thanks Edit : My bad , Never know before I had to go twice into the "Apply" section: First one to apply and cleanup / resetbase, then a second one just to rebuild the "install.wim". I was confused because in the 1st pass Boot.wim and Winre.wim were "rebuild and compressed with maximum", but not install.wim. This was different in some older versions. 6.2 or 6.3.. And the doc is one year old. I just made a new ISO and ended up with 3,540 GB only