<?xml version="1.0"?>
<rss version="2.0"><channel><title>ImgBurn Support Latest Topics</title><link>https://forum.imgburn.com/forum/6-imgburn-support/</link><description>ImgBurn Support Latest Topics</description><language>en</language><item><title>Build does not work right when trying to replicate 99-title DVD</title><link>https://forum.imgburn.com/topic/28224-build-does-not-work-right-when-trying-to-replicate-99-title-dvd/</link><description><![CDATA[<p>
	Ugh, Here I am again. For some reason, whenever I try to make a 16.3GB VIDEO_TS into a 8.5GB ISO, it doesn't work right. If I have "Preserve Full Path Names" checked, it can save the contents space but it sets the contents type to "Data" instead of "DVD-Video", but if I don't, it doesn't save space and gives me a warning and sets it to Blu-Ray type instead of "DVD-Video". This is very weird, because I have an ISO of Baby Neptune 2009, and it is bigger than 8.5GB in total, and it does play as a DVD-Video ISO. However, the ISO I am making does not play right for some reason when tested in VLC. I do have the "Optimise Duplicate Files" option checked, but it doesn't work for DVD-Video. Also the layer-break pop up does not show for some reason.
</p>

<p>
	BTW, yes I am trying to replicate the 99-title protection seen on Disney DVDs from late-2008 until mid-2012 on my ISO.
</p>

<p>
	Would it be possible to make a version of ImgBurn that can build a DVD-ISO with duplicate/fake titles from an HDD/SDD/that has 99-titles?
</p>
]]></description><guid isPermaLink="false">28224</guid><pubDate>Sun, 15 Mar 2026 20:49:52 +0000</pubDate></item><item><title>DVD ejected mid-verifying session</title><link>https://forum.imgburn.com/topic/28230-dvd-ejected-mid-verifying-session/</link><description><![CDATA[<p>
	So I was burning an ISO file onto a DVD-RW, and at the end when it completed it wanted to start verifying but then the DVD got ejected by the drive. After closing the disk drive again, I got some errors in ImgBurn. I checked the disk itself in explorer and it did copy every file but i'm wondering if something did go wrong?
</p>
<p>
<a class="ipsAttachLink" href="https://forum.imgburn.com/applications/core/interface/file/attachment.php?id=13130&amp;key=2971a164bd8df2a514e926c2eaf1df8b" data-fileExt='log' data-fileid='13130' data-filekey='2971a164bd8df2a514e926c2eaf1df8b'>ImgBurn.log</a></p>]]></description><guid isPermaLink="false">28230</guid><pubDate>Fri, 17 Apr 2026 13:03:00 +0000</pubDate></item><item><title>Issues with audio when burning a CD on IMG-burn</title><link>https://forum.imgburn.com/topic/28231-issues-with-audio-when-burning-a-cd-on-img-burn/</link><description><![CDATA[<p>
	I've been trying to burn a CD, but 2 of the audio files (FLAC) come out tinny and low quality. The rest of the files (17 total) do not have this issue. I have even tried converting the two problematic files to .wav in hopes it might do something, but it ran into the same issue. <br />
	<br />
	I am using Verbatim CD-R's and a samsung SE-208 dvd writer
</p>
]]></description><guid isPermaLink="false">28231</guid><pubDate>Fri, 17 Apr 2026 23:44:31 +0000</pubDate></item><item><title>Burning ISO hangs at 11% Erasing Disc - Drive activity light not flashing</title><link>https://forum.imgburn.com/topic/28229-burning-iso-hangs-at-11-erasing-disc-drive-activity-light-not-flashing/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I have just setup a new desktop computer.
</p>

<p>
	It is running Windows 11 Version 25H2 Build 26200.8246 and ImgBurn 2.5.8.0.
</p>

<p>
	The drive has the latest version of the firmware installed.
</p>

<p>
	I was trying to burn an ISO to a Ritek DVD+RW and ImBurn said the disc needed to be formatted first.
</p>

<p>
	The Erasing Disc then starts and the light on the Blu-ray Combo drive starts flashing but after some seconds stops flashing.
</p>

<p>
	The progress starts counting up from 0% and reaches 11% but then stops there.
</p>

<p>
	I left it running for over 30 minutes but the progress remainedl at 11%.
</p>

<p>
	All this time the light on the drive does not flash at all.
</p>

<p>
	I tried running the burn several times and also tried running ImgBurn in compatibility mode for Windows 8.
</p>

<p>
	I also tried another Ritek DVD+RW disc and a Philips DVD+RW but the same problem occurred.
</p>

<p>
	However, I was successful burning with a erase burning the ISO with a Ritek DVD-RW disc so the problem seems to be isolated to DVD+RW discs.
</p>

<p>
	I can successfully burn the ISO using AShampoo Burning Studio Free so the problem is confined to ImgBurn.
</p>

<p>
	A Google search of the problem suggests to Disable ImgBurn setting "Perform OPC before write" but I checked it and it is not enabled.
</p>

<p>
	The saved log is attached.
</p>

<p>
	Regards,
</p>

<p>
	fbagnato
</p>
<p>
<a class="ipsAttachLink" href="https://forum.imgburn.com/applications/core/interface/file/attachment.php?id=13129&amp;key=becd31ceef269bbdc6f8c0fe12bb6c11" data-fileExt='log' data-fileid='13129' data-filekey='becd31ceef269bbdc6f8c0fe12bb6c11'>ImgBurn.log</a></p>]]></description><guid isPermaLink="false">28229</guid><pubDate>Thu, 16 Apr 2026 08:07:45 +0000</pubDate></item><item><title>how can i burn a data  compatible with windows and macos?</title><link>https://forum.imgburn.com/topic/28227-how-can-i-burn-a-data-compatible-with-windows-and-macos/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	I remember ,once i burned a dvd and i found an option to burn compatible with windows and macos file system
</p>

<p>
	may i know if there is an option to burn a dvd/cd compatible with both ?
</p>

<p>
	and where is it?
</p>

<p>
	ps: just because once imgburn asks me compatible with macos , i have re-installed on a new computer windows 11
</p>

<p>
	thanks
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28227</guid><pubDate>Mon, 30 Mar 2026 15:03:31 +0000</pubDate></item><item><title>Problem with BD-R DL Discs...</title><link>https://forum.imgburn.com/topic/28228-problem-with-bd-r-dl-discs/</link><description><![CDATA[<p>
	Hello,<br />
	<br />
	I was having a problem trying to burn some back up Blu-rays for while I travelled. I haven't had any problems burning for the past two years or so and I have recently got a 25 pack of Kodak BD-R DL discs and four in a row were just coasters. Somewhere along the lines they failed to burn. So, I am a little confused as to why. I use DVDFAB and have ImgBurn 2.5.8.0 set to do the burning. The first three were just DVDFab using the file. And then I made an ISO file to see if burning that would fix the issue and alas, I am here.<br />
	<br />
	My burner, Pioneer BDXL BDR-XD08 is about a little over a year old. I have been burning regular single layer BD-R and dual layer BD-R discs until now. Whenever I inserted one of these blank discs, it gave a disc name of "CMCMAG-DI6-000" which I did a Google search and it was nothing but trashing the type of disc it is. <br />
	 
</p>

<p><a href="https://forum.imgburn.com/uploads/monthly_2026_04/Screenshot2026-04-01073719.jpg.6e545e6347ebb8d2f9febfae7cab60c4.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13128" src="https://forum.imgburn.com/uploads/monthly_2026_04/Screenshot2026-04-01073719.jpg.6e545e6347ebb8d2f9febfae7cab60c4.jpg" data-ratio="70.83" width="408" class="ipsImage ipsImage_thumbnailed" alt="Screenshot 2026-04-01 073719.jpg"></a></p><p>
<a class="ipsAttachLink" href="https://forum.imgburn.com/applications/core/interface/file/attachment.php?id=13127&amp;key=590ff1656da8c337f923d6cf8a26ff06" data-fileExt='log' data-fileid='13127' data-filekey='590ff1656da8c337f923d6cf8a26ff06'>ImgBurn.log</a></p>]]></description><guid isPermaLink="false">28228</guid><pubDate>Wed, 01 Apr 2026 11:53:41 +0000</pubDate></item><item><title>Fails to write to second Blu-ray layer</title><link>https://forum.imgburn.com/topic/28226-fails-to-write-to-second-blu-ray-layer/</link><description><![CDATA[<p>
	Hello,<br />
	I have a stack of Verbatim BD-R DLs which I bought a couple years ago and have used on and off since then, without any issues.  However, beginning a couple weeks ago, any attempts to burn to these discs leads to an error like the following:
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			I 05:20:21 ImgBurn Version 2.5.8.0 started!<br />
			I 05:20:21 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)<br />
			I 05:20:21 Total Physical Memory: 8,243,660 KiB  -  Available: 5,133,244 KiB<br />
			I 05:20:22 Initialising SPTI...<br />
			I 05:20:22 Searching for SCSI / ATAPI devices...<br />
			I 05:20:22 -&gt; Drive 1 - Info: BUFFALO Optical Drive 2.00 (D:) (USB 2.0)<br />
			I 05:20:22 Found 1 BD-RE XL!<br />
			I 05:20:59 Operation Started!<br />
			I 05:20:59 Building Image Tree...<br />
			I 05:20:59 Calculating Totals...<br />
			I 05:20:59 Preparing Image...<br />
			I 05:21:00 Contents: 9 Files, 15 Folders<br />
			I 05:21:00 Content Type: BD Video<br />
			I 05:21:00 Data Type: MODE1/2048<br />
			I 05:21:00 File System(s): UDF (2.50)<br />
			I 05:21:00 Volume Label: [Not Configured]<br />
			I 05:21:00 Size: 30,478,893,196 bytes<br />
			I 05:21:00 Sectors: 14,882,279<br />
			I 05:21:00 Image Size: 30,479,941,632 bytes<br />
			I 05:21:00 Image Sectors: 14,882,784<br />
			I 05:21:00 Operation Successfully Completed! - Duration: 00:00:00<br />
			I 05:21:09 Operation Started!<br />
			I 05:21:09 Building Image Tree...<br />
			I 05:21:12 Calculating Totals...<br />
			I 05:21:12 Preparing Image...<br />
			I 05:21:12 Contents: 9 Files, 15 Folders<br />
			I 05:21:12 Content Type: BD Video<br />
			I 05:21:12 Data Type: MODE1/2048<br />
			I 05:21:12 File System(s): UDF (2.50)<br />
			I 05:21:12 Volume Label: Test<br />
			I 05:21:12 Size: 30,478,893,196 bytes<br />
			I 05:21:12 Sectors: 14,882,279<br />
			I 05:21:12 Image Size: 30,479,941,632 bytes<br />
			I 05:21:12 Image Sectors: 14,882,784<br />
			I 05:21:13 Operation Successfully Completed! - Duration: 00:00:03<br />
			I 05:21:13 Operation Started!<br />
			I 05:21:13 Source File: -==/\/[BUILD IMAGE]\/\==-<br />
			I 05:21:13 Source File Sectors: 14,882,784 (MODE1/2048)<br />
			I 05:21:13 Source File Size: 30,479,941,632 bytes<br />
			I 05:21:13 Source File Volume Identifier: Test<br />
			I 05:21:13 Source File Volume Set Identifier: 5C722AA400E31767<br />
			I 05:21:13 Source File Application Identifier: ImgBurn v2.5.8.0<br />
			I 05:21:13 Source File Implementation Identifier: ImgBurn<br />
			I 05:21:13 Source File File System(s): UDF (2.50)<br />
			I 05:21:13 Destination Device: [0:0:0] BUFFALO Optical Drive 2.00 (D:) (USB)<br />
			I 05:21:13 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000)<br />
			I 05:21:13 Destination Media Supported Write Speeds: 2x, 4x, 6x<br />
			I 05:21:13 Destination Media Sectors: 24,438,784<br />
			I 05:21:13 Write Mode: BD<br />
			I 05:21:13 Write Type: DAO<br />
			I 05:21:13 Write Speed: 6x<br />
			I 05:21:13 Hardware Defect Management Active: No<br />
			I 05:21:13 BD-R Verify Not Required: Yes<br />
			I 05:21:13 Link Size: Auto<br />
			I 05:21:13 Lock Volume: Yes<br />
			I 05:21:13 Test Mode: No<br />
			I 05:21:13 OPC: No<br />
			I 05:21:13 BURN-Proof: Enabled<br />
			I 05:21:13 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x)<br />
			I 05:22:00 Filling Buffer... (80 MiB)<br />
			I 05:22:03 Writing LeadIn...<br />
			I 05:22:04 Writing Session 1 of 1... (1 Track, LBA: 0 - 14882783)<br />
			I 05:22:04 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 14882783)<br />
			I 05:22:04 Writing Layer 0... (LBA: 0 - 12219391)<br />
			W 05:31:12 Waiting for buffers to recover... (LBA: 3853792)<br />
			W 05:31:22 Waiting for hard disk activity to reach threshold level...<br />
			I 05:31:33 Writing Sectors...<br />
			I 05:44:21 Writing Layer 1... (LBA: 12219392 - 14882783)<br />
			W 05:44:28 Failed to Write Sectors 12245248 - 12245279 - Reason: Write Error<br />
			W 05:44:28 Retrying (1 of 20)...<br />
			W 05:44:29 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:29 Retrying (2 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (3 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (4 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (5 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (6 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (7 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (8 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (9 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (10 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (11 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (12 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (13 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (14 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (15 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (16 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (17 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (18 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (19 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:44:30 Retrying (20 of 20)...<br />
			W 05:44:30 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:45:21 Retrying (21)...<br />
			W 05:45:21 Retry Failed - Reason: Invalid Address For Write<br />
			W 05:45:21 Retrying (22)...<br />
			W 05:45:21 Retry Failed - Reason: Invalid Address For Write<br />
			E 05:47:41 Failed to Write Sectors 12245248 - 12245279 - Reason: Write Error<br />
			E 05:47:41 Next Writable Address: 3853792<br />
			 
		</p>
	</div>
</blockquote>

<p>
	This always happens when it is beginning to write to the second layer.  I have used two separate drives and the errors occur on both.  Afterwards when I turn the failed disc over, I see small bubbles have appeared where it has attempted to write to the second layer:
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="13126" data-ratio="86.00" style="width:100px;height:auto;" width="765" alt="image.png.92a5af676d4e1daa15843f2c92df5b22.png" src="https://forum.imgburn.com/uploads/monthly_2026_03/image.png.92a5af676d4e1daa15843f2c92df5b22.png" />
</p>

<p>
	The obvious conclusion would be that the discs are bad, but I have not heard of the first dozen discs in a stack being fine and the others being unusable.  I've also never seen this "bubble" issue before.  Before I spend another $100 on new double-layer Blu-rays I'd like to know if bad discs definitely are the culprit, and it is not something wrong with the way my computer is trying to author the disc.  Thank you.
</p>
]]></description><guid isPermaLink="false">28226</guid><pubDate>Wed, 18 Mar 2026 21:17:01 +0000</pubDate></item><item><title>Resuming a failed burn?</title><link>https://forum.imgburn.com/topic/28222-resuming-a-failed-burn/</link><description><![CDATA[<p>
	Please forgive me if this is something obvious, I looked and didn't find anything and I'm a complete novice when it comes to burning discs. 
</p>

<p>
	Last night I was running a burn while I slept and woke up to discover it got interrupted partway through thanks to my computer having dismounted every connected USB device; this is not an unusual problem for me, everything just gets spontaneously disconnected and promptly reconnects, real obnoxious in the moment but doesn't cause any real problems. ImgBurn gave me the option to resume, but it couldn't see the drive anymore. My computer had successfully reconnected it but ImgBurn didn't see it, so I figured I just have to close and reopen the program for it to find it again, which it did, but at that point anything relating to that last burn operation was gone. 
</p>

<p>
	Now I have a disc with an incomplete burn, the ISO file, and ImgBurn which knows the burn was incomplete. Attached is the log from the <em>second</em> time I opened the program, since I didn't think to save it the first time, and the results of the verification operation on the incomplete disc. Is there a way I can continue it from where it stopped? What happens if I start burning the ISO again? The disc cannot be erased; is it lost? 
</p>

<p>
	Any advice helps. Thanks. 
</p>
<p>
<a class="ipsAttachLink" href="https://forum.imgburn.com/applications/core/interface/file/attachment.php?id=13123&amp;key=1560d90edf7da8f4c566de31f5287be1" data-fileExt='log' data-fileid='13123' data-filekey='1560d90edf7da8f4c566de31f5287be1'>ImgBurn.log</a></p>]]></description><guid isPermaLink="false">28222</guid><pubDate>Tue, 10 Mar 2026 01:28:12 +0000</pubDate></item><item><title>ImgBurn BD-R Defect Management</title><link>https://forum.imgburn.com/topic/19688-imgburn-bd-r-defect-management/</link><description><![CDATA[
<p>I have a ASUS BW-12B1ST Burner. </p>
<p> </p>
<p>I've got two coasters while burning a data disk onto BD-R discs using ImgBurn 2.5.6.0.  They are Newegg "low-cost" Optical Quantum discs.  While using ASUS's CyberLink Power2Go, I get perfect burns.</p>
<p> </p>
<p>I like ImgBurn's interface much better. Only thing different is Power2Go has a Defect Management checkbox for BD-R discs.  I'm assuming a small portion of disc is reserved on the BD-R to re-locate "bad" sectors during burn process.</p>
<p> </p>
<p>In the old days, DVD+/-R/RW's did not have this ability, I realize, only DVD-RAM.  </p>
<p> </p>
<p>But BD-R &amp; BD-RE is suppose to have this capability, because of its increase density and likelihood for defects on even new discs.  What are the steps to enable Defect Management in ImgBurn so as to put my Burner into "Defect Management" Mode for BD-R discs?</p>
<p> </p>
<p>Thanks!</p>
]]></description><guid isPermaLink="false">19688</guid><pubDate>Mon, 05 Mar 2012 21:18:31 +0000</pubDate></item><item><title>Pioneer BDR-S13U-X (fw 1.03) Randomly Hangs PC When Burning Discs</title><link>https://forum.imgburn.com/topic/28219-pioneer-bdr-s13u-x-fw-103-randomly-hangs-pc-when-burning-discs/</link><description><![CDATA[<p>
	Essentially what happens is, when the disc is done burning (DVD or BD, I haven't burned many CDs), when it does the "Cycle Tray before Verify" step, a good 50% of the time, instead of progressing normally, the drive gets locked in some sort of null state, where it never reports the disc being re-inserted. It hangs in such a way that any software that dares try to interact with the optical drive hangs or crashes. Only way to close ImgBurn in this state is through Task Manager, and if I try to open the drive in File Explorer, it crashes the entire explorer.exe process and the start menu disappears for a few minutes. Swapping out the disc with another or leaving the drive empty does not change the situation. The only fix is a full reboot - but even that gets interrupted - whether I Restart or Shut Down, the PC gets to the stage where it's no longer displaying anything and the monitor goes to sleep, but the PC continues to hang and never fully shuts down/reboots until I force it to with the restart or power buttons. If I take no direct action, the computer will simply never turn off, because the optical drive is preventing it from doing so.<br />
	<br />
	For context, this issue was present on Windows 10 and still on Windows 11, my machine has an Asus PRIME B350-M motherboard, Ryzen 7 5700X CPU, 16GB of RAM, and an RTX 3060 (though the issue was also present when I ran an ancient GTX 980). I do have software like MakeMKV and XReveal installed, though I never let these programs auto-run and the issue still happens on a fresh boot where they have never been opened. I'm not sure if this is an issue with the motherboard - I keep the BIOS up to date and it's never fixed the problem - or the drive itself - I'm never upgrading the firmware if that's the only thing that would fix this bug, because it's a holy grail drive one of the last that came stock from the factory with the LibreDrive-compatible 1.03 firmware. It works great for ripping all manner of discs, and when it does burn and verify the results are consistent and very good, but this is a pretty major annoyance, and I was wondering if anyone else had dealt with it or knew of any fixes.
</p>
]]></description><guid isPermaLink="false">28219</guid><pubDate>Sun, 04 Jan 2026 07:22:27 +0000</pubDate></item><item><title>Chapters</title><link>https://forum.imgburn.com/topic/28206-chapters/</link><description><![CDATA[<p>
	Howdy! If this is the wrong section of the forum, I apologize--just let me know.
</p>

<p>
	I've been using imgburn for years for my BDs and have never had this problem.
</p>

<p>
	I burned two movie titles (folders) to a BD for the first time (I had only done single-title discs before this), and the chapters are not working for either movie. I'm sure the chapters are part of the files because I had previously burned one by itself and was able to use them.
</p>

<p>
	Does anyone know why this may be?
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">28206</guid><pubDate>Mon, 18 Aug 2025 21:58:28 +0000</pubDate></item><item><title>Is this burn okay ? Graph inside</title><link>https://forum.imgburn.com/topic/28215-is-this-burn-okay-graph-inside/</link><description><![CDATA[<p>
	Just fitted replacement equipment in my Bravo SE as it wasn't working before, just checking if you think this graph is okay for a DVD burn at 16x and verify (via USB 2). Thanks 
</p>

<p><a href="https://forum.imgburn.com/uploads/monthly_2025_11/PIONEER_BD-RW_BDR-206D_9.06_10-NOVEMBER-2025_03-39_TTH02_MAX.png.adb50b3d4bb83f9bebf94a84f994b685.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13120" src="https://forum.imgburn.com/uploads/monthly_2025_11/PIONEER_BD-RW_BDR-206D_9.06_10-NOVEMBER-2025_03-39_TTH02_MAX.png.adb50b3d4bb83f9bebf94a84f994b685.png" data-ratio="90.3" width="711" class="ipsImage ipsImage_thumbnailed" alt="PIONEER_BD-RW_BDR-206D_9.06_10-NOVEMBER-2025_03-39_TTH02_MAX.png"></a></p>]]></description><guid isPermaLink="false">28215</guid><pubDate>Mon, 10 Nov 2025 04:05:32 +0000</pubDate></item><item><title>unexpected network error</title><link>https://forum.imgburn.com/topic/28216-unexpected-network-error/</link><description><![CDATA[<p>
	There's a first time or everything and this one message I've never encountered before.
</p>

<p>
	My setup is as follows: main PC is Win10 pro, network server is Ubuntu 20 with a bunch of attached PCs, android phones and tablets, and a Unifi network. 
</p>

<p>
	In the process of simultaneously backing up two separate home network folders onto BD-R DLs using two <span>LG WH16NS40 </span>drives this message popped up during verification. At the same time. I figured the network dropped off somehow and sure enough, Windows Explorer had lost connection. I use Webmin for server management and reconnected immediately but ImbGurn failed to resume verification after repeatedly clicking the Retry button. Explorer also reconnected.
</p>

<p>
	Strangely no log for the session in question for the entire day. The most recent log was from 2025-11-22, last Saturday.
</p>

<p>
	I will verify the backups against ISOs but my main question is why didn't ImgBurn resume verification? If the network did indeed drop - and I'm not sure it actually did drop - shouldn't ImgBurn rseume the job? Or am I missing something?
</p>

<p>
	BD-R DLs are sensitive things. I use them quite a bit and a loss of 10% is not unusual but a bad disc will usually show up during the write portion. If it's during the verify it'll be a obvious read error. This error wasn't the data or the disc, it was about a broken transfer from data to disc. The LS40s don't have a great reputation but mine have lasted 5+ years under production level use, reading/writing several times per day.
</p>

<p>
	I'd appreciate some advice on this, especially on a method of checking ImgBurn's connection to the network without interrupting the job at hand. Verifying against an ISO is OK but it's after the fact. It would also be great to verify a disc against files, not just an ISO.
</p>
]]></description><guid isPermaLink="false">28216</guid><pubDate>Mon, 01 Dec 2025 21:41:37 +0000</pubDate></item><item><title>Disc says it burned successfully, but when reinserted, it's blank again</title><link>https://forum.imgburn.com/topic/28212-disc-says-it-burned-successfully-but-when-reinserted-its-blank-again/</link><description><![CDATA[<p>
	For some reason, sometimes whenever I finish a burn, it fake completes, as when I reinserted the exact disc in my Laptop, it shows as blank again. How do I fix this?
</p>
]]></description><guid isPermaLink="false">28212</guid><pubDate>Sat, 25 Oct 2025 22:23:46 +0000</pubDate></item><item><title>IMGBurn stopped working with my Primera Bravo SE</title><link>https://forum.imgburn.com/topic/28214-imgburn-stopped-working-with-my-primera-bravo-se/</link><description><![CDATA[<p>
	This is not unique to IMGBurn, when I use the PTPublisher software that comes with the machine as soon as a disc is inserted and tried to write to, in that software it also comes up with an error saying it suddenly can't find the robot. In IMGBurn it pops up a error message, it says the below as soon as it tries to write to a disc. What might be going on here ? What is likely at fault ? It was working fine last week, I don't think I made any changes myself, unless a Windows update did something. I can still use IMGBurn to eject the disc, so it is still making communication. 
</p>

<p>
	<br />
	I 05:59:35 ImgBurn Version 2.5.8.0 started!<br />
	I 05:59:35 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)<br />
	I 05:59:35 Total Physical Memory: 67,023,860 KiB  -  Available: 31,387,532 KiB<br />
	I 05:59:35 Initialising PTRobot...<br />
	I 05:59:35 PT_SDK Version 1.6.2.0<br />
	I 05:59:35 Initialising SPTI...<br />
	I 05:59:35 Searching for Auto Loader devices...<br />
	I 05:59:37 -&gt; Auto Loader 1 - Info: Disc Publisher SE 1.24 08/05/2008<br />
	I 05:59:37 Found 1 Auto Loader!<br />
	I 05:59:37 Searching for SCSI / ATAPI devices...<br />
	I 05:59:37 -&gt; Drive 1 - Info: PIONEER BD-RW   BDR-X12 1.03-ID56 (K:) (USB 2.0)<br />
	I 05:59:37 -&gt; Drive 2 - Info: PIONEER BD-RW   BDR-206D 9.06-ID75 (J:) (USB 2.0)<br />
	I 05:59:37 Found 1 BD-RE and 1 BD-RE XL!<br />
	E 06:00:44 CreateFile Failed! - Device: '\\?\usbstor#cdrom&amp;ven_pioneer&amp;prod_bd-rw___bdr-206d&amp;rev_9.06#09ad00083851&amp;0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'<br />
	E 06:00:44 Reason: The system cannot find the file specified.<br />
	E 06:00:48 CreateFile Failed! - Device: '\\?\usbstor#cdrom&amp;ven_pioneer&amp;prod_bd-rw___bdr-206d&amp;rev_9.06#09ad00083851&amp;0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'<br />
	E 06:00:48 Reason: The system cannot find the file specified.<br />
	I 06:01:15 Close Request Acknowledged<br />
	I 06:01:15 Closing Down...<br />
	I 06:01:15 Shutting down SPTI...<br />
	I 06:01:15 ImgBurn closed!
</p>
]]></description><guid isPermaLink="false">28214</guid><pubDate>Wed, 05 Nov 2025 06:05:12 +0000</pubDate></item><item><title>Build mode Destination previous file output name not remembered</title><link>https://forum.imgburn.com/topic/28210-build-mode-destination-previous-file-output-name-not-remembered/</link><description><![CDATA[<p>
	I'm having to reinstall everything on my PC and I've got an issue with ImgBurn.  I imported all of my saved settings from a REG file, but Build mode did not auto populate my old previously existing Destination file location and name.  So, I created a new image file in Build mode with the desired folder location and file name.  However, upon closing and opening ImgBurn again, the application now wants me to enter the file name and location on each Build operation.
</p>

<p>
	 
</p>

<p>
	This had never happened to me before in at least 10 years.  Importing the .REG file always seemed to work.  And shouldn't changing the Destination path and name have been repopulated on next open of ImgBurn?
</p>

<p>
	 
</p>

<p>
	Is there a setting I missed before?
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">28210</guid><pubDate>Sun, 19 Oct 2025 13:45:47 +0000</pubDate></item><item><title>hidden files</title><link>https://forum.imgburn.com/topic/28209-hidden-files/</link><description><![CDATA[<p>
	I was creating an image from a folder  and it did not include hidden / system files ---- where is the option to include all files 
</p>
]]></description><guid isPermaLink="false">28209</guid><pubDate>Mon, 22 Sep 2025 15:44:20 +0000</pubDate></item><item><title>Any Way I Can Handle Problem Where My USB Hard Drive "Unmounts" Itself Causing Imgburn to Abort</title><link>https://forum.imgburn.com/topic/28207-any-way-i-can-handle-problem-where-my-usb-hard-drive-unmounts-itself-causing-imgburn-to-abort/</link><description><![CDATA[<p>
	I'm using Imgburn to copy files from USB hard drives to BD-R Bluray discs.
</p>

<p>
	Sometimes the USB hard drives are having problems where they stop being "ready" and unmount themselves so that they no longer even appear in Windows Explorer while I'm copying files from them to Bluray disc using Imgburn.
</p>

<p>
	Imgburn halts and displays an error message saying something to the effect that the hard drive is not ready. It is not saying the Bluray destination drive is not ready, just the hard drive being used as the source is not ready.
</p>

<p>
	I tried unplugging the USB hard drive cable and then plugging it back in and the drive once again appeared in Windows Explorer. I even copied the file from the hard drive that was being copied when Imgburn aborted to another hard drive as a test that the hard drive was really once again ready and working and that copy completed with no errors so I know that source file was now once again readable.
</p>

<p>
	What I then wanted to do was get Imgburn to resume where it left off and continue copying files from the now-ready-again source hard drive, but Imgburn would not do that even when I clicked on the "try again" button (it just kept saying hard drive not ready even though it was clearly now ready again) and I could not find a way to get Imgburn to resume from where it left off. Instead I had to throw out the BD-R disc I was using and start all over again.
</p>

<p>
	Is there a way to get Imgburn to resume where it left off once I get a disappeared hard drive to re-appear again?
</p>

<p>
	I haven't included any log files here because I really don't think they will add anything I haven't already pointed out that is relevant, but if you ask, I will add the log file.
</p>
]]></description><guid isPermaLink="false">28207</guid><pubDate>Thu, 04 Sep 2025 00:34:51 +0000</pubDate></item><item><title>Is it possible to save .cue sheet without reading entire cd?</title><link>https://forum.imgburn.com/topic/28208-is-it-possible-to-save-cue-sheet-without-reading-entire-cd/</link><description><![CDATA[<p>
	Hi. I am trying to make backups of my audio CD collection and for the most part I use EAC for it's accurate rip feature but I prefer the neater .cue sheets and .cdt files made by imgburn.  Is it possible to save .cue sheet (and .cdt) without reading entire cd? Seems like there should be an option for that in "View Media Information" dialog or somewhere else.  Currently it seems these files are only created after the entire read is complete or am i not looking in the right place?
</p>
]]></description><guid isPermaLink="false">28208</guid><pubDate>Fri, 05 Sep 2025 18:15:21 +0000</pubDate></item><item><title>Is the media creation date stored in the "Volume Set Identifier"? I want to know the burn dates of my mastered BD-R media</title><link>https://forum.imgburn.com/topic/28205-is-the-media-creation-date-stored-in-the-volume-set-identifier-i-want-to-know-the-burn-dates-of-my-mastered-bd-r-media/</link><description><![CDATA[<p>
	I'd like to know if the media creation date is stored in the "Volume Set Identifier" by chance and if so, is it a date and time, just a date, and how many characters do I need to convert it to an actual operating system date and time?
</p>

<p>
	I know the log file stores enough data to possibly get it from there but let's pretend that got deleted by accident or corrupted. And I wanna get it from the media itself. Is this possible?
</p>
]]></description><guid isPermaLink="false">28205</guid><pubDate>Sat, 09 Aug 2025 18:58:25 +0000</pubDate></item><item><title>Help with Write Modes</title><link>https://forum.imgburn.com/topic/19436-help-with-write-modes/</link><description><![CDATA[
<p>Hi,</p>
<p> </p>
<p>Could someone explain to me about the write modes (DAO/DiscAtOnce, TAO/TrackAtOnce, SAO/???), what each mode do, the pro and cons, and when to use them.</p>
<p> </p>
<p>Before IMGBurn, I've used Nero and UltraISO. Nero seems to only allow TAO on CD, for DVD there's only DAO. UltraISO seems to permit both DAO and TAO on CD and DVD. </p>
<p> </p>
<p>I usually go with TAO if available, with the assumption that writing is done a track at a time hence more "meticulous" writing and more assurance of burn quality. Am I right about this? </p>
<p> </p>
<p>I want to be sure once and for all about the write modes, and not just guessing as I am now.</p>
<p> </p>
<p>Thanks very much</p>
]]></description><guid isPermaLink="false">19436</guid><pubDate>Mon, 16 Jan 2012 09:13:32 +0000</pubDate></item><item><title>BDR-DL Verbatim with Pioneer BDR-TD05</title><link>https://forum.imgburn.com/topic/27613-bdr-dl-verbatim-with-pioneer-bdr-td05/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I want to burn a blu-ray iso on a BD-R DL
</p>

<p>
	My burner is a Pioneer BDR-TD05 1.02 and I use VERBAT-IMf-000<br />
	My burner is connected to my computer with SATA to USB converter.
</p>

<p>
	I have tried to burn at 2x and 1x but it fails.
</p>

<p>
	How can I know if the VERBAT-IMf-000 are compatible with my burner?
</p>

<p>
	Thank you
</p>
]]></description><guid isPermaLink="false">27613</guid><pubDate>Sun, 22 Jun 2025 11:24:25 +0000</pubDate></item><item><title>I/O Error with FX interactive games when trying to dump them.</title><link>https://forum.imgburn.com/topic/27624-io-error-with-fx-interactive-games-when-trying-to-dump-them/</link><description><![CDATA[<p>
	Hello there guys, i recently have been buying some games from fx-interactive, and when trying to dump some games, like submarine titans, it gives me a I/O Error, i can't even copy the content from the cd to a folder.
</p>

<p>
	I already used alcohol 95 and 52%, none of them work too, but works with other cd's.
</p>

<p>
	Any idea?
</p>

<p>
	Below, you can see my screenshots showing the problem i got and the log.
</p>

<p>
	 
</p>

<p>
	Thanks.
</p>

<p>
	<a class="ipsAttachLink" data-fileid="13109" href="https://forum.imgburn.com/applications/core/interface/file/attachment.php?id=13109&amp;key=66025dc883fade18092a795c7191402c" data-fileext="log" rel="">ImgBurn.log</a>
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="13108" data-ratio="70.53" width="414" alt="imagen.png.266fc37e9cbfb7eae80bfee02da0805c.png" src="https://forum.imgburn.com/uploads/monthly_2025_07/imagen.png.266fc37e9cbfb7eae80bfee02da0805c.png" />
</p>
]]></description><guid isPermaLink="false">27624</guid><pubDate>Sun, 13 Jul 2025 01:14:32 +0000</pubDate></item><item><title>Pioneer BDR-XD05W and Sony BD-R 50GB Failures</title><link>https://forum.imgburn.com/topic/27623-pioneer-bdr-xd05w-and-sony-bd-r-50gb-failures/</link><description><![CDATA[<p>
	Hello, I'm having some issues with recent Sony BD-R 50GB DL media either failing mid burn or throwing errors during the verification stage. I recently purchased a 5-Pack of <a href="https://ebay.us/m/jIASeU" rel="external nofollow">these</a> discs that came from Japan. Historically, I've had success with Sony discs, so I bought some more to, hopefully, keep up the successful trend. Unfortunately, it hasn't been going well. The burner is a <em>P</em><em>ioneer BDR-XD05W </em>(external drive, "Y" USB cable). Prior to today, I had two Sony BD-R 50GB discs leftover from a previous order from ~5 years ago. Both of those discs burned successfully—no issues at all. The next day, I got these new Sonys in the mail to try out. Using the same drive, PC, and USB ports, the first disc failed at 50% of the burn process (at the turn of the layer change). I burned at 2x speed. The error stated "<em>Invalid Address For Write</em>". I then attempted a second disc, this time I burned at 4x, and switched up the USB connectors (there are four on this particular PC). The burn completed successfully without errors, but then it failed during the verification stage at 50% stating "<em>Reason: L-EC <br />
	Uncorrectable Error</em>". I then clicked re-try and got the error "<em>Reason: Positioning Error Detected by Read of Medium</em>". Finally, I clicked "Continue" and it progressed onward to completion with no further errors, however, I suspect the disc will likely has integrity issues given the flagging.  <br />
	<br />
	The drive worked perfectly well the day before on two burns (but with the older BD-R media). I attempted to buy the exact same media, however the packaging is admittedly not exactly identical to the older kind, and the new discs have additional burn speeds: 2x, 4x, and 6x versus just 2x. When I checked the ImgBurn logs, the Disc ID of the old media is <em>MEI-T01-001</em> while the Disc ID of the newer Sony media is <em>VERBAT-IMf-000</em>—so there is clearly a model difference. Is it likely an issue of my Pioneer drive simply not liking this particular Sony media? I thought about purchasing some Verbatim media like <a href="https://www.amazon.com/gp/product/B004HA8IQC/ref=ox_sc_act_title_1?smid=ATVPDKIKX0DER&amp;th=1" rel="external nofollow">these</a> but I assume the Disc ID may very well identical to the Sony's and produce the same issue? I'll post the logs of the two failures below, thanks for the help.
</p>

<p>
	<u>Burn attempt #1</u>:<br />
	<br />
	I 20:55:50 ImgBurn Version 2.5.8.0 started!<br />
	I 20:55:50 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)<br />
	I 20:55:50 Total Physical Memory: 8,266,800 KiB  -  Available: 2,467,496 KiB<br />
	I 20:55:50 Initialising SPTI...<br />
	I 20:55:50 Searching for SCSI / ATAPI devices...<br />
	I 20:55:50 -&gt; Drive 1 - Info: HL-DT-ST DVD-ROM DH40N A101 (D:) (SATA)<br />
	I 20:55:50 -&gt; Drive 2 - Info: PIONEER BD-RW   BDR-XD05 1.22-GENERAL (E:) (USB 2.0)<br />
	I 20:55:50 Found 1 DVD-ROM and 1 BD-RE XL!<br />
	I 20:56:48 Operation Started!<br />
	I 20:56:48 Source File: xyz.iso<br />
	I 20:56:48 Source File Sectors: 24,376,672 (MODE1/2048)<br />
	I 20:56:48 Source File Size: 49,923,424,256 bytes<br />
	I 20:56:48 Source File Volume Identifier: xxx<br />
	I 20:56:48 Source File Volume Set Identifier: 48EF58BB0173F3F1<br />
	I 20:56:48 Source File Application Identifier: ImgBurn v2.5.8.0<br />
	I 20:56:48 Source File Implementation Identifier: ImgBurn<br />
	I 20:56:48 Source File File System(s): UDF (2.50)<br />
	I 20:56:48 Destination Device: [0:0:0] PIONEER BD-RW   BDR-XD05 1.22 (E:) (USB)<br />
	I 20:56:49 Destination Media Type: BD-R (Disc ID: <strong>VERBAT-IMf-000</strong>)<br />
	I 20:56:49 Destination Media Supported Write Speeds: 2x, 4x, 6x<br />
	I 20:56:49 Destination Media Sectors: 24,438,784<br />
	I 20:56:49 Write Mode: BD<br />
	I 20:56:49 Write Type: DAO<br />
	I 20:56:49 Write Speed: 2x<br />
	I 20:56:49 Hardware Defect Management Active: No<br />
	I 20:56:49 BD-R Verify Not Required: Yes<br />
	I 20:56:49 Link Size: Auto<br />
	I 20:56:49 Lock Volume: Yes<br />
	I 20:56:49 Test Mode: No<br />
	I 20:56:49 OPC: No<br />
	I 20:56:49 BURN-Proof: Enabled<br />
	I 20:56:49 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x)<br />
	I 20:56:49 Advanced Settings - Optimal Writing Speed: No<br />
	I 20:56:50 Filling Buffer... (80 MiB)<br />
	I 20:56:50 Writing LeadIn...<br />
	I 20:57:11 Writing Session 1 of 1... (1 Track, LBA: 0 - 24376671)<br />
	I 20:57:11 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24376671)<br />
	I 20:57:11 Writing Layer 0... (LBA: 0 - 12219391)<br />
	W 21:43:58 Failed to Write Sectors 12097248 - 12097279 - <strong>Reason: Write Error</strong><br />
	W 21:43:58 Retrying (1 of 20)...<br />
	W 21:44:07 Retry Failed - <strong>Reason: Invalid Address For Write</strong><br />
	W 21:44:07 Retrying (2 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (3 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (4 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (5 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (6 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (7 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (8 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (9 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (10 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (11 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (12 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (13 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (14 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (15 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (16 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (17 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (18 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:07 Retrying (19 of 20)...<br />
	W 21:44:07 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:44:08 Retrying (20 of 20)...<br />
	W 21:44:08 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:35 Retrying (21)...<br />
	W 21:49:35 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:40 Retrying (22)...<br />
	W 21:49:40 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:41 Retrying (23)...<br />
	W 21:49:41 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:41 Retrying (24)...<br />
	W 21:49:41 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:41 Retrying (25)...<br />
	W 21:49:41 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:42 Retrying (26)...<br />
	W 21:49:42 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:42 Retrying (27)...<br />
	W 21:49:42 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:42 Retrying (28)...<br />
	W 21:49:42 Retry Failed - Reason: Invalid Address For Write<br />
	W 21:49:42 Retrying (29)...<br />
	W 21:49:42 Retry Failed - Reason: Invalid Address For Write<br />
	E 21:49:43 Failed to Write Sectors 12097248 - 12097279 - Reason: Write Error<br />
	I 21:49:43 Synchronising Cache...<br />
	W 21:49:50 User opted to skip the 'Close Track/Session/Disc' functions.<br />
	E 21:49:50 Failed to Write Image!<br />
	I 21:49:50 Exporting Graph Data...<br />
	I 21:49:50 Graph Data File: C:\Users\Bill\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-XD05_1.22_FRIDAY-JULY-11-2025_8-56_PM_VERBAT-IMf-000_2x.ibg<br />
	I 21:49:50 Export Successfully Completed!<br />
	E 21:49:50 Operation Failed! - Duration: 00:53:01<br />
	I 21:49:50 Average Write Rate: 7,678 KiB/s (1.7x) - Maximum Write Rate: 8,832 KiB/s (2.0x)<br />
	<br />
	<br />
	<u>Burn Attempt #2: Successful, but Fails at Verification</u>:
</p>

<p>
	<br />
	I 22:10:46 ImgBurn Version 2.5.8.0 started!<br />
	I 22:10:46 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)<br />
	I 22:10:46 Total Physical Memory: 8,266,800 KiB  -  Available: 6,225,484 KiB<br />
	I 22:10:46 Initialising SPTI...<br />
	I 22:10:46 Searching for SCSI / ATAPI devices...<br />
	I 22:10:46 -&gt; Drive 1 - Info: HL-DT-ST DVD-ROM DH40N A101 (D:) (SATA)<br />
	I 22:10:46 -&gt; Drive 2 - Info: PIONEER BD-RW   BDR-XD05 1.22-GENERAL (E:) (USB 2.0)<br />
	I 22:10:46 Found 1 DVD-ROM and 1 BD-RE XL!<br />
	I 22:11:11 Operation Started!<br />
	I 22:11:11 Source File: xyz.iso<br />
	I 22:11:11 Source File Sectors: 24,376,672 (MODE1/2048)<br />
	I 22:11:11 Source File Size: 49,923,424,256 bytes<br />
	I 22:11:11 Source File Volume Identifier: xxx<br />
	I 22:11:11 Source File Volume Set Identifier: 48EF58BB0173F3F1<br />
	I 22:11:11 Source File Application Identifier: ImgBurn v2.5.8.0<br />
	I 22:11:11 Source File Implementation Identifier: ImgBurn<br />
	I 22:11:11 Source File File System(s): UDF (2.50)<br />
	I 22:11:11 Destination Device: [0:0:0] PIONEER BD-RW   BDR-XD05 1.22 (E:) (USB)<br />
	I 22:11:11 Destination Media Type: BD-R (Disc ID: <strong>VERBAT-IMf-000</strong>)<br />
	I 22:11:11 Destination Media Supported Write Speeds: 2x, 4x, 6x<br />
	I 22:11:11 Destination Media Sectors: 24,438,784<br />
	I 22:11:11 Write Mode: BD<br />
	I 22:11:11 Write Type: DAO<br />
	I 22:11:11 Write Speed: 4x<br />
	I 22:11:11 Hardware Defect Management Active: No<br />
	I 22:11:11 BD-R Verify Not Required: Yes<br />
	I 22:11:11 Link Size: Auto<br />
	I 22:11:11 Lock Volume: Yes<br />
	I 22:11:11 Test Mode: No<br />
	I 22:11:11 OPC: No<br />
	I 22:11:11 BURN-Proof: Enabled<br />
	I 22:11:11 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x)<br />
	I 22:11:11 Advanced Settings - Optimal Writing Speed: No<br />
	I 22:11:12 Filling Buffer... (80 MiB)<br />
	I 22:11:12 Writing LeadIn...<br />
	I 22:11:41 Writing Session 1 of 1... (1 Track, LBA: 0 - 24376671)<br />
	I 22:11:41 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24376671)<br />
	I 22:11:41 Writing Layer 0... (LBA: 0 - 12219391)<br />
	I 22:37:08 Writing Layer 1... (LBA: 12219392 - 24376671)<br />
	I 23:25:10 Synchronising Cache...<br />
	I 23:25:11 Closing Track...<br />
	I 23:25:12 Finalising Disc...<br />
	I 23:25:30 Exporting Graph Data...<br />
	I 23:25:30 Graph Data File: C:\Users\Bill\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-XD05_1.22_FRIDAY-JULY-11-2025_10-11_PM_VERBAT-IMf-000_4x.ibg<br />
	I 23:25:30 Export Successfully Completed!<br />
	I 23:25:30 Operation Successfully Completed! - Duration: 01:14:19<br />
	I 23:25:30 Average Write Rate: 11,060 KiB/s (2.5x) - Maximum Write Rate: 17,632 KiB/s (4.0x)<br />
	I 23:25:30 Cycling Tray before Verify...<br />
	W 23:26:03 Waiting for device to become ready...<br />
	I 23:26:04 Device Ready!<br />
	I 23:26:05 Operation Started!<br />
	I 23:26:05 Source Device: [0:0:0] PIONEER BD-RW   BDR-XD05 1.22 (E:) (USB)<br />
	I 23:26:05 Source Media Type: BD-R (Disc ID: VERBAT-IMf-000)<br />
	I 23:26:05 Source Media Supported Read Speeds: 6x<br />
	I 23:26:05 Source Media Supported Write Speeds: 2x, 4x, 6x<br />
	I 23:26:05 Source Media Sectors: 24,376,672<br />
	I 23:26:05 Source Media Size: 49,923,424,256 bytes<br />
	I 23:26:05 Image File: xyz.iso<br />
	I 23:26:05 Image File Sectors: 24,376,672 (MODE1/2048)<br />
	I 23:26:05 Image File Size: 49,923,424,256 bytes<br />
	I 23:26:05 Image File Volume Identifier: xxx<br />
	I 23:26:05 Image File Volume Set Identifier: 48EF58BB0173F3F1<br />
	I 23:26:05 Image File Application Identifier: ImgBurn v2.5.8.0<br />
	I 23:26:05 Image File Implementation Identifier: ImgBurn<br />
	I 23:26:05 Image File File System(s): UDF (2.50)<br />
	I 23:26:05 Read Speed (Data/Audio): MAX / MAX<br />
	I 23:26:06 Read Speed - Effective: 2.5x - 6x<br />
	I 23:26:06 Verifying Session 1 of 1... (1 Track, LBA: 0 - 24376671)<br />
	I 23:26:06 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 24376671)<br />
	I 23:26:06 Verifying Layer 0... (LBA: 0 - 12219391)<br />
	I 23:47:01 Verifying Layer 1... (LBA: 12219392 - 24376671)<br />
	W 23:47:10 Failed to Read Sectors 12221312 - 12221343 - <strong>Reason: L-EC Uncorrectable Error</strong><br />
	W 23:47:15 Failed to Read Sector 12221312 - Reason: L-EC Uncorrectable Error<br />
	W 23:47:15 Sector 12221312 maps to File: \BDMV\STREAM\00025.m2ts<br />
	W 23:50:21 Retrying (1)...<br />
	W 23:50:26 Retry Failed - Reason: Positioning Error Detected by Read of Medium<br />
	W 23:52:16 Retrying (2)...<br />
	W 23:52:20 Retry Failed - Reason: Positioning Error Detected by Read of Medium<br />
	W 23:52:23 Retrying (3)...<br />
	W 23:52:28 Retry Failed - Reason: L-EC Uncorrectable Error<br />
	W 23:52:41 Failed to Read Sector 12221312 - Reason: L-EC Uncorrectable Error<br />
	W 23:52:41 Sector 12221312 maps to File: \BDMV\STREAM\00025.m2ts<br />
	I 00:38:54 Exporting Graph Data...<br />
	I 00:38:54 Graph Data File: C:\Users\Bill\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-XD05_1.22_FRIDAY-JULY-11-2025_10-11_PM_VERBAT-IMf-000_4x.ibg<br />
	I 00:38:54 Export Successfully Completed!<br />
	I 00:38:54 Operation Successfully Completed! - Duration: 01:12:48<br />
	I 00:38:54 Average Verify Rate: 11,166 KiB/s (2.5x) - Maximum Verify Rate: 27,715 KiB/s (6.3x)<br />
	 
</p>

<p><a href="https://forum.imgburn.com/uploads/monthly_2025_07/BurnFailure50(Disc1Attempt1).PNG.ae1be57aad0388c8e789cb0f0d43701e.PNG" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13106" src="https://forum.imgburn.com/uploads/monthly_2025_07/BurnFailure50(Disc1Attempt1).PNG.ae1be57aad0388c8e789cb0f0d43701e.PNG" data-ratio="72.2" width="410" class="ipsImage ipsImage_thumbnailed" alt="Burn Failure 50%  (Disc 1 Attempt #1).PNG"></a></p>
<p><a href="https://forum.imgburn.com/uploads/monthly_2025_07/VerificationFailure(Disc2Attempt2--VerificationStage).PNG.44ec0a968593331b87b81fb549a229f0.PNG" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13107" src="https://forum.imgburn.com/uploads/monthly_2025_07/VerificationFailure(Disc2Attempt2--VerificationStage).PNG.44ec0a968593331b87b81fb549a229f0.PNG" data-ratio="72.55" width="408" class="ipsImage ipsImage_thumbnailed" alt="Verification Failure (Disc 2 Attempt #2--Verification Stage).PNG"></a></p>]]></description><guid isPermaLink="false">27623</guid><pubDate>Sat, 12 Jul 2025 17:49:00 +0000</pubDate></item><item><title>BD doesn't play on standalone player. Works on PC. Created with DVDFAB, burned with IMGBURN</title><link>https://forum.imgburn.com/topic/27622-bd-doesnt-play-on-standalone-player-works-on-pc-created-with-dvdfab-burned-with-imgburn/</link><description><![CDATA[<p>
	Hi everyone, 
</p>

<p>
	I'm running into issues with Blu-rays that I've burned with ImgBurn and created with DVDFab.
</p>

<p>
	The issue is that the disc is not recognized on the standalone Sony player, which is plugged into the TV. It does work fine on my PC, though. 
</p>

<p>
	Here are the steps that led me here:
</p>

<p>
	1. Created the movie and mastered a ProRes 422 .mov file
</p>

<p>
	2. Inserted this file into DVDFab's "UHD Creator" and added my subtitles. Then, I rendered and created an ISO file, which I saved on my PC. These are the settings I used:
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="13105" data-ratio="29.39" width="946" alt="image.png.5e1b9fb7c005d1b1bfa56443cbbb992d.png" src="https://forum.imgburn.com/uploads/monthly_2025_07/image.png.5e1b9fb7c005d1b1bfa56443cbbb992d.png" />
</p>

<p>
	3. Opened ImgBurn in Burn mode and set Write Speed to 3x, as someone said this might cause the problem. Checked the verify button.
</p>

<p>
	4. After burn and verify, the disc plays wonderfully on my PC, but not on the standalone. When inserting it there, it goes blank for a second and then returns to the player's menu.
</p>

<p>
	 
</p>

<p>
	This is what ImgBurn says about the disc on the right hand side:
</p>

<p>
	 
</p>

<p>
	PIONEER BD-RW   BDR-UD03 1.14 (USB)<br />
	Current Profile: BD-R
</p>

<p>
	Disc Information:<br />
	Status: Complete<br />
	State of Last Session: Complete<br />
	Erasable: No<br />
	Sessions: 1<br />
	Sectors: 6,722,144<br />
	Size: 13,766,950,912 bytes<br />
	Time: 1493:50:44 (MM:SS:FF)<br />
	MID: CMCMAG-BA5-000<br />
	Supported Read Speeds: 6x<br />
	Current Read Speed: 2.5x - 6x
</p>

<p>
	File System Information:<br />
	Sectors: 6,722,144<br />
	Size: 13,766,950,912 bytes<br />
	Time: 1493:50:44 (MM:SS:FF)
</p>

<p>
	TOC Information:<br />
	Session 1... (LBA: 0)<br />
	-&gt; Track 01  (Mode 1, LBA: 0 - 6722143)<br />
	-&gt; LeadOut  (LBA: 6722144)
</p>

<p>
	Track Information:<br />
	Session 1...<br />
	-&gt; Track 01 (LTSA: 0, LTS: 6722144, LRA: 6722143)
</p>

<p>
	Disc Definition Structure:<br />
	Certified: No<br />
	Scanned: No<br />
	Manufacturers Name: PIONEER<br />
	Additional ID: BD-RW BDR-UD03<br />
	Serial Number: ALDL451685WL
</p>

<p>
	BD Disc Information:<br />
	Disc ID: CMCMAG-BA5-000<br />
	Disc Type: BD-R<br />
	Disc Size: 120 mm<br />
	Disc Class: 0<br />
	Disc Version: 1<br />
	Number of Layers: 1<br />
	Layer Type: Writable<br />
	DVD Layer Present: No<br />
	CD Layer Present: No<br />
	Channel Bit Length: 74.50 nm (25 GB Per Layer)<br />
	Push-Pull Polarity: Positive<br />
	Recorded Mark Polarity: HTL<br />
	BCA Present: Yes<br />
	Maximum Transfer Rate: Not Specified<br />
	First PAA of Data Zone: 131,072<br />
	Last PAA of Data Zone: 1,658,494
</p>

<p>
	 
</p>

<p>
	Also, I'm using 25gb discs with a 4x write speed. And I'm taking a 2160p video file and crating a 2160p Blu Ray out of it.
</p>

<p>
	 
</p>

<p>
	Does anybody have any ideas what the issue could be? Is it likely to be a DVDFab creating problem or a ImgBurn burning Problem?
</p>

<p>
	 
</p>

<p>
	Or is it neither and the non-4k-player just can't play a 2160p file?
</p>

<p>
	 
</p>

<p>
	My next step will be to try creating a folder with DVDFab instead of an ISO file. And then I will try creating a 1080p file instead and testing it with my player.
</p>

<p>
	 
</p>

<p>
	Cheers,
</p>

<p>
	Leopold
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">27622</guid><pubDate>Fri, 11 Jul 2025 08:57:38 +0000</pubDate></item></channel></rss>
