Hi Robbie,
Thanks for posting that information up. By the looks of it, something has modified your start up items in the Windows Registry (i.e. what applications start when you login to Windows) and is now preventing Viscosity from reading/writing this list. Viscosity checks to see if it is in the startup list to adjust the preference within Viscosity in case an administrator sets Viscosity to start at login while Viscosity is closed. We have just put up a new beta and included a fix to prevent this crash from occurring if you would like to give it a go, but I would highly recommend running a virus scan if you can to make sure nothing malicious is at play.
You can grab the latest beta here - https://www.sparklabs.com/forum/t/beta-latest-build-of-viscosity-for-windows/362/1
Regards,
Eric
