(09-08-2025, 10:50 AM)admin Wrote:

(09-07-2025, 01:21 PM)Almighty1 Wrote: This is what the GUID looks like currently:


Note this is what it looked like when the new SSD was restored from Hasleo originally:


What was done was the following as I wanted to expand Local Disk(C) to use the 2.7TB Free space but it will not work untill I move Windows RE tools and DELLSUPPORT to after the Free 2.7TB space except none of the partition software allowed it because DELLSUPPORT was bitlocker unlocked & encrypted so I had to decrypt the DELLSUPPORT partition and then moved the Windows RE tools after 2.7TB Free space and DELLSUPPORT partition after Windows RE tools before expanding the C: partition to use the 2.7TB Free space which is now immediately after the original C: partition so hopefully that does not effect the GUID.

Did you check the 'Keep partition layout' or 'Sector-by-sector restore' options when restoring? If these options were not selected, the C: drive should automatically expand when restoring to a larger disk. Even if the C drive does not automatically expand, you can still manually adjust the target partition size on the 'Review and change the disk layout' page.

For the actual restore, I did check the "Keep partition layout" before clicking on Proceed even though I tried it with and without it just to see the difference before doing the actual restore.  The Sector by sector was always unchecked.  I remember when I tried it without checking keep partition layout, the C: might have expanded but at that time, my goal was more to start using the 4TB SSD since the 1TB was out of space basically and it seemed like the C: was still 1TB and even when I tried to manual edit it, it treated 1TB as the largest size for that partition.  Yesterday, when I had another 5TB portable Western Digital My Passport 2.5" HDD to test either unpartitioned or with one NTFS partition using 100% of the space, the C: automatically used all the free space as you had mentioned.  If the 4TB SSD wasn't my main drive, I would have tried to see what happens if the 4TB was the target.  Maybe I will try the 4TB SSD again later with the 4TB SSD already partitioned like now and see what happens when I don't select Keep partition layout and see what happens in the next few days and report back.  Thanks for the excellent software!

(09-09-2025, 11:34 PM)Almighty1 Wrote: Gave v5.4.2.3 a try and kept the "Keep partition layout" unchecked and on the 4TB SSD with the current partitions, it does show C: as using up all the space and not 1TB so it's working correctly.

(10-15-2025, 11:20 PM)Dude Guyman Wrote: Observations about v5.4.2.5.

1. It now forces a 1+ GB download of PE files, from Windows 11 I think, even if you do not check the box for it to do so.
2. When running/booting it from a rescue disk, the Windows 10 logo appears during start up, then a few seconds later the windows 11 logo appears on top of it, and both are visible overlayed on top of each other.

It all seems to function fine though. Just seems a bit "spaghetti coded" now.

(10-16-2025, 12:52 AM)admin Wrote: We have not changed the code for creating WinPE, so this issue should be caused by changes in the operating system itself. To further analyze the issues, please click "" > "Save log file" to open the save log file dialog, save the log file and then send it to us via email at [email protected]. We will do our best to resolve this issue.

(10-16-2025, 02:18 AM)Dude Guyman Wrote: No edit function? Anyway, this was my own doing. I had previously ran the command "reagentc /disable" (disables the recovery environment) and it turns out that also deletes the WIN-RE files that Hasleo was using, so that caused the download of the alternate WIN11-PE files. I ran "reagentc /enable", rebooted, then made a new "recovery/boot" ISO and got the usual expected behavior and no more overlayed WIN10-RE and WIN11-PE logos. Still odd that it would overlay them like that, but it's fixed now.

The good news is that it did actually work and get the files it needed to make a functioning recovery ISO, even though I had tinkered with the WIN-RE files in the operating system. My bad!