Im not asked i know but sometimes i had simular Isues and it helps Run Start.cmd or Toolkit.cmd as Admin . . . sometimes the one and somtimes the other is right w0rkin ! ? !
Hello trim18 well when I install Windows from version 8.1 to the latest build that I also use in the case of W10 LTSC the first thing I do is open Regedit and disable UAC and then use the command net user xxx / active: yes and I rename the Administrator account for my own name on gpedit.msc as recommended by the M$FT itself so that I have absolute control of the machine since I am the only user and I have never had any problems and still due to habit when I work with the Toolkit I right clic button of the mouse to avoid any problem and about my post our Master MSMG will readily explain I'm sure of this ...
Am I misunderstanding, or is it normal that I'm unable to update my installation and am getting error 0x80240016? I made Win10_1909_Pro_18363.449 when it was the latest, but I cannot update it, the process always fails. SSU and .NET updates work fine. I've tried everything to update/repair my image. I don't have the list of what I removed, I'm pretty sure I only removed what wouldn't come back with an update at the time. - So just apps. But I may have misunderstood and removed some components that I thought were declared safe to remove and would not have any effect blocking updates or being put back by them... (But maybe I was mistaken?) Sorry if that's vague. Any suggestions/requests for more detail? @MSMG I also want to bring up the option of "disable components" for those that it is easy to do so for. This way we can at least have a smooth functioning image out of box AND if mistakes are made in what is disabled - WE CAN TURN IT BACK ON! This would be a great option for some components that are easily disabled - even if you still work on complete removal of them. It's definitely not a waste of effort or redundant because it solves many potential issues and doesn't require redoing every CU. - A list of silly services to disable by default is a good feature too. For example:
Hmm in my opinion we should not "mess" with services when using the Toolkit because this part of Windows is crucial so I always leave it to enable / disable services only after installing the system I think it is a matter of logic see if everything it went well in the installation and we used the command sfc / scannow and there was no problem accused there yes i open services.msc to execute this process because this way if there is any problem it is simple to undo the changes avoiding therefore the re-installation of the system just my two cents ...
Hello Master MSMG I would like to know if you can compile a test version of Toolkit Helper to use with the 1809 build of W10 LTSC 2019 because as I already stated for version 1909 the test version of the Toolkit Helper works like a charm now my thank you very much
Adding switches to use MSMG Toolkit non-interactively would be so awesome, any chance of that happening? I would love to set up a monthly updates integration script.
The ToolkitHelper that ships in Toolkit_9.5.7z is dated 10/25/19 and ToolkitHelper that is available separately in the MEGA folder is dated 12/31/19. Which one should I use?
Except anti malware executable service! ^_^ It's annoying It's suck' And finally it's caused my HDD Usage Reach 100% Everytime i turn on pc Nice job MICRO$OFT Best Regards NST_Adventure
Hello friend please I would like to know where I find the option to convert install.wim to ESD inside the Toolkit or how you managed to do this thanks
From the main menu, option 2 (Convert) then option 4 (Convert WIM Image to ESD Image). This is the last step before creating the ISO image and not available while the source is selected.
are you sure.? can you remove apps.? as i remeber trying it on 446 then on the next CU and could not remove apps..it needed to be in the supported CU. am waiting for support on latest 592.
ok ill try to do it today..ill report back. never mind. too tired to do all again..i clean flash stock ISO. also need to flash my phone rom..
@Feartamixg well I honestly don't want to justify my serious failure when asking about the conversion from WIM to ISO and at the same time I confess that I didn't know it was possible to use the previous options WITHOUT corrupt the Script so as a consequence with a simple question asked by noob developer I learned great things about how to use the fantastic possibilities of Toolkit v9.5 I also had an ISO with only 2.6GB as a prize of course this way I thank you so much for your invaluable help mate
Dear MSMG, I am servicing Windows Server 2019 Evaluation DVD downloaded from Microsoft which have Multi Indexed (4) Install.wim file in sources folder. While servicing this with MSMG_ToolKit, I analysed ToolKit.cmd script & found some logical bugs, which may raised due to my lack of knowledge or understanding. 1) In Tools -> Load Registry Menu Processing, the first if satisfied & load Registry followed by 2nd if that also satisfied & immediately unload registry. 2) In Select Sources Menu, if we select to mount Recovery Image also then the WinRE.wim will be mounted only from the 1st indexed image of multi indexed Install.wim even if we choose to mount all images of install.wim. Is all indexed images inside Install.wim shares same WinRE.wim from 1st indexed image of Install.wim file? Thanks for your support.
yay well i just installed the "new" W10 LTSC x64 on another partition religiously following the tips I just received and one thing I found and liked was the ISO size only 2.6GB this time I also integrated my standard language (pt-BR) I am very happy because there was no error during the installation; as soon as the new Windows started I just accessed settings and changed to my simple default language like what lol I can still be mistaken but this new build didn't take even 5 minutes to complete the installation !! I have already made a comparison between the two systems and the new build is faster than the "old" build according to the task manager on the old one, the startup took 5.6 seconds while on the new one it only took 4.1 seconds ... taking in account that I leave configured to boot with Windows only what is necessary hmm happier it is impossible hehe so the next step is to format and forget the "old" LTSC in time is there any way to delete the C: \ Windows partition and remain only the partition E: \ local disk because if this is possible I should save a lot of time I read somewhere about it using the command bcdedit but the old man does not remember