This is a known issue with your version of UPM. It is fixed in UPM 2.2. Please see UPM-1931 for more information (and more specifically, this comment with instructions on how to update to 2.2 to acquire the fix.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.