alienfx-tools VS Windows UI Library

Here. For fan control you only need AlienFan-GUI, for lights + fans - AlienFX-GUI.

Any AW/Dell software needs to be purged. With Holy fire/orbital bombardment/moon sized space station, etc. For CPU stuff, Intel XTU/AMD Master as appropriate. For GPU Afterburner. HWinfo more than replaces CC for system monitoring. And alienfx covers the hardware features in a lightweight and 99% functional way (its mostly just missing features). If you do have issues with it, just ping the dev and they will get it sorted. Not bad for a single person dev team.

Major points: disable the capsule update thing in BIOS (you don't want auto updates reinstalling stuff your trying to get rid of). Get HWinfo, Afterburner, and alienfx to replace AWCC.

First, make sure anything and everything from Dell is flushed from the system: CC and SA are both notorious for gumming up the works. Best practace/least hassle is to just wipe the shipped OS and start fresh. XTU, Afterburner, HWinfo, and alienFX should be everything you need, be very lightweight, and not be a borderline performance virus.

https://github.com/T-Troll/alienfx-tools? The only issue it seems to have is not having some systems recognized, but that is just a case of getting a message to the dev and getting it added.

Get the following: AMD Master (or XTU for Intel), Afterburner, HWinfo. That covers tweaking the CPU/GPU and monitoring. Then alienfx for the Dell specific hardware. That should all be a fraction of the size and work without issue.

Give https://github.com/T-Troll/alienfx-tools a try, its a little thin on fancy UI but it should have all the features your after and its not CC.

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).