I'm trying everything to restore a backup of a physical Windows PC to a Proxmox VM, but to no avail. Has anyone succeeded?

I'm a long-time Veeam agent for Windows free user. Always worked when needed. When a couple of days ago Veeam prompted me to install the latest version I did so and created a new recovery usb stick when prompted to do so.

The recovery stick didn't work: no keyboard, no mouse. Found out that it's the latest Microsoft update bricking the winre environment. None of the suggested solutions worked. Veeam is silent about the problem. Waiting for a Microsoft fix.

Found Hasleo Backup. Installed it. They have their own winpe environment. It works. The backups are faster and smaller than Veeam, both full and incremental. Everything works, mounting images is easy and fast. Recovery stick offers the same interface as the full Windows environment.

How is this possible? Questions on this forum gets answered. Bugs get fixed. Where's the catch?

Hello.
When creating a backup system with a schedule, a task is created. However, when manually enabling it, the following error appears: The system cannot find the path specified (0x02FD008500000000). Even though the folder hasn't been adjusted and is specified correctly.

The only solution is to reopen the task editor and, without changing anything, click Select folder under Save location and save the task again. Then the task starts without any problems.

Trying to clear my head a bit from the early days...

At what point is the HBS Emergency Disk built using the System's existing WinRE-base WIM rather than the MicroSloth downloaded (PE-based I believe) WIM.

I assume using the off-line (OPE) version is PE-based.

Any help, greatly appreciated!

Привет.
При использовании диска аварийное восстановление загрузка происходит очень долго. Появляется пустой синий экран, на котором можно перемещать только курсорную мышь. Программа запускается примерно через четыре минуты, после чего всё работает нормально. 
При использовании диска аварийного восстановления загрузка происходит очень долго. Появляется пустой синий экран, где можно только двигать курсором мыши. Программа запускается только примерно через четыре минуты, после чего всё работает нормально. То же самое происходит при добавлении Hasleo в список загрузки или при попытке восстановить системный раздел. Всё работает нормально, но только после долгого ожидания.
Я создал образ WinPE из системы и поставил галочку, чтобы загрузить его с сайта Microsoft — никакой разницы.
Windows 11 и Hasleo – все последние версии.
Так и должно быть, или я что-то делаю не так?

How far back does compatibility of Backup Image Files (DBI) go with the Emergency disk? That is, will an emergency disk made with the latest version of HBS, recognise and restore an image file made a year ago?, six months ago? AND vice versa - will a DBI file made now be recognised by an Emergency disk made a year ago, six months ago?

Hello everyone,

I'm wondering about the following: I'm a full time Linux user and would like to perform firmware updates of my Thunderbolt controller and my PD controller, but ASUS does not provide executable binaries for Linux unfortunately (only the BIOS / UEFI image is available and can be flashed via ASUS ezFlash in the BIOS / UEFI). Im not interested in installing Microsoft Windows on my PC at all, but would like to flash my PD controller and my Thunderbolt (ASMedia) controller on my motherboard. Would it work if I would boot from a WinToUSB stick and then perform the flash or is this not possible / risky? My system is using an ASUS X870E based AM5 motherboard (so relatively recent).

1)
Does fastboot need to be turned off before you make a system image or is it safe to leave it on and make a system image?


2)
I had this very strange thing happen when I made a system image which I had validated (checked) upon image-finish and did a re-check through Tools > check image, both times there where no errors. When I rebooted the machine the image was gone, like it was never made ...
The image was made on a drive that plenty free space and no type of encryption.
But:

• I used very long names with spaces and dashes (no special characters, just a-z, 0-9 and dash and underscore) but the image name was very long and the foldername in which the image was created also had a very long name.
  
  
• When I booted the system with linux-lite-usb I saw that the drive I tried to save the image on was read-only. The other drives on my system where normal read-write. In windows I can read/write normally on it. But in linux (live environment) and in hasleo usb-boot I could not place the created system image. But I find it strange that the image could be created successfully without errors and validation did not yield errors
  

• All was done through the backup-suite usb live environment
  
• In following backup attempts after I made the image I went to the option to "restore" the image just to look if it actually existed, and in the backup-suite the image existed! But when booting to windows they where gone!
  

I just upgraded my computer and installed a new NVMe SSD. I want to move the EFI partition from the old drive to the new drive using EasyUEFI to boot directly from NVMe. However, after copying and adjusting the boot entry, the computer still reports No bootable device.

I have tried:

Using Manage EFI System Partition to select the NVMe drive as the primary ESP

Adding a boot entry manually in EasyUEFI

Checking in BIOS, the boot option has appeared

But when booting, it still cannot boot.

Is there any step I am missing? Does EasyUEFI fully support moving EFI between SATA and NVMe drives, or do I need additional steps in BIOS/UEFI?

Hello all,

after WinToUSB Free v10.0 setup completed I also was happy to notice that it already included own x64 version of its executable.
But why after WinToUSB 10.0 setup completion, its x64 executable icon was not created and so enabled for its direct execution on my x64 OS (Windows 7 SP1 x64 Ultimate) ?

I mean the 'Hasleo WinToUSB' icon it created only into its own menu (with same name) into Programs (since I choose not to create another one also on Desktop) would have been better if created to launch its x64 executable icon ('C:\Program Files\Hasleo\WinToUSB\x64\WinToUSB\bin\WinToUSB.exe') rather than only having x86 version icon created ('C:\Program Files\Hasleo\WinToUSB\bin\WinToUSB.exe').

Or otherwise setup might have been a little smarter to possibly let me choose if I preferred to run x64 version icon only or even propose me to have both x64 and x86 version icons rather than simply forcing me to only be able to choose x86 version icon.

What do you think about this ?

Thanks in advance for anyone else attention and quite obviously more related comment on this.

Best Regards
Rob