Has anyone else had any issue with xp machines bluescreening after upgrading to 5.2.10? The bluescreen error is C000021a which references back to a problem with the winlogon.exe. No problems with Win7. Im assuming the difference is the XP use of a Gina and Windows 7 not. Rgiht now our machines are set to the primary gina of sbgina.dll with a passthrough to Msgina.dll.
Safeboot use to install itself to a folder called c:\program files\safeboot\ or something like that. On the new versions it installs to c:\program files\mcafee\endpoint encryption. I think the problem we have is that gina registry key was pointing to the old folder, but the sbgina.dll was now located in the new folder. Is anyone else having this bug on machines that have been upgraded several times and have the old folder structure?
usually you upgrade by modifying the file sets within EEM - you'd only have a path issue if you re-ran the install package, and the new package was set to install into a different folder than the current installation?
Stick to the file group method and you should not come across this issue.
each file for the client in the file set should have a destination path of [appdir] - this means put it in the place the initial install set went.
the only thing which can change the install path, is the installer itself.
So, if you somewhere along the road have had EEPC files ending up in two different paths, either someone set an explicit path for the file in eem, changed the registry key for the client, or re-ran the install package.
Maybe on one of your affected machines, check what the registry safeboot installpath key is set to?