I found the way to fix the issue quickly was to rename the current Dreamweaver configuration folder (something like "configuration-old" will do). Then be sure to start the extension manager and remove all extensions and then add back Security Assist.
By doing this, I was able to get the extension to work correctly. What I am not sure of is if it was another WebAssist extension causing the conflict or just the configuration folder becoming corrupt over time.
As I have time, I am adding back each extension and then testing to ensure there are no conflicts with other WebAssist products.
If you have non webAssist extensions installed, you may want to disable them and then test it out.