SDFtool Flasher

Forum for discussions about UHD-capable dives
MrMegadeth99
Posts: 24
Joined: Sat Jun 08, 2024 3:01 am

Re: SDFtool Flasher

Post by MrMegadeth99 » Wed Apr 22, 2026 3:53 pm

If I do that then the drive doesn't read 4Ks or blu ray discs. With BP50 it at least still reads blu ray discs. Do you know what went wrong? I followed the steps exactly and even watched the tutorial video on the first page of this post.

MrMegadeth99
Posts: 24
Joined: Sat Jun 08, 2024 3:01 am

Re: SDFtool Flasher

Post by MrMegadeth99 » Wed Apr 22, 2026 5:02 pm

My drive is actually WP50NB40 but the instructions say for WP/BP. It shouldn't matter right?

Mr_Orange
Posts: 222
Joined: Sun Jul 14, 2019 6:11 am

Re: SDFtool Flasher

Post by Mr_Orange » Wed Apr 22, 2026 8:46 pm

MrMegadeth99 wrote:
Wed Apr 22, 2026 5:02 pm
My drive is actually WP50NB40 but the instructions say for WP/BP. It shouldn't matter right?
You should be doing this:
WP/BP50NB40 to > BP50NB40-NB50-1.03MK then to > BP60NB10 1.02MK or 1.00MK

MrMegadeth99
Posts: 24
Joined: Sat Jun 08, 2024 3:01 am

Re: SDFtool Flasher

Post by MrMegadeth99 » Wed Apr 22, 2026 9:21 pm

I did that but when I flashed to 1.00 my drive wouldn't even read blu ray or 4K. I got it to read blu ray again when flashed back to 1.01. You think I should try flashing to 1.02?

Dexeltin
Posts: 1
Joined: Sat May 02, 2026 4:37 pm

Re: SDFtool Flasher

Post by Dexeltin » Sat May 02, 2026 4:52 pm

Lazarus wrote:
Thu Sep 21, 2023 11:57 pm
Hello
I have an LG WH16NS40 drive (rev 1.05), version 1.17.4 of MakeMKV installed. I am trying to run SFDtool Flasher and I get a Microsoft .NET error of Unhandled exception. If I continue past the error the app loads but the select drive box is blank. MakeMKV sees the drive correctly as a MT1959 platform. I am running Windows 11. Is the error because of Win11?


Thanks
Hi everyone! I ran into the same issue as Lazarus. The solution is straightforward—just download the latest version of MakeMKV and install it with administrator permissions. That fixed the problem for me.

I spent almost two hours getting it to work, and I can confirm the issue (and the fix) applies to both Windows 10 and Windows 11.

Post Reply