Hello! New user here with a perplexing question. My PC has a speedy Samsung 9100 4TB nvme SSD C: drive and I cloned it to nice new Micron Crucial X10 external USB SSD drive. I did a disk to disk clone and pretty much kept all the defaults when stepping through the process. The drive has just under 1 TB of data on it and the first time I cloned the drive it took about 20 mins which was basically what I was expecting based on how much data was on the drive and the fact it was going from SSD to SSD.
But the second time and now the third time I cloned the drive, which is running right now, it is taking just over 5 hours, which I definitely was NOT expecting! And it is actually slightly less data being cloned now because the first time there was a Windows.old folder on the c: drive but I removed it after the first clone and nothing big has been installed since then. There were never any errors encountered and the resulting cloned drive after examination looked perfectly normal every time.
So the question remains why the heck is it taking so long now compared to that first clone? Before I start the clone process I make sure to shut off all the components of my anti-virius software so that it doesn't interfere and that's about it, I just let it do its thing. As I said I basically leave the defaults so I don't select sector by sector or any other options that would slow down the process. And check me if I'm wrong but shouldn't it be closer to 20 mins for a clone this size and SSD to SSD as opposed to 5 hours?
Any insight on what might be causing the slowdown or options I might be missing, etc. would be appreciated. It's not the end of the world because I do end up with a valid clone but it sure would be nice to figure out what is happening here.
Thought I'd document my experiences and journey with Hasleo products to upgrade the SSD on my Asus Zenbook A16 Snapdragon X2 device running Windows 11 ARM Pro 26H1.
When trying to create an Emergency Disk using Hasleo Backup Suite for Windows ARM (v5.8.2.0) using the "Enable support for 'WINDOWS UEFI CA 2023'" option I kept getting an error at the 5% mark that said "Failed to run system API. (0x02F4001500000003)".
Using the "Download WinPE components" option successfully created the ISO but I couldn't get the system to boot off it, it boot looped after trying to load. Tried turning off Secure Boot and a bunch of other things, nothing worked. Think the WinPE build needs updates to work with Windows ARM 26H1.
-----------------------------
Next, I bought Hasleo Windows To Go (because I have Windows 11 Pro, I think with Home it's free): https://www.easyuefi.com/wintousb/ And I was able to clone and boot a clone of the entire Windows 11 ARM 26H1 OS on my Asus Zenbook A16 off an external USB drive.
To get it to boot off the external USB SSD I had to:
1.) Turn off Secure Boot in the BIOS
2.) Get USB driver in Windows on the USB drive to init on boot, otherwise I got a 0x7b blue screen (attached screenshots with details of fix)
This is much nicer than a WinPE environment since it's a literal clone of the entire OS. I'm booting off the 2TB version of this external SSD I bought a year or so ago: https://www.amazon.com/dp/B0D47DZB1G connected to the USB3 USB-A port.
Sometimes the BIOS boot drive selector (hold down esc during boot process) wouldn't see the USB drive as an available option to boot from. I had to do a complete shut down/power off and start from a clean boot to get it to see it, or go into the bios, toggle something like fast boot, and force a complete restart.
Used the new USB drive to restore to a new SSD using the free version of Hasleo Backup Suite. First time I restored it froze/bluescreened at the 95% restore mark with a USB driver error. I ran the restore again and it succeeded on my second attempt. Just upgraded the SSD in the A16, just in time, was starting to delete things.
Also bought/used this thermal pad on the new SSD, seems to be running cool: https://www.amazon.com/dp/B09V53W559. Since the Zenbook is a thin light I thought safest to go with thinnest 0.5mm available on the single sided SSD.
Note: I also have Bitlocker disabled since first setting up this system, in case that has an effect.
I want to congratulate @AdvancedSetup for becoming the first VIP member of the Hasleo Forums.
For those of you who do not know @AdvancedSetup, he is the Root Admin at the Malwarebytes Forum, with a post count there currently of 128,800+ plus posts. I know that he is also an esteemed member of the Wilders Security Forum, ElevenForum, the BleepingComputer Forum, and probably others that I do not frequent.
He is very highly respected far and wide in cyberspace for his malware expertise, but also for his general computer expertise that few can rival. I know that personally since first encountering him online 12 years ago.
The "Welcome to the Hasleo Forum" Topic post will be updated within days to reflect this new Hasleo Forum rank, and the stringent requirements to attain it. For the record, he did not seek this new rank. It is a recognition by @admin of his outstanding record of assisting users whenever, and wherever he can.
About a week ago when HSB V5.8.2.0 was first installed I created an Emergency Disk and exported the ISO. The ISO was subsequently copied to my Ventoy boot USB. That ISO version is a big 1,097,600 KB. When Ventoy is booted and hbswinpe is launched I have keyboard, mouse, and wifi access. The problem is I an unable to recreate that ISO version, and I cannot remember what I did.
All the versions that I currently rebuild are about 550,000-625,000 KB and do not have keyboard, mouse, or wifi access. Some version have been built with the Hasleo Offline WinPE, and some with netwtw6e.inf and netwifimp.inf drivers included. Makes no difference.
One hint might be when the PE Network Manager is started from the Tools menu it gives the error "An error occurred while starting the TCP/IP Registry Compatibility service (2)!". This does not happen with that original build.
Any ideas or suggestions, and is there any useful information obtained from mounting the ISO and examining its contents?
I’m using Hasleo Backup Suite Free V5.6.2.1 and I am trying to restore a file to its original location. The online tutorial shows a radio button in the Restore dialogue labelled ‘Restore to original location’ but I can’t find that button in my version of the program. When I enter the file’s original location in ‘Restore to:’ I don’t find the restored file where it should be, instead I find a chain of folders mimicing the original file path starting at C:. If I specify restoring to C: I find another chain of folders in C:. How can I copy a file from backup to its original location on my PC?
When a system image is mounted is there a way to access the protected folders? The access is needed to restore some of the folders in C:\Users\me\* that were stored in a previous build.
I did some searching on the Backup Forum but didn't find this information. I "assume" that when performing a backup of one's System Disk the copying of the Recycle Bin is excluded. I'd just like confirmation. Thanks!
Greetings all! While listening to documentation needs here at the Forum, and balancing that with some of my own needs, I have decided to create an all encompassing, PDF-based Feature Compendium for the Hasleo Backup Suite. I'm in discussions with Hasleo on how best to offer an on-going, updated version of this document to the user community... that's the difficult part as the on-line documentation changes quite often. We'll keep working on this project and try and bring it to some sort of conclusion.
In the meantime, the "point-in-time" version of this document (as of today) is called Hasleo Backup Suite - Tutorials located on my GOOGLE Drive Feel free to use the title's active link to download this current version until we figure out how to go public with a fully supported version.
There is a known issue with Windows KB5083769 update that causes backups to fail. Almost all backup software is affected, including Acronis, Macrium, and Hasleo. For more information, please refer to: https://forums.malwarebytes.com/topic/33...il-update/
Regarding Hasleo Backup Suite, several users have reported that file backups get stuck at 0% or 79%. Strangely, disk backups are not affected. The solution is to uninstall KB5083769, restart the computer, and then run the backup again.
