Pioneer BDR-206 fails verification at BD-R DL layer break in ImgBurn, but Windows Disc Image Burner works

[griff7337]

Hello,

I’m having a repeatable problem burning Verbatim BD-R DL discs with ImgBurn. The burn completes successfully, but verification fails immediately after the layer transition.

Hardware and media

• Pioneer BDR-206DBK
• Firmware: 1.56
• Drive label says manufactured March 2024
• Vantec NexStar DX2 USB 3.0 optical-drive enclosure
• Verbatim 50 GB BD-R DL, rated 8x
• Media ID: VERBAT-IMf-000
• Windows 11

 

ImgBurn failure

I have tried:

• Multiple brand-new discs from the same spindle
• Multiple unrelated Blu-ray 3D ISOs
• 2x and 4x write speeds
• A generic powered SATA-to-USB adapter
• The Vantec enclosure specifically designed for 5.25-inch optical drives
• Different USB ports

The burn itself completes and finalizes normally. Verification consistently fails at or just after the start of layer 1:

Verifying Layer 0... LBA: 0 - 12219391
Verifying Layer 1... LBA: 12219392 - ...

Failed to Read Sectors 12219424 - 12219455
Reason: L-EC Uncorrectable Error

 

Other attempts failed around:

LBA 12219456

 

So the failure is always within the first few sectors of the second layer.

Some of the failed-verification discs appear to play through the entire movie normally, although one separate PowerISO attempt failed during writing and produced an unusable second layer.

 

Important new result

I burned another BD-R DL ISO using the built-in Windows Disc Image Burner, with:

• The same Pioneer drive
• The same Vantec enclosure
• The same Verbatim spindle
• The same computer and USB setup

Windows completed both the burn and its full verification successfully.

That suggests the drive, enclosure, and media can produce a valid BD-R DL, but ImgBurn’s write process consistently creates unreadable sectors at the layer transition.

The Pioneer also successfully backed up an entire pressed dual-layer Blu-ray using MakeMKV without any read errors.

 

Questions

Is there any known ImgBurn-specific issue involving:

• Pioneer BDR-206 drives
• VERBAT-IMf-000 media
• BD-R DL layer transitions
• SPTI versus Windows IMAPI
• OPC or another advanced ImgBurn setting
• USB optical-drive enclosures

I understand ImgBurn should theoretically be sending standard commands and that there should not be a major difference between burning an ISO with ImgBurn and Windows. However, the result is currently repeatable: ImgBurn fails at the layer break, while Windows burns and verifies successfully.

What logs or settings would be most useful to post for comparing the successful Windows burn against the failed ImgBurn burns?

[dbminter]

I am curious to follow up on your suggestion that it could be ImgBurn's writing process that is faulty, and it's always possible.  Since the built in Windows burning and verifying engine seems successful, I would be interested to see a manual Verify operation performed on one of these Windows burned BD-R DL's.  See if it fails around the layer change.  If it does, then the issue isn't the ImgBurn writing engine, since ImgBurn didn't write the disc, Windows did, but apparently ImgBurn's reading engine.

 

As for known issues with ImgBurn and the layer change with BD-R DL, it's a known issue that many users report with BD-R DL's, regarding the circumstances.  It seems that for the most part BD-R DL just isn't very reliable, regardless of hardware.  See my other testing thread for possible enabling Hardware error correction and other settings.  For instance, my best experience has been with Verbatim DataLife Plus BD-R DL and Ritek's in an LG WH16NS60 in the same VanTec enclosure you're using with ImgBurn burning at 2x only.

[griff7337]

53 minutes ago, dbminter said:

I am curious to follow up on your suggestion that it could be ImgBurn's writing process that is faulty, and it's always possible.  Since the built in Windows burning and verifying engine seems successful, I would be interested to see a manual Verify operation performed on one of these Windows burned BD-R DL's.  See if it fails around the layer change.  If it does, then the issue isn't the ImgBurn writing engine, since ImgBurn didn't write the disc, Windows did, but apparently ImgBurn's reading engine.

 

As for known issues with ImgBurn and the layer change with BD-R DL, it's a known issue that many users report with BD-R DL's, regarding the circumstances.  It seems that for the most part BD-R DL just isn't very reliable, regardless of hardware.  See my other testing thread for possible enabling Hardware error correction and other settings.  For instance, my best experience has been with Verbatim DataLife Plus BD-R DL and Ritek's in an LG WH16NS60 in the same VanTec enclosure you're using with ImgBurn burning at 2x only.

Thank you for the reply!

I manually verified the Windows-burned disc in ImgBurn against the original ISO, and it completed successfully:

Verifying Layer 0... LBA: 0 - 12219391
Verifying Layer 1... LBA: 12219392 - 16002559
Operation Successfully Completed

 

I’ll run another controlled ImgBurn burn at exactly 2x and report the full log. I previously selected 3x on one attempt, but the drive fell back to 2x and that disc still failed at the layer transition. I’ll repeat it deliberately at 2x with the current Vantec enclosure and no other disc software running.

[dbminter]

It does seem that Windows built in burning engine is different that ImgBurn's.  Of course, ImgBurn is just sending standard operational commands to drives.  So, WHY it should make a difference is a bit odd.  However, you can't really argue with results.

 

Of course, there's no sure fire result until you play the entire contents of the Windows burned BD-R DL in a standalone Blu-Ray player.  Some of my 4x tests passed Write and Verify, but they apparently weren't written correctly, causing freezes on playback at certain points.  Reburning those discs at 2x played fine.

[griff7337]

Thanks. I agree the result is strange, but it now looks very consistent.

I also completed another controlled ImgBurn burn at 2x. It failed verification again at the same point:

Verifying Layer 1...
Failed to Read Sectors 12219424 - 12219455
Reason: L-EC Uncorrectable Error

So both 2x and 4x ImgBurn burns fail immediately after the layer change.

The Windows-burned disc:

• completed Windows verification successfully
• then passed a manual ImgBurn verification against the original ISO
• crossed the layer transition with no read errors

I’ll still play the entire Windows-burned disc in a standalone player to rule out playback freezes that verification may not reveal. I have not watched an entire full-length film fully through, so Ill make sure to do that ...

Appreciate the help 👍

[dbminter]

How exactly can one burn an ISO image file created by ImgBurn with the Windows burning engine you used?  It's something I could maybe play around with, too.

[griff7337]

I launch Windows Disc image burner with:

1. Press Win + R.
2. Run: isoburn.exe "C:\path\to\image.iso"

I think you can also right-click the ISO and select 'burn disc image'

I should clarify though that the ISO I burned with Windows was not created by imgburn- It was an existing Blu-ray ISO from another source. Though I did originally create an ISO from a blu ray disc I already had in order to test the drives full dual layer read functionality to make sure it wasnt broken, I did use makemkv and imgburn for that.

[dbminter]

I found isoburn.exe on my Windows partition.  It is apparently a command line driven utility.  I can also try the context menu to see if that works.

 

Does it have settings where you can set the write speed or does it just use the maximum speed allowed by the drive?  And I guess it automatically verifies because the only command line switch I see is /q which apparently opens the isoburn program window.  Which may have settings available there.

 

Anyway, it's something I can play around with later.

[dbminter]

This reminded me of another issue with double layer BD burning.  Some years ago, it was determined that ImgBurn would fail more often than not writing BD-RE DL on the LG WH16NS40, yet when you used Roxio's burning engine, it would succeed all the time.  At least, that's my memory of the situation.  It was odd results back then, too, but I played around with it and it did seem to bear out that it worked with Roxio's burning software but not as well with ImgBurn.

[griff7337]

My isoburner.exe has a selection for the drive and a check box for verification, this is what pops up after run:



I think I can chalk this up to some weird dual layer burning quirk with imgburn- I may try another utility too to see what happens because for certain images Windows rejects the burn if they are extremely close to the full BD-R DL capacity, even though ImgBurn says they technically fit... 

Luckily whatever error I am running into with the disks I burned using imgburn that I saw during verification, doesnt seem to affect playback. This weekend I'll watch one entirely through to double check.

[dbminter]

On 7/16/2026 at 4:05 PM, griff7337 said:

I launch Windows Disc image burner with:

1. Press Win + R.
2. Run: isoburn.exe "C:\path\to\image.iso"

I think you can also right-click the ISO and select 'burn disc image'

I should clarify though that the ISO I burned with Windows was not created by imgburn- It was an existing Blu-ray ISO from another source. Though I did originally create an ISO from a blu ray disc I already had in order to test the drives full dual layer read functionality to make sure it wasnt broken, I did use makemkv and imgburn for that.

 

How do you enable Verify?  This thing only works via the command line.  The option to Burn disc image is not available on my system on Windows 11, even under Show more options.

 

The entire command line is ISOBURN.EXE /Q "D:" "C:\Image.iso" without the quotes around D:.  They are only present here because without the quotes, it becomes 😧 on these forums.

 

Never mind.  I figured it out.  The /Q option opens the window, but automatically starts the burn apparently.  If you just run

ISOBURN.EXE E: "C:\Image.iso"

it opens the main interface where you can select Verify image.