From 16215 PE. Again, I don't know why it isn't running on your end. This is an actual usage, I mean, the idea of SFC not being able to scan an offline OS (not compare to but scan and fix offline) would make it a "fair weather" tool. If a protected system file (real system file, not some of the nonsense that MS has been labeling protected) were to become corrupted there a decent chance the OS won't boot or will kernel panic/BSOD on boot. Obviously making an online SFC scan impossible.
Unfortunately I'm new to this windows customization stuff so i didn't quite get that. Do I extract those components from intall.wim and just put them in to \ToolKit-v7.4\Packs\Apps\w10 ? I'm 3d designer and I do this out of necessity. Win10 bloatware and over useless crap like game mode etc really screwing up my workflow at home (creators update my ass!). However new calculator converter and mail app I find really useful. So useful in fact, they are my only reasons why I’m still using win pro instead ltsb. Pairing those apps with ltsb is my dream come true so I can ditch this win pro nightmare for good.
What is error 14003 "Assembly not present on your PC"? It happens when I try to remove some MSMG or custom components after Windows was already updated. DISM detects those components as existing, yet throws that error at me. For custom packages I do not specify the versions - just base package name, which, I assume, means that version number is not the issue. I researched that error and it is supposedly due to corrupt Component Store, but DISM ScanHealth, DISM Clean Up with ResetBase, and SFC ScanNow all pass with flying colors... I am still a bit lost on NET 3.5 integration. Would it's integration before applying cumulative update simply make the image size overly large due to ResetBase not capturing it properly? Why is it then possible to perform ResetBase with NET 3.5 once the imagine is online / once OS is installed? Maybe it's best to integrate DX9, Servicing Stack, then NET 3.5 and 4.7 and Flash, perform online ResetBase in Virtual Machine, capture the image, remount with MSMG Toolkit, apply the cumulative update, and perform Component removal, perform ResetBase? That way NET 3.5 gets updated properly and the Toolkit is be able to remove all supported components without version issues.
MSMGT version: 7.3 ISO base: 1511 april 2016 x64 After removing all apps, maps component, onedrive, cortana, telemetry, edge, defender, system restore I get a black screen in the second phase of windows installation. The only thing I can see is the cursor and thats if I move it around. What could it be?
Code: Name PackageFullName ---- --------------- E2A4F912-2574-4A75-9BB0-0D023378592B E2A4F912-2574-4A75-9BB0-0D023378592B_10.0.15063.0_neutral_neutral_cw5n1h2txyewy 1527c705-839a-4832-9118-54d4Bd6a0c89 1527c705-839a-4832-9118-54d4Bd6a0c89_10.0.15063.0_neutral_neutral_cw5n1h2txyewy Anyone knows what these 2 package does?
1) NET 3.5 (and only it) creates pending operations so ResetBase can not be run while it does not boot with the install.wim image. After booting the image (in a VM for example) the pending operations are executed and .NET 3.5 is installed properly in the image allowing the ResetBase after that. 2) The ideal order is: Integrate Servicing Stack and then .NET 3.5, boot into a VM in audit mode after sysprep/generalize and capture the image, remount with MSMG Toolkit integrate all the features you want (.NET 4.7, DX9, etc) and then integrate cumulative update. Because there will be no pending operations, the MSMG Toolkit will automatically perform the ResetBase when applying/saving. 3) No need to perform online ResetBase in Virtual Machine the MSMG Toolkit will do this again so leave to do only once in a last step. Note: .NET 4.7 by itself does not create pending operations but if it is installed soon after 3.5 then it will have pending operations as well.
Wait for the next version of ToolKit as I have added few fixes for Integrate Apps section related to Apps Dependency and Yes you can install any app you wish on W10 RS1 Enterprise LTSB 2016.
Don't know, you should better extract the package from the image and then check the internal files/the mum/manifest file to know what exactly the package is for.
I have just added the option to remove the components using a package list (RemovePkgs.txt) and it's in 4-4. Will explore the option to export the current package list.
Its the april 2016 refresh as I pointed out in the original post. [Edit] I should also mention that with an older version of the toolkit (v.6.0 I think) everything went really well. I believe that we need an archive of the toolkit's different versions due to the toolkit always heading forwards and looking to service the latest builds of windows leaving behind the older ones.
From long time Refreshed Images never worked properly with ToolKit due to the DISM and I have always advised to use the original release image i.e 10586.0 in your case. You mentioned you removed apps, so far the DISM was not allowing to remove the apps from the refreshed image, may be the newer version of DISM included with the ToolKit might have allowed it, right know I don't have a refreshed image to test it. I have not let down the option to service the older Builds, if you checkout the changelog of recent versions of ToolKit, I have added back the TH2 support too for integration and removal.