Armory Crate still not working since 09-12-2025

[Gennady21]

Nothing has changed since I wrote this post 09-12-2025 12:20:30 AM. Armory Crate continues to crash. This is the third update since then, but nothing has changed. ASUS hasn't responded at all and refuses to look into the situation. The best they could do was move such topics to Read Only so that they wouldn't constantly pop up on the forum.

[inge70]

What did you install or do BEFORE ArmouryCrate stopped working for you?

What hardware are you using?

Did you happen to install the latest Nvidia driver, version 591.44?

If so, you should manually check for updates in ArmouryCrate and install them, because the latest Nvidia driver caused problems with ArmouryCrate.

These issues were resolved on December 8, 2025, with two updates: one for VGADII and one for the GPU plugin.

If the problem wasn't caused by the Nvidia driver, please describe what you did on your PC.

This certainly didn't happen on its own.

Here, and I'm sure for many other users as well, ArmouryCrate is running version 6.3.6.0.

[Gennady21]

Do you really want to help or just chat?
After updating to version 6.3, I started having problems with it, and I'm sure everyone else who's complaining has the same issue. If you're one of the developers, I can provide more technical information about the location of the unhandled exception in the ArmouryCrate.HWComponent.dll code.
After renaming ArmouryCrate.HWComponent.dll to ArmouryCrate.HWComponent.dll.tmp, the service starts normally and doesn't crash.
I don't understand why NVidia drivers are needed if the programmers don't have proper testing?

[inge70]

I am not one of the developers of Armoury Crate, nor do I work for Asus.

I'm a regular user like you, since this is a normal forum, even though Asus employees occasionally post here.

Whether Asus employees reply depends on WHERE in the forum the question is posted (I've learned that the hard way).

Therefore, your question about whether I "only" want to chat is irrelevant here. However, I understand that you apparently only want help directly from Asus.

I don't need to be accused of anything, so I will only reply this one more time!

But back to the issue:

Based on your screenshot, it seems that the error in ArmouryCrate occurs in conjunction with NetRuntime.

It appears that the ArmouryCrate installation is corrupted.

Renaming the DLL file, a suggestion they likely received from this forum, only removed the error in the reliability history, but clearly didn't fix the problem with Armoury Crate itself.

Regarding the Nvidia driver I mentioned:

Nvidia driver 591.44 was released on December 4, 2025, for Nvidia graphics cards and caused many users to experience a problem where Armoury Crate stopped working.

Only the last two updates to Armoury Crate (as I already mentioned) resolved the issue for Asus.

If you don't have an Nvidia graphics card, this problem doesn't affect you.

However, since you haven't mentioned any hardware specifications, providing assistance will be difficult.

Nvidia driver 591.44 was released on December 4, 2025, for Nvidia graphics cards and caused many users to experience problems with Armoury Crate.

The problem was only fixed by Asus with the last two updates to Armoury Crate (as I already mentioned). Check your PC/Windows for errors using the following commands:

1) sfc /scannow

2) Dism /Online /Cleanup-Image /CheckHealth

3) Dism /Online /Cleanup-Image /ScanHealth

4) Dism /Online /Cleanup-Image /RestoreHealth

Run these commands one after the other in the command prompt (CMD), as administrator.

If no errors are found, the only remaining option is to completely uninstall ArmouryCrate using the Asus uninstaller (found on the Asus motherboard website).

I hope you find a solution.

[Gennady21]

Oh, please, let's do without this sfc /scannow.
I'm so sorry, but as soon as I see this in the recommendations, I immediately understand the level of who's writing this and for whom.

It turned out to be simpler. They compiled the DLL with the updated CRT, and now my workaround via symbolic links doesn't work because the CRT function throws an exception for not being able to traverse the path.

I don't know what kind of idiots write this, but I've already pointed out the hardcoded paths within their code several times – no one has fixed anything. For testing, it wouldn't hurt to install two Windows installations, with the second one on drive D:. Then all their botched work would immediately become apparent.

[Gennady21]

I managed to patch their DLL and the service started. If anyone is experiencing similar issues, you can patch it as described in the previous post.
After that, the service started and I even gained access to where it should be. This will work for you until the next update, until these developers prove their "professionalism" once again.