I downloaded the recent Nightly Next version of Krita (krita-x64-5.3.0-prealpha-f71221a1) from Krita.org, so I could give some of the updated features a try. When I initially opened the app this morning it was done directly from the bin folder, after I extracted it. As I was happy with the stability, I decided to pin the app to my taskbar for ease of use, as I always do. However, when I click on the App icon I’m now presented with the prompt you see in the image below. I had no trouble with this from the previous Nightly Next build I was using (which I believe was krita-x64-5.3.0-prealpha-f80efca7). I suppose my questions are, these…
Did something go wrong with the build that I should be worried about opening it?
If not, why am I getting this odd prompt and is it safe to circumnavigate it?
In the past, like a year ago, I had problems running a Next version on Windows 11 but I didn’t use any kind of link. I just tried to run the executable in the portable .zip package folder.
The error message was something to do with ‘potentially dangerous executable’ .
Sometimes. I was able to get around the problem by running as Administrator but sometimes it gave me different forms of grief and weird messages. I stopped bothering with Next on Window 11.
I assumed it was because Windows Defender hadn’t been updated with the information that the latest version of Next was regarded as safe.
Try running the .exe file directly to see what message you get. I think it’s because of Windows 11’s paranoia.
It works fine if I open it directly from the bin folder, extracted from the zip. I just worry about why it’s giving me grief when I try to run that same executable from a shortcut. What makes it think it’s dangerous in one case, but not the other. I even scanned it with Defender, and it didn’t make a fuss. I found it odd that address ended with .Ink for some reason.
(Edit)
I was just poking around and decided to check the properties of the executable. At the bottom it had this:
I’m guessing it’s because it’s a portable version (so no installation needed). Still strange windows is fine with me opening it directly, but not from the shortcut.
