On Monday (25 September 2017), we released version 4.7.0 of SecureAPlus. Along with some minor bug fixes and modifications it marked the inclusion of support for Windows Subsystem for Linux (WSL). In what was to be an improvement on the level of security for Windows 10 users also came with an unintended effect on devices running older operating systems – users were not able to boot to their OS after a reboot.
With some feedback from affected users, the update was quickly pulled and any further instances were avoided.
So What Happened?
Due to the inclusion of the new feature some changes were made in compiling the update resulting in an unintended dropping of support for devices running Windows 7 and older.
A Silver Lining?
SecureAPlus updates are slow to pick up so the majority of users were unaffected. Windows 10 users are unaffected by this so the update is inconsequential. Those that ran Windows 7 and older that manage to get updated were not all affected as the SecureAPlus driver does not update until the next reboot.
SecureAPlus automatic-updates do not force or prompt users for a reboot, only updates that were installed via a downloaded installer prompt for a reboot and even then they can refuse to reboot.
Only Windows 7 and older users that had an auto-update and subsequently rebooted their device manually for any reason were affected.
SecureAPlus version 4.7.2 is now available to the public and is no longer affected by this issue. Windows 7 users and older can now update to this latest version either manually or automatically.
If you are one of the users who was/is affected, the SecureAPlus team will do its best to help you through fixing the issue. Simply drop us an email at firstname.lastname@example.org and our team will provide support.
We are also extending affected user’s licenses (determined by device) by 1 month for the trouble regardless of whether you have Freemium or Premium (with or without Add-ons).