Serious Discussion Move file bug: Windows 11

[Victor M]

Windows 11 24H2 is buggy when it moves files from a UAC protected directory.

When I select to move 50 files out from a UAC protected directory like Windows/System32//CodeIntegrity/Cipolicies/Active and paste it into /Documents, sometimes it doesn't show the multi-file prompt nor the UAC prompt.

The problem does not occur when moving files in to the UAC protected directory.

The solution is to copy, not move, the files once. And then the multi-file prompt and UAC will show up again from then on.

This bug may also be caused from the files coming from a Linux machine.

 

[Bot]

Sorry I couldn't contact the ChatGPT think tank

 

[Divergent]

Windows 11 24H2 is buggy when it moves files from a UAC protected directory.

When I select to move 50 files out from a UAC protected directory like Windows/System32//CodeIntegrity/Cipolicies/Active and paste it into /Documents, sometimes it doesn't show the multi-file prompt nor the UAC prompt.

The problem does not occur when moving files in to the UAC protected directory.

The solution is to copy, not move, the files once. And then the multi-file prompt and UAC will show up again from then on.

This bug may also be caused from the files coming from a Linux machine.

Files from Linux: A Likely Culprit.

You hit on a very strong point about the files coming from a Linux machine. This is a highly probable piece of the puzzle. Linux and Windows handle file permissions and attributes quite differently—think POSIX permissions versus NTFS ACLs. When you move files from a Linux environment to Windows, especially into a UAC-protected spot, Windows can genuinely struggle to properly apply or even understand the security information attached to those files. This mismatch could absolutely throw UAC for a loop, leading to the inconsistencies you're seeing.

Why This Bug Might Be Happening
Beyond the Linux factor, here are a few other possibilities for what's going on:

* Permission propagation headaches: It's possible that the initial "move" operation just isn't properly carrying over the necessary permissions or ownership details when files jump from a Linux file system to a highly protected Windows folder.

* Caching gone rogue: Windows tries to be smart, often optimizing file moves by caching things like UAC consent or file metadata. If this caching mechanism gets corrupted, or if it just can't make sense of files with "unusual origins" (like from Linux), it could prevent those prompts from popping up.

* A new bug in 24H2: Since you mentioned Windows 11 24H2 specifically, it's entirely plausible this is a fresh bug, or a "regression," introduced in that particular version. We've seen other reports of quirky file explorer and UAC behavior in 24H2, so your experience wouldn't be unique.