HBS Free v5.5.2.0 - Windows Server 2025 - Error 0x075400690000045D

[al3x]

I just tried around a bit with the new HBS Free v5.5.2.0.

When I install the free version in a VM with Windows Server 2025 Standard, I receive the following error:
There are bad sectors on the drive. (0x075400690000045D).



Pretty sure this can't happen in a VM.

And why is the free version able to backup on a server edition?
Shouldn't this trigger another error message?

I tried the same with an earlier snapshot and version v5.4.2.5 doesn't throw that error.

Log's attached, hope that helps 

[Froggie]

HBS v5.5.2.0 has been deprecated so it won't run on ENTERPRISE, EDUCATION or SERVER... a licensed copy is now required for that use (PAID version just became available with this release).

[al3x]

That I know but the error message is still wrong because there are no bad sectors.

And currently the free version of v5.5.2.0 seems to be capable of backups on all systems (tested with Win10 Enterprise) so far, just restore and PE build doesn’t work.

[admin]

I just tried around a bit with the new HBS Free v5.5.2.0.

When I install the free version in a VM with Windows Server 2025 Standard, I receive the following error:
There are bad sectors on the drive. (0x075400690000045D).



Pretty sure this can't happen in a VM.

And why is the free version able to backup on a server edition?
Shouldn't this trigger another error message?

I tried the same with an earlier snapshot and version v5.4.2.5 doesn't throw that error.

Log's attached, hope that helps 

This issue seems to be caused by bad sectors on the destination drive where the backup image files are stored, so please check whether there are bad sectors on the destination drive.

[al3x]

There shouldn’t be any, this is all virtual in a VM. The destination is another VMware drive created temporarily to try backups. I made a snapshot beforehand, rolled back to that point later, installed v5.4.2.5 and the backup worked just fine.

But I will try again tomorrow, maybe make a video of the full process.

[admin]

There shouldn’t be any, this is all virtual in a VM. The destination is another VMware drive created temporarily to try backups. I made a snapshot beforehand, rolled back to that point later, installed v5.4.2.5 and the backup worked just fine.

But I will try again tomorrow, maybe make a video of the full process.

Sorry, it's an issue with the source drive. We need to analyze it further.

[admin]

There shouldn’t be any, this is all virtual in a VM. The destination is another VMware drive created temporarily to try backups. I made a snapshot beforehand, rolled back to that point later, installed v5.4.2.5 and the backup worked just fine.

But I will try again tomorrow, maybe make a video of the full process.

Sorry, it's an issue with the source drive. We need to analyze it further.

The log file show Windows returned the error code 0x45D (The request could not be performed because of an I/O device error. ) when Hasleo Backup Suite tried to read the data from the destination drive, such issue is usually caused a hardware issue, such as bad sectors.

[al3x]

Well, I don't know what to tell you.

Here's a video that shows 3 runs I did:
https://youtu.be/v0Fbm76sY7w

Run 1) Backup with HBS v5.5.2.0 Free from within Windows (ends with bad sector error)
Run 2) Backup with HBS v5.4.2.5 Free from within Windows (succeeds)
Run 3) Backup with HBS v5.5.2.0 Pro from WinPE (succeeds, but takes longer)

I did all 3 tests in one take to show that I have not changed anything between.

Maybe there's a small chance that something might actually be wrong with my VM but I wouldn't know how that would've happened.
Also, no problems with my other VMs (Win11 Pro, Win10 Pro, Win7 Ultimate).

It's not a big deal for me personally as I don't use Win Server 2025 and I don't need the backup to work.
I just thought I report it in case something is wrong with the version. 

[al3x]

It looks like this is a combination of multiple things that need to happen to cause this error:
- only with HBS v5.5.2.0
- only with Windows Server 2025
- only with destination drive of type NVMe
- maybe only with VMware Workstation Pro 25H2, can't verify with real hardware

I tried a destination drive with SATA emulation and it went through without problems.
This is kinda special, as NVMe in Windows 11 worked perfectly fine.

Maybe it's driver related, can't really tell.