Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / Windows 11 Quietly Mandates Enterprise File Explorer Group Policy Controls
Transcript
- Lucas: So Microsoft shipped a pretty significant set of quiet changes in Windows 11 version 24H2 that a lot of IT admins might have missed. I'm talking about new Group Policy settings specifically for File Explorer. Luna: Wait, I thought File Explorer policies have been around forever. What's actually new here? Lucas: Fair question. There have always been a handful of policies, but 24H2 adds over a dozen new ones. They're all under 'Windows Components > File Explorer' in the Group Policy Editor. Things like controlling whether the modern context menu shows up, or whether users can see the ribbon, or even if the navigation pane auto-expands. Luna: So Microsoft is finally giving IT admins the ability to shape the Explorer experience beyond just registry hacks. That's actually huge for deployments. Lucas: Exactly. And one specific policy I think every enterprise admin should know about is called 'Remove the File Explorer context menu.' Sounds scary, but it's actually a way to turn off the modern right-click menu — the one with the icons and the 'Show more options' link — and force the classic menu instead. That is a massive help desk ticket reducer. Luna: Because users still get confused by the two-step context menu. They click 'Show more options,' and then they call IT. I've seen that in my own org. Lucas: Right. And now you can just set that policy to 'Enabled' and everyone gets the classic menu. No registry scripts, no third-party tools. There's also a policy to control the shortcut arrow overlay on desktop icons. Another one to disable the gallery feature that appeared in 23H2. Luna: The gallery was a nice addition for consumers, but in an enterprise environment, it's just another distraction. I can see IT wanting to kill that. Lucas: Exactly. And the policy is literally called 'Turn off File Explorer Gallery.' Set it to 'Enabled', reboot, and it's gone. That's the sort of granular control that enterprises have been asking for since Windows 11 launched. Luna: Now, are these policies only available in the Pro and Enterprise editions, or does Windows 11 Home get them too? Lucas: Great question. They're available in Pro, Enterprise, and Education. Not in Home. But honestly, if you're deploying in a business, you're probably on Pro or Enterprise anyway. And they're all part of the 24H2 update, which started rolling out in late 2025 and is now broadly available as of mid-2026. Luna: So for IT admins who are still piloting 24H2, this is a good reason to accelerate that rollout. Lucas: I think so. And here's a concrete example: there's a policy called 'Remove default context menu items.' You can specify which entries — like 'Share' or 'Give access to' — are removed entirely from the context menu. That's huge for reducing security surface area. Luna: Because the 'Share' menu can accidentally leak data to the wrong people if a user clicks too fast. Lucas: Exactly. So you can strip it company-wide. Another policy lets you set the default view for all folders to 'Details' instead of 'Tiles' or 'Icons.' That's one of those small things that makes a big difference in user training. Luna: I've always thought that if Microsoft just made Details view the default everywhere, they'd save millions in support costs. Lucas: They'd probably save billions across all enterprises. But now you can enforce it through policy. And there's also a setting to disable the 'Compact view' mode in File Explorer — that one was a controversial UI change in 23H2 where folder spacing got tighter. A lot of users hated it. Luna: I remember that. The compact view made everything feel cramped. But you could only change it via a hidden registry key before. Now it's a policy? Lucas: Yes, now it's a policy: 'Do not allow compact mode in File Explorer.' Enable it, and the option disappears from the View menu. That's the kind of control IT wants. Luna: So putting it all together: Microsoft is moving toward a model where IT can strip Windows 11 down to exactly what the business needs, without forcing users to relearn the OS every year. Lucas: That's exactly the trend. And I think it's smart. Windows 11's consumer features — like the gallery, the new context menu, the compact view — they're fine for home users. But in a business, they create friction. These new policies let IT remove that friction without resorting to hacky scripts. Luna: And fewer hacky scripts means fewer things that break after a cumulative update. That's a win for stability. Lucas: Speaking of which, there's also a policy to control the 'Open in Windows Terminal' context menu entry — you can hide it if your users don't need command-line access. And you can disable the 'Pin to Quick Access' option. It's really comprehensive. Luna: I want to dig into the deployment logistics. How do IT admins actually roll these out? Is it just standard GPO, or is there something new? Lucas: It's standard Group Policy. You download the 24H2 administrative templates, load them into the Central Store on your domain controller, and then you can configure these policies just like any other. They also work with Intune's settings catalog if you're doing cloud-based device management. Luna: So no new tooling required. That's important because IT teams are already stretched thin. Lucas: Absolutely. And one more policy I think is worth calling out: there's one called 'Remove the 'Give access to' command from File Explorer.' That's a direct security control. If you're worried about users accidentally sharing folders to the wrong people, you can just remove that option. Luna: It's like a whitelist approach to the UI: you only show the things users actually need. That's good security hygiene. Lucas: Exactly. And it's a sign that Microsoft is listening to enterprise feedback. These aren't just cosmetic tweaks — they're practical controls that reduce support costs and improve security. Luna: I wonder if this means we'll see similar policy expansions for other parts of the OS, like Settings or the Start menu. Lucas: I hope so. The Start menu has needed better policy controls for years. But for now, File Explorer is where the action is. If you're managing Windows 11 devices, I'd strongly recommend checking out the 24H2 administrative templates and enabling at least the context menu policy. Luna: Before we move on, I want to tie this back to something practical. If listeners want to support the show and help us keep doing deep dives like this — no pressure — but we do have a donation page. It's buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Lucas: And we really appreciate it. Every little bit helps us stay ad-free and focus on the details that matter to IT pros. So thank you to anyone who contributes. Luna: Alright, back to the policies. Lucas, you mentioned the 'Remove default context menu items' policy. Can you give an example of how an admin would configure that? Lucas: Sure. The policy takes a list of CLSID GUIDs — those are unique identifiers for shell extensions. So you'd find the GUID for 'Share' or 'Edit with Photos' and add it to the list. It's a bit technical, but Microsoft's documentation has the GUIDs for common entries. For instance, the GUID for 'Share' is one seven-digit code, and once you add it, that option disappears from every user's context menu. Luna: So it's not a simple checkbox, but it's still far easier than editing the registry on every machine. Lucas: Exactly. And you deploy it once via GPO, and it applies to every user. That's the power of Group Policy. Luna: I think we should wrap up with a practical recommendation. For IT admins listening: what's the one policy they should implement today? Lucas: The context menu policy — 'Remove the File Explorer context menu' set to 'Enabled' — is the one that will save you the most help desk calls. Users stop calling about 'where did my old right-click go?' and you get a consistent experience. After that, I'd look at disabling the gallery, setting default view to Details, and turning off compact mode. Luna: That's a solid shortlist. And it's all free, built into the OS. No third-party tools needed. Lucas: Exactly. Microsoft is finally giving enterprises the tools they need to make Windows 11 work for them. And with 24H2, File Explorer is now fully manageable. It's a small change in the grand scheme of things, but for IT teams, it's a huge quality of life improvement.