Registry entry question (appcompatflags)

kira13

New member
My registry cleaner keeps flagging a VideoReDo entry, and I have a suspicion why, but I finally got around to asking someone.

This key:

HKEY_LOCAL_MACHINE\software\microsoft\windows nt\currentversion\appcompatflags\layers\

has this entry in it:

C:\Program Files\VideoReDoTVSuite\VideoReDo.exe

with a value of "DisableNXShowUI".

Now, on my machine at least, VideoReDo TVS has an executable file of VideoReDo3.exe, so I can see why the registry cleaner complains.

Is this an oversight with TVS vs. Plus, or is there an obscure reason for the entry to not point to the actual file? (I have been dutifully editing the entry each time I upgraded to the latest beta, but maybe I shouldn't have been, or maybe it just doesn't matter.)
 

Danr

Administrator
Staff member
I dont' know exactly what that registry is. It may be related to some old DEP error checking, but its not created directly by VideoReDo. Could be a residue from an old, old beta.
 

kira13

New member
Okay, sounds good.

But up until now, I have let the registry cleaner remove it every time, and it still showed up with each new version I installed. So it seems to still be in the registry entries that get added during installation.

Just thought you'd want to know.

Kira
 

Redmondman

New member
The installer *is* writing this key

I can corroborate (via Sysinternals ProcessMonitor) that the VRD-TVS installer *does* set this registry key. (Install version 3.1.5.564).
 

kira13

New member
I was going to edit to add this, but since someone else replied in the meantime...

I'm using this on Vista. Perhaps it's something Vista does in response to installing VRD TVS? But if so, you'd think it would pick up the correct executable. Oh, and as far as relating to DEP, I do remember either VRD+ or VRD TVS (I forget which I was using at the time) not installing when I first tried on Vista, and DEP did turn out to be the problem.

Now, based on Redmondman's reply, I'd guess it's not Vista doing it after all, but it still might be Vista-related. Redmondman, are you using Vista or XP? (Or something else?)

Kira
 

Redmondman

New member
I'm using XP. The stack indicates that it's being done by the installer, rather than by (for example) a system component's app-compat shim.

The entry itself does add VideoReDo.exe to the system's DEP exception list (so that execution in data segments is permitted).

If Dan or someone is willing to point me to symbols, I could identify the function in the EXE that's doing the registry set... :)
 

Danr

Administrator
Staff member
I can corroborate (via Sysinternals ProcessMonitor) that the VRD-TVS installer *does* set this registry key. (Install version 3.1.5.564).
You're right, it is being set by our installer.

From what I can tell its been doing it for over a year, probably in Plus as well. Early versions of Vista had a problem with our licensing manager and DEP, and this was an attempt to fool DEP. But it didn't really solve the problem. In the end the licensing manager vendor released a new version.

I think we can simply remove it from the installer for in future releases. However, in the meantime it shouldn't affect anything.

Thanks for researching it.
 
Last edited:

kira13

New member
Several apps I use regularly have registry entry issues; every so often, I think of writing to the companies that make the apps to ask them about their weird or obsolete or typo'ed entries, but this is the first time I've managed to do so. The DRD people are so responsive that it was a no-brainer to start here.

I actually meant to ask during the beta trials, but forgot. Sorry about that. (I figure it'll save someone else some confusion at some point once the unnecessary entry is removed. And it's always good to ask instead of just guessing that it *is* unnecessary.)
 
Top Bottom