Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HBS Free v5.5.2.0 - Windows Server 2025 - Error 0x075400690000045D
#11
(10-31-2025, 04:01 AM)al3x Wrote: 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.  Wink

This is indeed a peculiar issue. Could installing v5.4.2.5 have disrupted the environment where the problem occurs? Could you try installing V5.5.2.0 again after installing v5.4.2.5 to see if the issue persists?
Reply
#12
(10-31-2025, 01:46 PM)admin Wrote: Could you try installing V5.5.2.0 again after installing v5.4.2.5 to see if the issue persists?

I tried again with a fresh environment, same problem.
Changed the order of installation to first try with v5.4.2.5, this worked.
Then installed v5.5.2.0 and the issue was the same again.

Don't know what's causing it, but maybe this is related to VMware. If noone else is reporting these issues, I wouldn't worry about it too much for now Smile
Reply
#13
(Yesterday, 05:01 AM)al3x Wrote:
(10-31-2025, 01:46 PM)admin Wrote: Could you try installing V5.5.2.0 again after installing v5.4.2.5 to see if the issue persists?

I tried again with a fresh environment, same problem.
Changed the order of installation to first try with v5.4.2.5, this worked.
Then installed v5.5.2.0 and the issue was the same again.

Don't know what's causing it, but maybe this is related to VMware. If noone else is reporting these issues, I wouldn't worry about it too much for now Smile

It is strange that the issue only occurs in v5.5.2.0, we may need to carefully review the code changes made in v5.5.2.0.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)