Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / Windows 11 Fan Control Is an Enterprise Problem
Transcript
- Lucas: Luna, when was the last time you really noticed a laptop fan? Luna: Honestly? This morning. My Dell XPS spun up while I was on a Zoom call — just a quick burst, then silence. But it's that unpredictability that bugs me. Lucas: Right. And for the average user, it's a minor annoyance. But for an IT admin managing fifteen thousand Windows laptops across a company? That fan curve becomes a real operational headache. Luna: Yeah, I never thought of it that way. I mean, fans are just fans — they spin when it's hot, right? Lucas: That's the old model. What's happening now is that Windows 11, combined with modern hardware, is taking fan control away from users and even from IT. And it's causing real friction. Luna: How so? I thought fan curves were a bios level thing — something OEMs set and you live with. Lucas: They used to be. But over the last few years, especially with thin and light designs, OEMs have been locking down the BIOS fan tables. You can't tweak them with traditional tools like SpeedFan or NoteBook FanControl anymore. And Microsoft's recent Windows 11 24H2 update deprecated the old Win32 Fan Speed API, which broke a lot of those third-party utilities entirely. Luna: So there's a whole class of software that just… stopped working? That's a big deal for power users and IT. Lucas: It is. And it's not just enthusiasts. Enterprise IT often relies on scripts or tools to enforce consistent thermal profiles across a fleet — reducing fan noise in open-plan offices, or prioritising cooling in server-adjacent environments. When the API disappears, their scripts break. And the oem provided software — Dell Power Manager, Lenovo Vantage, HP Command Center — those are the only options left. But they come with their own issues. Luna: Such as? Lucas: First, they're often bloated. Lenovo Vantage, for instance, bundles warranty checks, driver updates, and bloatware. IT doesn't want that on every machine. Second, some OEMs are starting to charge for advanced power management features — Dell's Optimizer for business, for example, is a subscription add-on. And third, not all OEM tools let you set a static fan curve; many only offer 'quiet,' 'balanced,' and 'performance' presets, which might not match the company's thermal policy. Luna: So IT is stuck between a rock and a hard place. Either accept the OEM's preset, or lose fan control entirely. Lucas: Exactly. And here's where it gets even more specific. Some companies have actually reverted to Windows 10 LTSC — the Long-Term Servicing Channel — specifically because the old fan control APIs still work there. That's a drastic move, but it shows how important this is to some organisations. Luna: Wait — they're staying on an older OS just to keep fan control? That seems extreme. Lucas: It does. But consider a trading floor where every decibel matters, or a hospital where a sudden fan spin-up could distract a surgeon. For them, predictable acoustics are a requirement, not a preference. And Windows 10 LTSC gives them that predictability — at the cost of security updates and modern features. Luna: So Microsoft's deprecation of the fan API was probably meant to simplify the driver stack, but it's having these unintended consequences. Lucas: Exactly. And it's not just the API. The way Windows 11 handles power plans has also changed. In Windows 10, you could create custom power plans with granular fan settings via registry edits. In Windows 11, Microsoft has been pushing its own 'Modern Standby' and 'Power Throttling' policies that override manual settings. Luna: I remember reading that Windows 11 hides the 'Maximum processor state' setting behind a registry key for some devices. Is that related? Lucas: It's the same philosophy: reduce the number of knobs users can touch. Microsoft wants a consistent experience across devices, and that means fewer variables. But for IT, consistency isn't the same as control. They need the ability to say 'on these machines, fans never spin above 30 percent until the CPU hits 80 degrees.' That's not possible with the current tools. Luna: So what's the workaround? Are IT admins just living with it, or are they finding creative solutions? Lucas: Some are using Dell Command | Configure or Lenovo's ThinkPad BIOS configuration tool to set fan policies at the BIOS level before deployment. That works, but it's per-machine and hard to update. Others are using Group Policy to block OEM fan control software from running, forcing the device to rely on Windows' own thermal management — which isn't great. Luna: And third-party tools like SpeedFan — are they completely dead on Windows 11? Lucas: Not entirely. Some still work if you run them as administrator and disable driver signature enforcement, but that's a security risk. For most enterprises, that's a non-starter. The community has been trying to reverse-engineer the embedded controller protocols — there's an open-source tool called 'FanControl' on GitHub that works on some laptops — but it's hit or miss. Luna: If this is such a pain point, why haven't we heard more about it? I mean, this isn't a niche issue — millions of enterprise laptops are affected. Lucas: I think it's because fan noise is one of those things people tolerate until they can't. And when they complain, IT often doesn't have a good answer. They might swap the laptop under warranty, but the replacement has the same fan curve. So the complaints just get absorbed. But there's another layer to this: the push toward AI PCs with NPUs. Luna: Oh, interesting. How does the NPU change the thermal equation? Lucas: The neural processing unit in Qualcomm Snapdragon X or Intel Core Ultra chips runs cool, but it can cause unpredictable heat spikes when an AI workload kicks in. That triggers the fan more often. And since the NPU is new, OEMs haven't optimised their fan curves for it yet. So you get these bursty fan events that are even harder to manage. Luna: So the problem is getting worse, not better, as hardware evolves. Lucas: It seems that way. And Microsoft's response, as far as I can tell, has been silence. There's no public commitment to restore the fan API or provide a new one. The OEMs are each doing their own thing, which means IT has to learn four different tools just to manage fans across their fleet. Luna: Speaking of managing the fleet — if today's conversation made you think about your own setup or gave you a practical tip you can use, that's exactly what we hope for with this show. And if you find that kind of value here, listener support is what keeps this podcast ad-free and independent. You can help at buy me a coffee dot com slash fexingo. No pressure — just if you want to keep these deep dives coming. Lucas: Yeah, we really appreciate that. And it's because of that support that we can spend time on stories like this — the quiet, overlooked corners of enterprise tech that actually matter day to day. So thank you to anyone who's chipped in. Luna: Alright, back to the fans. Let's talk about one specific case that really illustrates this mess. Lucas: Sure. I was looking at a Reddit thread from an IT admin at a university. They deployed about three thousand Dell Latitude 7440s — a popular enterprise laptop — and within a month, they had over a hundred complaints about fan noise. The fans were spinning up during web browsing, not just heavy loads. Luna: What did they do? Lucas: They tried Dell Power Manager's 'quiet' profile, but that throttled performance too much. They tried adjusting Windows power plans, but the fan curve is baked into the BIOS. Eventually, they created a custom BIOS image using Dell Command | Configure that set a more conservative thermal policy. But that required reimaging every machine — a huge project. Luna: And did it work? Lucas: Partially. The fans were quieter, but some users reported thermal throttling during video calls. So they had to strike a balance. The real fix would be a per-app fan profile — quiet during Outlook, aggressive during a compile — but that doesn't exist in any OEM tool today. Luna: That's the kind of granularity you'd expect from a modern OS. But we're not seeing it. Lucas: Right. And here's the ironic part: Windows 11 has a 'Game Mode' that can boost GPU performance and change fan behavior for games. But there's no 'Work Mode' that does the same for productivity apps. So the OS clearly has the ability to adjust fan profiles per workload — it just doesn't expose it. Luna: So Microsoft has the plumbing, but they haven't built the faucet. Lucas: Exactly. And until they do, IT admins will keep fighting this battle with BIOS tools, third-party hacks, and workarounds. Some are even considering a switch to Linux for certain workloads — not because they prefer Linux, but because fan control is accessible via the 'lm-sensors' package. Luna: That's a drastic step for an enterprise. But it shows how much pain this single issue can cause. Lucas: It does. And I think it's a symptom of a larger trend: Microsoft and OEMs are moving toward a 'managed device' model where you don't control the hardware-software interface. The fan is just one example. Battery charge thresholds, webcam privacy shutters, even keyboard backlight timers — all of these are being shifted from user control to OEM or OS control. Luna: So we're trading control for convenience, or maybe for security in some cases. Lucas: Right. And for many users, that trade-off is fine. But for enterprises that need predictability, it's a genuine problem. The fan noise might seem trivial, but when it affects user satisfaction and productivity, it becomes a bottom-line issue. Luna: I wonder if Microsoft will ever bring back a more open fan API. Or if the npu driven future will force them to. Lucas: I think they'll have to, eventually. Because as AI workloads become common on the desktop, the thermal profile of a laptop will change dramatically. If the OS can't intelligently manage fans per workload, users will notice. And complaints will escalate from IT to procurement — and then to the C-suite. Luna: So maybe this quiet issue is about to get loud. Lucas: Let's hope so. Because a little more control over our fans would go a long way.