diff --git a/doc/bugs/Failing_to_execute_bash_remotes_windows/comment_2_7b8d82a32d6b82f1d50a54455aa4f643._comment b/doc/bugs/Failing_to_execute_bash_remotes_windows/comment_2_7b8d82a32d6b82f1d50a54455aa4f643._comment
new file mode 100644
index 0000000000..1ebf64afd1
--- /dev/null
+++ b/doc/bugs/Failing_to_execute_bash_remotes_windows/comment_2_7b8d82a32d6b82f1d50a54455aa4f643._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2017-03-08T19:20:21Z"
+ content="""
+git-annex on Windows already checks if external special remotes start
+with #! and tries to handle the shebang, since Windows does not do that
+natively. That was added in version 6.20160907.
+([[todo/refactor_shebang_handling_code_for_wider_use]])
+
+`git-annex proxy` does not do that, and I feel it's out of scope for it to
+do so. So the proxy stuff you tried is a red herring.
+
+It might be useful to use --debug to see what command git-annex tries to
+execute when running the external special remote program.
+"""]]