Replies: 3 comments 2 replies
-
I will update that in the next version, thanks. It's a practice these days to flag indie unsigned applications as "malicious", to distract people from doing what they want with their machines, and instead sticking only to programs promoted by various app stores and so on. ExplorerPatcher has its entire source code published, it is built on untouched machines in Microsoft's cloud and the binaries you get are untouched, straight what those computers have compiled (you can check the contents against the artifacts produced, you will see they are identical). By the nature of such an app, ExplorerPatcher employs some behaviors that might also be usually found in real malware applications: the tools are there, offered by the OS, it is up to the developer on what he/she decides to do with them. ExplorerPatcher doesn't do anything malicious to that end, using all these powers only to achieve its goal, and the libre nature when it comes to its auditing and lack of telemetry I think speak for themselves. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Weirdly the copyright is still the same in the newest version. |
Beta Was this translation helpful? Give feedback.
-
It is not necessary to maintain copyright later date. Many products on the market are sold with such outdated copyright notice. What is more importtant in the starting date. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This isn't really anything important, but when you open the Properties/Details page for the Installer it says Copyright 2006-2022 instead of 2006-2023.
Also, for some reason both Chrome and Windows think that the installer for 22621.1413.54.1 isn't safe, even though the installers for previous versions are.
Beta Was this translation helpful? Give feedback.
All reactions