[Bug Report] Not all devices' LED's change when loading via CLI

Description of Bug

Specifically on a Windows 10 machine. I have created a multitude of different colour profiles that when loading via the GUI, change all the LED's on my devices as set up (RAM, fans, GUI). However, when loading a profile through the CLI (in an attempt to allow a profile to load on windows startup), only my RAM changes to the specified profile.

I am running the following via the CLI for testing:

.\OpenRGB.exe -p Red.orp

This changes my RAM sticks to red, but not my other devices - they remain as they were during startup. Note that I've also tried to specify the relative and absolute path to the profile both to no avail. My %APPDATA% environment variable points to the Roaming folder which the code specifically looks for, and the profiles are saved to this default location so I shouldn't need to specify paths anyway I think?

Hardware Configuration

Crucial Ballistix RGB 3600Mhz CAS16 2x8 GB sticks MSI Gaming X Trio 2070 Super GPU Various fans connected to RGB headers on a motherboard supporting Asus AURA.

Also grabbed the artifact from the latest Master PR (5 hours ago), but this issue happpened even on the latest official release.

Let me know if any other info is required for diagnostics. It would be great to get to the bottom of this so I can have my profile start up with windows