This MSMG system is, by far, one fo the best application systems I've ever used, WHEN I can get the stars aligned properly to make it work. There's a prophesy which tells of a Highland foundling, born on the Winter Solstice, who passes through darkness into light and survives to challenge the voice of death and can make the MSMG application work for every ISO and MSMG version and every time! But really, the application is clearly put together by a genius, however the versioning and version numbers have become literal insanity. I read that I should use MSMG release 9.4 if the ISO is v1809. Ok, but there is no release 9.4 in the current archive and there becomes the confusion. Is it 9.4.1.7, 9.4.2.7 or 9.4.7? Well, its become more than confusing, because I'm not really what I would consider to be well versed in its use. So I don't know if MSMG is puking up hairballs every single time, now, forever because I'm using the wrong version or if something is screwed up because I've been copying the files in and out to try to find which version is the correct one or if something is procedurally wrong because I've taken too much time off and am so far behind, techwise, that I may as well be a target on the surface of a black hole with President Trump. Ok, so I'm doing a fresh setup with ISO Win10_1809_English_x64 and have the thought that it is 17763.1... Are all of my problems simply because I'm trying to do something with LTSC>? I'll let you know how I make out this time... But if I may make a very humble suggestion, the humblest since I am possibly the most inexperienced person to ever, have ever and may ever use MSMG: IS there some sort of nomenclature that could be adopted for naming so that its logical, consistent and easy to determine which "pre" goes with which "post", "part", "fragment", etc. I want to be clear that this is not an attempt at complaining. I apologize in advance if this is taken as a complaint. The software has worked well in the past, VERY WELL and the cost, well, the cost just can not be beaten, so there's that. Hoping that this email/comment finds everyone well, financially secure, on the outside of any padded rooms and generally happy and healthy. Best regards.
Let me correct, the 9.4 was the major release and 9.4.x are minor ones which where released immediately right after 9.4. I have fixed the info now. For Windows 7 - Windows v19H1 Integration or Customization use v9.4.2 For Windows 7 - Windows 10 v1803 Component removal use v8.8 For Windows 10 v1809/v19H1 Component removal use v9.4.2 The archived ones are inside the archive folder under the download the link.
Hello, MSMG ! Wanted to ask : is there currently a test version of MSMG Toolkit for testing Windows 10 Pro 1909 Build 18363.418 ?
Remember the "Good ol' Days" when you could just take ANY build of Windows 10, and work with it on the toolkit? Alas and alack, those days are gone.
Yeah can understand using two versions for servicing W7-W10 RS4, I'm taking steps to make a single version for all OS's. For Windows 7/8.1 Component removal, I know it's not good to use the base image without the updates since you will lose years of important fixes released so far but one issue exist that is unlike Windows 10, Windows 7/81 doesn't have a single update instead it has dozens of updates which makes it difficult to keep track while removing components and if the user doesn't add some selected updates it makes things more difficult. I'm planning to simply the updates with a update pack which only keeps the latest features and updates to be applied for Windows 7/8.1 and serves as a base image for component removal. For Windows 10 TH1-RS4 it's not a issue, when time permits will do also add support for it but right now Windows 7/81 is in my component removal list next to v1809/v1909.
Yes there's one, which I'm testing out, tomorrow will be testing the installation and if everything goes fine then will release a new build tomorrow.
@MSMG I've downloaded the latest MSMG(9.4.2) and the windows image(1903 10.0.18362). When I try to remove components, I get this message: This is the debug info:
yep I know this is very hard really, thanks a lot for your dedication with all here EDIT: Hi MSBG knows my problem with older versions of Windows are relative only the removals of components and as to the large number of updates I have no problem since for this step I use another solution that I myself "invented" and always Worked well and is also worth the LTSB/LTSC versions ok.
It's not about how to integrate updates but it's rather what updates to be included as mandatory before the removal for Windows 7/8.1
Very simple for Windows 10 v1909 component removal you do integrate the .NET FX35 + available updates and then remove components. For Windows 7.0/8.1 the required features and updates need to be listed out for removing components, suppose a user doesn't integrate some features or updates then the component removal coded for exact base image may fail.
A lot of work I don't know if it's worth it but if done would be awesome. Another problem with Windows 7 is that it does not have ResetBase support so it would need a way to clean up WinSxS. For a system that will lose support in a few days I think it is not worth investing a lot of time in it.