>>106177673
Don't use SDIO to blindly install/update every driver proposed, as not every driver is guaranteed to be 100% appropriate.
Last time I ran it, it recommended me to update Intel chipset device drivers, which doesn't really make much sense given what these drivers actually do.
>well, "drivers" - these "chipset drivers" are basically .INF files with no own .sys driver to load - basically a null driver to get rid of that yellow bang from the device manager, and name the device accordingly
>or in edge cases: making it use Windows' own (e.g. pci.sys), which would make sense e.g. when using older Windows on not era-appropriate hardware
>anyway, you'd be bloating the driver store at worst on this one
Hell, I'd use SDIO only as a last resort, when all reasonable methods fail (OEM and IHV driver pages, Windows Update or Microsoft Update Catalog.)

With trustable alternatives, only 3DP Net and 3DP Chip come to my mind.
>>106179643
>answer files - (auto)unattend.xml
>deploying custom files to a Windows installation - $OEM$ folder
>after-install scripts - e.g. setupcomplete.cmd or FirstLogonCommands section in the answer file
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/automate-windows-setup
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/update-windows-settings-and-scripts-create-your-own-answer-file-sxs
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup

https://schneegans.de/windows/unattend-generator/
Take usage of the silent install CLI switch when running the installers (also delve into other installer switches.)
>>106181117
.G marks generic detection - whatever hooks OpenRGB uses, at least one of them runs in kernel-mode.
Given the nature of this tool, you're pretty much fine with it. Make an exception so that Defender won't go apeshit
>or send the executable to M$ for analysis, and tell them it's actually legit software: https://aka.ms/wdsi