diff --git a/chrome/content/zotero/xpcom/itemTreeView.js b/chrome/content/zotero/xpcom/itemTreeView.js
index 23e1ac159..7f7b3faf7 100644
--- a/chrome/content/zotero/xpcom/itemTreeView.js
+++ b/chrome/content/zotero/xpcom/itemTreeView.js
@@ -2558,7 +2558,7 @@ Zotero.ItemTreeCommandController.prototype.onEvent = function(evt)
 Zotero.ItemTreeView.prototype.onDragStart = function (event) {
 	// See note in LibraryTreeView::_setDropEffect()
 	if (Zotero.isWin) {
-		event.dataTransfer.effectAllowed = 'move';
+		event.dataTransfer.effectAllowed = 'copy';
 	}
 	
 	var itemIDs = this.saveSelection();
diff --git a/chrome/content/zotero/xpcom/libraryTreeView.js b/chrome/content/zotero/xpcom/libraryTreeView.js
index a6cd76b35..90f25e055 100644
--- a/chrome/content/zotero/xpcom/libraryTreeView.js
+++ b/chrome/content/zotero/xpcom/libraryTreeView.js
@@ -208,6 +208,11 @@ Zotero.LibraryTreeView.prototype = {
 		// as the dropEffect. This allows the dropEffect setting (which we use
 		// in the tree's canDrop() and drop() to determine the desired action)
 		// to be changed, even if the cursor doesn't reflect the new setting.
+		//
+		// Update (07/2014): We now use 'copy' for effectAllowed on Windows in
+		// onDragStart, since with 'move' text can't be dragged to Chrome
+		// textareas (and probably other places). This locks the cursor at copy,
+		// even when Shift is used, but that seems less bad.
 		if (Zotero.isWin) {
 			event.dataTransfer.effectAllowed = effect;
 		}