All Activity
- Past hour
-
Your hardware must be the problem. If it says burn completed but Windows says the disc needs formatting, then nothing was written to the disc or your drive doesn't recognize anything was written to it. That would also explain why your player doesn't play it. There's nothing actually on the disc. Try this next. With one of those discs you burned inserted into the drive, use ImgBurn's manual Verify mode to see if ImgBurn can read the disc. Or try the Read mode to see if that disc can be detected and read. Verify is basically a Read operation without an image file being written from the read data. You could also see if you get a needs formatting message by taking that disc to another PC with a different kind of drive. Or you could try getting a different USB drive and see if that happens again. However, I believe the issue is nothing is actually written to the discs, which would explain why your player doesn't play anything. But, to troubleshoot such an issue is nearly impossible to do remotely. One would need to be on site with the discs and all the hardware in question to know for sure. BUT, none of that explains why you weren't given an ISO9660 message or a layer break setting option. Wait, did you actually create this ISO you're trying to burn or did you get it from another source? If you didn't create it yourself, you'd not get an ISO9660 settings message. You may not get a layer break setting option either. If you didn't actually create this ISO in question, then the ISO may not have been authored correctly for DVD Video settings.
-
Disk is in the drive, opened File Explorer, clicked on the drive and File Explorer tells me the disc needs to be formatted! No other info is available for that disc or any of the others I've attempted to burn. I have VLC Media player on my PC and it won't open the disc either. Since when does an ISO file have a VIDEO_TS in it? I just put a regular dvd I burned recently from an ISO file and there is no VIDEO_TS file on it. My hardware is not the problem. I found these insrucions online... Open ImgBurn and select "Write image file to disc" from the main menu (or go to Mode > Write). Under the Source section, click the Browse for a file icon (the small folder/magnifying glass) and select your movie ISO file. Under the Destination section, ensure your dual-layer DVD drive is selected. On the right-hand panel, change the Write Speed to a low setting like 2.4x or 4x. Note: Burning dual-layer discs at high speeds often causes write errors or playback freezing. Check the Verify box if you want ImgBurn to double-check the disc for errors after burning. Click the large Write button (the image-to-disc icon) at the bottom left to start the process. Once the process reaches 100%, your dual-layer DVD is ready to play.
-
You put one of the burned discs in the PC drive, open File Explorer, and open the root directory of the disc by double clicking on the drive icon represented in File Explorer. If it is a DVD Video standard DVD and your PC is configured to automatically start DVD movies, your PC software player will open it. That proves it's a DVD Video compliant disc, which means your Sony, I think it was?, DVD player is the culprit. Otherwise, if the disc actually has contents burned to it, double clicking on the drive will open its root directory. Then, you look for a VIDEO_TS folder in File Explorer. However, since you were not asked to set a layer break or any ISO9660 settings, you're almost certainly not making a DVD Video disc, which explains why your player isn't playing it. Since you seemed unaware of what a VIDEO_TS is, let me ask you precisely what you're doing. What guide did you follow? Are you just adding files that play on your PC like MP4 or MKV to the DVD+R DL, popping that disc in your DVD player, and expecting it to play the files? If you are, that won't work. You need a DVD Video compliant disc with a VIDEO_TS in the root directory.
- Today
-
I thank you for all your help so far, but I am just an end-user, not an expert. I've followed all the online instructions, bought the DVD+RDL discs you said to buy (for $65) and have already wasted five of these discs. I can't tell you what is on any of the discs as I can't open them to see. I've burned numerous "regular" sized ISO movies onto standard DVD+R discs with your program with no trouble but this is the first time I've tried to burn an ISO file so large onto a double layer dvd. No, I was not asked to set a layer break or the ISO9660 file system settings and no mention of a VIDEO_TS folder. That's all I know. How can I open a burned dvd+rdl to show you the root directory of a failed burn? Please guide me and I will provide everything I can! If you send me step-by-step burning instructions I will keep trying! Here is a screenshot of my latest attempt underway. Charles
-
gamegamerOB started following Cant burn to Dual layer 50gb blu ray.
-
I have tried three different drives and none of them worked. Got it to write on two of them, but it stopped at 11 and 23%. Just going to burn it to two 25gb drives, so no rush. ImgBurn.log
-
gamegamerOB joined the community
- Yesterday
-
As I said before, show me a screenshot of the root directory contents of the disc that won't play. I've got a feeling it's not a DVD Video compliant disc. When you created the image file in ImgBurn, were you asked to set a layer break? If you weren't, then there's most likely not a VIDEO_TS folder in the root directory of that disc. Also, were you asked to set the ISO9660 file system settings for a DVD Video disc by ImgBurn when you added a VIDEO_TS folder?
-
I got the new dvd's you suggested and tried to burn the same large iso file with no success as it was not playable on my Sony dvd player. Still at a loss as to what the problem is after following all the steps. Charles
-
Syraj joined the community
- Last week
-
Pioneer BDR-206 fails verification at BD-R DL layer break in ImgBurn, but Windows Disc Image Burner works
dbminter replied to griff7337's topic in ImgBurn Support
I finally got a test candidate to try out ISOBurn with for BD-R DL. I tested a Ritek BD-R DL and I would recommend using it going forward as opposed to ImgBurn for BD-R DL's. With ImgBurn, only 2x burning properly works. With ISOBurn, it takes about less than 90 minutes, the total burn time for 2x, to write 6x BD-R DL and Verify it in ISOBurn. ISOBurn also works on my VanTec Gen 1 USB enclosure and the LG WH16NS60. With ImgBurn, the VanTec Gen 1 enclosure never worked on my setup for either the NS60 or my ASUS BD burner. I would recommend not using ISOBurn's Verify option. While it is servicable, since you must have an ISO file to get it to work, I would save time and use ImgBurn's manual Verify operation against the image file's contents after successful burn. The major drawback to ISOBurn is it only works as a command line driven tool. So, I created a shortcut to run it with I've only just made the basic tests to my Ritek burn thus far. I've only performed 4x Forward Scan tests on all of the extras. I'm in the process of watching the 2.5 hours of the main feature right now. I've finished the first 25 minutes episode of 6. No playback problems thus far. However, until I get a Blu-Ray BD-50 that I need to watch all of its contents on, I can't for 100% certain say ISOBurn "works." Thus far, though, it seems to be the superior option to ImgBurn for burning BD-R DL. So, I thank you for pointing out this alternative option! -
ImgBurn 2.5.8 stops displaying the Log Window screen after it was closed from a former session
Nikon_Z9_II posted a topic in ImgBurn Bugs
I had ImgBurn 2.5.8 installed and encountered the problem that the Logging Window is NOT showing up, so I followed the instruction from the Forum as shown: "To resolve this, you can reset the window position by closing ImgBurn, opening the Registry Editor (regedit), navigating to HKEY_CURRENT_USER\Software\ImgBurn, and deleting the LogWindow entry." I deleted the registry entry for "HKEY_CURRENT_USER\Software\ImgBurn", closed ImgBurn and restarted it again. Again, the ImgBurn Log Window would NOT display. I do keep 2 versions of ImgBurn which is 2.5.7 and 2.5.8 and I never trusted 2.5.8 and have always used 2.5.7 since 2001 in my old PC's. I totally uninstalled ImgBurn 2.5.8 and re-installed ImgBurn 2.5.7 and the ImgBurn 2.5.7 install did not even created a shortcut for 2.5.7 but I easily created the 2.5.7 shortcut since the ImgBurn 2.5.8 shortcut I previously created was still existing in the desktop and ImgBurn 2.5.7 and 2.5.8 executable is named the same as "ImgBurn.exe". When I clicked the 2.5.7 shortcut named as "ImgBurn 2.5.7", the Log Window now appears. I believe this has to do with me closing the prior ImgBurn 2.5.8 Log Window and even following the advice to delete the Registry entry for "HKEY_CURRENT_USER\Software\ImgBurn" could NOT solve the problem. Now with ImgBurn 2.5.7 working with the Log Window opened up, I will use my new method of running a simulation first so the log is created and then a real backup with the contents plus the previously created simulation log. "EVEN IN SIMULATION mode, the LOG File SHOULD ACT the same way as a real backup process is performed" - I stated this because I need to verify this after successfully installing ImgBurn 2.5.7. Suggestion: Why not improve ImgBurn as 2.5.9 such that a C:\ disk drive log is created in "C:\Program Files (x86)\ImgBurn\Logs\......." every time ImgBurn is opened up and a new log is created with the log file name with stating "CCYY-MM-DD HH:MM:SS AM" or "CCYY-MM-DD HH:MM:SS PM" . Since the log is a Text file, logging can be done by just adding new records to the very end of the text file when ImgBurn is NOT closed and a new set of backup is created using the same log that was originally created when ImgBurn was first started. When ImgBurn is closed and a new session was initiated, then a new log with a different "CCYY-MM-DD HH:MM:SS AM or PM" is created. My reason for this I can perform a final burn which will include the previously created log file. I wanted the log file because ImgBurn renames the file being backed up if the maximum file length is exceeded and the log will show the new renamed name in the log file together with the CD/DVD or BD-R real backup contents for future reference. -
Nikon_Z9_II joined the community
-
The dvd's you recommended will arrive today and I will try burning one and let you know my results. Thanks again for your help! Charles
-
Just signed in to say, if you think full formating a new BD-RE 50GB DL disc is long, try a Sony BD-RE BDXL 100GB disc, which is over six hours with spares enabled. It is so long I don't think it is pratical to use.
-
lostair joined the community
- Earlier
-
First time burning discs, early into the process the drive stops reading the disc completely.
NeilTheGuy posted a topic in ImgBurn Support
Trying to write files/folders to a disc, everything went fine at first, drive could read the disc just fine and I was able to begin the process, but after I believe track 1 it's cut short and now my drive refuses to read anything, even after reinstalling it through Device Manager. Windows and ImgBurn still recognise the drive being there, but no media is read. ImgBurn.log -
NeilTheGuy joined the community
-
Is there a good burner for double layer BD-Rs (50 GB)?
dbminter replied to dury's topic in ImgBurn General
I've begun performing manual Verify tests on my first batch of Ritek BD-R DL discs burned beginning 2026-06-19 to make sure they're still readable after the passage of a bit of time. All 16 discs burned around that time passed manual Verifies! My only concern with the Riteks may be their longevity. My only experience with Ritek BD-R are 2 SL's that someone burned for me in 2012. On or before 13 years later, both were partially unreadable. Now, this doesn't mean the same experience will occur on their BD-R DL. I had a similar experience with my tests of Ritek DVD+R DL about 20 years ago. I got a batch of 3 of them. 1 was fully readable a year later, one was partially unreadable a year later, and the other was TOTALLY unreadable a year later. -
That's where I would start. Even if changing discs doesn't fix the issue, those discs will last MUCH longer than the CMC ones and will have better compatibility with other players.
-
I'll order those DataLife Plus DVD+R DL today!
-
That actually sounds like the disc was not burned at all. Are you SURE the disc is not blank? Discs that have been burned cannot be formatted. However, it could also be indicative of the other issue I found or a hardware failure. Load that disc that says it wants to be formatted in ImgBurn and try to perform a Verify or Read operation on it. The other issue I noticed is you've used Verbatim's junk Life Series DVD+R DL from CMC Magnetics. They can be very problematic, producing a variety of problems and issues. You're better off using the DataLife Plus DVD+R DL from Verbatim, NOT the Life Series. The DataLife Plus series you can generally only find online are made by Mitsubishi. They're the best ones out there and are generally the only quality choice.
-
I put the dvd into a drive and attempted to take a look at the contents, but every time I do that I get a message that the disk needs to be formatted. Strange. I'm trying to burn an ISO file of a long movie that is 8330058 KB. Charles
-
I need to see your disc's root directory contents. I've a feeling you're not actually creating DVD Video content which would only be revealed if I can see if there's a VIDEO_TS folder in the root directory of the disc you can't play. From the Log, I'm not seeing a DVD Video disc was actually created, but that relevant info may only be in a Log for a Build operation. Plus, there's something else in the Log that could be relevant, but I just have a hunch the reason the discs aren't playing is there's no VIDEO_TS folder in the root directory of the disc you're attempting to play.
-
Thanks for your help!! Last burn: 11:26:58 ImgBurn Version 2.5.6.0 started! I 11:26:58 Microsoft Windows 8 Professional (6.2, Build 9200) I 11:26:58 Total Physical Memory: 66,932,088 KB - Available: 56,215,952 KB I 11:26:58 Initialising SPTI... I 11:26:58 Searching for SCSI / ATAPI devices... I 11:26:58 -> Drive 1 - Info: HL-DT-ST BD-RE WH12LS30 1.01-C0 (I:) (USB) I 11:26:58 -> Drive 2 - Info: HL-DT-ST DVDRAM SP80NB80 RF02-J0 (H:) (USB) I 11:26:58 Found 1 DVD±RW/RAM and 1 BD-RE! I 11:35:08 Operation Started! I 11:35:08 Source File: G:\SAVING PRIVATE RYAN.ISO I 11:35:08 Source File Sectors: 4,165,029 (MODE1/2048) I 11:35:08 Source File Size: 8,529,979,392 bytes I 11:35:08 Source File File System(s): None I 11:35:08 Destination Device: [0:0:0] HL-DT-ST DVDRAM SP80NB80 RF02 (H:) (USB) I 11:35:08 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) I 11:35:08 Destination Media Supported Write Speeds: 3x, 4x, 6x I 11:35:08 Destination Media Sectors: 4,173,824 I 11:35:08 Write Mode: DVD I 11:35:08 Write Type: DAO I 11:35:08 Write Speed: 3x I 11:35:08 Link Size: Auto I 11:35:08 Lock Volume: Yes I 11:35:08 Test Mode: No I 11:35:08 OPC: No I 11:35:08 BURN-Proof: Enabled I 11:35:08 Write Speed Successfully Set! - Effective: 4,155 KB/s (3x) I 11:35:09 Book Type Setting: DVD-ROM I 11:35:09 Optimal L0 Data Zone Capacity: 2,082,528 I 11:35:09 Optimal L0 Data Zone Method: ECC Block Boundary I 11:35:09 Set L0 Data Zone Capacity Succeeded! I 11:35:09 Filling Buffer... (80 MB) I 11:35:09 Writing LeadIn... I 11:36:24 Writing Session 1 of 1... (1 Track, LBA: 0 - 4165028) I 11:36:24 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4165028) I 11:36:24 Writing Layer 0... (LBA: 0 - 2082527) I 11:53:56 Writing Layer 1... (LBA: 2082528 - 4165028) I 12:11:34 Synchronising Cache... I 12:12:02 Closing Track... I 12:12:04 Finalising Disc... I 12:12:50 Exporting Graph Data... I 12:12:50 Graph Data File: C:\Users\vohta\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_SP80NB80_RF02_SUNDAY-AUGUST-30-2026_11-35_AM_CMC_MAG-D03-64_3x.ibg I 12:12:50 Export Successfully Completed! I 12:12:50 Operation Successfully Completed! - Duration: 00:37:41 I 12:12:50 Average Write Rate: 3,947 KB/s (2.8x) - Maximum Write Rate: 4,236 KB/s (3.1x) I 12:12:50 Cycling Tray before Verify... W 12:19:49 Waiting for device to become ready... I 12:19:55 Device Ready! I 12:19:55 Operation Started! I 12:19:55 Source Device: [0:0:0] HL-DT-ST DVDRAM SP80NB80 RF02 (H:) (USB) I 12:19:55 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: CMC MAG-D03-64) I 12:19:55 Source Media Supported Write Speeds: 3x, 4x, 6x I 12:19:55 Image File: G:\SAVING PRIVATE RYAN.ISO I 12:19:55 Image File Sectors: 4,165,029 (MODE1/2048) I 12:19:55 Image File Size: 8,529,979,392 bytes I 12:19:55 Image File File System(s): None I 12:19:55 Read Speed (Data/Audio): MAX / MAX I 12:19:56 Verifying Session 1 of 1... (1 Track, LBA: 0 - 4165028) I 12:19:56 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 4165028) I 12:19:56 Verifying Layer 0... (LBA: 0 - 2082527) I 12:28:57 Verifying Layer 1... (LBA: 2082528 - 4165028) I 12:38:02 Exporting Graph Data... I 12:38:02 Graph Data File: C:\Users\vohta\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_SP80NB80_RF02_SUNDAY-AUGUST-30-2026_11-35_AM_CMC_MAG-D03-64_3x.ibg I 12:38:02 Export Successfully Completed! I 12:38:02 Operation Successfully Completed! - Duration: 00:18:06 I 12:38:02 Average Verify Rate: 7,684 KB/s (5.5x) - Maximum Verify Rate: 11,255 KB/s (8.1x) I 12:47:25 Close Request Acknowledged I 12:47:25 Closing Down... I 12:47:39 Shutting down SPTI... I 12:47:39 ImgBurn closed! ; All I could find on the dvd was: Device USBSTOR\CdRom&Ven_HL-DT-ST&Prod_BD-RE__WH12LS30&Rev_1.01\0123456789ABCDEF&0 was configured. Driver Name: cdrom.inf Driver Package ID: cdrom.inf_amd64_dc7b0d8271e8847c Class GUID: {4d36e965-e325-11ce-bfc1-08002be10318} Driver Date: 06/21/2006 Driver Version: 10.0.26100.1150 Driver Provider: Microsoft Driver Section: cdrom_install Driver Rank: 0xFF0006 Matching Device ID: GenCdRom Outranked Drivers: cdrom.inf:GenCdRom:00FF2002 Device Updated: false Parent Device: USB\VID_152D&PID_0578\0123456789ABCDEF Hope you can find what I'm doing wrong. Thanks, Charles
-
dbminter started following Can't burn DVD+R DL ISO FILES THAT PLAY
-
I'll need a bit more info. Copy and paste the entirety of the Write and Verify phases from one of these successful burns from the Log. You can access old Log entries from the Help menu. While you're at it, insert the last burned disc that won't play into your PC drive, open its root directory contents in Windows/File Explorer, and attach a screenshot of the directories and files in the root directory of the disc.
-
Vohtahn started following Can't burn DVD+R DL ISO FILES THAT PLAY
-
Windows 11 PRO Dell and use IMGBURN all the time for standard dvd's but have wasted 10 8x DVD+RDL Verbatim discs following online instructions to burn large ISO movies of about 8gb with LG drives. Last attempt IMGBURN said "success" and played the song but discs won't play in Sony player or even on my PC. Any help appreciated!!
-
Vohtahn joined the community
-
Do you have another burner? ; because I have Verbatim CD-R's of that same CMC Magnetics type and I don't have any obvious issues on my desktop burners. I typically burn at 8x or 16x tops though when it comes to burning standard Audio CD's (as a bonus with these Verbatim CD-R's (CMC Magnetics) that I have can overburn to at least 82min15sec successfully). I can't burn slower than 8x on CD-R's on my burners. there is a old HP burner I have that I 'may' be able to burn slower than 8x though since that burner has a 8x max burn speed, but I never hooked it up to try since I figure it's likely a weaker burner of the two old CD burners with a IDE connection I have. but I generally use my Liteon 24102b IDE CD burner (at 8x) for burning Audio CD's in recent memory. but it appears your burner is a laptop one which I heard those as a general rule are more so-so/questionable vs a desktop burner. p.s. I realize that CMC Magnetics are generally considered on the weaker side quality wise vs higher quality media. but at least in my opinion, CD-R's are not as picky as DVD when it comes to burn quality.
-
Hi, I'm not sure there's still any interest in this, but I wanted to see if I could replicate BurnPlot with Claude/ChatGPT and got pretty close. Here's the source in C++11. It should be compatible with Windows XP. burnplot-main.zip
-
I don’t recall it being something ImgBurn would modify if you’re just doing a Read operation. I suspect AnyDVD is just fixing things because it’s technically wrong on the original disc.
-
I have been using ImgBurn for many years now and have found it to be absolutely indispensible for reading and writing optical discs. I use it mostly to rip DVDs to ISO. Since DVDs are usually copy-protected, I have been running AnyDVD in the background. I have ripped hundreds, possibly as many as a thousand or more and the combination has always proved rock-solid. However, I HATE Windows and recently my Windows installation has been getting less and less usable, so I have been looking at options to rip DVDs under Linux. To that end, I have been spending a lot of time looking at the rips in a hex editor. All of the files that I have looked at have one byte changed from the DVD to the ISO, at the same offset and by the same amount. I cannot figure out why this byte would be changed or how. It might be something that AnyDVD is doing (in which case this might not be the best place to ask), or it might have something to do with ImgBurn. I have noticed this in only 4 discs so far. I thought I'd ask befor checking another few dozen or hundred... The byte in question is part of a 32-bit value in the VIDEO_TS.IFO file (and its corresponding .BUF file) at bytes 12 to 15 of that file. In the discs where I've noticed it, that value has been increased by exactly 1 (that's why it affects only a single byte, rather than all four). According to this website: http://www.mpucoder.com/DVD/ifo.html, the value represents the last sector of VMG set (last sector of BUP). Does anybody here have any insight as to why that value is being changed and whether it is being done by ImgBurn or AnyDVD? The other oddity I noticed, although it affects only one disc that I have found so far, is the ISO of one rip is 32k larger than the DVD that was ripped. When doing a checksum of that ISO against a rip I did under Linux, they of course didn't match. So when I noticed the filesize discrepancy, I truncated the ISO at that point and the checksums matched. It has me baffled! Any ideas? Thanks Brian
