Ultimate UHD Drives Flashing Guide Updated 2025

[xunil76]

Getting an error when trying to run SDFtool Flasher that says "ERROR: MakeMKV installation not found. Please install MakeMKV."

Thing is, I have MakeMKV v1.18.2 installed and registered

Probably in a non-default location. So copy SDFTool Flasher to that location. You can find it in "View" "Preferences" "General" when you run Makemkv. You made it difficult in the first place yourself.

There are perfectly valid reasons for not installing things into the default installation directory, which is why the vast majority of program installers give you that option in the first place (MakeMKV included, mind you). I never use the default C:\Program Files or C:\Program Files (x86) locations for installing anything, except for those select few things which don't give me any option to change the installation directory (which irks me to no end).

I have a C: partition that is literally for Windows and Windows only, then a D: partition where I install everything else. This is because starting at least with Windows Vista (if not earlier), Windows has an extremely annoying tendency over time to fill up whatever free space is available on C: (I'm looking at YOU, C:\Windows\WinSxS), and installing everything else onto a separate partition prevents me from ever even being able to use up all of that space on C: with my installed apps/games, which would prevent (and has in the past prevented) Windows Updates & the like from being able to complete. I even move the Windows page file onto another partition so that is not eating up space on C:.

That said, I tried copying SDFtool Flasher directly into the root MakeMKV installation folder, as well as "...\MakeMKV\Data" (which is what the Preferences you mentioned show as the data directory), and it still doesn't work in either case.

What did work, however, was creating a Symbolic Link from my existing MakeMKV installation directory on D: into the C:\Program Files (x86) folder...so anyone else running into this issue now knows how to workaround without resorting to completely uninstalling MakeMKV and reinstalling it into the default location. Hope that helps at least a few people out there.

Seems to me that there should be an option when coming across this error to manually point the SDFtool Flasher to the MakeMKV EXE file if it can't find it on its own; that would be a much more elegant solution to the problem for those like myself who prefer not to use the default installation path.

Perhaps this could be a feature request for a future update to the tool? Admittedly I'm not a coder myself, but I really doubt that would be very difficult to achieve.

[Coopervid]

Getting an error when trying to run SDFtool Flasher that says "ERROR: MakeMKV installation not found. Please install MakeMKV."

Thing is, I have MakeMKV v1.18.2 installed and registered

Probably in a non-default location. So copy SDFTool Flasher to that location. You can find it in "View" "Preferences" "General" when you run Makemkv. You made it difficult in the first place yourself.

There are perfectly valid reasons for not installing things into the default installation directory, which is why the vast majority of program installers give you that option in the first place (MakeMKV included, mind you). I never use the default C:\Program Files or C:\Program Files (x86) locations for installing anything, except for those select few things which don't give me any option to change the installation directory (which irks me to no end).

I have a C: partition that is literally for Windows and Windows only, then a D: partition where I install everything else. This is because starting at least with Windows Vista (if not earlier), Windows has an extremely annoying tendency over time to fill up whatever free space is available on C: (I'm looking at YOU, C:\Windows\WinSxS), and installing everything else onto a separate partition prevents me from ever even being able to use up all of that space on C: with my installed apps/games, which would prevent (and has in the past prevented) Windows Updates & the like from being able to complete. I even move the Windows page file onto another partition so that is not eating up space on C:.

That said, I tried copying SDFtool Flasher directly into the root MakeMKV installation folder, as well as "...\MakeMKV\Data" (which is what the Preferences you mentioned show as the data directory), and it still doesn't work in either case.

What did work, however, was creating a Symbolic Link from my existing MakeMKV installation directory on D: into the C:\Program Files (x86) folder...so anyone else running into this issue now knows how to workaround without resorting to completely uninstalling MakeMKV and reinstalling it into the default location. Hope that helps at least a few people out there.

Seems to me that there should be an option when coming across this error to manually point the SDFtool Flasher to the MakeMKV EXE file if it can't find it on its own; that would be a much more elegant solution to the problem for those like myself who prefer not to use the default installation path.

Perhaps this could be a feature request for a future update to the tool? Admittedly I'm not a coder myself, but I really doubt that would be very difficult to achieve.

Glad you sorted it out. Being so knowledgable about all you posted, I wonder why you yourself didn't figure it out. Upgrade your C: drive with enough space and forget about all that stuff that just creates issues. That's what I would do.

[xunil76]

Probably in a non-default location. So copy SDFTool Flasher to that location. You can find it in "View" "Preferences" "General" when you run Makemkv. You made it difficult in the first place yourself.

There are perfectly valid reasons for not installing things into the default installation directory, which is why the vast majority of program installers give you that option in the first place (MakeMKV included, mind you). I never use the default C:\Program Files or C:\Program Files (x86) locations for installing anything, except for those select few things which don't give me any option to change the installation directory (which irks me to no end).

I have a C: partition that is literally for Windows and Windows only, then a D: partition where I install everything else. This is because starting at least with Windows Vista (if not earlier), Windows has an extremely annoying tendency over time to fill up whatever free space is available on C: (I'm looking at YOU, C:\Windows\WinSxS), and installing everything else onto a separate partition prevents me from ever even being able to use up all of that space on C: with my installed apps/games, which would prevent (and has in the past prevented) Windows Updates & the like from being able to complete. I even move the Windows page file onto another partition so that is not eating up space on C:.

That said, I tried copying SDFtool Flasher directly into the root MakeMKV installation folder, as well as "...\MakeMKV\Data" (which is what the Preferences you mentioned show as the data directory), and it still doesn't work in either case.

What did work, however, was creating a Symbolic Link from my existing MakeMKV installation directory on D: into the C:\Program Files (x86) folder...so anyone else running into this issue now knows how to workaround without resorting to completely uninstalling MakeMKV and reinstalling it into the default location. Hope that helps at least a few people out there.

Seems to me that there should be an option when coming across this error to manually point the SDFtool Flasher to the MakeMKV EXE file if it can't find it on its own; that would be a much more elegant solution to the problem for those like myself who prefer not to use the default installation path.

Perhaps this could be a feature request for a future update to the tool? Admittedly I'm not a coder myself, but I really doubt that would be very difficult to achieve.

Glad you sorted it out. Being so knowledgable about all you posted, I wonder why you yourself didn't figure it out. Upgrade your C: drive with enough space and forget about all that stuff that just creates issues. That's what I would do.

I guess over the years I've just gotten accustomed to most software being able to account for things like this either automatically, or by allowing the user to manually point it to the correct installation directory, and just didn't really think about that until you mentioned it was likely because MakeMKV wasn't in the default location, so thanks for that!

[Coopervid]

You are welcome. Mike's software doesn't account for the user using his forehead hitting the keyboard and everything works like magic.

[Mr_Orange]

You are welcome. Mike's software doesn't account for the user using his forehead hitting the keyboard and everything works like magic.

It's really not that unusual to have one partition for Windows and another for actual program installations. I do exactly the same as the OP. SDF Flasher is hardcoded with the default location of MakeMKV which, in itself, is not good practice so even when putting the .exe in the same folder as MakeMKV, it still doesn't work.

Marty has indicated that he might change that in the future though.

[Coopervid]

You are welcome. Mike's software doesn't account for the user using his forehead hitting the keyboard and everything works like magic.

It's really not that unusual to have one partition for Windows and another for actual program installations. I do exactly the same as the OP. SDF Flasher is hardcoded with the default location of MakeMKV which, in itself, is not good practice so even when putting the .exe in the same folder as MakeMKV, it still doesn't work.

Marty has indicated that he might change that in the future though.

I did this also in the old days of DOS and the early Windows versions but then I changed it because I also ran in such issues from time to time when there was a non-standard location for some programs. If in any case I run out of space I just clone my C-drive to a larger SSD and use the old one for other purposes like storing video files.

[skywinder21]

Hey guys, I'm working on getting a Buffalo housed BRXL-16U3 reading UHD disks.

Looks like it's a fully repackaged Pioneed BDR-209M running BDR-212T firmware.

Drive Information
OS device name: \Device\CdRom0
Current profile: BD-ROM
Manufacturer: PIONEER
Product: BD-RW BDR-209M
Revision: 8.53
Serial number:
Firmware date: 2019-03-07
Bus encryption flags: 1B
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: RS8F00
Firmware name: PIONEER BDR-212T
Firmware type: Original (unpatched)
Firmware version: 8.53/ID52
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

What do I need to do to flash it for UHD?

Thanks in advance!

PM sent.

Worked out great! Had to try from 2 different PCs to get the drive to show up in the flasher, but it works! Thanks again!

[Coopervid]

Hey guys, I'm working on getting a Buffalo housed BRXL-16U3 reading UHD disks.

Looks like it's a fully repackaged Pioneed BDR-209M running BDR-212T firmware.

Drive Information
OS device name: \Device\CdRom0
Current profile: BD-ROM
Manufacturer: PIONEER
Product: BD-RW BDR-209M
Revision: 8.53
Serial number:
Firmware date: 2019-03-07
Bus encryption flags: 1B
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: RS8F00
Firmware name: PIONEER BDR-212T
Firmware type: Original (unpatched)
Firmware version: 8.53/ID52
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

What do I need to do to flash it for UHD?

Thanks in advance!

PM sent.

Worked out great! Had to try from 2 different PCs to get the drive to show up in the flasher, but it works! Thanks again!

Is McAffee installed on the PC where it didn't show up?

[TheBesto]

Hey guys!
I'm starting to look into saving my physical blu-ray collection into a digital one in order to avoid potentially losing them in the future.
As one can notice, I ended here (coming from the LTT video from a bit more than a year ago).

As a software engineer, I'm trying to understand what's behind the scene regarding all the steps that are linked in the tutorial on first page.
I do understand the need for a drive that can read Blu-Rays (duh), but then I fall a bit short on what the flashing step is supposed to be for.
Can someone explains a bit what it does? Is it to enable 4K HDR support on drives that does not have it? Is it to enable reading protected blu-rays as if they were not? Both, something else?

Also, it seems that, at least in France, most of the drives referenced in the tutorial are not available anymore to purchase.
The only exception is the Buffalo BRUHD-PU3-BK which I do find on Amazon, but it is quite expensive.
Do you have any recommandation there? It seems that the Asmcom website that would deliver pre-flashed drives is not available at the time (getting connection errors when trying to go there).

Thanks in advance

Hi, I'm from France and having the same issue here - can you PM me ? So we can discuss about it a bit

Hey! Just to sum this up for everyone that would like to know more:
- Got myself a Verbatim 43888, as suggested by Coopervid
- Just received it yesterday
- Tested it without flashing - could not rip 4K Blu-Rays but worked for CDs / DVDs / Blu-Rays
- Flashed it (as described in main post + viewtopic.php?f=16&t=22896)
- It now works to rip 4K Blu-Rays as well

It's just a little bit picky, as there are so far multiple discs that failed (one got a corruption error, another somehow made MakeMKV have a fatal error and exit, another seems to be trying to access something he can not, ... I've not yet figured out everything, but since some of them worked, I'm confident I'll succeed with those as well in time).

Now @Amos_Burton if you wish to know more, I'll let you PM me

[Coopervid]

Hey guys!
I'm starting to look into saving my physical blu-ray collection into a digital one in order to avoid potentially losing them in the future.
As one can notice, I ended here (coming from the LTT video from a bit more than a year ago).

As a software engineer, I'm trying to understand what's behind the scene regarding all the steps that are linked in the tutorial on first page.
I do understand the need for a drive that can read Blu-Rays (duh), but then I fall a bit short on what the flashing step is supposed to be for.
Can someone explains a bit what it does? Is it to enable 4K HDR support on drives that does not have it? Is it to enable reading protected blu-rays as if they were not? Both, something else?

Also, it seems that, at least in France, most of the drives referenced in the tutorial are not available anymore to purchase.
The only exception is the Buffalo BRUHD-PU3-BK which I do find on Amazon, but it is quite expensive.
Do you have any recommandation there? It seems that the Asmcom website that would deliver pre-flashed drives is not available at the time (getting connection errors when trying to go there).

Thanks in advance

Hi, I'm from France and having the same issue here - can you PM me ? So we can discuss about it a bit

Hey! Just to sum this up for everyone that would like to know more:
- Got myself a Verbatim 43888, as suggested by Coopervid
- Just received it yesterday
- Tested it without flashing - could not rip 4K Blu-Rays but worked for CDs / DVDs / Blu-Rays
- Flashed it (as described in main post + viewtopic.php?f=16&t=22896)
- It now works to rip 4K Blu-Rays as well

It's just a little bit picky, as there are so far multiple discs that failed (one got a corruption error, another somehow made MakeMKV have a fatal error and exit, another seems to be trying to access something he can not, ... I've not yet figured out everything, but since some of them worked, I'm confident I'll succeed with those as well in time).

Now @Amos_Burton if you wish to know more, I'll let you PM me

Wash UHDs with liquid soap before trying them.

[skywinder21]

PM sent.

Worked out great! Had to try from 2 different PCs to get the drive to show up in the flasher, but it works! Thanks again!

Is McAffee installed on the PC where it didn't show up?

No McAffee - just Windows Defender ... It did not show up on my Win 11 Pro, Asus laptop, but did work just fine on my Win 11 Pro HP Elitebook...

[Coopervid]

Worked out great! Had to try from 2 different PCs to get the drive to show up in the flasher, but it works! Thanks again!

Is McAffee installed on the PC where it didn't show up?

No McAffee - just Windows Defender ... It did not show up on my Win 11 Pro, Asus laptop, but did work just fine on my Win 11 Pro HP Elitebook...

Thanks. Still looking to find the reason when the flasher doesn't fin the drive.