Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
23H2 -> 25H2 and HBS
#1
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


Attached Files Thumbnail(s)
   
Reply
#2
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?
Reply
#3
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
Reply
#4
(12-12-2025, 12:16 PM)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.
Reply
#5
You are correct. The small delay upon disconnect made me think that the problem existed for the minor edit.
I tested again with just the small edit and the USB drive disconnected properly

With a clean bootup followed by a incremental backup of my C: disk the problem happened.

JayDee
Reply
#6
(Yesterday, 12:54 AM)JayDee Wrote: You are correct. The small delay upon disconnect made me think that the problem existed for the minor edit.
I tested again with just the small edit and the USB drive disconnected properly

With a clean bootup followed by a incremental backup of my C: disk the problem happened.

JayDee

Is the F: drive the destination drive for storing backup image files? Please check if any Hasleo Backup Suite processes are still accessing the F: drive.
Reply
#7
I killed any HBS I could find in Task Manager... still could not disconnect the USB

Note: I usually run HBS from a non-admin account (elevated of course)
        I tried running from an admin account and I was able to disconnect the usb.
        So it seems to be related to permissions.
        This issue did not arise before the switch to 25H2

        BTW when I started HBS from the non-admin account, I tried switching to the
        admin account after the backup completed to try the disconnect. It did
        not succeed.
Reply
#8
Possibly (KB5068861) fixes this issue?
It mentions that some processes can persist and may not even be visible
in task manager.

At the moment that update has not been offered to my computer.

I may try a manual installation

JayDee
Reply
#9
Yes, installing that update is a good step, as it is likely to fix the lingering process issue you mentioned. Looking forward to your feedback after the update!
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)