At the ApexSQL Support Forums someone reported it and the developers say it will be fixed in the next version, however they don’t know when they are going to release it. The solution is either to try using an older version of SQL Edit, use a Windows XP Virtual Machine to run it or just wait till they have fixed it.
