I've created a clone of my Win10 home edition on a 2tb Sandisk USB SSD protected by bitlocker.   Windows works as expected.  The problem is when I'm logged in I cannot view the drive WINTOUSB: (D), which is providing the functionality normally seen in C: and contains all the windows and user files.   When I click on the drive in Explorer I see the the message "You don't currently have permission to access this folder".  Is there any way to access this folder when logged in?  I can access it from other computers, just not when logged in to the bootable version.

Occasionally (I've seen it twice now), when I am in the "Common Tools/View Logs" entry, and I click on Delete, the "View Logs" window and the main app window both close.  When I re-open the main app and go to the "View Logs" entry, the logs are gone as expected.

I don't do this very often so I don't know whether it happens every time I try to delete the logs... just bringing this to your attention.

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.