DVD-RB PRO won't start on W7HPx64

[laserfan]

I've owned this for years, and have been dual-booting to an old Windows XP Pro 64-bit installation to use it. This weekend I decided to install to my W7HPx64 partition instead, and although Reg-RB.exe ran fine this morning, and I got a new license .RBK file, when I try to launch Rebuilder.exe itself it doesn't run. I get a blip of the "wait" spinning cursor (maybe a tenth of a second) but nothing else, nor do I see any attempts to run in Task Manager.

I've uninstalled-and-reinstalled, and also used "Run as Admin" for both the installer and then Rebuilder.exe, but it's not launching.

I've never seen anything like this before and wonder what I might be doing wrong????

:confused:

BTW jdobbs thanks for fixing the license server on your holiday weekend!

[gonca]

DVD-RB PRO works fine on WIN7x64 on my system. Check anti-virus and on an of-chance DEP

[jdobbs]

If you are running COMODO -- that's probably the issue. If not, check other "protection" software you have installed. The issue is NOT with DVD-RB -- it's overly zealous anti-virus software that is probably using some kind of heuristic detection mechanism (interpret "heuristic" as "wild-ass guess"), and it affects more than just DVD-RB. If you have it I'd recommend you dump COMODO and get something that isn't interfering with your day-to-day computer activities. AVG-Free is pretty good.

[laserfan]

DVD-RB PRO works fine on WIN7x64 on my system. Check anti-virus and on an of-chance DEP
I *REALLY* thought you had nailed it gonca with DEP, my having long ago forgotten about DEP problems with W7, but after first changing to Win Only and then turning it off altogether, DVD-RB still wouldn't launch.

If you are running COMODO -- that's probably the issue.
I DO use CIS! And although I had first made Rebuilder.exe "trustworthy", and later [tried to] turn it off altogether, I did finally as a result of your post look at its Defense+ Excecution Control Settings and found that if I added an Exclusion to "Detect shellcode injections (i.e. Buffer overflow protection)" that solved the problem! Oddly, for all the stuff I have on this PC now DVD-RB is the only exclusion there... and it's no doubt a bug that disabling Defense+ does not disable that feature--the only solution is the shellcode exclusion.

But no I will not ditch COMODO for another--I've tried so many such programs and like it best, at least my (now older version) 5.10. Haven't tried new 6. But it's now resolved; glad you made me look hard at CIS.

Thanks guys for helping me. :)

[steptoe]

I used to use comodo, and found it very good

But, also found it had a very nasty habit of taking offense to some software and just refusing to allow it run, and not bother telling you or flagging up as a suspect file first. Regardless of what settings I tried to change

It too had 'issues' with DVD-RB and letting it run, without much head scratching and banging it on the table to convince comodo to allow it to run


Shame really as it suited my needs, but what I use now does more and also tell me if its blocking something or warns me it wants to block something from running, which I can allow and it will still monitor it and flag up again if it thinks something not right with what the software is trying to do

[Groucho2004]

If you have it I'd recommend you dump COMODO and get something that isn't interfering with your day-to-day computer activities.
Or don't use AV software at all. We had that discussion some time ago... (http://forum.doom9.org/showthread.php?p=1412791#post1412791)

[laserfan]

Well my problem was solved so the point is moot, though I am curious steptoe why you didn't state the product you now use instead of CIS.

This was a really minor issue with CIS, which has been mostly set-and-forget for me and why I didn't think about the shellcode exclusion. The only major issue I've ever had with it was on an old XP machine running some Sony audio streaming software that I never could get to work--I had to uninstall CIS and am running MSSE on it instead.

Thanks again jdobbs for citing COMODO specifically here.