Question about AWCC (m15 R1)

Guys,

Since i've got my m15 R1, i've noticed that, differently from previous AW machines i had in the past, on the m15 with the new AWCC it did not get loaded at windows start up (no icon on the tray for instance) and it took quite a while before it would be loaded and usable once the OS had booted.
For example, trying to switch off alienFX lighting right after windows booted, did not work. opening AWCC right away took a long while and with a message that a service had to load and it would take several seconds to do so.
At first i thought it was a messed up installation from factory, since when i've got the machine i didn't had the time to install my ssd, clean install win etc. I had to go back to work.
When i got back after my shift, 2 months after the purchase, i had the time to install new ssd (3 of them) memory upgrade, do a proper clean installation etc. etc.
but still, AWCC works the same way.
It is just supposed to be like this or there is something i can tweak/config to make it running and working as it was on the old AW machines?

 

I've never noticed this issue but then I very rarely use AWCC.

 

Please, if it is no bother, try to boot your machine, once in windows, try to either:
Open right away AWCC
switch on/off your alienFX lighting

just to see if you can replicate the issue.

basically, what's happening, is that it take several minutes to load and being actually usable. Once it load fully, it works without issue

 

I can confirm this is still happening with the latest version (5.2.42.0). If you try launching AWCC too soon after boot you'll get a toast notification that it isn't ready yet and to wait 30 seconds, or it won't load at all. Exactly as you described.

Once fully loaded it acts normally, though it still has that memory leak if you leave the Fusion tab running.

 

@DrewN
Thanks for the feedback. So it seems isn't something on my installation but a common issue.

 

Getting something like this as well. When the latest AWCC is launched just after login, it complains about unrecognized AlienFX devices. Restarting AWCC resolves the issue. Pretty appalling coding.

Also seems that if startup AWCC error occurs, it will cause terrible (+15-20W) power draw even if AWCC is closed (need a reboot to resolve). AWCC normally causes high power draw, but can be closed to avoid this. What a horrible piece of software.