So, far I haven't got the Access denied errors while adding/removing components from an mounted image. The ToolKit is just a Batch Script which uses the DISM to do the required tasks and DISM uses some background process to perform it's operation and even though when the DISM operation is completed, it's background process still will be using the mount folder and it will take some time to release it. When the ToolKit is operating, did you accessed the mount folder to do any other operation? If so then these kind of things can happen with DOS batch files. Tryout once again with the ToolKit and use a fresh OS Image and see if it works. My advise is to stop using sfc scannow if you are chopping/modding windows components as it will definitely give more errors and more time will wasted correcting it.
I tested to integrate Nvidia driver (Display.Driver and HDAudio) with NTLite and size FileRepository in wim is 29 856 615 560 B.
Yeah, I did try to access it per someone's advice, but not the one created and controlled by MSMG Toolkit. I tried to access the registry, so I could modify it before the installation, but it didn't work and gave me Access Denied errors for any attempt to access the registry. It would be SO AWESOME if MSMG Toolkit provided an option to get into Install RegEdit and change some things around, like making all desirable AppX's as NON-InBox AppX's, allowing very fast uninstallation right after the initial clean install of the OS. I wanted to access the registry to of the image to leave only 3 AppX's as Inbox AppX's. Its weird, but MSMG Toolkit did not prevent packages like Biometrics from not being on the Inbox AppX list, but then again, I might've had Access Denied errors for that one... I will try again, but I also don't understand why I had to manually use WimLib to split the Pro version of Install.wim from the Home version, which significantly reduced the size... SFC ScanNow compares file integrity with the integrity of the image that was used to install the OS, so if file-size/version changes were made in the image, then there should be no errors... Some questions: - How to properly access Image registry through MSMG Toolkit for editing? - Is it still recommended to integrate Net Framework 3.5 AFTER all the updates, integration of drivers & DirectX, removal (aside from Manual Setup removal!), etc? - Is there any point in mounting Boot.wim? Should I integrate drivers or something into it?
I do not need all the inf files. I just write where the problem with a 30 GB folder FileRepository. Display.Driver (files and 57 inf). Integration one inf = one folder with Display.Driver files Integration 57 inf = 57 folders with Display.Driver files = 30 GB FileRepository
I just made this great image.wim by using Toolkit 7.3 through NSudo 4.3 and all desirable packages MSMG Toolkit allowed to remove were removed without any errors what-so-ever. I was even able to get into the registry to find that none of the removed packages had any traces in the registry. HOWEVER, even in this great image a bunch of packages remained in "Windows\SystemApps" folder: The above package do end up in the registry after the installation and they also appear in the AppRepository SQL database file. They exist in registry directories, like "HKEY_LOCAL_MACHINE\WimRegistry\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Config" If I remove all references for those specific and exact names, will the relevant SystemApps sub-folders disappear or do I have to remove them manually??? Someone told me that all SystemApps can only be removed using DISM commands. Which packages contain those SystemApps? I can't find any with identical titles or names...
1) You can access the registry when the Toolkit is idle by mounting the appropriate registry hives from Toolkit folder using a Admin Command prompt Code: reg load HKLM\WIM_Software "Mount\Install\Windows\System32\config\software" reg load HKLM\WIM_System "Mount\Install\Windows\System32\config\system" reg load HKLM\WIM_Current_User "Mount\Install\Users\Default\ntuser.dat" reg load HKLM\WIM_User_Default "Mount\Install\Windows\System32\config\default" Now use the Regedit to Modify the Registry, the mounted hives will be in [HKEY_LOCAL_MACHINE] After the Registry Editing you can unload the registry hives using these commands Code: reg unload HKLM\WIM_Software reg unload HKLM\WIM_System reg unload HKLM\WIM_Current_User reg unload HKLM\WIM_User_Default I will add an option to the Toolkit's Options menu to load and unload Image registry in the next version. 2) To split or remove an index from image you can use the WIM Manager from the Tools and the wimlibimagex uses a different algorithm and that's why the image size different from using the imagex/dism. 3) Yes .NetFX35 should be integrated as a last step and also if your are Removing Manual Setup the it should be done after the NetFX35 only if the NETFX35 files are not present in the Packs\NetFX35 folder. 4) Integrating Drivers to Boot.wim is optional and it's only need for people who need USB3 support under winpe or any other device to be working while using the setup.
Search the packages list generated by install_wim_tweak.exe tool to get the package names Here's some of the packages names Code: Microsoft-Windows-Security-AADBrokerPlugin-Package Microsoft-OneCore-AccountsControl-Api-Package Microsoft-Windows-AppReadiness-Package Microsoft-Windows-Client-AssignedAccess-Package Microsoft-OneCore-CloudExperienceHost-Package
Paste this line in the RemovePkgsList.txt file present in the Packs folder and use the Remove Components using Package List from Remove Menu (4->4) Microsoft-Windows-PhotoBasicPackage
Usually drivers folders comes with support for multiple OS having separate .infs for each OS. Try the method I did suggested and find out what's the actual files/folder required for the system you are installing the driver.
Ok, I'll do that and after that I'll say if it went ok. Can I remove User Account Control among other components? Also, I tried upgrading from an untouched Windows 10 Pro x64 install to a Windows 10 Enterprise x64 modified by this tool one and during the update the PC shutdowned and not only didn't it upgrade from Pro to Enterprise but also it didn't remove the apps which aren't present in the modified version. If I upgrade from an untouched Windows 10 Enterprise x64 install to a modified Windows 10 Enterprixe x64 by this tool one will I have this problem?