What's new in Never10 1.3.1
Apr 20, 2016
- Fixes a defect in the v1.3 command-line parser: The command-line argument scanner was not ignoring (as it should) the contents of the program's path. So v1.3 might register path text as commands.
New in Never10 1.3 (Apr 11, 2016)
- Added simple one-click enumeration and deletion of any previously downloaded Windows 10 files. The option will be presented to the user when it is available. Added multiple command-line verbs which suppress the presentation of Never10's GUI user-interface to support enterprise-wide deployment of Windows 10 disabling.
New in Never10 1.2 (Apr 1, 2016)
- Removed the read-only registry key protection added in version 1.1.
- Never10 appeared not to work for one person. I quickly prepared a version without the read-only enforcement and asked him to use it instead. He reported that it then worked. I may have overreacted, and probably did, his system may have been weird or in some odd state since many others have carefully tested Never10's operation and have never reported any such behavior. But since it is certainly conceivable that Windows might take offense to having the permissions removed from those keys, and since, for example, the Group Policy editor doesn't do that, I felt that “better safe than sorry” would be the best policy. And, frankly, the write-protection was almost certainly unnecessary anyway.
New in Never10 1.1 (Mar 29, 2016)
- Added read-only protection to the registry keys. Added a version number to the app's user-interface. We received some authoritative reports of some systems balking at our SHA1 Authenticode signature, so we obtained a new SHA256 code signing certificate from DigiCert.