Update ASUS Armoury Crate guide

_posts/2023/2023-02-11-asus-armoury-crate.html

@@ -4,12 +4,13 @@ category: Blog
 tags: []
 ---
 
-{%capture content%}Back in December 2022, I bought myself a Laptop in the hopes that I would be able to take it anywhere and keep working or playing. The idea mostly worked, with the massive downside that I forgot entirely about which vendor made the Laptop: ASUS. ASUS, like MSI, is one of those that will silently push Malware, Spyware and Bloatware as a required Windows update, often hiding it as a new driver.
-{%endcapture%}{%include blocks/paragraph.liquid content=content%}
+{%capture content%}Back in December 2022, I bought myself a Laptop in the hopes that I would be able to take it anywhere and keep working or playing. The idea mostly worked, with the massive downside that I forgot entirely about which vendor made the Laptop: ASUS. ASUS, like MSI, is one of those that will silently push Malware, Spyware and Bloatware as a required Windows update, often hiding it as a new driver.{%endcapture%}{%include blocks/paragraph.liquid content=content%}
 
 {%capture content%}Unfortunately for me, Microsoft Windows is a necessity for Windows development - cross-compiling may work, but the generated binaries are horribly wasteful and slow. It's just better to use Microsoft Visual Studio instead, and get proper decent binaries out. So, I needed a solution for the ASUS problem, and I think I found one.
 {%endcapture%}{%include blocks/paragraph.liquid content=content%}
 
+{%capture content%}Guide last updated on 2023-03-16{%endcapture%}{%include blocks/paragraph.liquid content=content%}
+
 {%capture content%}How to (temporarily) remove Armoury Crate{%endcapture%}{%include blocks/heading.liquid level=1 content=content%}
 
 {%capture content%}1. Disable the feature in BIOS/UEFI{%endcapture%}{%include blocks/heading.liquid level=2 content=content%}
@@ -22,13 +23,15 @@ tags: []
 {%capture content%}With the "feature" disabled, we can now enjoy some time before Windows will reinstall everything. So lets start by disabling, stopping and deleteing the Services that it created - and the best way to do that is a good old {%capture code%}cmd{%endcapture%}{%include inline/code.liquid content=code%} Terminal running as Administrator! We're not using Powershell here, because the {%capture code%}sc{%endcapture%}{%include inline/code.liquid content=code%} command is broken in Powershell. Once you have it open, the following command will make quick work of the Services:
 {%endcapture%}{%include blocks/paragraph.liquid content=content%}
 
-{%capture content%}@for %L IN (ASUSSystemDiagnosis ASUSSystemAnalysis ASUSSwitch ASUSSoftwareManager ASUSOptimization ASUSLinkNear ASUSLinkRemote ASUSAppService) DO (
+{%capture content%}@for %L IN (ASUSSystemDiagnosis ASUSSystemAnalysis ASUSSwitch ASUSSoftwareManager ASUSOptimization ASUSLinkNear ASUSLinkRemote ASUSAppService asus asusm AsusCertService AsusROGLSLService) DO (
 sc config %L start=disabled
 sc stop %L
 sc delete %L
 )
 {%endcapture%}{%include blocks/code.liquid content=content%}
 
+{%capture content%}Optionally you can remove the sc delete %L part if you only wish to soft-disable the Driver, without actually removing it. This prevents windows from reinstalling it, but it will still update it adding new things.{%endcapture%}{%include blocks/paragraph.liquid content=content%}
+
 {%capture content%}3. Remove the "Driver"{%endcapture%}{%include blocks/heading.liquid level=2 content=content%}
 
 {%capture content%}Now that nothing is using the driver itself anymore, we can begin by figuring out where it is, and what it was registered as. This time we'll use a {%capture code%}Powershell{%endcapture%}{%include inline/code.liquid content=code%} Terminal running as Administrator, and a single command will do all the work for us: