MSMG ToolKit

You need to login to view this posts content.

 

Huh? Versions newer than 7.7 do not support RS2? Why not? I used 7.9 to remove stuff and it worked, so...

 

He is referring to LTSB 1607. That's what I use for now.
Hope that MSMG will continue to work on his toolkit.

Cheers.

 

Yeah, I am running LTSB 2016 1607-14393.1914 right now and I used abbodi's script to update the images, but used Toolkit 7.9 to remove many packages, aside from some of those that change version number if rebasing took place (2x Hyper-V related packages I believe).

 

You need to login to view this posts content.

 

Good for you. However several people reported that v1607 doesn't work after ToolKit v7.9.

 

Several people have reported problems with LTSB since version 7.8 and in this version a new method was introduced to remove the packages (manual removal) using the ToolKit Helper. I do not know if this new method is also used for LTSB but several people have reported that the older versions of the Toolkit work perfectly with LTSB.

 

7.7 for Windows LTSB

The only issue is this (see link) and only if you add the games (very easy fix)
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-242#post-1390376

 

I've found a little bug in Versions 7.7 and 7.9 removing Media Player managing 1703 or 1709 images (not with 1607):
MSMG ToolKit removes properly "Microsoft-Windows-MediaPlayer-Package", "Microsoft-Windows-WindowsMediaPlayer-Troubleshooters-Package" and "Microsoft-Windows-WMPNetworkSharingService-Package"
but not related language-packages, which are still present. A simple workaround is adding "Microsoft-Windows-MediaPlayer-Package", "Microsoft-Windows-WindowsMediaPlayer-Troubleshooters-Package" and "Microsoft-Windows-WMPNetworkSharingService-Package" in RemovePkgsList.txt, so language-packages will be removed.

 

Why don't we just all chill out, sit back have a beer, and a joint, and wait for the next version!

 

make clear, who better for rs2 7.7 or 7.9 ? then 7.9 is safe for rs2?

 

See post #5013!

 

You're right, mate

 

Sort of a tangential issue but its one I can't stand in Windows 10.

Way back in the XP days I would integrate the new SP into my image, burn it to a CD, boot to it and then upgrade my OS. I found this was the best way to ensure that everything would go off without a hitch.

Today with USB3 flash drives it would be awesome if we could do the same upgrading from RS2 to RS3 but as anyone that has tried to do an upgrade/repair install with windows 10, it stops you and tells you to do the upgrade from within windows.

Is there a flag that can be set that allows upgrades from bootable media and if so can we get that option added to this toolkit?

 

Windows 10 upgrades can't be run from boot, just start setup.exe from the running windows you want to upgrade.

 

You need to login to view this posts content.

 

In thesis 7.9 is safe for RS1/RS2/RS3 since it supports these versions the issue is that 7.8 onwards is more bugged than the older versions so I would use 7.7 for RS2 also but if you have time take a test with 7.9 and see if you encounter any problems.

I think 7.8/7.9 should be beta versions until you make sure they are stable enough.

 

thank you for your clarification and assistance i appreciate that

btw @MSMG can i req , upload toolkit to github? make us can tracking what the progress

 

Just to follow-up on what AeonX said... For rs2, try running 7.9 using the "ToolKit.cmd"
You only need the "Start.cmd" for rs3. I used the 7.9 version of ToolKit.cmd on LTSB 2016 (rs1) and it worked great!

Save your breath. GitHub is an on-going plea. If you search in this thread, MSMG offers some rational for not putting the ToolKit onto GitHub.
try: site:forums.mydigitallife.net github MSMG
[edit]
changed 'this' to 'GitHub' for clarity

 

Hello. How to turn a PRO version into a Workstation.

thank you