Page 1 of 1

New Asus BW-16D1HT: MakeMKV 1.18.2 stuck at Scanning CD-ROM devices, 1.17.7 crashes

Posted: Mon Nov 17, 2025 1:25 am
by nigel_pyjamas
I have been using MakeMKV without any issues for years with my old Lite-On blu-ray drive, and more recently on Linux (Mint).

Last week, I purchased a new BW-16D1HT on Amazon, since it was recommended on the Ultimate UHD Drives Flashing Guide Updated 2025 page. Now, when launching MakeMKV, it hangs at "Scanning CD-ROM devices" forever.

What I tried so far:
  • Uninstalled makemkv and makemkvcon 1.18 (I think), then installed 1.17.7 (that one crashes immediately on launch)
    Tried VLC and Handbrake: they will list some of the short tracks, but will not list the main movie file
    When running "makemkvcon f -l", it says "found 1 drive" and lists it properly
    The drive appears when I insert a blu-ray or DVD, and I can browse the files normally. I can even watch some of the files, though the playback is very choppy
    Turned off my PC, waited for 5 minutes, and tried again
While I had 1.17.7 installed, I even tried flashing the drive using this command:

Code: Select all

./makemkvcon f -d 'dev_21:1' -f /tmp/sdf.bin rawflash enc -i /tmp/ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
but I get an error message:
Reading input file /tmp/ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
There is a disc in drive, please remove it and try again
DEBUG: Code 4278542595 at 4x}OdB6]jwJ6=qYm;3kV-<Z@yk:nX!bk:29396644
Command produced error code 0xff056103
There is no disc in the drive.

Also tried with sudo, to no avail.

I turned on the logs, this is what I get:
Debug log started at Fri Nov 14 08:46:40 2025 , written by MakeMKV v1.18.2 linux(x64-release)
001005:0000 MakeMKV v1.18.2 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/nigel/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 8.5.0/OpenSSL/3.0.13/1.59.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at [$&!cPHsNoNC,vJT%<05$ :29393631
No SDF v0a2: ASUS_BW-16D1HT_3.11_212012011759_KLEP48G2326
SDF auto v0a2: ASUS_BW-16D1HT_3.11_212012011759_KLEP48G2326

By the way, the first time I booted my PC with the new drive, I heard this nasty Commodore 64-like sound. This is normal, right? The drive seems to be reading data discs fine.
I would like to know if the problem is the firmware, which might be blocking copyrighted material, or is my drive DOA.

Oh, and I checked the sticker on the drive, and it says 2025...

Finally, as a reminder, I'm on Linux Mint.

Re: New Asus BW-16D1HT: MakeMKV 1.18.2 stuck at Scanning CD-ROM devices, 1.17.7 crashes

Posted: Wed Nov 19, 2025 11:26 am
by Coopervid
nigel_pyjamas wrote:
Mon Nov 17, 2025 1:25 am
I have been using MakeMKV without any issues for years with my old Lite-On blu-ray drive, and more recently on Linux (Mint).

Last week, I purchased a new BW-16D1HT on Amazon, since it was recommended on the Ultimate UHD Drives Flashing Guide Updated 2025 page. Now, when launching MakeMKV, it hangs at "Scanning CD-ROM devices" forever.

What I tried so far:
  • Uninstalled makemkv and makemkvcon 1.18 (I think), then installed 1.17.7 (that one crashes immediately on launch)
    Tried VLC and Handbrake: they will list some of the short tracks, but will not list the main movie file
    When running "makemkvcon f -l", it says "found 1 drive" and lists it properly
    The drive appears when I insert a blu-ray or DVD, and I can browse the files normally. I can even watch some of the files, though the playback is very choppy
    Turned off my PC, waited for 5 minutes, and tried again
While I had 1.17.7 installed, I even tried flashing the drive using this command:

Code: Select all

./makemkvcon f -d 'dev_21:1' -f /tmp/sdf.bin rawflash enc -i /tmp/ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
but I get an error message:
Reading input file /tmp/ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
There is a disc in drive, please remove it and try again
DEBUG: Code 4278542595 at 4x}OdB6]jwJ6=qYm;3kV-<Z@yk:nX!bk:29396644
Command produced error code 0xff056103
There is no disc in the drive.

Also tried with sudo, to no avail.

I turned on the logs, this is what I get:
Debug log started at Fri Nov 14 08:46:40 2025 , written by MakeMKV v1.18.2 linux(x64-release)
001005:0000 MakeMKV v1.18.2 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/nigel/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 8.5.0/OpenSSL/3.0.13/1.59.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at [$&!cPHsNoNC,vJT%<05$ :29393631
No SDF v0a2: ASUS_BW-16D1HT_3.11_212012011759_KLEP48G2326
SDF auto v0a2: ASUS_BW-16D1HT_3.11_212012011759_KLEP48G2326

By the way, the first time I booted my PC with the new drive, I heard this nasty Commodore 64-like sound. This is normal, right? The drive seems to be reading data discs fine.
I would like to know if the problem is the firmware, which might be blocking copyrighted material, or is my drive DOA.

Oh, and I checked the sticker on the drive, and it says 2025...

Finally, as a reminder, I'm on Linux Mint.
Read this:

viewtopic.php?f=3&t=37670

and flashing according to the guide works like that:

. type "./makemkvcon f -l"

This will show your drive identifier should look similar to this ''/IOBDServices/D5D25996'
Found 1 drives(s)
00: /IOBDServices/D5D25996, /dev/rdisk3, /dev/rdisk3
HL-DT-ST_BD-RE_BU40N_1.01_211910161032_MOFK6283224


7. to perform the flash, type "./makemkvcon f -d '/IOBDServices/D5D25996' -f /tmp/sdf.bin rawflash main -i /tmp/your firmware filename here
or ./makemkvcon f -d '/IOBDServices/D5D25996' -f /tmp/sdf.bin rawflash enc -i /tmp/your firmware filename here
if your firmware is on the encrypted list