RockinChaos

Hi! Sorry for not leaving an update, I was way too lazy to be asked to do the solution @VolterPL provided until now. It works pretty much perfectly however, the PowerShell command Disable-PnpDevice is WAY too unreliable and rarely ever works. It usually throws an error resembling; Disable-PnpDevice : Not supported At line:1 char:1 However, spam "force update" for the MM800 would allow it to finally work... only once.. then it would break again. So instead I did all the steps that @VolterPL explained but I replaced PowerShell with DevCon. The way I did it is rather crude but works for me but could probably be better optimized by someone who actually knows what they are doing. The disable task action I created with DevCon is to set the program to cmd.exe and the "Add arguments (optional):" to /C devcon remove "USB\VID_1B1C&PID_1B3B*" The enable task is the same but with the "Add arguments (optional):" to /C devcon rescan The disable task simply removes the device rendering it essentially disabled, I did it this way because directly disabling it didn't work so I forcibly removed it. Then the enable task simply rescans for the removed hardware and enables it. How to install devcon; devcon is no longer something you can independently install, rather you need to install WDK and copy the devcon.exe from the x64 or x86 respectively to your Windows/System32 See; https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk And a video on where to drag the devcon.exe (it is a VERY old version of windows but it works.); [ame] [/ame] This devcon method should work on pretty much every version of windows. And again, just so I am clear--I am doing the EXACT steps that @VolterPL provided except step #3 and #4 as "USB\VID_1B1C&PID_1B3B*" should work for everyone since devcon is just removing any devices for that path which should only ever be the MM800. The tasks I am talking about for devcon disable/enable is his step #5 not devcon itself. Devcon is simply acting as PowerShell in my situation. Sorry if that isn't clear. I may edit this to provide a better writeup and/or a video explanation as it is quite complicated for some users.

@VolterPL Wow! Thanks for the comprehensive write-up! I will try this out and let you know how it works out.

I agree, this is ridiculous and a complete waste of money. Can someone please release a firmware containing this simple fix. They claim that it's not possible, however, if I turn the brightness all the way to off, then lock the computer, the LED's stay off. Therefore a "sleep" setting is possible if they simply make the device think the brightness is set to zero.