Nero Burning Rom 2015 incompatibility

Hi,
I have a compatibility problem with Nero Burning Rom 2015. I must disable dopuslib32.dll to have Nero browser working good.
Are there downsides if I disable dopuslib32.dll?
My os is Windows 7 Pro x64 and Opus version is 11.13

If you disable the shell execute hook (the highlighted line in your screenshot) then parts of Explorer Replacement will no longer launch Opus instead of Explorer, but I think otherwise things should be fine.

How did you determine that line was causing the problem?

Nero support team suggested me to disable all non Microsoft shell extension. I did many experiments and now I realized that there is this incompatibility with Opus.
I hope directory Opus developer resolve this incompatibility.

Here a short video that shows Nero Burning Rom 2015 incompatibility
mediafire.com/watch/c8u8y469nxi6du2/Rec.avi

I've tried to reproduce this but can't, and also can't see a reason that the shell execute hook would be involved in any way.

I'm not sure from the video if you are left-clicking or right-clicking, but I have tried both and found it without issue, except for a crash which happens even if Opus is not installed on the machine:

The tree in Nero, on my virtual machine, has a Floppy Disk Drive (A:) entry, and there is a lengthy delay / spinning hour glass when I right-click it. If I right-click another drive during that delay, Nero will often crash. At other times it won't crash but I'll see both the A: entry and another entry selected at the same time. Once I even saw the Program Files folder branch added to the tree below a non-existent A: drive.

So I would say there are some bugs/instability in Nero's tree code, which may be related to what you're seeing, or may be separate issues. Either way, I cannot reproduce what is in your video.

I have also tried putting a debug version of the shell extension on the machine which logs whenever it is called, and it is never called when right or left-clicking the folder tree in Nero. (Which makes sense, since there's no reason ShellExecute or ShellExecuteEx should be called in response to a left or right click on a folder tree.)

If you are right-clicking, one possibility is that the problem is caused by a second shell extension in conjunction with the Opus shell extension. For example, if there is another shell extension which, when asked to add its items to the menu, triggers a ShellExecute or ShellExecuteEx call, then the shell execute hook might become involved. That would be very unusual, so it seems unlikely, but you could check by disabling all extensions except the Opus one and see if it still happens.

The video looked like Windows 8 so I tried on both Windows 7 and Windows 8, and had the same results. I could crash Nero and trigger other Nero bugs without Opus being involved, via the A: drive method I mentioned, but could not trigger any additional bugs with Opus installed and the hook enabled.