System.IO.PathTooLong Exception: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. README.txt Toolkit requirements: "The ToolkitHelper.exe requires Microsoft .NET Framework 4.8."
Either VC++ integration is broken or VC++ related component removal is broken (or both or combination) for Win11 22621.963 because applications that depend on VC++ (such as MSI Afterburner) produce "side-by-side" or "1075" dependency error upon launch if: #1. All MSMG-allowable components are removed offline #2. VC++ is integrated offline I am still hunting down the exact cause, but if you do #1 + #2 offline, programs dependent on some VC++ versions do not launch and produce either "side-by-side" or "1075" dependency errors. That is reproducible. At least 2 programs are affected: - MSI Afterburner - YogaDNS
This seems to be no problem Replaced winre.wim on Windows 7 at C:\recovery with a Drive Snapshot WINPE (boot.wim) image renamed to winre.wim. Boots just fine to restore a backup. Same for any other (custom) WINPE image...
What's the point in this anyway? Sry for the guestion... Why not just create a (updated) install.wim and apply it to another partition/new drive. Add it to the boot menu using EasyBCD (like i learned here ) Then u can boot all windows...no hassle and no WINPE and no winre if u remove it. Replace WINRE with a custom WINPE(fix disk) to have a nice setup. Or just rip it out to safe some space?! and create another partition and extract (custom)WINPE there to have a recovery/fix disk It's never been easier like this... Keep up the good work here. It's like a machine
The entire point of removing WinPE is to reduce ISO size and system size (post-install). Boot Index 1 (WinPE) is basically bare-bone OS for troubleshooting, repair, deployment - something that most average users don't need. Boot Index 2 (Windows Setup Environment) is responsible for setup boot, system installation process, run cmd within it (Shift + F10), etc. Boot Index 1 (WinPE) size is approx 1.5 GB, Boot Index 2 (Windows Setup Environment) - 1.7 GB. The question is why after removal of Boot Index 1 (1.5 GB) there is almost no significant change to the boot.wim size and ISO size itself. I'm guessing, boot.wim compression is so high to the point where it doesn't really matter if Boot Index 1 (WinPE) is removed or not.
Hi @MSMG , Could you add `.empty` files to all the folders that are currently empty? This will help us in tracking changes between toolkit versions using git, as git does not track empty directories. Foe example, If I want to hard reset everything to v13.0 from v12.9, git reset --hard will clear all the empty directories causing me to forget the path to add features like `Packs/MultimediaRestrictedCodecs/w10/10.0.19041/` Simple way you could do this if you had WSL installed is , just before zipping it , from the root of the toolkit run Code: find . -type d -empty -exec bash -c "touch {}/.empty" \;
It's not like this. It's like mirroring with symlinks if the files have the same hash the size doesn't change anything. I remember that in the old days the winre of each index was repackaged and the hash of each one was different, making the iso bigger. Currently work in winre.wim is done only on one file. When saving, this file is copied to all indexes, and everything has the same hash, reducing the size of install.wim. Same case in boot.wim. when excluding winpe, it will only reduce the space of what is expressively modified for winpe to work. That's why the decrease in size is so small.
Writing in Portuguese, then translating to English always generates some misunderstanding. I thought that in that sentence "It's like mirroring with symlinks" I had been clear that it was an analogy. If the analogy doesn't fit well, that's okay. What matters is that with the rest of the explanation it was possible to understand. Or was it bad to understand? Maybe it's better to write it another way: "It's similar to the result when using symlinks". In other words, you don't have a duplication of data that would result in double utilization of storage space.
all good young man, I like to watch you, I can learn a lot from you. translation is always stupid, i use it too.
hello sir, just asking. does anyone knows how to make windows 10 ltsc 2021 become 19045 instead 19044? thanks for reply
Read their post again. If you put the folder on the desktop, the path will look something like: C:\Users\Voko\Desktop\MSMG The path needs to be as short as possible, so moving the MSMG into the root of your C: drive would shorted the path to C:\MSMG Simply move the MSMG folder into Local Disk (C:) on the left hand panel of Windows File Explorer and this will give you the above path which is shorter. Take the time to study Readme.txt which comes with the ToolKit, as this recommendation is also mentioned there: