I had a similar issue with the latest awcc and my R13.  Did the same thing with the uninstall, clearing the registry, even installing older versions.  Look for my post from this thread "Aurora R14, AWCC not working, cannot reinstall", if you would like to try another wacky solution that does Not involve reinstalling windows!  I am now up and running totally fine with 5.5.26.  In summary, it was a stuck prior version of the peripherals/components drivers that no amount of registry editing was going to find.

Thanks for the tip. Unfortunately, it didn't work for me. The 5.5.26 installer still does not successfully complete for me after following your instructions. But I did find another temporary fix that I'm going to go with for now. I managed to successfully reinstall AWCC 5.4 and that is working. So until they come up with a working solution for 5.5, I'll just run with AWCC 5.4 for now.

Further update. The earlier version of AWCC is not fully functioning either. The failure again points to a couple of factors. Inability of the installer to continue if it encounters files missing that it want to clean up, and also a failure on peripheral identification and initialization. 

Where I am now is that the core AWCC will load but only identifies the CPU.It then indicates that it needs to download additional components which I suspect are the peripheral drivers. If I skip the download AWCC continues to run in the crippled state II described. If I start the download, it will hang either with or without the spinning purple dots. Windows notifications will indicate that the component download is complete but then hangs at 70% installed. That’s probably the same point at which the main installer program quits during a complete install attempt. I’m going to report this on my open ticket in hopes it will help engineering to identify and fix the issue(s).

And a final update. After being away for a few days, I restarted my computer, and AWCC auto-updated to v5.5.35.0, A00, and magically fully works again. There is still the issue with core isolation not playing well with the OC settings, but other than that, AWCC seems back to normal.

Unfortunately as new Windows Updates come, AWCC will give you more problems. Everything is a temporary solution. It's ridiculous that this software is so bugged. If there was another software that I can control my fans and prolong the life on my laptop, I'd pay for it in a heartbeat. I've been using my M17R3 for 2.5 years now. On average, every other month I encounter problems with AWCC. However, for the past few months, I can't even install AWCC because the wizard keeps getting interrupted. So I resorted to a 2020 version - worked for awhile - and then today my thermals and peripherals are just in an infinite loop again. I reckon it has to do with Windows Update and what not. Ridiculous.

I have said before they should break up AWCC into it's base components, like fan control, OC control, RGB control and Sound control etc...

This way you can install what you need and drop all the rest that you don't need.

Agree completely. Most “all-in-one” types of software packages are sort of like “jack-of-all-trades, master-of-none” deals. This goes back to my earliest experiences with integrated software. In the 1980s, Ashton-Tate was selling Framework. That package was nowhere close to as good as Lotus 1-2-3, WordPerfect, and d-Base were separately. Thus began a long parade of mediocre all-in-one software suites, the latest of which are Office 365 and AWCC. The ability to pick and choose would be a good thing, IMO.

I think a full AWCC is over a gigabyte, which is a lot for what it does...

I thought I was able to prevent awcc from auto-updating on my working 5.5.26, but I was wrong.  I have microsoft store set to no autoupdates, and I disabled awcc from the firewall.  It still auto-updated to 5.5.35, must launch some hidden service that allows it to automatically download and install without user prompts (is this bypassing microsoft security?). The firewall block did prevent the modules from updating, which of course the .26 modules do not work with .35.  So had to manually download and run the full awcc installer. 

All is working fine now on 5.5.35, would really like a method to prevent these auto-updates. 

Try:  Look in Support Assist/ settings/ automate scan & optimization and  repair sections if they are enabled if so, disable. these may be the cause why they auto-update.

AWCC has become the Apple version of iTunes, a bloated mess. I wonder if they have the skilled people to actually tear it apart and fix what is broken or just start from scratch? And does Dell really want to pour money and time into a utility that does work for the most part?

Steadler,   never never never run or install Support Assist.  At least with awcc the worst is your rgb lights turn off.  With support assist you will wind up bricking your motherboard. 

I do know this...it seems that Dell and Microsoft are in contact regarding AWCC's inability to co-exist with W11 Core Isolation, at least as far as running OC controls in AWCC, and are working on a fix. I'm not sure whether or not that qualifies as either company having enough qualified people to do a decent job on any fix they roll out. Strangely enough AWCC had been working OK for me for almost a year before this little adventure.

@Jupiter_7 Do you have specifics on how Support Assist can potentially brick your mobo? I've had it running for a year now, have installed a few updates to it and haven't had any issues with it. I'm genuinely curious about it.

If...you are a '' Dell TechExpert '', why are those issues similair to me are solved a couple of months ago at my R13 history, and you bring up the same issue 12-17-2022?

Thats pretty weird if you asked me.

Hiya,

I had the similair problems and they are resolved with help from Support, the conflict with Windows Core Isolation you can simply turn that off.

I wonder what kind of CPU u use, im a i7 12700KF user and with the latest AWCC 5.5.35.0