Use for loop instead of manual command

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

@@ -19,33 +19,14 @@ tags: []
 
 {%capture content%}2. Remove the Services{%endcapture%}{%include blocks/heading.liquid level=2 content=content%}
 
-{%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 commands will make quick work of the Services:
+{%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%}sc config [SERVICE] start=disabled
+{%capture content%}@for %L IN (ASUSSystemDiagnosis ASUSSystemAnalysis ASUSSwitch ASUSSoftwareManager ASUSOptimization ASUSLinkNear ASUSLinkRemote ASUSAppService) DO (
-sc stop [SERVICE]
+sc config %L start=disabled
-sc delete [SERVICE]
+sc stop %L
-{%endcapture%}{%include blocks/code.liquid content=content%}
+sc delete %L
-
+)
-{%capture content%}Of course, you replace {%capture code%}[SERVICE]{%endcapture%}{%include inline/code.liquid content=code%} with the name of the service, below is a list of the ones I know:
-{%endcapture%}{%include blocks/paragraph.liquid content=content%}
-
-{%capture content%}ASUSSystemDiagnosis
-ASUSSystemAnalysis
-ASUSSwitch
-ASUSSoftwareManager
-ASUSOptimization
-ASUSLinkNear
-ASUSLinkRemote
-ASUSAppService
-{%endcapture%}{%include blocks/code.liquid content=content%}
-
-{%capture content%}The result of this replacement would be the following command series for ASUSSystemDiagnosis:
-{%endcapture%}{%include blocks/paragraph.liquid content=content%}
-
-{%capture content%}sc config ASUSSystemDiagnosis start=disabled
-sc stop ASUSSystemDiagnosis
-sc delete ASUSSystemDiagnosis
 {%endcapture%}{%include blocks/code.liquid content=content%}
 
 {%capture content%}3. Remove the "Driver"{%endcapture%}{%include blocks/heading.liquid level=2 content=content%}
@@ -70,3 +51,6 @@ ForEach-Object {@{ `
 
 {%capture content%}ASUS's Driver and Services are absolutely horrible for input latency, as well as system performance. They've caused me quite a few audio stutters, and combined with other shitty drivers and services made any proper audio playback near impossible. This behavior from Microsoft and Laptop manufacturers needs to stop, but it likely won't until a government steps in - so here's me hoping the European Union will do something to stop this. It's bad enough on "smart"phones, we don't need it on Laptops and Desktops too...
 {%endcapture%}{%include blocks/paragraph.liquid content=content%}
+
+{%capture content%}A downside is that Windows will immediately reinstall the Driver when it checks for updates again, and I found no way to prevent that. It is a similar situation to the random RGB device driver Windows kept installing for my AMD Ryzen 5950X, except this time it's on purpose. Maybe someone else knows how to prevent this entirely.
+{%endcapture%}{%include blocks/paragraph.liquid content=content%}