After licence agrement crash (close) ... try on 2 computers ... original msmg work but ur custom wont for me
I know this works, but using the older nsudo is more practical (nsudo 6.2 bundled with TK 8.8 works as well)
Please, give me some data about: What OS version are you using. Extract the new Toolkit and Custom Toolkit into a new folder and test one more time. So I can get a better idea of what's going on. Note: I tested it with 19044.1947 with no problems. with 19045.1889 I had several problems with the functioning of several scripts. I still don't recommend it for daily use.
I have a script (RunAsTrustedInstaller) in my package, to install nSudo and/or PowerRun from the context menu. If it is installed from the toolkit folder, it will take nSudo from the toolkit folder and send it to the System32 folder. If it is run in any other folder, it will download nSudo previous version which is the latest stable version available for download, and install it from the context menu. There is option for PowerRun and uninstall option for both. (always uninstall before re-installing a new version of the same App. You can install nSudo and PowerRun. They do not interfere with each other and you will have both options in the context menu).
Right now I'm on 19045.2006 (AMD64) but I can test quickly on whatever you/I like May matter that I use both clink and conemu (higly suggested to everyone deals with command line), but I use them since the stoneage and never troubled be. P.S. tested on a different machine on Server 20348.1006 and the bundled nsudo works as expected. (clink and conemu are installed as well)
You don't need a special script (or nsudo) to copy something new in system32, explorer is enough. You need TI rights to delete, replace (and sometimes rename) system files that are already there That said I think I bisected the problem. The thing fails using the remote desktop, same machine, same toolkit folder, same nsudo version are working locally or connected remotely via VNC. It must be a nasty nsudo regression that no one else noticed. I'll try something different than 1904x anyway.
I tested on 22h2 windows 11 custom made by msmg and on 21h2 windows 10 stock build all without defender ... original msmg run normal but when i run ur custom msmg i have problem when i run it with generic laucher or from folder custom msmg i after licence agrement get close cmd with ur forked tool (immediatly after i acept licence agrement get close immediatly)
Are you extracting from the package, only the "Customtoolkit.cmd" file and the "GenericStart ..." to the Toolkit folder? Because Custom Toolkit depends on the contents within the package folders. Note: I will separate the content that is an extra. These are only independent utility scripts that use Toolkit's Bin folder for its operation. I believe it will be less confusing. I'll just leave an "ExtraUtilities.zip" inside the package.
I simulated what is happening to you and managed to reproduce the problem. Check the presence of these files "EnvironmentPath.zip" and "EnvironmentPath.cmd" within the bin folder. Reverse the order of these 2 lines (148 and 149) in "CustomToolkit.cmd". from: Code: if "%WorkingFolder%" neq "" if "%WorkingFolder:~-1%" neq "\" set "WorkingFolder=%WorkingFolder%\" if "%WorkingFolder%" equ "" set "WorkingFolder=%SystemDRIVE%\TK\" to: Code: if "%WorkingFolder%" equ "" set "WorkingFolder=%SystemDRIVE%\TK\" if "%WorkingFolder%" neq "" if "%WorkingFolder:~-1%" neq "\" set "WorkingFolder=%WorkingFolder%\"
The script doesn't just do that. This adds the registry entries linked to Powerrun or NSudo executables so that the options appear in the context menu when right-click in scripts. And, this have a for loop in this execution by the context menu so that the execution remains in the script "working dir". Which is not possible with the traditional method that changes the "working dir" to System32.
Guys, what option should I choose to integrate these updates to a 19041.1 uup image so I'll have 19044.1889: SSU-19041.1852-x64.cab Windows10.0-KB5003791-x64.cab Windows10.0-KB5007401-x64.cab Windows10.0-KB5008575-x64.cab Windows10.0-KB5011577-x64.cab Windows10.0-KB5014676-x64.cab Windows10.0-KB5016616-x64.cab I've already tried "Integrate Windows Setup Media Updates" but it didn't work, so I guess it's one of these but it isn't clear to me which one I should choose? =============================================================================== MSMG ToolKit - Integrate WHD General Updates Menu =============================================================================== [1] Integrate to Windows Setup Boot Image [2] Integrate to Windows Setup Install Image [3] Integrate to Windows Setup Install & Recovery Image [4] Integrate to Windows Setup Boot, Install & Recovery Image
So, played with it a bit more and actually looked at behavior. Pressing a choice button also changes the state of the choices before it. So if choices from 1 to 5, pressing 4 changes the state of 4 3 2 and 1. I don't think I can explain it any better.