Thu Aug 15, 2019 9:54 pm
Hello,
I think it's the latest upgrade-update in windows 10 build 1903 that causes this.
1903 has stricter rules about app permissions. It can be set to not allow app install if said app does not come from MSFT store. I had set this to allow "wild" apps, and it still warned me when I was going to install version 2.50.
Run setup as admin (R-cklick to run as admin), when the warning popup shows, hit "more information" to get to the option to install it despite this...
And after installation succeeded, you will indeed be surprised that the first time you run it from the icon, drag/dropping a title into the fields does not result in the behaviour we was used to.
So I again launched from icon, but with R-click as admin.
This time drag/drop worked for one field, so I dragged the other file onto it as well.
After the machine was rebooted, I tried this again, without running it as admin, and it worked like old times.
So, I really think it is build 1903 that throws a curve ball.
Behaviour of subtitle edit also changed, see. When film and srt files have same name, the film should load automatically.
Well, as of a few days ago this is no longer true. As user with admin rights, (not R-clicked) it only sometimes works.
Maybe it has to do with associations and permissions, but it could also be about the way filenames are written.
I observed that in some cases, windows cuts off parts of the filename that follow a dot.
(some releases have over a dozen dots in their filename)
Maybe it does not like spaces either?
When I use a bulkrename tool to replace every dot by a space, the film sometimes still does not launch despite the fact that I had doublechecked that those names was identical (even by copying the Film-name to srt-name).
(sometimes is a keyword here. Because sometimes it works as expected, sometimes it don't.)
And that can make you wonder about your sanity, but even worse, when one reports odd behaviour it can meet sceptisism because other people cannot reproduce the reported behaviour...
So, we will have to ask fijnproever one important question.
What build of windows is he on?
My fear is the following:
In build 18xx things may work smoothly, and in 19xx they may no longer work, or not smootly.
So, if one is on 1903, one has to go look at security settings, and/or settings for developers (where you will see the option about store apps)
Kind regards, Jaak.
An afterthought: Maybe I's not mad. The world's just gone cuckoo, though.