Hi Marcel.
just to be clear. The procedure described should start Slick as if it's installed the very first time to find out if your 'normal' configuration is causing the problem.
Go to 'C:\Programme\SlickEdit\win' using explorer or preferably TotalCommander
or the CMD shell (cmd.exe).
e.g. in CMD shell type
D:\Tools\Editor\SlickEdit\win>
vs -sc C:\TEMP telling Slick to use 'C:\TEMP' as it's config dir.
Ensure that there is no Slick config stuff (especially
vslick.sta) in 'C:\Temp' before doing so.
There should be no error message like 'C:\Programme\SlickEdit\vslick.sta' is not recognised as a compatible state file or pcode file'.
HS2