dbminter

I spoke from over 10 years of experience with LG. The old joke is LG stands for Lucky Good in that it's Lucky Good if it works right. I've had multiple copies of the WH16NS40 and they all had the same problems. They will fail 9 times out of 10 to Verify writes to BD-R and RE DL. They only write BD-RE at 1x for 2x media. It will always write corrupt data to the 2nd layer of BD-RE DL when formatted as a giant floppy. When writing to BD-R and you experience a write rate drop, the maximum it will resume writing is 6x. When writing to Ritek 8x DVD+RW, it will complete Verify even if the data is corrupt when you try to access it. The first LG drive I had was a rebranded DVD burner from IOMega. I quickly got rid of it because it would 50/50 write DVD Video discs that played back with skips and pops in the video. I only used an LG drive at all because it was the only internal BD drive that was writing to 8x DVD+RW after Pioneer borked the 1.34 firmware. I wouldn't have used it otherwise, and when Pioneer fixed the problem with their 1.50 firmware, I quickly removed the LG (It had stopped writing to DVD-R, anyway.) and replaced it with a Pioneer 209. There was also someone else who reported problems with that LG drive writing to BD DL media. After they replaced the LG with a Pioneer 2209, the problem went away. So, my experience with LG has left me with a bad taste in my mouth about their WH16NS40 BD drive. Much prefer Pioneer's 209 and 2209 BD drives. As for DVDInfo Pro, something is causing the drive to return the disc is smaller than it should be. That would be either the drive, the disc, or DVDInfo Pro, or a combination of those things.

Every time ImgBurn generates a line in the log, does it write the log to the disc each time? Or does it queue the entire log until the operation is completed and then the log file is written to disc? If it writes the log only after an operation is completed, might I suggest that ImgBurn write to the log file each time it generates an output message? That way, if an operation fails due to a command that never completes, the log can still be viewable.

So, you have successfully burned these Ritek BD-R before? Just that you burned less than 99% of the total available disc space? It seems you're using an LG BD burner. I'd still say that LG drive probably doesn't like Ritek BD media very well. LG's, I know, are absolutely useless for writing BD DL media, so it wouldn't surprise me if it can't write 100% of the available space on a disc. Particularly a Ritek one. As I said, before I laid the entire blame on the Ritek's, I'd try some Verbatim's and see if you can write to the edge of those. It may just be that Ritek discs are pretty bad and that quality Verbatim media might solve the issue. Or the LG drive may just be pretty rotten and can't write to the very edge of any BD-R media.

Probably the drive doesn't like the Ritek BD-R you're using. Ritek is a 2nd tier optical disc manufacturer. Have you used these discs with any frequency before and they worked out okay? I'd recommend trying Verbatim BD-R and see if that can be written to to the edge. I know the Pioneer 209 and 2209 will write Verbatim BD-R at almost to the edge, just a shade under 25 GB.

What are the contents of this disc? If it's not a bootable disc, i.e. just a disc of some contents that aren't made in any fancy way, you could try just creating a new ISO in ImgBurn Build mode. See if that ISO mounts. Of course, this doesn't solve why Windows won't mount that ISO. But, you could spend the rest of your life trying to debug a Windows issue and get nowhere. It's the nature of the Windows beast. When something goes wrong with an internal Windows function, too often than not, the only solution is to restore Windows from an image where it worked before/reinstall Windows. However, it's probably just a case of a weird ISO that isn't mounting correctly as you said another image does work. Probably something wrong/weird with the source disc that is creating a weird ISO.

Yeah, you probably just had a random fluke where one worked. Even crap media will, on occasion, succeed every once in a while. If those discs don't work on both firmware revisions, the problem is either the drive or the discs. And Ritek is a 2nd tier disc manufacturer. And you should never go for Ritek for double layer media. Verbatim, pretty much, makes the only good DVD+R DL discs, so they probably make the only good BD DL media. I only use their BD-RE DL and sometimes TDK made Verbatim's BD-RE DL, which I've also used successfully. I recommend reflashing that drive back to 1.50. There was a bork in the firmware with 1.34 involving Ritek 8x DVD+RW discs not writing correctly, always failing Verify, that Pioneer fixed with 1.50. So, who knows what else they fixed? Of course, who knows what else they might have broke?! I wrote to Pioneer nearly 2 years ago about that DVD+RW issue, but never expected anymore firmware updates to the drive after almost 2 years. Color me surprised when it came out on the 2nd of March!

If you're adventurous, you could try reverting the Pioneer firmware from 1.50 to 1.34 with DVRTool. See what I did here: http://forum.imgburn.com/index.php?/topic/24254-random-trouble-with-bd-writeverify/ However, be aware that my experience with DVRTool works with the Pioneer BD-2209 drive. It may not work with your drive.

Yes, under what context do you mean that BDMV folders will write? Are you writing them to ISO first and burning them or using the on the fly build? Or using some other program entirely to write these folders to discs?

I encountered a similar problem. I got a 209 to supplement my 2209 from Pioneer. I put the 209 in my enclosure to test it before installing it internally, which was its target destination. I updated the firmware to 1.50 from 1.34. I tried burning a Verbatim BD-R SL, but at 70% into it, the write rate dropped to 0.0x and never resumed. The drive light was off but the enclosure light was flashing. Had to power off the enclosure and had a coaster. I tried a DVD+RW and the same thing happened at 97% into Verify. I installed the drive internally in case it might be the enclosure or a conflict with the enclosure and the 209. The 2209 was no problem back in January with this same enclosure. The drive works fine installed internally, it seems, so it must be either the enclosure or an incompatibility between the enclosure and the 209. This doesn't appear to be your problem because the screen shot seems to indicate your drive is installed as SATA, which is internally installed.

Booting into Safe Mode would be my next troubleshooting suggestion, too. You can then see if it's something in your Windows installation that might be causing the problem. As LUK said, some kind of software interference, like antivirus. It could be the drive needs replacing. I'd also see about getting an enclosure and putting the drive in that and testing and see if you still get that or other errors. However, an enclosure isn't necessarily a viable idea. I put my new Pioneer 209 BD in one and was getting weird errors where Writes and Verifies would drop to 0.0x and never resume. So, I installed the drive internally, since that was always its intended target. It worked. So, either my enclosure has died after just 2 months or there's an incompatibility between the 209 and the enclosure. Swapping out the drive would also verify if the drive is the problem or some kind of software interference or a different hardware error. However, of course, any swapping out of drives for other drives or putting them in an enclosure requires work and sufficient knowledge in cracking open the PC case.

Oh, wait, there was a log attached! My bad!

I've been collecting all kinds of things that have been accruing over the past 26 years. I even still have my FORTRAN projects back when I was taught it in college. No one uses FORTRAN anymore, even back when I was taught it. And I haven't touched FORTRAN since 1995, but I've kept all the programs I wrote during college.

ImgBurn will burn BDMV folders. What happens exactly when you try to burn BDMV folders? Do you get the same error? As to the nature of the error, I can see a few potential things. How old this drive? The Pioneer 208, I think, is a pretty old BD burner. The drive might have simply come to the end of its life cycle. I see you were using Ricoh media. Have you always used this Ricoh media before? It may be your drive doesn't like that particular Disc ID. Are you burning this ISO to DVD or BD media? Ricoh media can be pretty iffy for some drives. It's a generally lower tier quality media. If it's a DVD disc, try using Verbatim DataLife Plus media, which you can only find online. NOT the Life Media series you find in stores. If it's BD, try Verbatim BD if you haven't already. Unless it's BD-RE SL. Don't use Verbatim BD-RE SL. Try updating the firmware of this drive. Pioneer recently released the 1.50 branch of its current and older BD drives after more than a year of no updates. That might help. You should do it anyway even if it doesn't. In Write mode, right click on the drop down list of target drives and choose the option to Check for firmware updates. Post the entire log of this failed burn, not just the error screen that pops up. Help --> ImgBurn Logs

I said abandoned because I haven't seen a THUMBS.DB file in a folder except for 10 year plus old backups of folders I did. Restoring them restored the THUMBS.DB that was backed up with the folders back with Windows Vista. I haven't seen a "live" THUMBS.DB file in any folder on any Windows installation I've had since Vista. Except for, as I said, deprecated contents. So, I just guessed it was abandoned. I looked it up. It seems that THUMBS.DB did make it all the way to Windows 8, but doesn't seem to be live anymore in Windows 10.

Actually, firmware 1.50 might improve the results of your issue. I checked the release notes for 1.50. They say these improvements were made to the firmware: Improvement of the recording quality with BD-R TL(2x 4x 6x : MCM) Performance improvement during high-speed rotation Improvement of the operational stability when recording DVD-RAM That first line is of importance here. However, it seems to indicate MCM BD-R TL discs. However, MCM makes Verbatim's DVD-R and DVD+R DL. Don't know if they make Milleniata's Verbatim M-Disc BD-R TL or not. Though, it seems you'd have a higher possible success rate with BD-R TL under this 1.50 firmware. It's definitely something worth investigating if you wanted to invest the time and money.

One thing I noticed Pioneer updated in this firmware also relates to 8x DVD+RW. In the past, writing initially began at 6x for the first 2 and half minutes. That time has been cut down to one minute and 15 seconds.

As far as the 2209 goes, firmware updates make a lot of difference. For instance, when I first got the 2209, there were 2 Verbatim DVD+R DL media brands with the same Disc ID. One disc had an inkjet printable surface and one was branded. The 2209 had no problems with the branded discs, but would always fail Verify on the inkjet discs, even though they were the same DID. Internally, they should not have been different, but apparently, they were. The next firmware update to the 2209 fixed this issue. Then, when the 1.34 firmware came out, it caused Ritek 8x DVD+RW that would burn and Verify under 1.33 to fail Verifies until fully formatted in another drive. Hence why I started using the LG for my 8x DVD+RW. Then, the 1.50 firmware came out for the 2209 and 8x DVD+RW completes Verifies now. And now that my LG needs replacing and the 2209 appears to work again with 8x DVD+RW, I'm getting the Pioneer 209 BD that doesn't support BDXL and M-Disc since I don't need those. It has the same firmware revision number (In fact, the other, newer Ultra HD BD drive Pioneer put out also has the same firmware revision number.) as the 2209 does now, so it should write to 8x DVD+RW fine, too. I didn't know about the firmware update until today. I had checked a few weeks ago, but there wasn't one. Don't know what prompted me to check today, but I did, and there it was.

Now, IF you wanted to gamble the money on it, you could try some more Verbatim BD-R X/TL M-Disc with this new Pioneer BDR-2209 1.50 firmware. See if this new firmware handles those kinds of media better. However, as I said, it's a gamble. But, if you had any left, why got give it a throw?

Well, what do you know? After over a year of no new firmware updates, Pioneer updated the 1.34 firmware of the BDR-2209 to 1.50. I had thought that the 2209 would never receive another firmware update. I'm testing an 8x DVD+RW right now, in the Verify stage where it failed before, to see if they fixed the borked firmware from before. So, if the OP got the 2209 and has decided to keep it, there is a new 1.50 firmware released around March 2nd. It's dated December 2017, though, oddly enough. Surprisingly enough, the LG WH16NS40 also got a firmware update after like almost 4 years. But that was to plug a decryption hole in Ultra HD Blu-Ray's. Maybe that's why the 2209 got one, too. Simply to plug a Hollywood Hole, a goof that the big movie producers don't want. And nothing done to actually better the drive. And, the 1.50 firmware PASSED! They actually followed up on my e-mail and fixed the borked firmware, it seems!

I only use double layer discs when necessary. For DVD-Video jobs that require DVD+R DL and for BD-RE DL to make my monthly system and files backups to. I avoid using multi-layer media whenever I can. Even though it takes more BD-R to do a backup than it would BD-R DL, they're more likely to finish without errors and not have a problem reading back later on in years.

But, THUMBS.DB was abandoned after Windows Vista. The OP's original intention seemed to indicate he wasn't using that version of Windows. But, if you are using Vista, just do the steps as described above.

Which makes sense. After all, I believe long file/folder names are actually still 8.3 names with ~ in them and desktop.ini may just link the long file name with the 8.3 name. For reference, here are two related posts I made about this topic where I encountered this same thing: http://forum.imgburn.com/index.php?/topic/24759-imgburn-created-2-folders-in-the-same-directory-with-the-same-name/?hl=%2Btemporary+%2Bburn+%2Bfolder http://forum.imgburn.com/index.php?/topic/24760-drag-and-drop-from-optical-renames-target-folder-as-temporary-burn-folder-on-fall-creators-update/?hl=%2Btemporary+%2Bburn+%2Bfolder&do=findComment&comment=160787

As far as I know, what you suggested by about inserting the media and letting Windows generate the thumbnail data in the Users cache is probably the best and easiest way to go. I can't think of any way you could manually import that information with the switch over from THUMBS.DAT.

I had this happen once or twice before. I couldn't explain it either. Somehow, on the disc I burned, TWO folders in the same sub-directory were named the same thing, Temporary Burn Folder. I didn't think that was even possible under Windows's file structure. My folders were also supposed to be named Disc 1 Of 2 and Disc 2 Of 2. I also burned to BD-R. It was reproducable for a while but after I rebooted, it stopped doing that.

You're right. I just inferred the OP wanted to make an ISO of a bootable USB stick. However, the contents from the stick could be used to make a bootable recovery disc. I thought ImgBurn couldn't make an ISO of the stick, but I never thought about using its contents to Build an ISO until you pointed that out.