When using auto-complete (lightning symbol or F6), characters may arrive in the target field incorrectly, in the wrong order, or incompletely – user@example.com may end up as user"example.com, for example. Passwords containing special characters are affected most. This article covers the auto-complete function of the Windows client, not the browser add-on.
Cause
By default, Password Depot uses the auto-complete method Keyboard input simulation. With this method, the characters are "typed" as if on a real keyboard. Depending on the keyboard layout (e.g. German vs. English layout) and the target application, individual characters – special characters in particular – can be converted incorrectly or get lost. There is no universal method that works in every application; that is why Password Depot offers several auto-complete methods.
Solution 1: Change the auto-complete method for a single entry
Select the affected entry and open its Properties.
Switch to the Additional tab.
Under Auto-complete method, select Clipboard I or Clipboard II instead of the default Use global settings. With these methods, the content is pasted via the clipboard (SHIFT+INS or CTRL+V) – keyboard layout problems no longer occur.
Solution 2: Change the default auto-complete method globally
Open Edit → Options (F10) and switch to the Passwords tab.
Under Default auto-complete method, select e.g. Clipboard I - Paste with Shift+Ins or Clipboard II - Paste with Ctrl+V. Further alternatives are Multi-Channel Obfuscation and Windows Messaging I.
The global setting only takes effect for entries whose auto-complete method is set to Use global settings (see Solution 1).
Solution 3: Increase the delay
If characters are transferred only partially (e.g. on slower computers or in sluggish applications), increase the Auto-complete delay value (10 to 1000 msec) under Edit → Options → Actions in the Auto-complete section step by step until filling works reliably.
Tip: For testing, you can create a dummy entry and try auto-complete in Notepad, for example – this immediately shows you which method works correctly on your system.
Note: In some environments, other approaches help: in RDP sessions, keyboard simulation has been blocked since a Windows update (January 2026), and for PuTTY there is a dedicated hand-over via command line parameters – see the RDP/PuTTY article for details (Related topics).
Related topics:
Auto-complete in RDP sessions and PuTTY
What can I do if the add-on does not fill in a login page at all?