LIGHTNING UK!

ImgBurn has nothing to do with USB sticks, it burns disc ISO images to blank discs (cd / DVD / bd )

That log was about 4 or 5 different burns wasn't it? Only the last one seemed to be taking a while for the drive to write the leadin and you aborted it. If your drive is unable to burn decent discs at any of the supported speeds and you've already tried what I've suggested, buy yourself a new drive.

Try all supported write speeds. Look for firmware updates for your drive. Clean the drive with a cleaning disc. Try another spindle of discs - if the ones you're using are all from the same one.

You still need to pick one of them and enable the seamless option.

Take control your antivirus and tell it not to.

You can find out which drive is causing that by following what's written in the FAQ. This is not a general windows 10 issue, it works fine with that OS.

Your issue looks a lot like this one. http://forum.imgburn.com/index.php?/topic/23822-burning-dvdr-dl-error-the-semaphore-timeout-period-has-expired/

So it's probably down to the drivers now being used then or something. The drive seems to have been disconnected after 10 or so seconds of being 'busy'. That's beyond my control, I'm specifically setting a much longer timeout than that.

I thought you said ImgBurn could read the cd text on the disc you burnt? So it can burn and read it just fine. You're burning a cue, so none of the options you're talking about are relevant.

This is a common system issue with USB connected drives. Other adapters, enclosures and controllers can sometimes work around the problem. You just need a combo that works properly. Where possible, use the drive internally.

Clonecd was designed for that type of thing. You can't use ISO for that, it relies on the extra data in the img and sub files.

If ImgBurn can see it on the disc you burnt, I'm not sure how there can be a problem with it? It's either there or it isn't. Sorry, I'm not really sure what to say.

That looks like safedisc or securom copy protection to me. I'm afraid ImgBurn won't work with protected discs.

Can you post the log from the burn / verification of the master you made please? Also, switch to Read mode and see if ImgBurn can see the cd text on the disc by clicking the media information button in the Source box.

Help me out here... what were you offered and what did you install?

Nothing is bundled, the opencandy plugin offers things dynamically from a massive list of apps. I don't know what you're offered and it can change each time you run the installer. If something it offered and you installed has done that to your machine, they need to be made aware of it as I'm quite sure it shouldn't be.

Do not mess around with the hardware read error retires setting, put it back on the default (of not setting it). Post the log of the next burn + verify you do once you've reset the settings back to default.

Because you have to add something into a manifest within the exe to make windows report newer versions of windows. Otherwise it'll never go beyond windows 8 (8.0). 2.5.8.0 predates 8.1 and 10.0, therefore it's missing said info from the manifest in the exe. It's purely cosmetic though so nothing to worry about. I believe booting into safe mode makes windows report the real os version to the program.

Players alway play from index 1 when skipping tracks or starting the first one. If you want 5 seconds of silence before the first track starts, you'd need to insert it into the audio file you're burning.

You should have listened to it You need to burn it to a double layer disc.

Nope, it's not the data. The program is simply sending the 'reserve track' command to the drive with a value for the size to reserve (based on the amount it has to burn). You're well within the limits where the size of the disc is concerned. Commands should either succeed or fail... never get 'stuck'.

The Optiarc burnt them just fine so I'd say it's more likely to be the drive itself now. It's not even that the liteon did a bad job on the overburnt one, even the normal burn (that seemingly worked) is pretty awful.

That drive can't overburn.

There should always be a way for people to (relatively easily) exclude files or totally disable protection for a defined period of time. I know that's what I do when I need to run something that my AV is unhappy with. As they're deleting anything that uses opencandy platform (not specific to ImgBurn), it's opencandy that need to sort things out with them really. I don't understand why they auto delete something (ImgBurn setup) that uses something (opencandy platform) that can offer a 'potentially' unwanted program. It's like deleting all websites that use Google Adsense. Goodbye half of the internet! Surely they could devise a better way of dealing with it?

A non shrunk version would certainly be easier to read. You can see that the error rate on the 2nd layer is very high though, that's why it's unreadable. I doubt it'll make a difference but you could try enabling the 'Perform OPC Before Write' option in the settings and see if it helps the drive learn how to burn the variation of MKM-003-00 that you've got. I'd be interested to see a scan from the disc you said you burnt a non oversized image to.