--- title: "4.9.6.1 Server Release Notes" slug: "4961-server-release-notes" updated: 2023-08-17T16:52:44Z published: 2023-08-17T16:52:44Z canonical: "mfa.rapididentity.com/4961-server-release-notes" --- > ## Documentation Index > Fetch the complete documentation index at: https://mfa.rapididentity.com/llms.txt > Use this file to discover all available pages before exploring further. # 4.9.6.1 Server Release Notes **Downloads** [4.9.6.1 Server](https://idauto.s3.amazonaws.com/mfa/server/4961/RapidIdentity_Server_v4961.msi) [4.9.6.1 Client-Side Components](https://idauto.s3.amazonaws.com/mfa/server/4961/RapidIdentity_Client-Side-Components_v4961.exe) ## Bug Fixes - MFA client authentication methods now follow OTP PIN policy fail limits (the attempts are user-configurable values, and the user can pick from Select box and Save - Fixed an enrollment issue of contactless cards in the case of a bad read - Fixed Admin Portal link failing issues when using from Self Service Portal - When installing the 4.9.6.1 Server, the "Need Help? Click here for installation Guide" button now forwards users to the RapidIdentity MFA Install Guide page --- ## Known Issues & Workarounds - FIDO PIN expiration policy for Self Service Portal is not working - There is no UI or page in the MFA Portal to set up failed PIN attempts for the PingMe authentication method separately; *The OTP PIN policy can be used for now* #### Version Rollback Issue Workaround > Unable to install previous versions after uninstalling 4.9.6.1 on NPS/Radius-enabled MFA Servers 1. Uninstall MFA server v4.9.6.1. 2. Stop IIS and remove the 4.9.6.1 installed directory (C:\Program Files\Identity Automation). Start IIS again. 3. Install the previous version (e.g. MFA server v4.9.4.6). 4. In IIS, navigate to SERVERNAME > Sites > API. Click on Advanced Settings and update the Physical Path to C:\Program Files\2FA\ONE Server\api. Click OK. 5. Navigate to ONE and click on Advanced Settings. Update the Physical Path to C:\Program Files\2FA\ONE Server\website and click OK. 6. Navigate to oneService and click on Advanced Settings. Update the Physical Path to C:\ProgramFiles\2FA\ONE Server\servicesite and click OK. 7. Navigate to REstServices and click on Advanced Settings. Update the Physical Path to C:\Program Files\2FA\ONE Server\restservices and click OK. 8. Restart IIS. #### Admin Portal Access Issue Workaround > Users are unable to access the Admin Portal after a clean 4.9.6.1 installation. After doing a clean installation of MFA server v4.9.6.1 and the database tables are successfully built, the URL in the *web.config* files will need to be updated accordingly. Please see our article about updating your server URL in the [following article](/v1/docs/your-request-cannot-be-processed-error). #### Radius-Enabled Server Portal Access Issue Workaround > The following steps are actually for **both** RADIUS and non-RADIUS enabled servers. Both should follow the same steps, but for RADIUS-enabled servers, continue to steps 5 - 6. 1. Open *regedit* and expand to the path: ``` HKEY_LOCAL_MACHINE\SOFTWARE\2FA Technology\ONE Server\Radius\[PolicyName] ``` 1. Verify that the key InstallPath exists at the above path, and if it does not, create it as a string type (e.g. *C:\Program Files\Identity Automation\RapidIdentity MFA*). 2. Expand to the path: ``` HKEY_LOCAL_MACHINE\SOFTWARE\Identity Automation\RapidIdentity MFA ``` 1. Select the InstallPath key from the list and double-click to edit the key. A popup will appear, and in the Value Data field, remove the *backslash* from the end of the string if it exists, and click OK. Change: ``` C:\Program Files\Identity Automation\RapidIdentity MFA\ ``` to ``` C:\Program Files\Identity Automation\RapidIdentity MFA ``` 1. Navigate to: ``` HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\AuthSrv\Param ``` 1. If the ExtensionDLLs key exists, verify the path matches the following (or **create it** as a *String Value* and include the below path for the value): ``` C:\Program Files\Identity Automation\RapidIdentity MFA\radius\2fanps.dll ```