Windows disc image burner verifying stuck

I tried removing with the Remove Filter button, the dialog went away and the filter was still in the list. Restarting ImgBurn had no effect. After removing it manually in the registry, it disappeared from the list.

However, when I wrote the last post, ImgBurn appeared to be verifying the disk without issue. Now it stops @ 82% complete and hangs. And the system itself still hangs after aborting ImgBurn's verification process. A hard reboot is necessary to recover the system.

There are now no filters listed in the ImgBurn filters tool, so I'm really confused as to what's going on.

I tried removing Windows Movie Maker as I never use it and it was mentioned in a post somewhere that sometimes causes issues. But no change in behaviour.

For what it's worth, a Windows 7 Ultimate installation does not have a Sonic Shared directory in the Common Files area of either Program Files or Program Files (x86). It's something to do with Sonic's software, but I'm just lost as to what or how that might have been installed.

...

What do you mean it didn't work?

You couldn't remove it from the list?

What exactly happened when you clicked 'Remove Selected Filter' ?!

You might find that Cyberlink used the Roxio engine (almost nobody writes their own!). Uninstalling that app wouldn't remove the filter driver because it could be used by any number of other applications. Maybe you can google 'uninstall px engine' for more info?

• Remove From My Forums

• Question

•  downloaded process completed successfully, iso image burned to DVD but at the end of verification, status showed "The disc image didn't burn successfully because an error occurred. (Error code: 0x80004005)"

  Any suggestions !

Answers

• Hi Techman11,

  According to my research, Windows Disc Image Burner is a third party application. Kindly notice that it is out of our support scope. For third party application issue, you could contact the application vendor for help, they are more familiar with their product.

  Based on your description, you are trying to burn a Windows 10 installation, you can check the following link and use the media creation tool to create your own installation media.
  Get Windows 10
  https://www.microsoft.com/en-us/software-download/windows10

  Best regards

  ---

  Please mark the reply as an answer if you find it is helpful.

  If you have feedback for TechNet Support, contact

  • Proposed as answer by Wednesday, August 3, 2016 1:25 PM
  • Marked as answer by Kate LiMicrosoft employee Monday, August 8, 2016 6:07 AM

Frank nicely explained the Windows-specific verification. I’ll give a more general answer.

What does Verify disc after burning actually do to verify the data?

I mean, does it create a hash of the source and destination content and then compares them? If it is so, does it store the hash of the burned content in RAM? Or does it save it in a temporary file on the hard drive? Is there a log file of what is going on?

That is certainly one way that a comparison can be implemented: hash one file (hopefully with a sufficiently large—read low chance of collision algorithm), repeat for the other, and compare hashes. If that is how a verification is implemented, then you will be able to see the drive-LED flash for a while, then the CD/DVD-LED flash for a while.

Another way to implement the verification is to read a block of one file, then the same block from the other file, compare them, then repeat until the end of the file is reached. In this case, you will see the LEDs of the two drives alternating back and forth.

Of course, if the the hard-drive and optical drive don't have LEDs, then it won’t be as obvious, but you can still see it with something like ProcessMonitor because it will log a series of reads from one, then the other either in a single, big burst each or alternating, small bursts.

I imagine it is some kind of comparison between the original files and the files that have been burned on the disc, but does anybody know how it is really done at a low level?

Actually, all it really does is to flush the drive cache so that the comparison function is reading the data from the actual disc instead of from the memory cache. Obviously this is a critical step because if the verification is done from cache, then it does not represent what is actually on the disc, so corruption can easily slip through.

You can see whether a comparison is done from the drive or from the cache in RAM by how fast it occurs. If you manually do a simple comparison (e.g., with WinDiff or WinMerge or by hashing them with a hashing tool), you will notice that the comparison happens much faster than expected because it is reading the files from memory cache. You must flush the cache to force it to read from the actual disc. For optical drives (and other removable media like flash-drives and memory-cards, simply ejecting the drive is enough to flush the cache, but for hard-drives, it is not nearly as simple (though usually that doesn’t matter because the new copy is the one you want to test).