They say it's Microsoft's fault or don't answer. I tried adding the updates in the post-setup and restart the PC after the first login (like they said) so that they can be installed and they aren't.
Hello what is a supported way to do some registry modifications against the image? For example I'd like to adjust the FsDepends driver parameter for the VHDX boot And I'm interesting in enabling Hyper-V in the very image Did anybody try to intermix the MSMG Toolkit with WindowsImageTools Powershell module? It's possible (in theory) to recreate the toolkit itself with this module, but I didn't see any point of doubling such hard work. So I am interesting in some combined process involving the best of both tools
That is some component you removed with NTLite that is breaking the installation of updates (mainly CU). It has no relation to restarting the PC or not. It is only known that removal of a component has a "bug" or a bad effect when someone removes, has problems and reports. For example, in Win8.1 removing WMP11 with NTLite breaks the installation of the monthly rollup update (a type of cumulative update) and even after several NTLite updates I have not seen in the changelog the fix of that. NTLite allows you to remove things very deeply into the system so avoid removing what you do not know what it is and do not know the consequence. Many things that seemingly are not necessary you find out later that you need them when some program depends on them. Example: Hyper-V depends on Remote Desktop components for some features.
If I only integrate the updates I don't have any problem but if I do that and remove and configure other things I already have. I added the updates to NTLite's post-setup and they weren't installed since the build number remains the same. Also, it creates a $OEM$ when I already have one (from abbodi1406's KMS_VL_ALL's pre-activator folder) so should I copy its content for the new $OEM$ folder?
Do not add to the post-setup and try to install the same updates in a clean install of the image you created. If you get errors it's because some of the components you've removed are causing this.
Mine are msu files. That's what I said (if I integrate them and not remove anything afterwards I don't any trouble installing the latest CU through Windows Update) but I really need those components to be removed.
Delete the $OEM$ folder created by NTLite, this is enough to not install the updates after the setup. Then copy the $OEM$ folder from abbodi1406's KMS_VL_ALL. If you want to use the 2 at the same time you will have to merge the contents of the folders and of the setupcomplete.cmd Oh well then you will have to test one by one until you find which component is causing it. There is nothing to do, report the bug in the NTLite forum and wait for a fix.
That's what I want (to use the 2 at the same time), so I can't delete the $OEM$ folder created by NTLite.
I said this just for testing purposes. You will not be able to find where the problem is if you want to do everything at the same time. You have to isolate the processes and do them separately. Remove only with MSMG Toolkit and see the result. If all goes well then the problem is in NTLite. Adding the updates to the post-setup will not help in this case.
Like I told you, I know that's NTLite that causes this. I just don't know which component removal causes it. And I've been trying to know what causes it by removing component by component but I can't find the cause so I just gave up.
What are the DISM commands to integrate them? Maybe that's what NTLite or MSMG ToolKit do and afterwards I can't install the latest CU through Windows Update after removing some components with NTLite so I stay the same.
I use WinRAR, but WinZip should surely work. The command is Code: Dism /Image:<path to mount folder> /Add-Package /PackagePath:<path to cab file> If you want to do it online substitute /Online for Image:<path to mount folder> You can find lots of informative stuff about dism by searching. Much is published by MS.
Open Winrar, go to File, Open Archive, Select All Files on the bottom right, and browse for your file, and select open. Or simply paste the path in the File Name box, and click on Open.
Thanks, I didn't know I could open files with WinRAR this way. Can I do this for other files which I don't have a context menu option to open or extract them? There are 4 files: 2 cab, 1 xml and 1 txt. Which of the 2 cab files of the 2 msu files I have to extract (probably the one which isn't WSUSSCAN)?
You are correct. The one that is not WSUSSCAN. All the others are irrelevant. You can open other archives this way, and some executables (the self-extracting ones) such as Nvidia Driver executables. If you can't open it, it will let you know.