DOpus v13.14
Windows 10.0.19045.5131 (NOTE: Developer Mode ON)
UAC is set to the default top level.
There's no "ADMINISTRATOR" label in the toolbar.
I'm unable to create a folder in "Program Files" or read/traverse some "NT Service/TrustedInstaller"-owned folders (such as "WindowsApps"). If I close DOpus and re-run it as "administrators", I'm able to do both of those things. "ADMINISTRATOR" does appear in the title bar when I run the app as administrator. The Admin button stays disabled in all cases.
I've rechecked the compatibility settings and everything is unchecked (including DPI settings for both myself and "all users").
Yep, I thought it was some permissions issue. I'd just like to be able to bypass by using the timed "Admin" button instead of be required to restart dopus.exe as ADMINISTRATOR.
Restarting is a viable work-around. I was just hoping I could fix the "Admin" button.
Strange. If you use File Explorer to make a folder under Program Files, does that trigger a UAC prompt?
As in "Always notify me"? I think the default is the level below that, FWIW, although the difference between the two levels only affects File Explorer and other parts of Windows, not third-party apps like Opus.
Admin Mode won't help there, unfortunately, since it doesn't change how directories are read. It's a rare case where elevating the whole program is needed if you want to look in that directory. (But elevating like that is not recommended in general.)
I sometimes use an elevated command prompt instead, if I'm just trying to get a list of subfolders. (You can then paste the path into Opus and go into the subfolder in a lot of cases. It's only the parent directory that blocks non-admin users from listing the installed applications under it. The applications themselves are readable. It's a very strange choice on Microsoft's part.)
Of course, the real solution to the WindowsApps directory is to avoid installing things via the Microsoft Store.
I noticed over the weekend that the Admin button is now active again. I'm not sure of how it was re-enabled. I have rebooted a few times for other program configuration needs. And there was an Win10 update applied...
I wish I knew what the problem was; but, just working is sometimes better than knowing.