After authenticating in to FDE, the error 'Parameter Incorrect' shows before Vista GINA is displayed.

As a workaround, log in to the PolicyServer and locate the group where the device belongs. Set the policy TokenPassThru = No.

This error message appears due to following possible causes:

• FDE policies are not enabled for the group of the user where you are installing.
• You are trying to install as an Enterprise level account.
• The device is re-imaged.

To resolve the issue:

1. Ensure that FDE and MobileSentinel policies are enabled for the group you are trying to install the device for.
2. Use a user account that is setup properly at the group level.
3. If the device had FDE before, it is possible that the device is still in the Enterprise. You must delete the Device ID out of the PolicyServer from enterprise devices.
4. Ensure that the client has Microsoft .NET v2.0 SP1 or later and Windows 3.1 installer or later.

While Single Sign-On SSO is enabled, logging in to the FDE pre-boot shows 'Invalid Password'. Clicking OK passes the user into Windows without any further user input.

This is caused by the AutoAdminLogon registry key not being reset during an upgrade to SP5. This issue is resolved in the upgrade to FDE SP6.

To resolve the issue:

1. Open the Windows Registry by selecting Run and enter regedit then click Enter.
2. Search for the registry [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]AutoAdminLogon"="1" and change the value from "1" to "0".
3. Exit regedit.
4. Reboot PC and log into FDE.

You receive the following error:

This FDE patch could not be successfully applied to this computer. System.Exception: FDE 3.0.9.5 update has been suspended due to error 27 at Update_308_309a.Update.PerformUpdateWorkerForOldClients() at Endpoint Encryption.UpdateController.PerformUpdate().

This error can be caused by low disk space or a fragmented hard disk drive.

To resolve the issue, free up available space on the machine or defrag the hard disk drive and re-attempt the upgrade. Depending on how fragmented the drive is, multiple defrags may be required to successfully apply the patch.

The following error shows:

Uihr.exe Common Language Runtime Debugging Services: Application has generated an exception that could not be handled. Process id=0xbd8 (3032), Thread id=0xa88 (2696)

The setup is being run from a remote network share. The .NET security settings are preventing the application from installing over a network share.

To resolve the issue:

1. Copy the application setup files to the local computer.
2. Run the setup local location from there.
3. Adjust the .NET security settings to allow the application to run by using the Microsoft .NET security Policy Administration Tool.
4. Click Start > Control Panel > Administrative Tools > .NET Security Wizards.
5. Double-click Adjust .NET Security.
6. Click Next.
7. Change Local Intranet to Full Trust.

This error occurs because the PC is not XVESA-compliant and FDE does not run on non-XVESA-compliant computers.