[Bug Report] OpenRGB 0.5 doesn't work properly with Corsair Vengeance RGB Pro any longer

When I first discovered almost three weeks ago (3rd or 2nd of January) and used OpenRGB 0.5 for my Corsair Vengeance RGB Pro RAM, everything worked well and I was able to define LED effects that day without any problems.

Three days ago, I wanted to reconfigure the LED effect and ran into the following issue:

1. When starting OpenRGB, it recognizes my RAM first correctly. 2.** When selecting any LED color or effect change, the LED's on the RAM goes out.**
2. Any further trial to restart the LED's via OpenRGB fails - not light, no effect.
3. I have to relaunch the LED's via Corsair iCue, then the light works again.
4. As soon as trying to change anything via OpenRGB, lights go out again and no way to relaunch them via OpenRGB.
5. When trying a re-detect of all supported components, my two RAM bars disappear from the list and only my MSI mainboard remains.
6. When exiting and relaunching OpenRGB, it hangs and creates an "stopped working" event in Windows event manager.

Yesterday, I tried the following:

1. Starting OpenRGB - RAM is detected correctly.
2. Instantly doing a re-detect => RAM disappears.

Hardware: Ryzen 5 5600X MSI X570 Gaming Edge WiFi 2x Corsair DIMM 16 GB DDR4-3600 @3800 MHz, CMW16GX4M2C3600C18, Vengeance RGB PRO Gigabyte RTX 3080 Gaming OC Kingston A2000 1 TB m2-SSD Windows 10 Pro 64bit 20H2; last updates done two days ago