A Protection Error usually results when the operator who is logged on doesn't have "authority" to access a file.

Most of the miscussion groups assume that it's entirely a matter of the user who is logged on having access in computer settings, but it appears from some of the splatter that a file that has "access restrictions" (i.e. DRM features) could lock the file if a user other than the one who bought/rented it attempts to access it.

The usual advice is to turn off file sharing on the drive containing the files (in this case all of the files you're trying to burn) and run the burn as administrator. (About 30% of those who try this fix say it doesn't work.)

If the burn goes part way and then flips up the error, it's possible that it's hit on a file or two that have locked themselves because the license has expired or a prior access has "breached" the DRM protections. I don't know of a solution to the DRM lockout other than to eliminate the offending file from the burn list.

A possibly simple way to eliminate an offending file, it that's what's blocking your burn is to create a new folder, open a command prompt, go to the new folder and copy the files to be burned using the command:

xcopy <source folder>\*.* /s /c

The <source folder> is the folder where the files are. You run the command from the folder where you want them copied to. Omit the /s if there aren't any subfolders, but the /c is critical if its a "protected file." The protected file won't be copied, and copying ordinarily stops when an error is encountered; but the /c allows the copying to proceed after it clanks on that one. The "missing tune" in the list that should be copied probably is the cause of the problem if it's the DRM issue.

Otherwise, you can try making sure that the folder you're burning from is shared for "all users" and/or run as Administrator, although reported success with either is "spotty."

John