Armoury Crate installation tips

[lordberti]

This is how it is described by Microsoft itself.

Citation:

After installing this update KB5013943 and KB5012643, some .NET Framework 3.5 apps might have issues or might fail to open. Affected apps are using certain optional components in .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components.

You can mitigate this issue by re-enabling .NET Framework 3.5 and the Windows Communication Foundation in Windows Features. For instructions, please see Enable the .NET Framework 3.5 in Control Panel.

[Jimbo93]

This is how it is described by Microsoft itself.

Citation:

Cool. Thanks. Still something is odd. If AC needs Net 3.5 it would have told me long ago to enable it. And my apps work with it disabled.

[lordberti]

Try it.

It has everything to do with ending support for 4.5.2, 4.6 and 4.6.1 leaving only 3.5 and 4.8. But software programmers should use 4.8 as 3.5 is outdated.

Source:
https://devblogs.microsoft.com/dotne...nd-of-support/

[Jimbo93]

Try it.

It has everything to do with ending support for 4.5.2, 4.6 and 4.6.1 leaving only 3.5 and 4.8. But software programmers should use 4.8 as 3.5 is outdated.

Source:
https://devblogs.microsoft.com/dotne...nd-of-support/

No thanks . as everything is good for me with it off. I would love to hear from AC developers whether it should be enabled or not.

[Jimbo93]

I have asked MasterC to say if AC needs .NET 3.5 at all. Should be interesting.

[Jimbo93]

The OP has been updated based on new info and results.

[Jimbo93]

I wish somebody could give some feedback on that new WMIADAP tip. Could be its just my system/hardware. But I suspect others have the same issue or I would not be suggesting it.

https://rog.asus.com/forum/showthrea...163#post863163

[Jimbo93]

Well after spending a lot more time troubleshooting and such I have made significant progress on my system. Some of the key things that helped:
uninstall GeForce experience and only reinstall after wmiadap is working reliably, meaning as long as ac is in static, I can just restart when I want no worry about signing out and waiting to sign in. Th steps to correct the wmiadap issue were time consuming. I guess no one else has seen the issue.

I made some repairs to .net framework. Easy stuff to do. I can share more later.

I made repairs to windows defender AND I added exclusions to defender for asus and nvidia program directories.

[Jimbo93]

Well, if you have followed this thread you know that something weird was going on with my system and it was most evident by the behavior of the wmiadap process. Other symptoms were, slow to sign out and shutdown windows, lower than expected cpu benchmarks when windows defender AV was in real time protection mode, and cpu frequency remaining suspiciously high when power setting was set to balanced performance and the system was idle.

I have solved it!

I pulled another trick out of the bag. I have a powershell script written by a Microsoft expert to rebuild the WMI repository, found it a few years ago on Technet. Anyway, after backing up the repository for safety, I ran the script, and it has solved all of the issues above.

Call me happy. And I have no idea how the problem occurred really.

[Jimbo93]

I confirmed that there was an issue with the WMI repository. There is a registry key that keeps a record of all .MOF files which are used to configure/setup WMI on your machine. Well there was one program's .MOF that decided to write to WMI over and over and over, maybe over a thousand times. I am pretty certain that is a less than optimum situation...lol. I had to edit that .MOF file list in the registry and then run the WMI rebuild script again. What this did for me is really smooth out windows, and especially armoury crate. before it seemed a little more jumpy. and not slow just better running.