At some point in the last two days, I used Nero's updater and pulled the latest version of Nero down.
Now I cannot burn a DVD-R or DVD-RW at 16x, 8x, or 1x (RW).
I keep getting " Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)"
in the log, and it tells me verification failed.
However, I can still burn DVD+Rs no problem.
I can't seem to find a way to regress my Nero version, and have a hard time actually believing that it's Nero's fault, but the media has stayed the same, and this USED TO WORK FINE.
Hi Allen42
You can try and do a clean install of Nero - either to the latest or a version that you prefer.
Uninstall Nero, run the clean tool.
Reboot now run a registry cleaner like the free ccleaner. Use the issues and cleaner options.
Now reinstall Nero. If you want to use an earlier version you can find them here.
I'm not much for verifying the discs. I mainly rely on playback or accessing the files again (data discs).
For the discs that failed verfication - have you tried playing them back or seeing if the burner recognizes the files on them?
Yeah I'd hate to have to use an older version when a newer one w/ more options (if you use them) is available for free.
Wasn't aware of a conflict w/ Pinnacle and the newer Nero versions - txs for that bit!
Well I guess to fix it would be if you're not using Pinnacle - uninstall it and run ccleaner again.
If you are still using it - lame advice here but might want to send Nero tech support a failed log from the latest version then a successful one for the earlier reinstalled using the same type of discs.
I'd be very curious!
Unfortunately, this project is all about using Pinnacle to compile ALL of our old home movies onto DVD, so I'm using Pinnacle Studio 10 a lot right now.
The conflict I think is "supposed". The Nero cleaner did disable something in Pinnacle though, as Pinnacle driver check now shouts when I fire up Pinnacle. I'm not burning anything with Pinnacle, so I don't care, but disabling whatever it disabled still didn't fix the problem.
I just might send Nero a log... I did keep several. I confirmed that whatever the problem is, it exists in 7.5.0.9 and 7.5.0.9a as well.
