I figured it out. It doesn't make any sense but its microsoft so expected. When you burn files to disc it copies them to that temporary folder and burns them from there. When it tries to delete them it checks to see if they are being used. Unfortunately windows just checks the file name and not its location. Since the same file name in another folder was being used by another program I had running in the background windows wouldn't delete the one no longer in use in the temp directory. This is also why restarting did nothing since that program runs with startup. I tested this theory on my next disc and noticed something interesting. I added the files to be burned and then changed half the file names so there was only one instance of that file. After burning, they still would not delete. I closed the program using the original files and they deleted. :\ Next I'm going to try making my own copies, renaming them, then adding them to burn and see if that works. I'm also going to try doing it normal with that program not running but alas out of things to burn for the moment and I'm bound and deterimined to figure out what exactly is going on. We really shouldn't need a workaround, microsoft should make a patch to make it work like its supose to. A way to stop a file being used like dissconnecting a drive would be nice. You could then force deletion of a file no matter what.