Hasleo Software Forums
23H2 -> 25H2 and HBS - Printable Version

+- Hasleo Software Forums (https://www.easyuefi.com/forums)
+-- Forum: Hasleo Software (formerly called EasyUEFI Development Team) (https://www.easyuefi.com/forums/forum-1.html)
+--- Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software) (https://www.easyuefi.com/forums/forum-10.html)
+--- Thread: 23H2 -> 25H2 and HBS (/thread-4369.html)



23H2 -> 25H2 and HBS - JayDee - 12-12-2025

Safe removal issue:
I have been running with Windows 11 23H2:
  safe removal
       Reflect: OK
       HBS: OK

Upgraded to Win 11 25h2
  safe removal
      Reflect: OK
      HBS: cannot eject even with eject apps

For non-HBS reasons I had to revert to Win 11 23H2
    and found safe removal
      Reflect: OK 
      HBS: OK

New upgrade to Win 11 25H2
  safe removal
      Reflect: OK
      HBS: cannot eject even with eject apps
            see screenshot

Is there some setting I should know about in Win 11 25H2?

JayDee


RE: 23H2 -> 25H2 and HBS - admin - 12-12-2025

The screenshot you provided shows that system processes are still accessing the drive. Could you tell me what operations you performed before this issue occurred?


RE: 23H2 -> 25H2 and HBS - JayDee - 12-12-2025

Opened HBS
Did a minor edit to a schedule
Saved and exited.

I did the minor edit simply to check the issue.
Simply opening and exiting HBS was insufficient to trigger the issue.
It would appear that it is necessary to actually cause some change
for the issue to appear.

This time I clicked the disconnect and did nothing else.
After a significant delay (several minutes), it did disconnect.

I will continue to test to see how often it disconnects and how long.

JayDee


RE: 23H2 -> 25H2 and HBS - admin - 12-12-2025

(25 minutes ago)JayDee Wrote: Opened HBS
Did a minor edit to a schedule
Saved and exited.

I did the minor edit simply to check the issue.
Simply opening and exiting HBS was insufficient to trigger the issue.
It would appear that it is necessary to actually cause some change
for the issue to appear.

JayDee

This is really strange. In this situation, HBS shouldn't have changed or accessed the F: drive.