I remember i had this issue also and used your workaround. I believe it was caused by the Dropbox Shell Extension, which is injected in every process. Anyone with Dropbox can reproduce?