[... snip ...]
Does it happen with a default config? To create a default config, first exit SlickEdit and backup your existing config directory, then delete the contents under the directory named with the version number, like "11.0.2". Do not delete this directory, just the contents. When you start SlickEdit, it will create a default configuration. You can restore you config by deleting the default config and copying the backed-up (back-uped?) files back in the the 11.0.2 subdirectory.
A much simpler method using the command line, if the Slickedit executable is in the
%PATH% or
$PATH, is to change directory to the base of the Slickedit configuration directories (i.e. on Windows,
cd "%HOMEDRIVE%%HOMEPATH%\My Slickedit Config"), create a convenient test configuration directory, e.g. (on Windows,
md Test), and then invoke Slickedit explicitly passing the new configuration directory, i.e. on Windows,
vs -sc "%CD%\Test" This will start up Slickedit just as though it was freshly installed, you will be prompted to create tag files (which you can decline), choose a keyboard emulation, acknowledge the license agreement, etc.
No diffing and copying involved, and another advantage is being able selectively import textual configuration and macro file differences from your usual Slickedit config until you reproduce whatever the problem may be (although for files that Slickedit saves while shutting down, you'll have to start up in your original Slickedit profile to correctly diff your own config files and those in the new config).