Nero 6.6.0.12 borks NVision 3.1.0.0

vbimport

#1

Nero 6.6.0.12 causes nero Vision 3.1.0.0 to crash early in the burning proceedure when burning to image (using the image recorder option).
This crash is reproducable and has been tested across two PCs.
I have not tested if other burning options are affected.
It’s a pain to fix too.

Cheers,

Guy


#2

Yup. Just ran across this myself. I had to uninstall nero ultra 6 and reinstall. Has ahead software been told?

Magnesium.


#3

Yes, I informed Nero.


#4

Nero has released a new version of NeroVision Express 3
version 3.1.0.0d released April 19th.

Hope this helps…
Go look here:


Just wanted to inform u guys…


#5

I wonder if they test every new release. Propably not!!


#6

New version doesn’t fix the problem. Does Nero ever make a release that doesn’t break three things for every one it fixes? I keep hoping every release fixes the problems they introduce, but they just get more shoddy every time.


#7

…and all the idiots can do is mail back asking for information that I don’t have. FFS why can’t they test it themselves?


#8

If they carry on like this it will be ‘keygen time’ for me when v7 comes out. I have been using Nero since v4 came out and have (officially) upgraded each time.


#9

I had nothing but problems with 3.1.0.0d. It still doesn’t work with my Plextor convertx and now I can not transcode any files. Keep getting that junk error message and the Nero error file says “SEH exception”. This was a problem in one of the earler versions and seems to be back now.


#10

Why would they when they have all of us as beta testers! :wink:


#11

There is a patch that fixes these issues it is located here:

Be careful when installing this patch as it sometimes deletes the HKLM\Software\Microsoft\Windows|currentVersion\Run key and all of its subkeys. Back it up before you install the patch and reboot thene merge the backup key you made and reboot. This solved all my problems hope it works for you guys too!


#12

I wonder what kind of patch it is since it might delete this registry key!!


#13

A very badly written patch I’d say!


#14

or a messed up OS config as the patch didn’t delete this registry group on either of my machines.