[brazen1]

Run as admin was one of the things I've already tried. Still no affect. I can't understand why the .exe works for you and not myself? Is your W10 CU x64 architecture or x86? I'm on x64 Ultimate, not Pro, Home or School. I've also tried running the .exe's in compatibility modes. Having no idea the contents of your .exe's, am I correct in assuming it is a switch for Windows HDR on and off only? And if so, since I can manually control HDR, this rules out that something in my O/S is canceling your executions? I mean I have a lot of things turned off in the O/S including services, firewalled, etc. But those things don't seem to prevent me from manually setting the switch so I assume they shouldn't interfere with the .exe executing it for me either. If those .exe's are not dependent on some sort of settings in the player (even though I believe the settings are correct) it shouldn't matter if the player is even installed, correct? Step one is just to turn HDR on. The next step is to call up the player with proper settings and away you go, correct? I can't imagine what is unique on my end and not yours assuming it's a complicated native switch. If it's attempting to access the switch via real time registry, it's going to fail over here. Maybe that's it? I assume the switch is not as easy as a command in a Windows folder. I have no idea how that switch works or what it interacts with other than GPU drivers to reveal it and you wrote it's Nvidia friendly. Over my head guessing. Anyway, hope it's a simple mistake on my end or simple code edit on your end. Really like to get this going. Maybe if enough other testers step in the common denominator will be revealed. So far, looks like Intel integrated GPU is working and AMD for you and whatever your alpha testers used. Was there an actual NVidia test bed as well? Thanks for the dedication.