Search the Community

Hello all! Long time user, first time poster. I've been through the ringer with this and have combed over old form posts and FAQs to no avail, so I'm hoping y'all can help me resolve this. What I'm using: Verbatim BD-R DL 50gb 8x OWC Mercury Pro 16X Blu-ray Drive What I'm trying to burn: 3x Project4K ISOs The story: Originally, I used my old drive (Samsung External Blu-ray Writer TSST SE-506CB/RSBD 6X USB 2.0 Slim) and everything went well for the first two ISOs ("SW" & "EM"). However, when I tried burning the third ISO ("JD"), I received a L-EC Uncorrectable Error message. After some research, I determined it was the drive. This theory was further proven when I tried to burn the first two ISOs ("SW" & "EM") again, only to receive I/O Errors. So, I replaced the drive (OWC Mercury Pro 16X Blu-ray Drive) and tried burning the "JD" ISO again with success (both with the burn and verification). However, just to be sure, I attempted another burn with the "SW" and "EM" ISOs and still receive an I/O Error (log below for both). It's worth noting that I've tried burning these at all supported speeds listed by Imgburn (2x, 4x, 6x) as well as with AWS with the same result. I'm not sure what else to do and would appreciate all suggestions. Thank you all for your time and be well. The log: I 21:44:57 ImgBurn Version 2.5.8.0 started! I 21:44:57 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 21:44:57 Total Physical Memory: 6,164,744 KiB - Available: 3,217,080 KiB I 21:44:57 Initialising SPTI... I 21:44:57 Searching for SCSI / ATAPI devices... I 21:44:58 -> Drive 1 - Info: HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB 2.0) I 21:44:58 Found 1 BD-RE XL! I 21:45:23 Operation Started! I 21:45:23 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K77.ISO I 21:45:23 Source File Sectors: 21,983,296 (MODE1/2048) I 21:45:23 Source File Size: 45,021,790,208 bytes I 21:45:23 Source File Volume Identifier: 4K77 I 21:45:23 Source File Volume Set Identifier: 4D955102014F6FAF I 21:45:23 Source File Application Identifier: ImgBurn v2.5.8.0 I 21:45:23 Source File Implementation Identifier: ImgBurn I 21:45:23 Source File File System(s): UDF (2.50) I 21:45:23 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 21:45:23 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 21:45:23 Destination Media Supported Write Speeds: 2x, 4x, 6x I 21:45:24 Destination Media Sectors: 24,438,784 I 21:45:24 Write Mode: BD I 21:45:24 Write Type: DAO I 21:45:24 Write Speed: 4x I 21:45:24 Hardware Defect Management Active: No I 21:45:24 BD-R Verify Not Required: Yes I 21:45:24 Link Size: Auto I 21:45:24 Lock Volume: Yes I 21:45:24 Test Mode: No I 21:45:24 OPC: No I 21:45:24 BURN-Proof: Enabled I 21:45:24 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 21:45:53 Filling Buffer... (80 MiB) I 21:45:53 Writing LeadIn... I 21:45:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 21983295) I 21:45:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21983295) I 21:45:54 Writing Layer 0... (LBA: 0 - 12219391) I 22:09:05 Writing Layer 1... (LBA: 12219392 - 21983295) W 22:09:41 Failed to Write Sectors 12498976 - 12499007 - Reason: Write Error W 22:09:41 Retrying (1 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (2 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (3 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (4 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (5 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (6 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (7 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (8 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (9 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (10 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (11 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (12 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (13 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (14 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (15 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (16 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (17 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (18 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (19 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (20 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:15:56 Retrying (21)... W 22:15:59 Retry Failed - Reason: Invalid Address For Write W 22:16:11 Retrying (22)... W 22:16:11 Retry Failed - Reason: Invalid Address For Write W 22:16:12 Retrying (23)... W 22:16:12 Retry Failed - Reason: Invalid Address For Write W 22:16:19 Retrying (24)... W 22:16:19 Retry Failed - Reason: Invalid Address For Write W 22:16:20 Retrying (25)... W 22:16:20 Retry Failed - Reason: Invalid Address For Write W 22:16:20 Retrying (26)... W 22:16:20 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (27)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (28)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (29)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (30)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (31)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (32)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:23 Retrying (33)... W 22:16:23 Retry Failed - Reason: Invalid Address For Write W 22:16:23 Retrying (34)... W 22:16:23 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (35)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (36)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (37)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:25 Retrying (38)... W 22:16:25 Retry Failed - Reason: Invalid Address For Write E 22:16:41 Failed to Write Sectors 12498976 - 12499007 - Reason: Write Error E 22:16:41 Next Writable Address: 0 I 22:16:41 Synchronising Cache... W 22:16:45 User opted to skip the 'Close Track/Session/Disc' functions. E 22:16:45 Failed to Write Image! I 22:16:45 Exporting Graph Data... I 22:16:45 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_9-45_PM_VERBAT-IMf-000_4x.ibg I 22:16:45 Export Successfully Completed! E 22:16:45 Operation Failed! - Duration: 00:31:21 I 22:16:45 Average Write Rate: 13,541 KiB/s (3.1x) - Maximum Write Rate: 17,917 KiB/s (4.1x) I 22:18:27 Operation Started! I 22:18:27 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 22:18:27 Source File Sectors: 22,447,264 (MODE1/2048) I 22:18:27 Source File Size: 45,971,996,672 bytes I 22:18:27 Source File Volume Identifier: 4K80 I 22:18:27 Source File Volume Set Identifier: 586DB1C6015683D8 I 22:18:27 Source File Application Identifier: ImgBurn v2.5.8.0 I 22:18:27 Source File Implementation Identifier: ImgBurn I 22:18:27 Source File File System(s): UDF (2.50) I 22:18:27 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 22:18:27 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 22:18:27 Destination Media Supported Write Speeds: 2x, 4x, 6x I 22:18:27 Destination Media Sectors: 24,438,784 I 22:18:27 Write Mode: BD I 22:18:27 Write Type: DAO I 22:18:27 Write Speed: 4x I 22:18:27 Hardware Defect Management Active: No I 22:18:27 BD-R Verify Not Required: Yes I 22:18:27 Link Size: Auto I 22:18:27 Lock Volume: Yes I 22:18:27 Test Mode: No I 22:18:27 OPC: No I 22:18:27 BURN-Proof: Enabled I 22:18:27 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 22:18:58 Filling Buffer... (80 MiB) I 22:18:59 Writing LeadIn... I 22:19:00 Writing Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 22:19:00 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 22:19:00 Writing Layer 0... (LBA: 0 - 12219391) I 22:42:10 Writing Layer 1... (LBA: 12219392 - 22447263) W 22:45:32 Failed to Write Sectors 13809728 - 13809759 - Reason: Write Error W 22:45:33 Retrying (1 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (2 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (3 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (4 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (5 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (6 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (7 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (8 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (9 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (10 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (11 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (12 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (13 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (14 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (15 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (16 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (17 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (18 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (19 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (20 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:56:26 Retrying (21)... W 22:56:29 Retry Failed - Reason: Invalid Address For Write E 22:56:32 Failed to Write Sectors 13809728 - 13809759 - Reason: Write Error E 22:56:32 Next Writable Address: 0 I 22:56:32 Synchronising Cache... W 22:56:34 User opted to skip the 'Close Track/Session/Disc' functions. E 22:56:34 Failed to Write Image! I 22:56:34 Exporting Graph Data... I 22:56:34 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-18_PM_VERBAT-IMf-000_4x.ibg I 22:56:34 Export Successfully Completed! E 22:56:34 Operation Failed! - Duration: 00:38:07 I 22:56:34 Average Write Rate: 12,269 KiB/s (2.8x) - Maximum Write Rate: 17,923 KiB/s (4.1x) I 22:58:05 Operation Started! I 22:58:05 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 22:58:05 Source File Sectors: 22,447,264 (MODE1/2048) I 22:58:05 Source File Size: 45,971,996,672 bytes I 22:58:05 Source File Volume Identifier: 4K80 I 22:58:05 Source File Volume Set Identifier: 586DB1C6015683D8 I 22:58:05 Source File Application Identifier: ImgBurn v2.5.8.0 I 22:58:05 Source File Implementation Identifier: ImgBurn I 22:58:05 Source File File System(s): UDF (2.50) I 22:58:05 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 22:58:05 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 22:58:05 Destination Media Supported Write Speeds: 2x, 4x, 6x I 22:58:05 Destination Media Sectors: 24,438,784 I 22:58:05 Write Mode: BD I 22:58:05 Write Type: DAO I 22:58:05 Write Speed: MAX I 22:58:05 Hardware Defect Management Active: No I 22:58:05 BD-R Verify Not Required: Yes I 22:58:05 Link Size: Auto I 22:58:05 Lock Volume: Yes I 22:58:05 Test Mode: No I 22:58:05 OPC: No I 22:58:05 BURN-Proof: Enabled I 22:58:05 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x) I 22:58:36 Filling Buffer... (80 MiB) I 22:58:36 Writing LeadIn... I 22:58:44 Writing Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 22:58:44 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 22:58:44 Writing Layer 0... (LBA: 0 - 12219391) I 23:14:29 Writing Layer 1... (LBA: 12219392 - 22447263) I 23:27:38 Synchronising Cache... I 23:27:42 Closing Track... I 23:27:43 Finalising Disc... I 23:28:19 Exporting Graph Data... I 23:28:19 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-58_PM_VERBAT-IMf-000_MAX.ibg I 23:28:19 Export Successfully Completed! I 23:28:19 Operation Successfully Completed! - Duration: 00:30:14 I 23:28:19 Average Write Rate: 25,905 KiB/s (5.9x) - Maximum Write Rate: 26,740 KiB/s (6.1x) I 23:28:19 Cycling Tray before Verify... W 23:28:27 Waiting for device to become ready... I 23:29:02 Device Ready! I 23:29:06 Operation Started! I 23:29:06 Source Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 23:29:06 Source Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 23:29:06 Source Media Supported Read Speeds: 2x, 4x, 6x, 8x I 23:29:06 Source Media Supported Write Speeds: 2x, 4x, 6x I 23:29:07 Source Media Sectors: 22,447,264 I 23:29:07 Source Media Size: 45,971,996,672 bytes I 23:29:07 Image File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 23:29:07 Image File Sectors: 22,447,264 (MODE1/2048) I 23:29:07 Image File Size: 45,971,996,672 bytes I 23:29:07 Image File Volume Identifier: 4K80 I 23:29:07 Image File Volume Set Identifier: 586DB1C6015683D8 I 23:29:07 Image File Application Identifier: ImgBurn v2.5.8.0 I 23:29:07 Image File Implementation Identifier: ImgBurn I 23:29:07 Image File File System(s): UDF (2.50) I 23:29:07 Read Speed (Data/Audio): MAX / MAX I 23:29:08 Read Speed - Effective: 3x - 8x, 8x - 3x I 23:29:08 Verifying Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 23:29:08 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 23:29:08 Verifying Layer 0... (LBA: 0 - 12219391) I 23:45:16 Verifying Layer 1... (LBA: 12219392 - 22447263) W 23:45:25 Failed to Read Sectors 12219392 - 12219423 - Reason: L-EC Uncorrectable Error W 23:45:33 Failed to Read Sector 12219392 - Reason: L-EC Uncorrectable Error W 23:45:33 Sector 12219392 maps to File: \BDMV\STREAM\00021.m2ts W 23:49:16 Retrying (1)... W 23:49:25 Retry Failed - Reason: Timeout on Logical Unit E 23:49:27 Failed to Read Sector 12219392 - Reason: L-EC Uncorrectable Error E 23:49:27 Sector 12219392 maps to File: \BDMV\STREAM\00021.m2ts E 23:49:28 Failed to Verify Sectors! I 23:49:29 Exporting Graph Data... I 23:49:29 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-58_PM_VERBAT-IMf-000_MAX.ibg I 23:49:29 Export Successfully Completed! E 23:49:29 Operation Failed! - Duration: 00:20:21 I 23:49:29 Average Verify Rate: 20,048 KiB/s (4.6x) - Maximum Verify Rate: 36,105 KiB/s (8.2x) I 23:49:31 Close Request Acknowledged I 23:49:31 Closing Down... I 23:49:31 Shutting down SPTI... I 23:49:31 ImgBurn closed! HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_9-45_PM_VERBAT-IMf-000_4x.ibg

While it seems madFLAC is pretty standard with ImgBurn, while not as convenient, I use Foobar2000 to convert FLAC back to standard WAV temporarily anytime I want to burn a standard Audio CD. but on Linux it appears I don't have much choice as, at least to my knowledge, madFLAC can't be setup on ImgBurn on Linux. so my ImgBurn is just on a basic installation which it can directly use WAV files without issue. so I guess the general point is... even if you can't get any special stuff (madFLAC etc) working with ImgBurn, as long as ImgBurn installs and it's basic function works, you can do what I do to create a standard Audio CD with ImgBurn.

I bought a music box-set that contains a number of discs (CD, DVD Audio, Blu-ray audio). To prevent damage to the originals, I would like to create 1:1 disc clones (as my personal copies, ie. not for resale) and play those instead of my originals. Some of these formats contain 24bit/96kHz uncompressed, 24bit/192kHz uncompressed, 24-bit/48 kHz uncompressed, Dolby Digital @448 kbps, Dolby Digital @640 kbps. Can someone direct me on how I can create exact 1:1 copies. Thanks.(I'm located in Canada)

Hello experts. I'm in need of create image file from optical disc in these 3 formats: dmg , pdi , gi It was on the list of ImgBurn supported formats, not sure if is read only or write also supported? If not, please advise which Windows software can do it? Or anywhere we can download a small disc image in dmg , pdi , gi formats? Thankssssss

Good morning to the whole community. I'm trying to understand where is the mistake I'm making even though I have dozens of tests without a correct result, that is, I can't boot the ISO created from a bootable USB pen drive. Premise I downloaded Kaspersky Rescue Disk. The file is an ISO. I install the ISO on the pen drive through RUFUS. The pen drive is bootable and its operation is correct (tested on PC after bios post and before the operating system). Problem How do I get the reverse process now? That is, through imgburn I want to create a bootable ISO starting from the pen drive. Resolution (currently unsolved). Obviously I start the ImgBurn program, click on creating a new image from files/folders. I select the source letter of the pen drive, select the advanced tab, then select the bootable disk tab. I activate the make a bootable disk flag Now I tried to extract the boot image and insert it into the boot image. Start the creation of the ISO but the newly created file is not bootable (tested with a virtual machine) while the original ISO works correctly (again tested with a virtual machine). I also tried looking for a boot image from the disk, but I can't figure out which file to select and if there is any other flag or value I need to set This helps me understand which are the correct settings I need to use. The problem is that some programs allow you to directly create a bootable USB pen drive without the possibility of having an ISO to manage instead. Where is the error? Thank you

This isn't really a bug, per se. More like a request to adjust disc type determination logic. Here's the scenario: I was trying to create a DVD Video disc with a VIDEO_TS in the root directory. The root directory also had an AVI file in it. ImgBurn detected the VIDEO_TS folder and then asked me if I wanted to make a DVD Video disc, which I said yes to. ImgBurn THEN detected the AVI file and asked me if I wanted to make a Divx Disc. I said no to that. Should the ImgBurn logic in this case determine if the user makes one choice, like in the above situation, it should refrain from asking to change the disc type again? Thanks!

Hello people! I was burning some soundtracks onto CD's (using Microsoft Media Player for Windows 7) and i wanted to create a .CUE file of the CD so i can add track info and burn it o another CD. While the first one was created flawlessly, the other CD gets stuck while analizing Track 14. They both have the same amount of tracks and they are the exact same CD (HP Branded CD-R). Is the second disc faulty? or do i need to use another software? Also, here's the ImgBurn Log: I 15:04:23 ImgBurn Version 2.5.8.0 started! I 15:04:23 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 15:04:23 Total Physical Memory: 4.104.848 KiB - Available: 2.138.652 KiB I 15:04:23 Initialising SPTI... I 15:04:23 Searching for SCSI / ATAPI devices... I 15:04:23 -> Drive 1 - Info: ATAPI iHAS122 ZL0C (A:) (ATA) I 15:04:23 Found 1 DVD±RW/RAM! I 15:17:52 Operation Started! I 15:17:52 Source Device: [2:0:0] ATAPI iHAS122 ZL0C (A:) (ATA) I 15:17:52 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) I 15:17:52 Source Media Supported Read Speeds: 4x; 8x; 10x; 16x; 24x; 32x; 40x; 48x I 15:17:52 Source Media Supported Write Speeds: 16x; 24x; 32x; 40x; 48x I 15:17:52 Source Media Sectors: 308.661 I 15:17:52 Source Media Size: 725.970.672 bytes I 15:17:52 Source Media File System(s): None I 15:17:52 Read Speed (Data/Audio): MAX / 1x I 15:17:52 Destination File: C:\Users\exper\Desktop\dfwsef.bin I 15:17:52 Destination Free Space: 5.190.152.192 Bytes (5.068.508,00 KiB) (4.949,71 MiB) (4,83 GiB) I 15:17:52 Destination File System: NTFS I 15:17:52 File Splitting: Auto I 15:18:45 Abort Request Acknowledged E 15:18:46 Operation Aborted! - Duration: 00:00:53 E 15:18:46 Average Read Rate: N/A - Maximum Read Rate: N/A

I need clarification of Section 3.3.2.3.4 Bootable Disk settings. First and foremost I want to say that, in general, the documentation, tutorials, and guides are exceptional. There does seem to be a tendency to assume the audience is of direct peer quality, or close. On many occasions it taxes the critical thinking and comprehension, even those of us with IQ’s in the 99 percentile. This subject matter is not my forte, therefore I dabble, and sometimes dribble due to this, all from necessity. A few things that are not explained in the guides or found in the forums (at least I haven’t found relevance after looking for days). The article and related articles: How to create a Windows Vista / 7 / 8 installation disc (bootable) using ImgBurn, are the only things I have to go on. They don’t cover my needs or questions sufficiently. When creating a bootable disk the Platform ID is not explained. I understand what 80x86 means, and Power PC is, well, they might still be out there, and UEFI is the new-new ride. My question comes from trying to create a bootable OS DVD that contains multiple operating systems in both X86 and X64 versions. How do you make something like that – or does it matter from a BIOS or UEFI standpoint? I guess here, since there are no multiple options – you use the base machine “type”. Is this true? The “Patch Boot Information Table” is not explained anywhere except in the most vague of terms and only superficially. Only something about boot files larger than 1 MB. Under what condition would a boot table become larger than 1 MB? Is this to enable chain loading of the MBR into BIO’s? The “Extract Boot Image” is also not explained. I am guessing it copies the image from an existing image like the one already used on your C: drive, or one you were able to copy from another system. A little more detail would be nice. Is the boot image different between 32 and 64 bit machines? I would think not – not for an OS install disk, even with X86 and X64 options, but what does an oilseed engineer know? “Load Segment” is not discussed, there is only, “I get mine from the ImgBurn log”. Really vague. What is the significance of this value? Granted – you’re not here to give massive lectures on the finer points of computer science or software engineering. I’d like to be able to follow directions on using a complicated piece of software and learn along the way – not be given a complicated tool with part of the instructions, and told to fix the reactor (I think they did that with Fukushima) –Ops… Crap! You get my point… – Thank you.

Would it be possible to put in the settings (or on the GUI) an option to toggle all the file size/free space/image size dislpays between >bytes>Mbytes>Gbytes. I think it would make things easier for some, especially for the newbies who don't know to divide by 1024. Plus it's easier to make your target disc size at a glance when doing backups.

The Device Buffer is self explanatory to me, but I am curious as to what the Image Buffer precisely is. Thanks!

ImngBurn can create such an ISO, but whether that ISO will backup all files is questionable. And whether that ISO can be made "bootable" in a virtual machine or run as a Windows installation I wouldn't know. I've never done any virtualization, so I know nothing about VirtualBox.

the basis of this thread is creating an ISO file from a bootable USB pen drive. I started from the Kaspersky Rescu Disk base because I had the test ISO and it is available for anyone who wants to answer me and find a solution. It is obvious that if I have an ISO that without it I have to create a bootable USB pen drive and then create the ISO again. I actually have a bootable USB stick with the OnTrack EasyRecovery program bootable. The program itself creates this bootable USB pen drive. There is no ISO that I could handle differently. So here's the dilemma. So like in the first post, I have a bootable USB pen drive and I want to get a bootable ISO file. There are also other programs that allow you to create bootable pen drives but do not create ISOs. Now if it exists (and I think so, perhaps we need to look in the boot image for the solution) let's try to find the solution. Thank you all

With creating a bootable ISO from a set of files and a bootable image extract: nothing. What I do is with a bootable flash drive, I use a piece of paid software called Macrium Reflect to image the flash drive. It doesn't create ISO's though, but a proprietary file format it can write to flash drives.

The game is Policenauts, and the image for each disc comes with an ISO, a WAV file, and a CUE file. The CUE file specifies the correct file names, and it seems like the ISO burns fine. However, when it gets to the wav file, I get a directshow error: "DirectShow Error! - IMediaEvent::WaitForCompletion File Name: <file path>.wav" Index Progress: 4,233,600 bytes Index size: 4,461,744 bytes Reason: An operation was aborted because of an error. (0x00000003) Would you like to continue anyway and fill the remainder of this Index with digital silence?" I am on Windows 11, and other Saturn games have burned just fine, though usually they only contain one or more BIN files and a CUE pointing to them. This is the first time I've burned a game in ISO format, and the first time it's included a separate WAV file. The game launches just fine. The WAV file is short, plays fine on my computer, and doesn't seem that important (I speak some Japanese, and it seems to be a message that plays when you put the disc in a CD player, telling you to that it's for use in a Sega Saturn instead), but I'd still like the games to burn properly. It's a very minor issue, but still. I searched the forum for similar problems, and someone had the issue of having converted MP3 files to WAV, and getting a similar error. That person's solution was to burn the MP3 files without converting them to WAV, as either way, imgburn has to convert the audio file to CD-AUDIO during the burn. However, the image I have for Policenauts only comes with a WAV file for each disc, so I'm not doing any conversion before I start the burn. I know directshow filters for WAV files are supposed to be built into Windows, but perhaps they've been removed on Windows 11? A Microsoft help page for app development states that directshow has been "superseded by MediaPlayer, IMFMediaEngine, and Audio/Video Capture in Media Foundation," though I'm not 100% sure what that means. What can I do? EDIT: Okay! I stuck the game in a CD player, and the wav file is there, telling me in Japanese that the game is supposed to go into a Sega Saturn. So it's being written to the disc. I guess this isn't a problem at all. So why am I getting this error, and what does it mean?? I'm confused, but I guess this turned out to be a nonissue after all.

I would say so. PS1 games were on CD where layer breaks weren't a concern. However, I can't recall seeing .MDS ever associated with a PS 1 game CD image. Of course, I'm just going by ImgBurn, which I can't remember that it used MDS in its file set, but maybe it did.

Can ImgBurn create an ISO of an existing Windows10 OS Hard Drive that has 3rd party apps already installed beforehand? My plan is to take this Win10 ISO and use it inside of a VirtualBox VM I have running in Linux Mint. Will my idea work? I ask because I am uncertain if ImgBurn can create an ISO of an existing Win10 OS. And also whether VirtualBox will accept such an ISO. If ImgBurn cannot create such an ISO please share any alternatives that may work. Any opinions welcome.

Thanks for that Microsoft account workaround! I knew it existed, but I couldn't recall what it was. My setup is okay as it was a Windows 10 that I created back when local accounts were possible and upgraded to Windows 11. But, on my next new PC, I wanted to create a local account, but couldn't remember how to do it.

Sorry for the late reply as I just noticed your post here a week later. anyways, I took a quick look online and I think I found the Reddit post you mentioned which is about 5 months ago. when I did my HWID stuff it was late October 2023. so less than 5 months ago when I did the HWID activation. but for kicks I installed Windows 10 in a fresh QEMU/KVM VM a moment ago. then checked activation status, which is not activated as expected, then I tried that HWID method and... it worked ; you can clearly see it's activated... 'Activation Windows is activated with a digital license'. before that it was in red saying it was not activated etc. but just to make sure the HWID activation method also still works on Win11, I tried Windows 11 on a fresh VM a moment ago and checked activation status and said not activated. then I ran the HWID method and it shows 'Windows is activated with a digital license'. just to do one last test to confirm it lasts... I completely deleted the VM's virtual hard drive and created one fresh, but used the same UUID when it was activated a moment ago on the previous VM's virtual hard drive, and... it still worked as you install Win11, skip over the activation part when it asks, then once you reach the desktop I checked activation status and it's activated with no further action needed on my end. so in short... that HWID still works on Win10/11. TIP: to dodge Microsoft's 'forced' Microsoft account junk just type in 'no at thankyou dot com' (with 'at' being '@' and 'dot' being '.') and then enter any random password (it does not matter what it is and you don't even need to remember it) and it will error shortly after that and allow a local account instead (which you then create with your own password like usual which you want to remember) as I saw that on another site and heard it worked but I never tried that until now and it worked exactly as they said.

I have a 4.7gb DVD-R and when I tried to burn a Windows 10 ISO to it, imgburn said Disc Not Empty. I accidentally selected USB mode when windows told me and when I use format with imgburn it doesnt show DVD-R option. And when I try to burn with windows image burner it ejects the disc automatically. I dont have any other DVDs and I dont know if I screwed myself as I really need to recover my laptop. Is there any way to burn a windows 10 ISO file to it now??

That must be a older Windows 10 ISO as they have been too big to fit onto a standard 4.7GB for years now. you are better off setting up a bootable USB stick, 8GB will work. then just get the latest official ISO from Microsoft's website or use the Media Creation Tool etc.

Thanks Lightning for such a great tool and for your great support! Sorry to dig up such an old post, but I was seeking answers to a couple of the same questions, so glad that after some careful reading (including the URL you linked), things slowly became clearer for me. Thank you! Just a suggestion, which you are free to ignore, would be to make the following minor text changes under the Bootable Disc tab : Patch Boot Information Table -> Patch Boot Information Table (isolinux) Extract Boot Image -> Extract a Boot Image This would make it a little more obvious what these two items are, and whether they're relevant. So in my case, it would then be clear that I didn't need the Patch Boot Information Table option, and that the Extract Boot Image selection wasn't asking for some kind of image file, but was a little tool to create such a file (presumably to use in the Boot Image selection above). Joe.

Probably the program you are referring to is ventoy (open source). A utility that formats the USB pen drive and makes it multi-bootable. The program partitions the drive into two parts, the first with a very small operating system, the second available for the user to copy multiple bootable ISOs inside. Unfortunately OnTrack EasyRecovery does not create CDs or ISOs but only bootable USB pen drives. Extracting the files for a bootable ISO from the pen drive would be much more malleable and flexible as a solution, because an ISO can be managed much more easily without tying up a pen drive for a long time.

I remember doing a search online towards the end of last year for something to make ISO's from bootable flash drives. I had this application that would create a bootable flash drive and then you could select ISO's from the flash drive for booting from. That way, you don't need multiple flash drives, just multiple ISO's on one flash drive. I found nothing that could make ISO's, like you said. And as I said, Macrium Reflect does not create ISO's. It instead uses a proprietary format. Is there a particular reason why you need ISO specifically and that any of those other program's read file formats aren't suitable?

If you have a bootable ISO you downloaded and wrote to a USB flash drive, why do you want to create a new bootable ISO? Did you add files to the flash drive and want them rolled up into a new bootable ISO? If so, for that, I use a piece of paid software called UltraISO. It allows you to inject files into an existing ISO.

Well, very few people actually patrol the forums much anymore. So, you're probably not likely to get another answer. In the meantime, if you haven't tried this already, see this Guide: Unfortunately, this guide is fairly old and it was what I followed to try and create bootable ISO's that never booted.