[+] Decreased load times
[+] New splash screen
[!] On some systems first time installed, the automatic logon would not work until a second restart.
[+] Option to show SALPS servers found in DNS from the Safe AutoLogon client
[+] Enhanced in-process encryption with additional encryption processes
[+] Decreased logon time when using SALPS from about 30 sec to about 5-10 sec; the time decrease is an estimate and depends on network and environment
[+] ‘Domain networks’ firewall on the Safe AutoLogon client computer can now be turned on and it will still get the password from a SALPS server
[!] Safe AutoLogon graphic was showing after the session logged off
[!] Password complexity was only calculated as a password was being typed in; now the complexity also shows when the program starts
[+] Added minimize option to application
[+] Misc improvements
[!] Fixed automatic logon on Windows Server 2016
[!] Fixed unsigned executable
[!] Non-administrators changing settings, when asking for credentials and prompt is canceled, spurious error is now not shown
[+] Updated software to be compliant with SALPS 8.0
[!] Updated query system for SRV records to avoid permissions error
[+] Improved SALPS communications on Windows 7 x86 systems if the SALPS was unavailable or the network was unplugged
[!] Fixed minor licensing issue with LAS across a WAN
[!] Fixed issue with SALPS if the username was not found, the CAD prompt was delayed to allow the user to login
[!] Adding a computer to the SALPS via command line might corrupt the SALPS database
[!] Changed DNS query code that could spuriously log a 9003 DNS error in the event file
[+] Settings can be protected from another group residing in another domain. If the client running Safe AutoLogon belongs to domain "A" and it logs in as a user on domain "A", the settings can be protected by a user that is a member of group "C" in domain "B". This gives more control over changing settings on the client.
[!] Windows 8.1 clients would not automatically logon after a power off/power on.
[!] If a SALPS server is listed in DNS, but the SALPS server doesn't exist and Safe AutoLogon is set to use local credentials, Safe AutoLogon would not automatically logon.
[+] The local hosts file can be used to list a SALPS server, if DNS servers cannot be updated with the SRV record
[+] A new command-line utility allows a previously-saved salset file to be saved on a local or remote computer
[+] Querying remote SALPS servers is no longer dependent on the current user’s security rights
[!] SALPS server order was not being saved
[+] Misc internal code updates.
[+] Updated licensing for more flexibility with the LAS, so the software doesn't check in with the LAS after each boot.
[+] Added a 'Check for Updates' option.
[+] Updated for Windows Server 2012 R2 and Windows 8.1 compatibility.
[!] Fixed the "code expired" error after pasting in a valid evaluation code.
[+] Added a Help file
[!] Misc internal improvements
[+] Added new language (Chinese). 15 languages supported: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Indonesian, Italian, Malay, Norwegian, Portuguese, Spanish, Swedish.
[+] Changed Options button functionality.
[+] Updated the menus for Arabic and Chinese languages; changed misc labels and times to display appropriate language.
[!] Fixed Safe AutoLogon not logging on if a company shows a security message prior to logging on and it is not acknowledged by the user by pressing the OK button after two minutes.
[!] Fixed the confirmation of removing a SALPS server may not be visible.
[+] Added new languages (Arabic, Malay, Indonesian). Languages supported (14): Arabic, Danish, Dutch, English, Finnish, French, German, Indonesian, Italian, Malay, Norwegian, Portuguese, Spanish, Swedish.
[+] Entire user interface is now shown in all supported 14 native languages.
[+] Simplified evaluation start screen.
[+] Certified for Windows 8.
[+] Added discount option on Settings window.
[!] Fixed issue with domain-joined XP and pressing the Shift key if Ctrl+Alt+Del were bypassed.
[!] Fixed issue when receiving SALPS settings for security groups privileges.
[+] Added the ability to use the SALPS server if automatic log-back-on is enabled when a user logs off.
[+] New graphics.
[+] Now compatible with Windows 8 and Windows 2012.
[+] Added new capabilities to coincide with the release of Safe AutoLogon Password Server 5.0.
[!] Fixed user security configuration not keeping its values.
[!] Fixed an issue with x86 Vista and x86 Windows 7 systems in a VM where the reboot may freeze the VM.
[!] On 64-bit systems, the About box was showing 32-bit.
[!] Fixed minor auto-logon issue with Win7x64.
[+] Faster AES calculations.
[!] Minor bug fixes, not logging on with some x64 computers.
[!] If the trial expired, or had 15 days left, the window indicating this information could not be closed.
[!] If there was no DNS server available or the SRV record's computer was unavailable, running the UI for the first time would show "Installation Date Unavailable".
[+] Optimized SRV record querying from DNS.
[+] Safe AutoLogon now looks for an SRV DNS record entry for the SALPS server by default, instead of storing the SALPS server locally on each SAL client.
[+] Running the software for the first time no longer prompts to scan for SALPS servers. Users can Scan for SALPS servers when adding them using Settings.
[+] Like on Vista/7/2008, the Safe AutoLogon graphic now appears on the "Welcome to Windows" page.
[+] The Settings window has been simplified.
[+] If the TLP license is expired and the user tries to run the software twice (within 15 seconds), a notification showing TLP expired is shown. This allows the program to end gracefully without notifying end users.
[+] Main UI Shows the maximum encryuption of the operating system.
[+] There now is always a fixed amount of asteriks in the Password field, regardless of the length of the actual password. This decreases the ability to guess the password based on the number of characters.
[+] More menu options.
[!] Fixed autologon issue happening on some computers.
[!] Fixed a few integration issues with the LAS on Novell networks.