Simply follow these steps:

1. Remove (unplug) all dongles
   
   
2. Download haspdinst.exe tool :
   https://package.windev.com/pack/addons/hasp/haspdinst.exe
   
   
3. Open the administrator command line and run: haspdinst.exe  -i -ld -fss
   
   
   
   
   
4. When the message "Sentinel Run-time ... operation successfully completed" is displayed, plug the dongle again and let Windows detect the dongle.
   
   
5. TCP and UDP ports 475 and 1947 must be opened on firewall, proxy ...
   The local driver administration website must be accessible in a web browser :
   http://localhost:1947/_int_/diag.html
   
   

Special cases:

• Uninstalling the driver can be done with the same haspdinst.exe program :
  https://faq.windev.com/8161-faq-read.awp
  
  
• Windows insider : this driver is not compatible with the versions of Windows (Preview Builds) deployed as part of the Insider program.
  
  
• Apple M1 processor, Microsoft Surface with ARM processor  The driver for a local dongle is only available for machines using an Intel x86 processor. Using WINDEV, WEBDEV or WINDEV Mobile on an ARM based machine is only possible when using a network dongle. See FAQ 3067 :
  https://faq.windev.com/3067-faq-read.awp
  
  
• Remote Desktop/TSE/RDP & Multiple licenses dongle ?
  If WINDEV, WEBDEV or WINDEV Mobile is launched remotely through the Windows remote desktop, the key must be of the network/multi workstation type. A single-user key cannot be used remotely through the Windows remote desktop (this is authorized by Teamviewer, VNC...).
  
  
• In the case of a network key for a multi-user license, apply the recommendations of this FAQ :
  https://faq.windev.com/3067-faq-read.awp
  
  
• "Sentinel LDK Licence Manager" service must be started. Make sure this service is running in case the dongle is not seen. If a local key is not recognized, make sure this service is running. Notably:
  
• port TCP/UDP 1947 must be opened
  
• set the startup type of the service to Automatic (delayed start)
  
• check whether any antivirus/spyware is not blocking the service