Then there is no real gain, if mounting 2 indexes of the same image parallel would already have a gain.
Like a professional athlete, I developed a few weird superstitions and eventually settled into a safe habit. I was concerned that there would be crc errors or esd compression errors. I would avoid running torrents while integrating and I couldn't figure out why I was running into problems with large AIO releases using esd format. I'm glad that MS is updating their builds every few months now because they know a lot of the microscopic details a lot better and generally have a much more flawless quality control than I ever could. I guess I could make updated LTSB/C versions, but TBH I got into the process because the older OS versions required hundreds of updates and would take a really long time to manually update from a fresh install. My updated versions were always meant to be like an updated MS release rather than a customized OS. I never really cared about the custom aspect or the piracy. I just wanted an updated clean install.
@murphy78 You were doing something right because your iso's always seemed to be very well regarded, i never used them but others did. Tweaking is always a personal thing so any tweaks are better accomplished with reg or bat files users can add if they want to. LTSC one saving grace is it doesnt need as many updates as 7 and 8.1 as long as the chosen updates give a stable install so i go with a known set of updates then only update when i feel like it. I test them out first and once i get a stable system i just create a new updates folder, date and build number.
I think you are referring to Toolkit's startup process, where it says Performing Toolkit pre-cleanup operation, please wait... Well all it does here is checking if there is any image mounted at these locations and then do un-mount them <Mount\Boot\1> <Mount\Boot\2> <Mount> <Mount\WinRE> Then it deletes and re-creates the Logs, Mount and Temp folders.
Some keys are left for compatibility issues, if you want to remove any protected keys then do use the NSudo prompt, it works best with the TrustedInstaller protected keys.
Since the Toolkit uses the DOS batch script, the batch script will only execute the next command after executing the current one, May be in other programming languages it is possible.
The missing file "pwsso.dll" is the result of eliminating "WindowsToGo", both manually, with RemovePkgsList and with the command "ToolKitHelper: AllComponents", in the 3 ways "sfc.exe / scannow" throws me the error using ToolKit v9.5 and ESD 18363.418. I do not complicate my life so I backed up the missing file and pasted it into the System32 folder when performing a new installation.
Does removing Windows Search from 1803 break completely searching? As in I won't be able to search files in folders? Code: =============================================================================== MSMG ToolKit - Remove Advanced Windows Components Menu =============================================================================== [A] Adobe Flash For Windows [B] Microsoft Edge Browser App [C] Microsoft Hyper-V [D] Microsoft Internet Explorer UI [E] Windows Cortana & StartMenu Search App [F] Windows Manual Setup Feature [G] Windows Media Player [H] Windows Photo Viewer [I] Windows Search [J] Windows Store Client [K] Windows System Restore ------------Remove At Last------------------- [L] Microsoft Telemetry [M] Windows Defender [N] Windows People Experience Host [O] Windows SmartScreen [X] Go Back =============================================================================== Enter Your Choice :
I use StartIsBack++ anyways It appears Windows Seach = Indexing service "Normal" searching files works always Cortana is the one that makes original start menu search work