I am using an Axe Memory 500 GB flash drive and creating Win 11 Pro on it. Formatting lasts 45 minutes by now and WintoUSB still doing the same thing. What's wrong? Never have encountered that long-lasting formatting.
I chose a partition scheme MBR for BIOS and UEFI. The partition style of my C drive is GPT. Maybe this was my wrong decision?

EDIT: I can't believe it!!! It's been much over an hour now

Edit2: That's it! I can't stand this any longer   Two hours have passed.

EDIT3: Sorry guys for leading you to confusion. That is something wrong with my computer. I hit the task manager and I saw 0% usage of CPU by WintoUSB. Apart from this, there's some different behavior of my PC I noticed.

I have installed WintoHDD on my Windows 10 PC, but when I try to run it I receive the message 'A required privilege is not held by the client' on screen and the software does not run? I have checked all the relevant permissions for drive, directories and exe files, but found no errors? However, I am able to run the program in safe mode, which is obviously useless as this does not allow any operations on the OS! Convention says that there must be an existing program preventing the startup, but I do not know how to identify such a program? Are there known third party programs that could block access? Many thanks.

The system takes a few seconds to settle down or the taskbar to appear as HBS is running. It would be better if HBS ran or took the missed backup after 5 or so mins of the system starting.

The Add Boot Menu tool creates "winpe.iso" in the bin folder of Hasleo. Is this winpe.iso and the Emergency Disk exported ISO the same?

Greetings!  My first attempt at using the CLI was apparently very successful... tying a CLI Differential creating command to an event trigger (USB discovery) via pre-Command w/Powershell.

I then set up a DAILY Incremental task.  When I try to execute a CLI image creation based on that task, It appears to run to about the 46% point then ends in failure, although it appears that the requested image was created.  The CLI command is below, along with the error from the LOG.  I'm using the same Powershell successful script mentioned above.  Any idea what's going on?

CLI: BackupCmdUI.exe /a run /g 9CE52D55-0C5F-44D9-B700-3198EC9E0A3C /t 2
LOG error: The handle is invalid. (0x00A5001200000000), The task failed with 0x00A5001200000000.

...additional DataPoint, both the scheduled version and the manual version work fine on that task.

Greetings!  I just started playing with your cloning feature.  First attempt... problem.  I kinda understand why it won't allow OS disk cloning to an external USB disk, but I don't understand the error msg that states destination disk is too small to clone a single Partition when the source partition is smaller than the destination disk, but originates from a larger disk.  Why wouldn't that be allowed... we're only dealing with a single partition clone?

Thanks in advance for helping me with my confusion...

Please provide an option to "check for updates" so users can disable the update check on systems managed by them.

I have the HBS Backup Schedule set to Daily-RunAtIntervals with Interval Time (1 hour) and "Run missed schedule at the next system startup" disabled.

HBS occasionally takes a missed backup when I start the system.

It seems there is some incompatibility between HBS and Windscribe VPN. HBS crashes the moment I connect to Windscribe. HBS creates empty dump files, and Windows Event Viewer reports no HBS errors. The situation improves if I add HBS executables to Windscribe's split tunneling feature.

I added the below HBS executables to Windscribe's split tunneling.
AppLoader
BackupService
BackupMainUI
BackupWorker
BackupSystemTray
Now HBS doesn't crash but doesn't take backups, or backups fail when I connect to Windscribe or it is connected.

Sometimes HBS crashes and shows an error "inter-process communication" if I only add BackupService and BackupSystemTray to Windscribe.

HBS Version 3.5 (Build: May 16, 2023)
Windows 10 Pro

I'm going to make Win11 Pro WTG on an Axe Memory flash drive of 500 GB.
I see an option in WintoUSB like "Virtual Hard Disk Size". Do I need to modify the number which showed up in there or am I supposed to leave this as it is?
Another question. Maybe stupid one, maybe not. 500 GB is a big-capacity flash drive. So I wonder how WintoUSB is going to treat this external device. Therefore should I choose VHDX or maybe legacy installation mode?

Edit: Okay now. Disregard the second question guys. I can put an ISO file thru WintoUSB two times after all. In case when something wrong would have been with WTG then I'll choose another installation mode making WTG again. There's no big deal.