RGB Utility issues and workaround

Hi!
My Windows 11 reports an error at unidentified USB Device on Port 13 (where RGB IC happen to reside) and some Microsoft compliant ACPI controller. When I try to use ASRock Polychrome RGB in BIOS it says no firmware is identified, contact support.
I have downloaded both 2.0.109 and 2.0.114b RGB Polychrome apps, both quit with 0xfff0 error. The firmware update doesn't work either.
Any ideas?

Guys, you will need to contact ASRock Tech Support:

http://event.asrock.tsd.com/

They should be able to help you out. This is an issue with the Polychrome software
so there isn't much we can do to help on the forums, unless someone has figured
out a way around it. In which case please feel free to share.

my thing doesnt work when i flash it instead it says this Enter ICP mode.
Company ID: 0x000000FF, Device ID: 0x00FF00FF
Enter ICP mode fail.

I have downloaded both 2.0.109 and 2.0.114b RGB Polychrome apps, both quit with 0xfff0 error. The firmware update doesn't work either.
teatv apk

download apk

!SOLUTION! !SOLUTION! !SOLUTION!
When downloading ASRock Polychrome RGB app on asrock.com website, change the field to where you choose OS version (ex: Windows 10, Windows 11) to "BETA AREA". Then will show up other version of this app (as beta), today shows "ASRock Polychrome RGB ver:2.0.136" as beta. The current version is ASRock Polychrome RGB ver:2.0.109.

After uninstalling the previous version, restart PC, and installing this Beta one, works just fine, except that I cant select individually the own components of my Steel Legend b450m. But this was already buggy before any way.

I am suspecting that this problemas is not a "version problem", but a problem in how the "WriteFW.bat & wICPFLASHADSBv2.exe" works on "RESET" the pre-installed firmware. I'm guessing that the action of RESET the firmware is not really doing that WHEN it founds the same version installed in BIOS, and it gives you a lot of other errors because it didn't fix itself. So, uninstall and reinstall that same version didn't really change nor update the installed firmware in bios. This clue came to me when another guy here say that he installs a previous version and it fix it, just like me with a different version, a beta version. If this problem happens again, I will do that, install a different version and try it, if this fix the problem, that means that the developer's team of ASRock should be drinking more coffee at work... that's a newbie's mistake.

I hope that fix the problem to you guys.

Any doubt, you can find me online on twitch.tv/tioakasha (probably I will be talking in portuguese, but just chat in english that I talk to you in english too lol!)

Bye!