Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HBS Free v5.5.2.0 - Windows Server 2025 - Error 0x075400690000045D
#1
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).

[Image: KrhO7w7.png]

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  Wink


Attached Files
.zip   backup-suite-log-20251029183922.zip (Size: 10.17 KB / Downloads: 1)
Reply
#2
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).
Reply
#3
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.
Reply
#4
(11 hours ago)al3x Wrote: 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).

[Image: KrhO7w7.png]

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  Wink

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.
Reply
#5
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.
Reply
#6
(4 hours ago)al3x Wrote: 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.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)