All Activity

Oh, that's not what's technically meant by an enclosure. That's a slim USB burner. An enclosure is a frame you put a drive into yourself and can take out if you wish to put in something else. Also, enclosures are generally 5.25" size drives when using optical disc burners. This is what I meant by the VanTec Gen 2 USB enclosure: https://www.amazon.com/External-Enclosure-Generation-Aluminum-NST-540S3-BK/dp/B09SS74KCN/ref=sr_1_3?s=electronics Unfortunately, slim optical disc burners are generally pretty rotten as writers. I don't use them, preferring half height drives like the LG WH16NS60 and putting them in an enclosure. Unfortunately, you can't really find internal half height optical burners anymore. The only half height burner I know of they still manufacture is the ASUS USB BH-16 model. However, I've not tested that in a while and I don't recall why I returned it to Amazon years ago after initially getting it. Your using a Lenovo might be a problem as it was for myself at the VanTec Gen 1 and OWC enclosures but the VanTec Gen 2 enclosure worked. Your Lenovo might be using a USB controller similar to my own which had a conflict with the USB bridges in the VanTec Gen 1 and OWC USB enclosures but not the VanTec Gen 2 USB enclosure.

Enclosure attached. I have a Lenovo Legion laptop. Legion Pro 5 16ARX8 - Type 82WM

I wouldn't proceed any further along this path, then. My experience is all burns will fail Verify right at the very beginning if you get a WriteIn single retry error. And you are using the VanTec Gen 2 USB enclosure or am I wrong with that? I've also noticed that the Gen 1 does work, apparently, depending on the USB controller in your PC. On my PC, the Gen 1 fails, but someone else I know uses the same setup with the same drive and Gen 1 enclosure without issue. So, they must have a different USB controller as they don't have a Lenovo PC and I do. You don't happen to have a Lenovo PC, do you?

Yes, it basically happens with every burn.

Have you always gotten this error? I 15:47:52 Writing LeadIn... W 15:48:12 Failed to Write Sectors 0 - 31 - Reason: Write Error W 15:48:12 Retrying (1 of 20)... I discovered if you get this error at the start of a BD-R DL burn, it will immediately fail to Verify if it completes burn. I also discovered this only happened on the VanTec Gen 1 and OWC USB enclosures. Which is why I've only had BD-R DL successes with the VanTec Gen 2 USB enclosure.

Thank you for this advice. I have made it further than ever on this. But it seems to have failed verification. Please take a look: I 15:46:40 ImgBurn Version 2.5.8.0 started! I 15:46:40 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 15:46:40 Total Physical Memory: 32,703,516 KiB - Available: 7,365,244 KiB I 15:46:40 Initialising SPTI... I 15:46:40 Searching for SCSI / ATAPI devices... I 15:46:40 -> Drive 1 - Info: HL-DT-ST BD-RE BU40N 1.03 (D:) (USB 2.0) I 15:46:40 Found 1 BD-RE XL! I 15:47:07 Operation Started! I 15:47:07 Source File: C:\Blu-Ray Burning\robbie Williams Volume 1\robbie Williams Volume 1\BDMV\BDMV.iso I 15:47:07 Source File Sectors: 20,542,592 (MODE1/2048) I 15:47:07 Source File Size: 42,071,228,416 bytes I 15:47:07 Source File Volume Set Identifier: 621AC942 I 15:47:07 Source File Application Identifier: tsMuxeR 2.10.1 (git-eb I 15:47:07 Source File Implementation Identifier: tsMuxeR 2ff53c13 I 15:47:07 Source File File System(s): UDF (2.50) I 15:47:07 Destination Device: [0:0:0] HL-DT-ST BD-RE BU40N 1.03 (D:) (USB) I 15:47:07 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000) I 15:47:07 Destination Media Supported Write Speeds: 2x, 4x, 6x I 15:47:07 Destination Media Sectors: 24,438,784 I 15:47:07 Write Mode: BD I 15:47:07 Write Type: DAO I 15:47:07 Write Speed: 4x I 15:47:07 Hardware Defect Management Active: No I 15:47:07 BD-R Verify Not Required: No I 15:47:07 Link Size: Auto I 15:47:07 Lock Volume: Yes I 15:47:07 Test Mode: No I 15:47:07 OPC: Yes I 15:47:07 BURN-Proof: Enabled I 15:47:09 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 15:47:52 Filling Buffer... (80 MiB) I 15:47:52 Writing LeadIn... W 15:48:12 Failed to Write Sectors 0 - 31 - Reason: Write Error W 15:48:12 Retrying (1 of 20)... I 15:48:24 Writing LeadIn... I 15:48:28 Writing Session 1 of 1... (1 Track, LBA: 0 - 20542591) I 15:48:28 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 20542591) I 15:48:28 Writing Layer 0... (LBA: 0 - 12219391) I 16:15:41 Writing Layer 1... (LBA: 12219392 - 20542591) I 16:32:16 Synchronising Cache... W 16:32:22 Potential 'WaitImmediateIO' Deferred Error - (0/3) - Session Fixation Error W 16:32:22 Synchronise Cache Failed! - Reason: Session Fixation Error W 16:32:22 Retrying (1 of 3)... I 16:32:23 Closing Track... I 16:32:24 Finalising Disc... I 16:33:02 Exporting Graph Data... I 16:33:03 Graph Data File: C:\Users\qrp91\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BU40N_1.03_20-JULY-2026_15-47_RITEK-DR3-000_4x.ibg I 16:33:03 Export Successfully Completed! I 16:33:03 Operation Successfully Completed! - Duration: 00:45:55 I 16:33:03 Average Write Rate: 15,645 KiB/s (3.6x) - Maximum Write Rate: 17,866 KiB/s (4.1x) I 16:33:03 Cycling Tray before Verify... W 16:33:52 Waiting for device to become ready... I 16:34:11 Device Ready! E 16:34:11 CompareImageFileLayouts Failed! - Session Count Not Equal (1/0) E 16:34:11 Verify Failed! - Reason: Layouts do not match.

The drive fails at the layer break with this media. If you try to burn a BD-R with movie content (BDMV and CERTIFICATE) you can try this brand new method that fills dummy data before and after the layer break. You must make sure that the data you burn doesn't exceed something in the 45 BG area potentially shinking it with CloneBD to that size. If your ISO is already compliant, mount it with Windows or Virtual Clone Drive. If not you have to shrink it to that size. In your specific case the burn fails 896 MB before the layer break. Therefore I suggest to use 1000 MB before and also 1000 MB after the layer break with dummy data. Here is the guide for it: https://mega.nz/folder/7IR2kZhD#S8_Ld_MXOZFbRZbewdYHOw

I wasted about half of my first stack of BD-R DL's testing them out. The most common issue was failure to Verify at the layer change, although I also got random failures like burning before the layer change in Layer 0 and a random lockup at near completion of a Verify. What I did learn was never to use the VanTec Gen 1 or OWC USB enclosures, e.g use the VanTec Gen 2 USB enclsoure, to burn at 2x, and use the WH16NS60 as opposed to the ASUS BH-16.

I will try that, thank you. After 7 discs that all crashed out early on in their burns, I've just spent the last four hours hoping and praying. BurnAware, after changing the cache to 2048mb, seemingly burnt through an entire disc. Unfortunately, it failed the verification process and does not play in my Xbox One S. Here's the log: Disc #1 of 1 [19:34:10] Preparing compilation [19:34:10] Anti-sleep mode activated [19:34:10] OPC activated [19:34:49] 41.33 GB [19:34:49] Burn process started [23:41:37] Closing track [23:42:59] Burn process completed successfully [23:43:00] Verify process started [23:43:00] Verify process failed Total time: 04:08:47 Average write speed: 0.7x (2938 KB/s) So looks like the drive is capable of writing onto both layers, but yeah sadly not a legible disc. I will try the hardware error fix you outlined above and get back to you

We live in dark times, and the faint light that remains grows dimmer with each passing day. People have lost interest in preserving information, sacrificing it for the convenience of streaming services and cloud storage. For quite some time now, I have watched with dismay as PC cases have stopped being designed to accommodate optical drives. What concerns me even more is that there are now very few Blu-ray burners available. The options are scarce, of poor quality, and expensive. To me, this is a symptom of society's decline. People no longer value information and knowledge the way they once did, and it also represents a loss of freedom. Respected technology brands such as ASUS, LG, Pioneer, and others, which once produced outstanding optical drives and Blu-ray burners, have all but disappeared from the market. What worries me most is this growing indifference, and especially the prospect of losing access to my collection simply because the optical drives needed to read those discs are disappearing. It is both sad and absurd. Yet that seems to be the direction things are heading. Blu-ray always felt like such an established format that I never imagined its future could be called into question. I should also add that I do not trust hard drives, SSDs, USB flash drives, or memory cards to the same extent. If there is a storage medium that has proven to be truly durable, it is the optical disc—especially high-quality Blu-ray discs. Sadly, they are now on the verge of extinction because almost nobody values them anymore.

You could try using the Hardware error correction and formatting with spare areas if you wish. See this thread here for more details:

As you pointed out, it's probably an incompatibility in the firmware with your LG burner and those Ritek DID's. The only thing I can recommend at this point is that you try Verbatim DataLife Plus BD-R DL. However, they're about twice the price of the Riteks, but if they're the only thing that work in that LG, at least it's an option. I've never used that particular LG BD burner, just the WH14NS40, WH16NS40, and the WH16NS60. The 16 NS40 is not recommended unless you don't mind the fact that it can't properly read CD's in ImgBurn. And, well, both the 16 NS40 and NS60 aren't manufactured anymore. In fact, the only BD drive I know that is still manufactured by a major company is ASUS's USB BH-16 model. I've tried the internal BH-16, but ImgBurn didn't produce regular positive results with that in my testing, even at 2x.

Tried Burnaware. Actually did a pretty good job writing the first half of the disc, but then crashed when it went to the next layer. At my wits end.

That error code is Windows's infamous "I don't know what the Hell went wrong" return code. It's "Unspecified Error."

Tried the isoburn.exe route and it spat the disc out. Gave me error code 0x80004005. Tried it a second time and it ran really quickly considering its a 40+gb ISO, then jumped to finalizing disc. Then it threw error up again saying: 'The disc image didn't burn successfully because an error occurred. Same error. 0x80004005 I'm not sure what the matter is with this drive. It can rip blu-rays but can't seem to write. It can't even erase a rewriteable from a company called BRTech.

You might want to invest in trying one more BD-R DL test. It involves using Windows's built in disc image burner. It may work where ImgBurn keeps failing. See this thread:

waoo, I know that

Having a very sad start to the weekend. Not managing to write an ISO to a 50gb BD-R. They are RITEK-DR3-000 BD-R DL 50GB (Inkjet Printable, 1-6x rated) Drive: HL-DT-ST BD-RE BU40N Firmwares Tested: 1.03 (stock), 1.00 (downgraded) Software: ImgBurn 2.5.8.0 Settings Tested: Write Speeds: 1x (rejected), 2x, 4x, 6x OPC: On/Off BURN-Proof: Enabled Lock Volume: On/Off Link Size: 0 (default) Write Type: DAO/SAO Best Result: Firmware 1.00 with OPC enabled at 2x reached 54% before layer break failure. Conclusion: RITEK-DR3-000 is incompatible with LG BU40N at firmware level. Drive cannot calculate correct sector addressing for layer transition on this media. Anyone have any advice for me?

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.

Try this with dummy data at the layer break. Devloped by teaching-droid. I was the beta tester und found some bugs. Now it works just fine and stable. https://mega.nz/folder/7IR2kZhD#S8_Ld_MXOZFbRZbewdYHOw

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.

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.

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.

I launch Windows Disc image burner with: Press Win + R. 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 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.