File explorer 3 dots menu still opening upwards in Build 261000.3321.
How long will it take to get a fix that works with any display scaling? 🤬🤷♂️
File Explorer truncated menu across builds
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Split from this thread.
Same problem with 27723.1000. File explorer 3 dots menu opens upward regardless of the position of the window.
It truncates the menu when the window is close to the top of the screen.
Note that the View and the Filter menus open correctly downward, it is only the 3 dots menu that opens in the wrong direction. 😂😂😂
Looks like they are propagating bugs from one build to the other instead of propagating fixes. 😝🤬🤷♂️
Windows Insider program | Windows Insider preview | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
155 answers
Sort by: Oldest
-
Anonymous
2025-02-19T03:44:47+00:00 -
Anonymous
2025-02-21T22:03:59+00:00 Still the same problem on Dev Build 26120.3291 on Feb 21, 2025.
MS seems clueless on this problem. When they tried to fix it, they added a new different bug. 😠😵💫🤬🤷♂️
-
Anonymous
2025-02-28T21:03:58+00:00 No changes with Build 26120.3360. Still broken. 🤷♂️
Same in Canary Build 27802.1000.
Still, they have no clue on how to fix this bug that was added by a useless experimental unrelated fix. 🤬🤷♂️
-
Anonymous
2025-03-07T22:08:01+00:00 Still the same problem with Build 27808.1000 on March 7, 2025. 🤬🤷♂️
-
Anonymous
2025-03-11T03:19:51+00:00 Finally, after more than 4 Months MS enabled an experimental fix that works correctly in Build 26120.3380.
Unfortunately, on my machines the fix was enabled only on 24H2 Beta and not in 24H2 Dev, even if they are now the exact same Builds numbers.
I will never understand why they create such a confusion with these experiments. 😝🤬🤷♂️
To get Dev to behave correctly like Beta I had to enable the experimental fix manually.
I just hope they propagate the same fix to all the other 24H2 builds where they added the same bug in the last 4 months. 🤞🤷♂️