Search the Community

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.

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

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!

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)

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.

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.

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.

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??

Here is the OP's log.txt for those who don't want to download it... I 20:50:22 ImgBurn Version 2.5.8.0 started! I 20:50:22 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 20:50:22 Total Physical Memory: 33,480,684 KiB - Available: 23,953,008 KiB I 20:50:22 Initialising SPTI... I 20:50:22 Searching for SCSI / ATAPI devices... I 20:50:22 -> Drive 1 - Info: HL-DT-ST BD-RE BP60NB10 1.02 (F:) (USB 2.0) I 20:50:22 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (E:) (SCSI) I 20:50:22 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 20:51:55 Operation Started! I 20:51:55 Source Device: [0:0:0] HL-DT-ST BD-RE BP60NB10 1.02 (F:) (USB) I 20:51:55 Source Media Type: CD-ROM I 20:51:55 Source Media Supported Read Speeds: 4x, 10x, 16x, 20x, 24x I 20:51:55 Source Media Supported Write Speeds: 24x I 20:51:55 Source Media Sectors: 333,000 I 20:51:55 Source Media Size: 783,216,000 bytes I 20:51:55 Source Media Volume Identifier: AIR_ALL_ORANGE I 20:51:55 Source Media File System(s): ISO9660 (Bootable), Joliet I 20:51:55 Read Speed (Data/Audio): MAX / 8x I 20:51:55 Destination File: D:\AIR_ALL_ORANGE.BIN I 20:51:55 Destination Free Space: 861,445,029,888 Bytes (841,254,912.00 KiB) (821,538.00 MiB) (802.28 GiB) I 20:51:55 Destination File System: EXFAT I 20:51:55 File Splitting: Auto I think I had a similar issue in the past with ImgBurn hanging on the analyzing tracks part. but in my case it was when reading a CD-RW disc, which those discs were pretty much faulty as once I got different ones it seemed to be okay after that on same drive. off the top of my head... try another CD/DVD reader if possible on that same CD as it could be possible your current reader has trouble reading it and may work okay on other drives.

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.

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.

drive: VERBATIM External CD / DVD / Blu-ray Writer (model 71097) [https://www.amazon.ca/dp/B09PY6SC9Y] media: VERBATIM M-Disc BDXL 100GB 4x [https://www.amazon.ca/dp/B017H13D62] i've gone through four discs so far, and at almost $400 a spindle, i'm reluctant to continue. what i've done: first attempt: tried to write files to disc. failed at 34% second attempt: tried to write files to disc again thinking something must just have gone wrong the first time. failed at 34% third attempt: copied everything to a different laptop, and tried writing files again. failed at 34% fourth attempt: did some research online, and tried creating an ISO with UDF 2.60 selected. copied files back to the first laptop, and tried burning again. failed at 68% all of this is new to me (CDs / DVDs are the extent of my prior experience), and i'm not sure if it's the drive, the media, both, or something else thanks in advance for any / all help log file from the most recent attempt: ; //****************************************\\ ; ImgBurn Version 2.5.8.0 - Log ; Tuesday, 06 February 2024, 16:19:37 ; \\****************************************// ; ; I 00:12:07 ImgBurn Version 2.5.8.0 started! I 00:12:07 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 00:12:07 Total Physical Memory: 16,219,512 KiB - Available: 14,091,400 KiB I 00:12:08 Initialising SPTI... I 00:12:08 Searching for SCSI / ATAPI devices... E 00:12:08 Failed to check for ImgBurn update! I 00:12:08 -> Drive 1 - Info: PLDS DVD-RW DA8AESH XL6M (D:) (SATA) I 00:12:08 Found 1 DVD±RW! W 00:12:15 Device Arrival Detected! I 00:12:16 Searching for SCSI / ATAPI devices... I 00:12:16 -> Drive 1 - Info: PLDS DVD-RW DA8AESH XL6M (D:) (SATA) I 00:12:17 -> Drive 2 - Info: PIONEER BD-RW BDR-UD03 1.14-GENERAL (E:) (USB 2.0) I 00:12:17 Found 1 DVD±RW and 1 BD-RE XL! I 00:14:49 Operation Started! I 00:14:49 Source File: C:\audiorec.iso I 00:14:49 Source File Sectors: 47,334,112 (MODE1/2048) I 00:14:49 Source File Size: 96,940,261,376 bytes I 00:14:49 Source File Volume Identifier: AUDIOREC_D1 I 00:14:49 Source File Volume Set Identifier: 58426F5002D240AE I 00:14:49 Source File Application Identifier: ImgBurn v2.5.8.0 I 00:14:49 Source File Implementation Identifier: ImgBurn I 00:14:49 Source File File System(s): UDF (2.60) I 00:14:49 Destination Device: [0:0:0] PIONEER BD-RW BDR-UD03 1.14 (E:) (USB) I 00:14:49 Destination Media Type: BD-R (Disc ID: VERBAT-IMk-000) I 00:14:49 Destination Media Supported Write Speeds: 2x, 4x I 00:14:49 Destination Media Sectors: 48,878,592 I 00:14:49 Write Mode: BD I 00:14:49 Write Type: Incremental I 00:14:49 Write Speed: 4x I 00:14:49 Hardware Defect Management Active: No I 00:14:49 BD-R Verify Not Required: Yes I 00:14:49 Link Size: Auto I 00:14:49 Lock Volume: Yes I 00:14:49 Test Mode: No I 00:14:49 OPC: No I 00:14:49 BURN-Proof: Enabled I 00:14:50 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x) I 00:14:50 Advanced Settings - Optimal Writing Speed: No I 00:14:50 Filling Buffer... (80 MiB) I 00:14:51 Writing LeadIn... I 00:15:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 47334111) I 00:15:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 47334111) W 00:32:08 Failed to Write Sectors 4505376 - 4505407 - Reason: The semaphore timeout period has expired. W 00:32:08 Retrying (1 of 20)... I 00:32:08 Writing Sectors... W 00:32:12 Failed to Write Sectors 4539680 - 4539711 - Reason: The semaphore timeout period has expired. W 00:32:12 Retrying (1 of 20)... I 00:32:12 Writing Sectors... W 00:32:21 Failed to Write Sectors 4614272 - 4614303 - Reason: The semaphore timeout period has expired. W 00:32:21 Retrying (1 of 20)... I 00:32:23 Writing Sectors... W 00:32:33 Failed to Write Sectors 4701216 - 4701247 - Reason: The semaphore timeout period has expired. W 00:32:33 Retrying (1 of 20)... I 00:32:35 Writing Sectors... W 00:33:54 Failed to Write Sectors 5283584 - 5283615 - Reason: The semaphore timeout period has expired. W 00:33:54 Retrying (1 of 20)... I 00:33:55 Writing Sectors... W 00:34:12 Failed to Write Sectors 5430880 - 5430911 - Reason: The semaphore timeout period has expired. W 00:34:12 Retrying (1 of 20)... I 00:34:16 Writing Sectors... W 00:34:17 Failed to Write Sectors 5442400 - 5442431 - Reason: The semaphore timeout period has expired. W 00:34:17 Retrying (1 of 20)... I 00:34:17 Writing Sectors... W 00:35:05 Failed to Write Sectors 5790400 - 5790431 - Reason: The semaphore timeout period has expired. W 00:35:05 Retrying (1 of 20)... I 00:35:05 Writing Sectors... W 00:35:08 Failed to Write Sectors 5814944 - 5814975 - Reason: The semaphore timeout period has expired. W 00:35:08 Retrying (1 of 20)... I 00:35:09 Writing Sectors... W 00:35:28 Failed to Write Sectors 5982144 - 5982175 - Reason: The semaphore timeout period has expired. W 00:35:28 Retrying (1 of 20)... I 00:35:32 Writing Sectors... W 00:35:53 Failed to Write Sectors 6127904 - 6127935 - Reason: The semaphore timeout period has expired. W 00:35:53 Retrying (1 of 20)... I 00:35:55 Writing Sectors... W 00:39:10 Failed to Write Sectors 7589344 - 7589375 - Reason: The semaphore timeout period has expired. W 00:39:10 Retrying (1 of 20)... I 00:39:15 Writing Sectors... W 00:39:58 Failed to Write Sectors 7901056 - 7901087 - Reason: The semaphore timeout period has expired. W 00:39:58 Retrying (1 of 20)... I 00:39:58 Writing Sectors... W 00:40:00 Failed to Write Sectors 7911552 - 7911583 - Reason: The semaphore timeout period has expired. W 00:40:00 Retrying (1 of 20)... I 00:40:00 Writing Sectors... W 00:40:09 Failed to Write Sectors 7987648 - 7987679 - Reason: The semaphore timeout period has expired. W 00:40:09 Retrying (1 of 20)... I 00:40:11 Writing Sectors... W 00:40:53 Failed to Write Sectors 8324128 - 8324159 - Reason: The semaphore timeout period has expired. W 00:40:53 Retrying (1 of 20)... I 00:40:57 Writing Sectors... W 00:41:52 Failed to Write Sectors 8732352 - 8732383 - Reason: The semaphore timeout period has expired. W 00:41:52 Retrying (1 of 20)... I 00:41:53 Writing Sectors... W 00:42:24 Failed to Write Sectors 8956864 - 8956895 - Reason: The semaphore timeout period has expired. W 00:42:24 Retrying (1 of 20)... I 00:42:25 Writing Sectors... W 00:42:45 Failed to Write Sectors 9139136 - 9139167 - Reason: The semaphore timeout period has expired. W 00:42:45 Retrying (1 of 20)... I 00:42:50 Writing Sectors... W 00:45:35 Failed to Write Sectors 10353056 - 10353087 - Reason: The semaphore timeout period has expired. W 00:45:35 Retrying (1 of 20)... I 00:45:38 Writing Sectors... W 00:46:38 Failed to Write Sectors 10793920 - 10793951 - Reason: The semaphore timeout period has expired. W 00:46:38 Retrying (1 of 20)... I 00:46:38 Writing Sectors... W 00:46:40 Failed to Write Sectors 10805472 - 10805503 - Reason: The semaphore timeout period has expired. W 00:46:40 Retrying (1 of 20)... I 00:46:40 Writing Sectors... W 00:46:59 Failed to Write Sectors 10972704 - 10972735 - Reason: The semaphore timeout period has expired. W 00:46:59 Retrying (1 of 20)... I 00:47:03 Writing Sectors... W 00:48:04 Failed to Write Sectors 11441536 - 11441567 - Reason: The semaphore timeout period has expired. W 00:48:04 Retrying (1 of 20)... I 00:48:08 Writing Sectors... W 00:48:32 Failed to Write Sectors 11628928 - 11628959 - Reason: The semaphore timeout period has expired. W 00:48:32 Retrying (1 of 20)... I 00:48:34 Writing Sectors... W 00:48:44 Failed to Write Sectors 11718496 - 11718527 - Reason: The semaphore timeout period has expired. W 00:48:44 Retrying (1 of 20)... I 00:48:46 Writing Sectors... W 00:48:54 Failed to Write Sectors 11785472 - 11785503 - Reason: The semaphore timeout period has expired. W 00:48:54 Retrying (1 of 20)... I 00:48:56 Writing Sectors... W 00:49:10 Failed to Write Sectors 11905408 - 11905439 - Reason: The semaphore timeout period has expired. W 00:49:10 Retrying (1 of 20)... I 00:49:12 Writing Sectors... W 00:49:19 Failed to Write Sectors 11962464 - 11962495 - Reason: The semaphore timeout period has expired. W 00:49:19 Retrying (1 of 20)... I 00:49:20 Writing Sectors... W 00:49:54 Failed to Write Sectors 12234400 - 12234431 - Reason: The semaphore timeout period has expired. W 00:49:55 Retrying (1 of 20)... I 00:49:58 Writing Sectors... W 00:50:40 Failed to Write Sectors 12575360 - 12575391 - Reason: The semaphore timeout period has expired. W 00:50:40 Retrying (1 of 20)... I 00:50:45 Writing Sectors... W 00:52:23 Failed to Write Sectors 13297920 - 13297951 - Reason: The semaphore timeout period has expired. W 00:52:23 Retrying (1 of 20)... I 00:52:27 Writing Sectors... W 00:53:43 Failed to Write Sectors 13890688 - 13890719 - Reason: The semaphore timeout period has expired. W 00:53:43 Retrying (1 of 20)... I 00:53:48 Writing Sectors... W 00:53:50 Failed to Write Sectors 13905984 - 13906015 - Reason: The semaphore timeout period has expired. W 00:53:50 Retrying (1 of 20)... I 00:53:51 Writing Sectors... W 00:53:54 Failed to Write Sectors 13926464 - 13926495 - Reason: The semaphore timeout period has expired. W 00:53:54 Retrying (1 of 20)... I 00:53:54 Writing Sectors... W 00:53:54 Failed to Write Sectors 13928672 - 13928703 - Reason: The semaphore timeout period has expired. W 00:53:54 Retrying (1 of 20)... I 00:53:54 Writing Sectors... W 00:54:06 Failed to Write Sectors 14026976 - 14027007 - Reason: The semaphore timeout period has expired. W 00:54:06 Retrying (1 of 20)... I 00:54:08 Writing Sectors... W 00:54:08 Failed to Write Sectors 14029056 - 14029087 - Reason: The semaphore timeout period has expired. W 00:54:08 Retrying (1 of 20)... I 00:54:09 Writing Sectors... W 00:54:22 Failed to Write Sectors 14149568 - 14149599 - Reason: The semaphore timeout period has expired. W 00:54:22 Retrying (1 of 20)... I 00:54:25 Writing Sectors... W 00:54:36 Failed to Write Sectors 14229888 - 14229919 - Reason: The semaphore timeout period has expired. W 00:54:36 Retrying (1 of 20)... I 00:54:37 Writing Sectors... W 00:54:59 Failed to Write Sectors 14397728 - 14397759 - Reason: The semaphore timeout period has expired. W 00:54:59 Retrying (1 of 20)... I 00:55:01 Writing Sectors... W 00:55:37 Failed to Write Sectors 14700032 - 14700063 - Reason: The semaphore timeout period has expired. W 00:55:37 Retrying (1 of 20)... I 00:55:42 Writing Sectors... W 00:57:52 Failed to Write Sectors 15662816 - 15662847 - Reason: The semaphore timeout period has expired. W 00:57:52 Retrying (1 of 20)... I 00:57:55 Writing Sectors... W 00:59:00 Failed to Write Sectors 16160000 - 16160031 - Reason: The semaphore timeout period has expired. W 00:59:01 Retrying (1 of 20)... I 00:59:04 Writing Sectors... W 01:00:34 Failed to Write Sectors 16758560 - 16758591 - Reason: The semaphore timeout period has expired. W 01:00:35 Retrying (1 of 20)... I 01:00:35 Writing Sectors... W 01:00:36 Failed to Write Sectors 16769344 - 16769375 - Reason: The semaphore timeout period has expired. W 01:00:36 Retrying (1 of 20)... I 01:00:36 Writing Sectors... W 01:00:44 Failed to Write Sectors 16825920 - 16825951 - Reason: The semaphore timeout period has expired. W 01:00:44 Retrying (1 of 20)... I 01:00:44 Writing Sectors... W 01:00:51 Failed to Write Sectors 16880736 - 16880767 - Reason: The semaphore timeout period has expired. W 01:00:51 Retrying (1 of 20)... I 01:00:52 Writing Sectors... W 01:01:06 Failed to Write Sectors 17001056 - 17001087 - Reason: The semaphore timeout period has expired. W 01:01:06 Retrying (1 of 20)... I 01:01:09 Writing Sectors... W 01:01:28 Failed to Write Sectors 17150144 - 17150175 - Reason: The semaphore timeout period has expired. W 01:01:28 Retrying (1 of 20)... I 01:01:30 Writing Sectors... W 01:01:30 Failed to Write Sectors 17152896 - 17152927 - Reason: The semaphore timeout period has expired. W 01:01:30 Retrying (1 of 20)... I 01:01:30 Writing Sectors... W 01:01:32 Failed to Write Sectors 17164736 - 17164767 - Reason: The semaphore timeout period has expired. W 01:01:32 Retrying (1 of 20)... I 01:01:32 Writing Sectors... W 01:01:52 Failed to Write Sectors 17340384 - 17340415 - Reason: The semaphore timeout period has expired. W 01:01:52 Retrying (1 of 20)... I 01:01:56 Writing Sectors... W 01:01:57 Failed to Write Sectors 17341888 - 17341919 - Reason: The semaphore timeout period has expired. W 01:01:57 Retrying (1 of 20)... I 01:01:57 Writing Sectors... W 01:02:22 Failed to Write Sectors 17559296 - 17559327 - Reason: The semaphore timeout period has expired. W 01:02:22 Retrying (1 of 20)... I 01:02:27 Writing Sectors... W 01:02:31 Failed to Write Sectors 17596608 - 17596639 - Reason: The semaphore timeout period has expired. W 01:02:31 Retrying (1 of 20)... I 01:02:32 Writing Sectors... W 01:02:55 Failed to Write Sectors 17788736 - 17788767 - Reason: The semaphore timeout period has expired. W 01:02:55 Retrying (1 of 20)... I 01:02:59 Writing Sectors... W 01:03:07 Failed to Write Sectors 17854592 - 17854623 - Reason: The semaphore timeout period has expired. W 01:03:07 Retrying (1 of 20)... I 01:03:08 Writing Sectors... W 01:03:40 Failed to Write Sectors 18123936 - 18123967 - Reason: The semaphore timeout period has expired. W 01:03:40 Retrying (1 of 20)... I 01:03:45 Writing Sectors... W 01:04:14 Failed to Write Sectors 18334080 - 18334111 - Reason: The semaphore timeout period has expired. W 01:04:14 Retrying (1 of 20)... I 01:04:17 Writing Sectors... W 01:04:40 Failed to Write Sectors 18525216 - 18525247 - Reason: The semaphore timeout period has expired. W 01:04:40 Retrying (1 of 20)... I 01:04:43 Writing Sectors... W 01:04:58 Failed to Write Sectors 18657728 - 18657759 - Reason: The semaphore timeout period has expired. W 01:04:58 Retrying (1 of 20)... I 01:05:01 Writing Sectors... W 01:05:24 Failed to Write Sectors 18853280 - 18853311 - Reason: The semaphore timeout period has expired. W 01:05:24 Retrying (1 of 20)... I 01:05:29 Writing Sectors... W 01:06:30 Failed to Write Sectors 19325568 - 19325599 - Reason: The semaphore timeout period has expired. W 01:06:30 Retrying (1 of 20)... I 01:06:34 Writing Sectors... W 01:06:43 Failed to Write Sectors 19408768 - 19408799 - Reason: The semaphore timeout period has expired. W 01:06:43 Retrying (1 of 20)... I 01:06:45 Writing Sectors... W 01:07:08 Failed to Write Sectors 19603040 - 19603071 - Reason: The semaphore timeout period has expired. W 01:07:08 Retrying (1 of 20)... I 01:07:12 Writing Sectors... W 01:08:29 Failed to Write Sectors 20197696 - 20197727 - Reason: The semaphore timeout period has expired. W 01:08:29 Retrying (1 of 20)... I 01:08:34 Writing Sectors... W 01:08:37 Failed to Write Sectors 20222080 - 20222111 - Reason: The semaphore timeout period has expired. W 01:08:37 Retrying (1 of 20)... I 01:08:37 Writing Sectors... W 01:08:38 Failed to Write Sectors 20227936 - 20227967 - Reason: The semaphore timeout period has expired. W 01:08:38 Retrying (1 of 20)... I 01:08:39 Writing Sectors... W 01:08:43 Failed to Write Sectors 20268032 - 20268063 - Reason: The semaphore timeout period has expired. W 01:08:44 Retrying (1 of 20)... I 01:08:44 Writing Sectors... W 01:08:53 Failed to Write Sectors 20344864 - 20344895 - Reason: The semaphore timeout period has expired. W 01:08:53 Retrying (1 of 20)... I 01:08:55 Writing Sectors... W 01:09:03 Failed to Write Sectors 20409408 - 20409439 - Reason: The semaphore timeout period has expired. W 01:09:03 Retrying (1 of 20)... I 01:09:05 Writing Sectors... W 01:09:18 Failed to Write Sectors 20507392 - 20507423 - Reason: The semaphore timeout period has expired. W 01:09:18 Retrying (1 of 20)... I 01:09:19 Writing Sectors... W 01:09:20 Failed to Write Sectors 20518432 - 20518463 - Reason: The semaphore timeout period has expired. W 01:09:20 Retrying (1 of 20)... I 01:09:21 Writing Sectors... W 01:09:37 Failed to Write Sectors 20664288 - 20664319 - Reason: The semaphore timeout period has expired. W 01:09:37 Retrying (1 of 20)... I 01:09:41 Writing Sectors... W 01:10:40 Failed to Write Sectors 21092128 - 21092159 - Reason: The semaphore timeout period has expired. W 01:10:40 Retrying (1 of 20)... I 01:10:42 Writing Sectors... W 01:11:26 Failed to Write Sectors 21433920 - 21433951 - Reason: The semaphore timeout period has expired. W 01:11:26 Retrying (1 of 20)... I 01:11:30 Writing Sectors... W 01:12:04 Failed to Write Sectors 21698624 - 21698655 - Reason: The semaphore timeout period has expired. W 01:12:04 Retrying (1 of 20)... I 01:12:08 Writing Sectors... W 01:12:19 Failed to Write Sectors 21793088 - 21793119 - Reason: The semaphore timeout period has expired. W 01:12:19 Retrying (1 of 20)... I 01:12:22 Writing Sectors... W 01:12:26 Failed to Write Sectors 21823456 - 21823487 - Reason: The semaphore timeout period has expired. W 01:12:26 Retrying (1 of 20)... I 01:12:26 Writing Sectors... W 01:13:03 Failed to Write Sectors 22084704 - 22084735 - Reason: The semaphore timeout period has expired. W 01:13:03 Retrying (1 of 20)... I 01:13:03 Writing Sectors... W 01:13:14 Failed to Write Sectors 22176096 - 22176127 - Reason: The semaphore timeout period has expired. W 01:13:14 Retrying (1 of 20)... I 01:13:17 Writing Sectors... W 01:14:08 Failed to Write Sectors 22582304 - 22582335 - Reason: The semaphore timeout period has expired. W 01:14:08 Retrying (1 of 20)... I 01:14:15 Writing Sectors... W 01:14:19 Failed to Write Sectors 22615872 - 22615903 - Reason: The semaphore timeout period has expired. W 01:14:19 Retrying (1 of 20)... I 01:14:20 Writing Sectors... W 01:14:23 Failed to Write Sectors 22645664 - 22645695 - Reason: The semaphore timeout period has expired. W 01:14:23 Retrying (1 of 20)... I 01:14:24 Writing Sectors... W 01:16:31 Failed to Write Sectors 23562080 - 23562111 - Reason: The semaphore timeout period has expired. W 01:16:31 Retrying (1 of 20)... I 01:16:37 Writing Sectors... W 01:18:27 Failed to Write Sectors 24370656 - 24370687 - Reason: The semaphore timeout period has expired. W 01:18:27 Retrying (1 of 20)... I 01:18:33 Writing Sectors... W 01:18:51 Failed to Write Sectors 24502976 - 24503007 - Reason: The semaphore timeout period has expired. W 01:18:51 Retrying (1 of 20)... I 01:18:53 Writing Sectors... W 01:18:57 Failed to Write Sectors 24543808 - 24543839 - Reason: The semaphore timeout period has expired. W 01:18:57 Retrying (1 of 20)... I 01:18:59 Writing Sectors... W 01:19:43 Failed to Write Sectors 24889664 - 24889695 - Reason: The semaphore timeout period has expired. W 01:19:43 Retrying (1 of 20)... I 01:19:49 Writing Sectors... W 01:19:54 Failed to Write Sectors 24935776 - 24935807 - Reason: The semaphore timeout period has expired. W 01:19:54 Retrying (1 of 20)... I 01:19:56 Writing Sectors... W 01:19:59 Failed to Write Sectors 24961280 - 24961311 - Reason: The semaphore timeout period has expired. W 01:19:59 Retrying (1 of 20)... I 01:20:00 Writing Sectors... W 01:20:04 Failed to Write Sectors 24997984 - 24998015 - Reason: The semaphore timeout period has expired. W 01:20:04 Retrying (1 of 20)... I 01:20:06 Writing Sectors... W 01:20:16 Failed to Write Sectors 25093536 - 25093567 - Reason: The semaphore timeout period has expired. W 01:20:17 Retrying (1 of 20)... I 01:20:20 Writing Sectors... W 01:20:25 Failed to Write Sectors 25140512 - 25140543 - Reason: The semaphore timeout period has expired. W 01:20:25 Retrying (1 of 20)... I 01:20:27 Writing Sectors... W 01:21:43 Failed to Write Sectors 25713600 - 25713631 - Reason: The semaphore timeout period has expired. W 01:21:43 Retrying (1 of 20)... I 01:21:50 Writing Sectors... W 01:22:01 Failed to Write Sectors 25789696 - 25789727 - Reason: The semaphore timeout period has expired. W 01:22:01 Retrying (1 of 20)... I 01:22:02 Writing Sectors... W 01:22:08 Failed to Write Sectors 25842240 - 25842271 - Reason: The semaphore timeout period has expired. W 01:22:08 Retrying (1 of 20)... I 01:22:10 Writing Sectors... W 01:22:13 Failed to Write Sectors 25873568 - 25873599 - Reason: The semaphore timeout period has expired. W 01:22:13 Retrying (1 of 20)... I 01:22:15 Writing Sectors... W 01:22:30 Failed to Write Sectors 26005248 - 26005279 - Reason: The semaphore timeout period has expired. W 01:22:30 Retrying (1 of 20)... I 01:22:34 Writing Sectors... W 01:23:30 Failed to Write Sectors 26417344 - 26417375 - Reason: The semaphore timeout period has expired. W 01:23:30 Retrying (1 of 20)... I 01:23:34 Writing Sectors... W 01:25:18 Failed to Write Sectors 27141120 - 27141151 - Reason: The semaphore timeout period has expired. W 01:25:18 Retrying (1 of 20)... I 01:25:20 Writing Sectors... W 01:25:48 Failed to Write Sectors 27330400 - 27330431 - Reason: The semaphore timeout period has expired. W 01:25:48 Retrying (1 of 20)... I 01:25:48 Writing Sectors... W 01:25:56 Failed to Write Sectors 27395328 - 27395359 - Reason: The semaphore timeout period has expired. W 01:25:56 Retrying (1 of 20)... I 01:25:58 Writing Sectors... W 01:25:58 Failed to Write Sectors 27397440 - 27397471 - Reason: The semaphore timeout period has expired. W 01:25:58 Retrying (1 of 20)... I 01:25:59 Writing Sectors... W 01:27:07 Failed to Write Sectors 27864512 - 27864543 - Reason: The semaphore timeout period has expired. W 01:27:07 Retrying (1 of 20)... I 01:27:07 Writing Sectors... W 01:27:20 Failed to Write Sectors 27972992 - 27973023 - Reason: The semaphore timeout period has expired. W 01:27:20 Retrying (1 of 20)... I 01:27:23 Writing Sectors... W 01:27:35 Failed to Write Sectors 28074176 - 28074207 - Reason: The semaphore timeout period has expired. W 01:27:35 Retrying (1 of 20)... I 01:27:38 Writing Sectors... W 01:46:41 Failed to Write Sectors 32585760 - 32585791 - Reason: Power Calibration Area Error W 01:46:41 Retrying (1 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (2 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (3 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (4 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (5 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (6 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (7 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (8 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (9 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (10 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (11 of 20)... W 01:46:41 Retry Failed - Reason: Invalid Address For Write W 01:46:41 Retrying (12 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (13 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (14 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (15 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (16 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (17 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (18 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (19 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write W 01:46:42 Retrying (20 of 20)... W 01:46:42 Retry Failed - Reason: Invalid Address For Write E 16:19:29 Failed to Write Sectors 32585760 - 32585791 - Reason: Power Calibration Area Error I 16:19:29 Synchronising Cache... W 16:19:33 User opted to skip the 'Close Track/Session/Disc' functions. E 16:19:33 Failed to Write Image! I 16:19:34 Exporting Graph Data... I 16:19:34 Graph Data File: C:\Users\inacu\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-UD03_1.14_FEBRUARY-6-2024_12-14_AM_VERBAT-IMk-000_4x.ibg I 16:19:34 Export Successfully Completed! E 16:19:34 Operation Failed! - Duration: 16:04:43 I 16:19:34 Average Write Rate: 1,126 KiB/s (0.3x) - Maximum Write Rate: 17,631 KiB/s (4.0x) I 16:19:35 Close Request Acknowledged I 16:19:35 Closing Down... I 16:19:37 Shutting down SPTI... I 16:19:37 ImgBurn closed!

I do feel the need to pass this along. It appeared to be a fluke, but it did happen, so it's worth noting. I had a DVD-R of home movies converted to DVD Video. I know this disc was playable because after I created it just the other day, I read it to an image file with ImgBurn, loaded the image file in DVDShrink, and wrote a new VIDEO_TS output to test it. It passed. Sunday, I put the same disc back in and copied the VIDEO_TS folder in File Explorer, but it would not play or load in anything, even DVDShrink. I put the disc back in today and read it back into an image that did read properly in DVDShrink. So, I haven't quite figured it out yet. It may have just been a fluke. It may have been a issue with the USB enclosure. On the LG WH16NS60, you have to sometimes turn off the enclosures and turn them back on before Windows will recognize data from DVD's. Some kind of Windows bug. A similar one may have happened in this case. Plus, I've been unable to reproduce the issue. Sunday, I copied another DVD-R of home movies the same way without issue just before the one I described above.

I do feel the need to pass this along. It appeared to be a fluke, but it did happen, so it's worth noting. I had a DVD-R of home movies converted to DVD Video. I know this disc was playable because after I created it just the other day, I read it to an image file with ImgBurn, loaded the image file in DVDShrink, and wrote a new VIDEO_TS output to test it. It passed. Sunday, I put the same disc back in and copied the VIDEO_TS folder in File Explorer, but it would not play or load in anything, even DVDShrink. I put the disc back in today and read it back into an image that did read properly in DVDShrink. So, I haven't quite figured it out yet. It may have just been a fluke. It may have been a issue with the USB enclosure. On the LG WH16NS60, you have to sometimes turn off the enclosures and turn them back on before Windows will recognize data from DVD's. Some kind of Windows bug. A similar one may have happened in this case. Plus, I've been unable to reproduce the issue. Sunday, I copied another DVD-R of home movies the same way without issue just before the one I described above.

I'm copying several CDs and DVDs to preserve my collection of videogames. Never had an issue before, all the videogames are original and well preserved (all PC games from 1996-2000). This specific game is a multitrack CD and obviously i can't create an ISO file from a multitrack CD, therefore i was trying to create a .bin file, but suddently it's showing sectors:0 size:0bytes and the process remain stuck at session 1 track2. I've waited over 40 minutes, restarted, opened Imgburn as administrator, tried some troubleshooting without any progress. Am i missing something? It may be caused by the fact that i've reinstalled ImgBurn after several years and may have forgotten some plug-ins i should have installed?

You can't span discs in ImgBurn. It only burns one project to one disc at a time. As for the non skipped part text in black, for whatever reason, those files were not included in the image creation. Why, I couldn't say. Could have something to do with the project settings or the files could be locked by the system. As for the text in red, I'm not familiar with the WUModels folder, but that is definitely being locked by Windows for whatever reason and thus it cannot be accessed. The Recycle Bin files and System Volume Information are also folders that cannot normally be accessed by file access means. That's why access was denied for them. For instance, if System Volume Information is visible in File Explorer, if you tried to open the folder, you'd get an access denied error from Windows.

Bingo. I did it. As I said before it was all a question of information. I'm transcribing them so they can be useful to someone else. The boot image is X:\boot\grub\i386-pc\eltorito.img in the case of the Kaspersky image. Platform image: 80*86 Load segment: 07c0 Sector to load: 4 Patch boot Information Table. But the most important thing is to manage the restrictions. That is ISO9660 and clicking on the year 1999 thus enables name length and other various variables which I will not explain in detail here. Created the ISO from the pen drive and... voilà success. However, I thank everyone for their help and collaboration. I'll try OnTrack EasyRecovery tomorrow and let you know. Greetings

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?

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

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.

What’s the reason behind trying to create an iso from your usb stick rather than using the iso you originally downloaded? The original iso was meant for burning to disc. What Rufus has created on your usb stick isn’t.

Yeah, sorry I couldn't help. As I said, I've never successfully gotten a bootable ISO made by Build mode.

Yes, I've seen that guide before. Unfortunately it is specific to a Microsoft file system. I haven't tried it. In fact my problem is also finding the famous boot image. I can't identify it as it's different from the guide. I think the structure created in the pen drive has to do with a Linux type operating system. Anyway, thanks for the support