I just upgraded to v 4.4 today, set up a new schedule, and ran a full back up.

However, the full back up seems to be hung.   Here is a screenshot of what I am seeing:



The elapsed time clock is advancing, but the estimated remaining time is remaining at 1 second.

The file size on the backup drive (a NAS) is not changing, and is a little less than 1/2 the size it should be.

I clicked on the cancel button, and it said cancelling please wait, but after over 5 minutes it had not cancelled. I tried to exit, by clicking the red 'x' in the top right of the screen, but a popup said the system was busy and I could not.

I have now restarted the system, will try again, and post back here with my results.


QNAP TS-216G 

Imagine this scenario:

1. User creates "File Backup X"

2. User selects:
x C:\01
x C:\02
x C:\03

3. User creates Backup.

4. User renames "02" to "02-R" and deletes "03"

5. User edits Backup. User sees:
x C:\01
o C:\02-R

Note: It is normal and expected that 02-R is not selected.

6. User creates renames 02-R to 02, and creates 03 again.

7. User edits Backup. User sees:
x C:\01
x C:\02
x C:\03

===> When editing a backup, not selected file paths are not shown if they are currently not available. Other backup suits show these files as selected and grayed out (not available). It's not a big problem, I just wanted to draw users' attention to this specific situation.

Hello,

am no longer able to safe backups. I do not know why.

The destination path is
H:\Backup\Windows\Hasleo\Data\VM_Data_2024-03-20

The files there are:
VM_Data_2024-03-20_20240321_Full_V1_1.DBI
VM_Data_2024-03-20_20240402_Incremental_V2_1.DBI
VM_Data_2024-03-20_20240408_Differential_V4_1.DBI
VM_Data_2024-03-20_20240408_Incremental_V3_1.DBI
VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI

I am able to RESTORE files from VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI with NO PROBLEMS when I ciick on the BLACK icon for restoring and select VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI .

But when I try to create another incremental, I get the error "0x083f00850000003 System cannot find the path specified".

When I go to Backup properties, the folder icon at the end of the field "Path" is greyed out. (I think that's normal).

I have a second backup on H: (based on 2023). The problem is the same there. So it is not a specific problem with the 2024-03-20 backup. It is a general problem.

When I click "Open Location", I also get the error! Even though the location is accessible (can restore, can see it in Windows Explorer).

I don't know what happened.

Hello,

when doing a File Backup and selecting C:, Hasleo Backup will save hiberfil.sys and pagefile.sys. I think this means it is not possible to save ALL files in C: _except_ hiberfil/pagefile.

Saving these two files makes no sense and wastes a lot of space.

My suggestion would be to add an option to Hasleo Backup Suite: "INCLUDE pagefile.sys and hiberfil.sys in File Backups".
This option could be either in a config.cfg text file "exclude_pagefile=1, exclude_hiberfil=1" so the user can change to 0, or an interface option.
I would suggest a config.cfg text file because this a very case that a user would want them to be included.

Thank you. 

You may want to prioritize this because it wastes a lot of space and I think there is no workaround. 

Please note that excluding the file from backup manually will prevent files from being backuped if they are newer than the initial full backup date unless the user checks the backup configuration before every backup.

===============
SOLUTION:
It is true that for every incremental/diff, Hasleo would backup a new version of hiberfil/pagefile.
However the problem is solvable:

Scenario A: User wants to save ALL of C: --> Use disk / partition backup.

Scenario B: User does NOT want to save ALL of C:
-> In this scenario it is not possible to save files that later are placed into C: ROOT (!) anyway -- unless the user manually adds them every time before an incremental (backup).
-> For this reason, there is no disadvantage in deselecting hiberfil and pagefile in c:
-> Average users might forget this. But the solution is easy: Just navigate to C:, go to right panel, scroll down, and deselect hiberfil and pagefile. You can even do this AFTER having created a backup because you can still edit the backup scheme. Subsequent incremental will thus NOT contain hiberfil/pagefile.

Hi everyone:

Recently I used WintoUSB 2.0 beta to install Windows 10 Tech Preview build 9841, the process is pretty smooth.

My question right now is: does the stable 2.0 release support upgrading builds right within the external drive without going through the entire process within WintoUSB again? Like either trick Windows into think my external drive is an HDD, or actually make the external drive emulate the environment of HDD.

I wanted to upgrade to build 9926 because the UI is just too beautiful to ignore. I'm gonna wipe my current install of build 9841 and download the latest version of WintoUSB just to install build 9926.

Currently, if Windows asked to upgrade my build, and I choose it to do so, it will pop up a message saying "Windows Technical Preview cannot be installed in a flash drive."

The changes made so that 1809 works seem to be reversed when sfc /scannow is run. I was attempting to fix an issue where Legacy booting worked but EFI would hang on loading everytime, recreated the boot partition with bcdboot, didn't work, tried sfc /scannow and now the system blue screens every time I boot legacy or EFI.

Just something for others to take note of.

Scenario #1.
I create a task that I will perform manually. In Backup options I check the option
I click the Proceed button, but the comment entry window does NOT appear, the task starts immediately.
Scenario #2.
I create a task that I will run manually. In the Backup options, I check the option...
Turn on Back up later and click Save. On the Home page, I click Backup or select the backup type from the drop-down menu and click Proceed, in both cases the comment entry window appears.
Summary: in scenario #1, the comment entry window should also appear, because here the task is also performed manually, not by the scheduler. Is it a bug or not a bug?

Usually, the user expects the uninstaller to remove all traces of the program installation. In our case, the uninstaller works sloppily. The program folder with logs inside, <ID>.SDI and <ID>.WIM files, registry keys are not removed. This is despite the fact that the program is light and does not dig deep into the system.

It's not about the date format, it's about the fact that the time stamp displayed in WinPE is completely incorrect. Below is an example with a backup created from under Windows.
In HBS v4.4 under Windows, the time stamp is 08:35 on March 30, which is the actual correct time.
When booting into WinPE, the time stamp is distorted: 22:35 on March 29.
This is extremely confusing for the user, causing a lot of inconvenience by having to calculate and match the false time to the correct time.
In my opinion, this is a serious flaw. The same problem was originally in Macrium Reflect, but the developers have successfully solved it.

Hey guys, first time user and lover of WinToUSB but I have some problems that I would like to seek guidance on.

I have created a USB-C Windows 11 installation using WinToUSB and everything appears to be working as designed. I am using this on a Lenovo Thinkpad T14s Gen3 device. The issue I have is when I reboot or shutdown the laptop from the Windows 11 WinToUSB installation the machine will stay powered on, that is, black screen, no activity. The only way to power off is to hold the power button for 5-10seconds, and then upon power on I can select the USB-C disk again and it boots into the WinToUSB installation normally (no errors about incorrectly shutting down or anything)

I am convinced this is likely a BIOS / Configuration issue in some way - can anyone assist?

Thanks