on two different files, i had to edit how they handle high dpi screens. couldn't open the advanced properties to do that with DO. But to my surprise FE opened them to edit fine.
What kind of files?
Which properties are you trying to edit?
How are you editing them? Do you mean via the Properties dialog?
.exe files. yes via the Properties, Advanced. files that need the advanced properties for high resolution to edited. See attached installation exe that creates the two files to be edited and a movie of the editing using FETurbo-Plugin.zip (99.4 MB) .
The Properties dialog that you edit those settings from is not part of Opus. It's part of Windows.
If it doesn't let you make changes to exe files when launched from Opus, it's probably due to your antivirus.
if it were AV wouldn't it happen with File Explorer also?
any suggested AV exclusions for Dopus?
I'm assuming you're using Windows Defender, as it's the main cause of this kind of problem lately.
Defender whitelists File Explorer by default.
The code being run that is failing is not even part of Opus. We have no code in Opus to change the DPI settings on executables. Everything in the Properties dialog for exe files, including the dialog itself, is either part of Windows or (rarely, these days) part of a shell extension something else has installed. Opus's only involvement is to ask Windows to open the Properties dialog and tell it the file(s) to open it for. Windows then runs its own code inside the dopus.exe process, and then Defender, another part of Windows, may block its own code from working properly because of the process it's in.
Antivirus decides whether to allow actions based on the process performing the actions, as well as the actions themselves. Some also factor in which company signed the main exe file. In our case, our signing certificate was about to expire (as they do every 3 years) and we recently renewed it, which has made Windows Defender trust Opus less until it has seen the new certificate for a while.
The worst thing is that Defender (not just it; there are some other awful antivirus as well) thinks actions are suspicious enough to block, but not suspicious enough to tell you it has blocked them. This means that if the action wasn't actually malicious, you are left wondering why it didn't work, and we have our time used up answering questions and investigating things while the people actually responsible -- Microsoft in this case -- broke things with no cost to them at all. Worse, if the action actually was malicious, the antivirus chose not to warn you, which makes no sense from a security point of view. If it believes you are or may be under attack, it should tell you there's a problem. If it doesn't, it shouldn't be blocking random actions.
Add C:\Program Files\GPSoftware\Directory Opus\dopus.exe to the whitelist(s). Defender has separate whitelists for the "virus & thread protection" and "ransomware protection" parts of it. The latter seems to cause a lot of the strange problems people have, if it has been turned on.
Or, even better, switch to an antivirus that doesn't break random things without telling you. Defender has become absolute garbage in the last few years. If you want a better antivirus, ESET/NOD32 has never caused any weird issues like this, at least in our experience, both as users of it for a very long time and in terms of support issues.
With the signature change, Defender has probably caused more issues this month than every other antivirus combined has in years. Defender is supposed to prevent malware but it has become malware itself.
1 Like
I always have Windows Defender disabled as best I could.
Been using Sophos Endpoint for last couple of years. Usually tells me when it blocks something.
But helpful to learn what you're saying.
Thanks.