+x

 

dbminter - 14 January 2023 4:25 PM

It most likely started with the release of 8.1.7248.  That was the build where I had a CBT issue where it was keeping partitions "In Use" in Disk Management when attempting to remove drive letters from partitions.  It had not been present before 7248.

I also believe it started in 8.1.7248.  See my detailed reply to this post
and specifically my reply posted 13 January 2023 1:29 PM (CST) that deals with a locked eSATA disk - configured in BIOS as a removable drive.


L.W. (Dan) Danz, Overland Park KS

The change log for 7248 does indicate a change was made to the CBT driver:

"Changed Block Tracker
Improved I/O scheduling under low memory conditions."

I can confirm this is an issue with Build 7368. 

Work around - I use two different batch files and a text file to force eject the USB drive used in cloning drive.

First batch file (I named EjectUSB.bat)

@echo off
set tempfile="%TEMP%\diskscrp.dsk"
REM ***************************************************************************************************
REM * You will need to replace the call to listvolumes.bat with the actual location of the batch file and accompanying TXT file *
REM ***************************************************************************************************
REM diskpart /s %userprofile%\documents\utilities\ejectusb\listvolumes.txt
call %userprofile%\documents\utilities\ejectusb\listvolumes.bat
echo.
set /p volume=" Which volume do you want to eject? "
echo.
echo select volume %volume% >>%tempfile%
echo offline disk >>%tempfile%
echo online disk >>%tempfile%
diskpart /s %tempfile% | findstr /C:"not valid"
if "%ERRORLEVEL%"=="1" (
 echo Disk has been unlocked successfully. Try to safely remove it now.
 pause
)
del /F %tempfile%
pause
echo any key to exit

The second batch file (I named listvolumes.bat)

diskpart /s %userprofile%\documents\utilities\ejectusb\listvolumes.txt
pause

The listvolumes.txt contains the following diskpart command:

list vol

Not 'fancy' but it works:-)

This should have been addressed by now.  I know it's not an issue with Samsung T7 USB SSD's as I've had no issues Ejecting those for months.

+x

 

dbminter - 19 September 2023 4:46 PM

This should have been addressed by now.  I know it's not an issue with Samsung T7 USB SSD's as I've had no issues Ejecting those for months.

Copy that. I sent an email to Macrium Support and the response I received was very disappointing and not very helpful:

At this time, we don’t have the bandwidth to complete your request. I apologize that we can’t provide a direct solution . . .   .

I plan on tinkering with making a Macrium script after the clone is completed that would run the EjectUSB.bat file (given in my initial post).