diff --git a/doc/bugs/Missing_file_content_in_secondary_worktree___40__win__41__/comment_3_69386f9f7c39782f4809beb5a7b6df92._comment b/doc/bugs/Missing_file_content_in_secondary_worktree___40__win__41__/comment_3_69386f9f7c39782f4809beb5a7b6df92._comment
new file mode 100644
index 0000000000..85e3b7bf95
--- /dev/null
+++ b/doc/bugs/Missing_file_content_in_secondary_worktree___40__win__41__/comment_3_69386f9f7c39782f4809beb5a7b6df92._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2025-07-11T16:42:26Z"
+ content="""
+I've verified that `populatePointerFile` is not getting called in this case,
+and does get called in the same situation on ext4. And that call is made by
+`reconcileStaged`, which is getting called. 
+So I would look in there for the bug.
+
+Except, interestingly, some percent of the time, on ext4, manually
+populating the pointer file followed by git-annex add also does not call
+`populatePointerFile`. The pointer file remains unpopulated  until another
+process calls `reconcileStaged`, and it gets populated then. This seems
+like also a bug, possibly another case of the same bug?
+"""]]