Last Modified: Dec 18, 2024
Affected Product(s):
APM-Clients APM, TMOS
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1
Opened: Mar 04, 2019 Severity: 3-Major Related Article:
K06273599
When Windows Driver Verifier is running on the Windows-based device, and you try to establish a VPN connection using BIG-IP Edge Client components, interaction with the VPN driver covpnv64.sys results in a Windows stop error/hard crash.
Microsoft Windows exhibits a stop error. This occurs because Driver Verifier detects an error condition in a Windows driver, in this case the F5 VPN driver covpnv64.sys, which occurs whenever you initiate an F5-based VPN connection. You must reboot the Windows device to restore functionality. If your company requires F5-based VPN connections when working from a remote environment, this issue prevents you from debugging and testing Windows drivers during development without additional considerations, as described in the Workaround section.
-- Windows Driver Verifier is running on your Microsoft Windows-based device. -- You try to establish a VPN connection using BIG-IP Edge Client software or a web browser.
You can prevent this issue from occurring using either of the following suggestions: -- Do not execute Windows Driver Verifier when running BIG-IP Edge Client or its web browser components if you plan to establish a VPN session. -- Do not use BIG-IP Edge Client or its web browser components to attempt to establish a VPN connection if you plan to run Windows Driver Verifier. If you are developing a driver and your corporate environment requires BIG-IP Edge Client or its web browser components for VPN connections, you can do either of the following: -- Perform your driver debug and test on a VM image running Driver Verifier while the host machine, where Driver Verifier is not running, connects to the corporate VPN. -- Use the Driver Verifier GUI to exclude covpnv64.sys during its processing. This enables you to debug and test the driver you are developing without encountering the Windows stop error. Additional information: From the Microsoft Windows Driver Verifier documentation page (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier): -- Running Driver Verifier could cause the computer to crash. -- You should run Driver Verifier only on computers you are using for testing and debugging. -- You must be in the Administrators group on the Windows device to execute Driver Verifier. -- Driver Verifier is not included with Windows 10 S. -- Driver Verifier is not distributed as a separate download package. Therefore, F5 recommends testing driver behavior in Windows 10 instead.
None