The out of warranty system on file for you (G7 15 7500) was never offered with any Linux support. As long as WSL is installed and running, AWCC will be blocked.

You’re right, my laptop was shipped with Windows 10. However, WSL is a feature provided natively in Windows, which bizarrely  makes it a windows feature. Also, this problem pops up with any Hyper-V enabled software, such as Android or iOS emulators for software developers. So please don’t try to wiggle your way out of this. Either give a company solution for this very expensive laptop, or give users control and let us take responsibility for our actions

You need to decide which is more important - WSL or the alienware control center.  You cannot use both.

Why do these have to be mutually exclusive? And why isn't Dell firmware compatible with the OS it ships with? It's not like WSL is a brand new feature, so they've had plenty of time to resolve this. Also, I'm curious to know what Hyper Visor has to do with a thermal monitoring software that makes them incompatible. I'd like to do my work and not have my laptop turn into a hot plate, and I feel that's a reasonable expectation to have.

@mb8055Hey, So I think Chris M. Dell is just acting to amuse himself.  Your issue has to do with Intel and Microsoft, not Dell.  It's helpful to remember that Dell is not a manufacturer; they are an assembler. 

Exceptionally little of your laptop (soft or hardware) can be called Dell technology.  With this in mind, we can look at AWCC, that 1.3GB POS (that's "piece of software", not what you were thinking ).  Each of it's component are comprised of other companies' tech.  Example, Dell doesn't make color-changing LEDs.  And when they buy them they generally also get sample code.  Take a look in ProgramFiles\Alienware\Alienware Command Center\Licenses for examples of this.

To your specific question.  Dell uses Intel's XTU drivers for processor clocking features.  XTU won't run with either Hyper-V, VMS or Virtual Machine Platform enabled.  Apparently, when any one of these is enabled, Windows itself becomes somewhat virtualized.  No idea if this happens in kernel or user space but it apparently breaks access to CPU clocking features.  With XTU, there's an annoying workaround, you can temporarily disable all virtualization.  Reboot.  Tune. Reboot.  Re-enable virtualization.  Reboot.  Settings persist. 

No idea if this works with AWCC or not, as my G7 7500 keeps heat like a steel forge.  At high altitudes I can boil water.  Overclocking is the last thing I need.  BTW, heat management design is something Dell can take "credit" for.

Now, had Chris told you this, he would not have fulfilled his daily quota of , so have a little sympathy.