In version 5.x of SafeGuard, the registry value "LastLoggedOnUser" is no longer evaluated correctly, resulting in a state where LastLoggedOnSAMUser and LastLoggedOnUser are no longer synchronous. This could lead to issues with third party logon applications. This has been fixed with the release 6 of SafeGuard. A hotfix for SafeGuard 5.60 is also available.
↧
Registry Value LastLoggedOnUser is no longer correctly evaluated after installation of SafeGuard 5.x
↧