File Explorer truncated menu across builds

Anonymous
2024-10-09T19:12:09+00:00

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. πŸ˜‚πŸ˜‚πŸ˜‚

https://aka.ms/AAsdjir

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.

0 comments No comments

155 answers

Sort by: Newest
  1. Anonymous
    2025-02-14T18:48:46+00:00

    Contrary to what they show in the blog, this is still broken with Build 26120.3281. πŸ˜‚πŸ€¬πŸ€·β€β™‚οΈ

    • Fixed an issue causing the see more β€œβ€¦β€ menu in the command bar to open in the wrong direction for some resolutions.

    Image

    Edit:

    I figured out the difference. It is caused by one of those experimental features that was enabled on Beta and not on Dev.

    The feature is the one that added the labels under the icons in the context menu of 23H2, which is not needed in 24H2, because those labels are already added without that experimental feature.

    Anyway, with this build 26120.3281, it seems to fix the 3 dots menu problem but adds the second problem for the F.E. not closing just with a click on the red. X. 🀣🀣

    "Short blanket" story again, fix one a break another. πŸ˜΅β€πŸ’«πŸ€¬πŸ€·β€β™‚οΈ

    Here is the other case on the same Build with the 3 dots menu fixed, but also the added bug for closing File Explorer. πŸ˜΅β€πŸ’«

    Image

    and the added bug, just a click on the red X is not good enough to close File Explorer, needs a "Click + Hover away". πŸ€£πŸ€£πŸ€·β€β™‚οΈ

    Image

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-02-11T18:39:49+00:00

    Still the same bug with Build 26100.3194, on Feb 11, 2025.

    When is this going to be fixed?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-02-05T21:16:19+00:00

    Still the same problem with Build 27788 on Feb 5. 2025.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-02-03T19:12:07+00:00

    MS fixed it, partially...

    If your scale is 100%, it will be fixed. If you set the scale back to any other value, it will break again.

    We already know that, see all the FBH reports and posts in previous pages above. Reported months ago, and still no fix. 😎

    https://aka.ms/AAsohjl

    https://aka.ms/AAty8ub

    https://aka.ms/AAtyk9a

    Was this answer helpful?

    0 comments No comments
  5. Caozhi Li 7,525 Reputation points Volunteer Moderator
    2025-02-03T13:26:01+00:00

    MS fixed it, partially...

    If your scale is 100%, it will be fixed. If you set the scale back to any other value, it will break again.

    Was this answer helpful?

    0 comments No comments