New
#570
I was curious - 7-zip x64 or x86?
Correct. But since the UUP>ISO scripts can be run post-install as well as prior to installing, knowing which files to copy in order to recreate index:3 would allow the script to make a fully-functional .ISO, including the Recovery environment need to fix that build as installed on our machines.
I'm going to take a close look into it later on - I suspect that some of the files may, in fact, be on that hidden partition, which is going to make it a lot harder to copy, but if those files are, instead, located elsewhere, and we can gain access to them, then this script could be taken to a whole new level.
Me too. On my previous VM, 20 GB VHD made it complain all day long with nothing installed other than the OS and the apps it installed. Even after removing everything I would never use and all the cruft (games, etc.) that the OS installed, it complained that it wanted another 825 MB of space.
Doesn't matter.
I use Xplorer2 as my default file manager in Windows, for a plethora of reasons. In order to test the theory of the .ZIPping of hte {HEX} dir, I decided to copy it first to a new drive.
I ran into a boatload of "Path not found" errors when doing so. OK, no sweat.
I then opened the default Windows Explorer File Manager and attempted the same copy again. And I run into this:
This is copying into the root of another folder, so the path is significantly shorter than the original path of C:\Windows\SoftwareDistribution\Downloads\{HEX} (all of which is now D:\{HEX} lol).
Yeah, not happening. So, it won't matter what Archiver you use, it is going to have issues. Even a direct copy and paste has issues.
So it makes sense that DISM is having issues with it as well.
You can now upgrade directly from build 14393 to 15063 and get a full ESD file, for anyone that wants one.
For the purposes of UUPtoISO, it may be of interest to compare the resulting ISO (the main difference being boot.wim in the ISO) but UUPtoISO still works well for clean installing Windows 10 Fast Ring builds.