Bugged invisible system tray context menu

[222qwe]

there was a well known bug for the ICUE software, where system tray context menu stuck on screen and not dismissable.

 

i think the programmers fixed(?) this issue by just making it transparent or something.

 

when i open the tray context menu and after dismissed the menu,

that exact menu area is blocked, so i can not interact with

 

it acts like empty invisible no action attached box of the menu.

 

i guess the programmers didn't dispose the tray menu context properly.

 

known solution for now is just quit the program and re-open,

and never click the tray icon.

[icuetrash]

yeah pity they still have not fixed the annoying simple bug. I am pretty sure they don't know how to fix it. iCUE sucks. iCUE is  theworst piece of junk 

Edited October 17, 2021 by icuetrash

[c-attack]

11 hours ago, icuetrash said:

yeah pity they still have not fixed the annoying simple bug

This is not something other people report and if it were even slightly common, the thread would 10 pages long at this point.  Try the basic repair install (Windows Apps -> Corsair iCUE -> Modify).  That often cleans up weird issues like this.  If it does not work, turn on debug logging from the CUE settings and then contact Corsair Support so you can send them logs.  

[icuetrash]

On 10/17/2021 at 11:39 AM, c-attack said:

This is not something other people report and if it were even slightly common, the thread would 10 pages long at this point.  Try the basic repair install (Windows Apps -> Corsair iCUE -> Modify).  That often cleans up weird issues like this.  If it does not work, turn on debug logging from the CUE settings and then contact Corsair Support so you can send them logs.  

 

The problem is still there even though I clean installed newest Windows 11 and latest iCue v4.16 on a brand new SSD.

the stuck right context menu  still there. v.4 just made it 'invisible' and not fixed at all. you can't click that area.

 

[amplex]

same here.

still persists.

repros:

https://forum.corsair.com/forums/topic/176684-icue-is-blocking-mouse-events-by-creating-an-invisible-window-in-the-lower-right-corner-of-the-desktop/

[c-attack]

4 people in 18 months is not a systemic bug.  Follow the original advice and do a repair install. If it does not go away, turn on debug logging and submit the file to Corsair Support so they can analyze it. 

[Bertrand Kim]

Don't you see this issue really?

Funny. There are tons of iCUE users in my country also have this problem while two years.

I have same issue in several PCs I have. It appears in any Windows version or any iCUE version after 2020 july

Thanks

Edited October 5, 2022 by Bertrand Kim

[c-attack]

5 hours ago, Bertrand Kim said:

have same issue in several PCs I have. It appears in any Windows version or any iCUE version after 2020 july

You're right.  The other 200,000 CUE users and I have a visual blind spot and have never noticed this before.  Unless of course it's a Windows 10/11 bug and there are hundreds of millions people who are blissfully ignorant of their flyaway menus.  

 

"Tons of people in your country" have this issue?  Ignoring the weight conversion factor for a moment, are you suggesting there is language version factor in this error?  Language version of CUE or language version of Windows?  Or was this just hyperbole?

 

This thread originates in June 2021, which is 16-17 versions of CUE 4 past.  The idea that an irritating bug like this is omnipresent throughout that entire time and no one else except 5 people care is ridiculous.  You need to start troubleshooting this as a local error.  Follow the advice the above and do a "repair install" of CUE from the Windows -> Apps list.  Click on Corsair iCUE and select "Modify".  Follow the prompts.  This will not erase profiles or settings.  If that does not resolve it, turn on the CUE debug logging and contact Corsair Support so you can get more technical step by step instructions.  

 

 

[Bertrand Kim]

Hi, I see more than 100 people have this issue while two years ago(maybe every korean iCUE users?). 

It's interesting the first man of this thread's author was using Korean Windows and I'm using that too. And some of the repliers to the thread below are using Korean nicknames. (ejk, Mna'cho', 'joonmin'aa)

 

Perhaps it is a local issue. I will look into it and contact Corsair Support.

 

Thanks in advance

[John Hoang]

I guess there is a conflict with other softwares. I've experienced the same thing with a software called UltraView. Uninstall this software will solve the issue.

[Bertrand Kim]

Note,

I've updated to Windows11 22H2 just now.

It looks like I don't see this issue anymore.

[c-attack]

It is possible there is a language or Windows version specific conflict. That would explain why we don’t see the enormous volume of complaints in this forum it would generate if it affected all users. If you are still seeing this problem, contact Corsair Support and include both the Windows and CUE language version info. There was a specific Windows build that caused this problem across any program in the system tray, but that was a good 14-16 months ago, so I don’t think anyone should be affected by that. 

Edited October 6, 2022 by c-attack

[beninuA]

On 10/6/2022 at 12:16 PM, c-attack said:

It is possible there is a language or Windows version specific conflict. That would explain why we don’t see the enormous volume of complaints in this forum it would generate if it affected all users. If you are still seeing this problem, contact Corsair Support and include both the Windows and CUE language version info. There was a specific Windows build that caused this problem across any program in the system tray, but that was a good 14-16 months ago, so I don’t think anyone should be affected by that. 

I have about 100 friends in Scandinavia too who are gamers and users of various amounts of Corsair Harware, and amongst them (Danish are by far the largest group with about 80 users), and about 10+ from Sweden and Norway each. What embarrasses me is that most of these friends use Corsair as a response to my recommendation of the hardware. The hardware I still love but as a software engineer with specialty in development of hardware drivers (for cash terminals amongst other things), software for use in both hospitals and general practice and pharmacies, security and backup solutions and as of late taylor made cloud storage solutions throughout 30 years, I have rarely seen such inconsistent coding and interface development as the one used in the iQUE panel. It has improved with the latest versions since late 2022, and not until late 2022 has this problem with the stuch context menu been solved. Whether it be users from Denmark, Sweden and Norway the numbers are consistent and about 65 percent of users experience a stuck context menu from systray. What is interesting is that Corsair distributes a version in Swedish as the only of the Scandinavian languages. Norwegian and Danish users use the original English version. But it is  was definitely not a language specific problem. You can right-click the systray icon and chose bring to foreground and see that a new context menu is provided sometimes a little to the left or right of the previous, so the previous disappear but no matter what menu item you choose in the context menu that opens when right-clicking the menu (usually bring iQue to foreground), the menu sticks to the screen. Luckily it stays behind full screen apps such as games, and that could be the reason it hasn't generated so many forum requests, as most users utilllize the functionaliy for gaming.
But for me and quite a few others we have changed from Logitech to Corsair because of the better quality of the hardware and the better keyboards - in particular the K100 RGB with the new Laser/MX hybrid keys, which I love. I have many Corsair components and I also use it for aesthetics but also in combination with the Stream Deck that is now included as a combo solution with iQue as I am a content provider using the entire Adobe CC suite for Video, VFX, Audio and Photo creation, and here it is of immense value to have all the different macro solutions with a corsair Keyboard a RPG Mouse with 17 keys and and two 32 key Stream Deck and a 15 key Stream Deck to control all the functions in Adobe Premiere Pro, After Effects, Audition, Illustrator, LightRoom, Photoshop, etc. and to be able to easily see the keys change color when changing programs and automatic profile change makes sure you always use the right profiles for the present software. So to me the Corsair hardware and software are more of a solution to customize my keyboards and peripherals to show different layouts depending of what software I use, so I can easily see what keys I must use in the different Adobe Suite applications to navigate my content and to know where my collection of macro keys are located on the keyboard as well as my Stream Decks.
And when you use it for creating special keyboard settings for use in various non-gaming software that doesn't run in full screen it can be a real nuisance to have a context menu cover the lower left corner of your left screen (in a 4 monitor setup - 3 for editing and 1 large wall screen for preview).

All this was just to say that a cum hoc ergo propter hoc-argument such as "Since it hasn't been discussed much it is not a widespread problem" is a logical fallacy. There can be dozens of other explanations it hasn't been discussed - number one probably the even  more widespread experience amongst users that software and hardware providers generally couldn't give a flying f..... about complaints in user forums like these, and that the general experience is that user input rarely results in instant debugging on part of the hardware-, driver-, software-provider, since they are always more interested in developing new revenue generating versions instead of perfecting the solutions that are already out there amongst millions of users being used daily despite all their flaws. It should be a general rule of thumb amongst software developing giants such as Corsair, that there should be no development of new device interfaces until the existing versions are bug-free as per the user input on forums such as this - the only exception of course being software for completely new products. But as long as a driver and control application for peripherals like iQue is still flawed the only responsible thing would be to send out UPDATES and the completely irresponsible thing would be sending out UPGRADES or totally new releases. We dont want new UPDATES until we have UPGRADES that makes the exisiting work. The exeption of course, being if the exisiting software is such a load of spaghetti development, that the only viable solution is to scrap the crappy goofy programming from the exisiting drivers and control panels and start from scratch with software engineers that actually know what they are doing. But as long as pumping out new software and hardware instead of making the existing solutions stable generates more revenue for Corsair they would of course never feel inclined to pursue the more customer friendly strategy.

In all fairness it should be said that after only five years of extremely poor interface the latest overhaul has finally made it a tad better, but still not as intuitive as the Lgotech software like the one for the 905 keyboard. But although I was a Logitech fan for many years I must admit that the ruggedness of Corsair products and Corsairs choice though many years to consistently use Cherry MX switches on their high end keyboards made my switch to COrsair a no brainer. The only problem is that Corsairs programmers are infinitely worse than those at Logitech, so their hardware is better but their software are still much worse than Logitechs both regarding bugs but also the interface itself that is much more intuitive in Logitech - at least until I decided to switch to Corsair about five years ago.

The only thing I still can't wait for is the fuly integrated LED (or even LCD) screens in each key on the keyboard, so you can create custom keyboards for particular programs so you don't have to buy these expensive adobe caps to put on you Cherry MX switches on a separate keyboard to control your editing station, but instead can have a keyboard that automatically change between the profiles including switching the image on each key making it clear what each key's function is depending on the active software. Technology should be available and it can't be such a difficult solution. Looking at StreamDeck shows there are only very few steps to implementing these slim 128x128px 32K color displays on top of all caps on Cherry MX switches. The concept has already been shown at several occation so proof of concept is a stage passed long ago.

[c-attack]

9 hours ago, beninuA said:

All this was just to say that a cum hoc ergo propter hoc-argument such as "Since it hasn't been discussed much it is not a widespread problem" is a logical fallacy. There can be dozens of other explanations it hasn't been discussed - number one probably the even  more widespread experience amongst users that software and hardware providers generally couldn't give a flying f..... about complaints in user forums like these, and that the general experience is that user input rarely results in instant debugging on part of the hardware-, driver-, software-provider,

Yes, I am sure there were dozens of possible explanations from probable to absurd.  This was a combined Windows/CUE task bar issue back in 2020 which was resolved long ago.  Unclear whether the original user who needed help was older software OS or CUE or was running additional software that interacts with the task bar.  Aside from cleaning up the installation of CUE on his/her end there is not a lot that can be done in a peer to peer support forum, hence the suggestion to contact Support to provide the necessary details to those that are in a position to analyze and resolve it.  However, it is ridiculous to assume it is an unreported widespread error and then do nothing on the user end.  Your argument there are numerous other far less likely but possible explanations is not very compelling since you offer none of merit, there are almost no technical details offered from any of the posters, and suggests you don't have much experience in resolving issues from people without technical backgrounds.  Regardless of the actual root cause of the issue, if you think initially treating this as a local issue before moving on to more complex origins that are not user side resolvable is a mistake, then you are not qualified to be dishing out your sermon.  

 

10 hours ago, beninuA said:

Luckily it stays behind full screen apps such as games, and that could be the reason it hasn't generated so many forum requests, as most users utilllize the functionaliy for gaming.

This is an example of a fallacy.  

 

10 hours ago, beninuA said:

Whether it be users from Denmark, Sweden and Norway the numbers are consistent and about 65 percent of users experience a stuck context menu from systray

I am amazed at your dedication to organize a Corsair owners group, collect everyone's software and hardware details, and then systematically poll the residents of three countries.  That is an amazing effort.  Make sure you pass those details on to Corsair Technical Support.  It's too bad you didn't join this forum until just now...  to post a wide ranging rant on a two year old post.  You are in the troubleshooting section of the forum.  It is for users to help other users with problems that are resolvable on their end and when they are not, to direct them to the place where they can continue troubleshooting efforts.  If you would like to post your thoughts on corporate guidance, best practices, feedback on specific Corsair gear, or your general opinion on whatever topic, the place to do so is here https://forum.corsair.com/forums/forum/236-corsair-icue/ .   The original poster surely had a real issue as did the others who posted after.  What advice are you giving them to solve their problem?  Don't do anything, just yell louder?

[beninuA]

On 2/12/2023 at 2:07 PM, c-attack said:

Yes, I am sure there were dozens of possible explanations from probable to absurd.  This was a combined Windows/CUE task bar issue back in 2020 which was resolved long ago.  Unclear whether the original user who needed help was older software OS or CUE or was running additional software that interacts with the task bar.  Aside from cleaning up the installation of CUE on his/her end there is not a lot that can be done in a peer to peer support forum, hence the suggestion to contact Support to provide the necessary details to those that are in a position to analyze and resolve it.  However, it is ridiculous to assume it is an unreported widespread error and then do nothing on the user end.  Your argument there are numerous other far less likely but possible explanations is not very compelling since you offer none of merit, there are almost no technical details offered from any of the posters, and suggests you don't have much experience in resolving issues from people without technical backgrounds.  Regardless of the actual root cause of the issue, if you think initially treating this as a local issue before moving on to more complex origins that are not user side resolvable is a mistake, then you are not qualified to be dishing out your sermon.  

 

This is an example of a fallacy.  

 

I am amazed at your dedication to organize a Corsair owners group, collect everyone's software and hardware details, and then systematically poll the residents of three countries.  That is an amazing effort.  Make sure you pass those details on to Corsair Technical Support.  It's too bad you didn't join this forum until just now...  to post a wide ranging rant on a two year old post.  You are in the troubleshooting section of the forum.  It is for users to help other users with problems that are resolvable on their end and when they are not, to direct them to the place where they can continue troubleshooting efforts.  If you would like to post your thoughts on corporate guidance, best practices, feedback on specific Corsair gear, or your general opinion on whatever topic, the place to do so is here https://forum.corsair.com/forums/forum/236-corsair-icue/ .   The original poster surely had a real issue as did the others who posted after.  What advice are you giving them to solve their problem?  Don't do anything, just yell louder?

I tried to explain my own experience in detail to ensure we were all on the same page and discussing the same issue. As for the trouble solving I tried several things myself such as  turning off relevant services and then activating them one by one in the services.msc panel, to see if there was a conflict with other control software, with an interface controlling other parts of ligtning in a DIY computer built with parts from various manufacturers. I haven't had much success yet and now that I have changed computer lately I have upgraded and the new version of iCUE doesn't seem to have this problem. My Motherboard is from ASUS (z790 ROG) and they also include RGB controls for their hardware such as the motherboard and my GPU. If someone have a persisting problem with the iCUE menu in systray I suggest they try running it without the ASUS ArmoryCrate starting at Windows startup. But on the other hand that is such a trivial suggestion I can only imagine that users with similar builds would already have tried that. But the troubles doesn't stop there. I now experience that the iCUE icon in systray has now gone. It is not a huge problem as I have a shortcut to iCUE in my taskbar, and the service seems to be running flawlessly, so when I start iCUE from my taskbar I get the iQUE panel anyway, so that's a much smaller problem than the formerly reported about the stuck, menu.

What offended me was the outright dismissal of the problem suggesting it was most likely a problem on the users end, since it hasn't been widely reported. As I already mentioned most users experience with the resulting actions on the software/driver/hardware manufacturers part - or lack thereof - could also contribute to the low number of reports on the official forum. At the same time it didn't take long to find pages of complaints through a simple google search.

My own experience on user forums provided by manufacturers is also that no matter how many users report the same problem, I rarely see the problem fixed in the following software/firmware/driver update. It was a simple observation. I admit it was of little technical help, but had the simple hope that Corsair would have staff dedicated to reading through these forums to keep themselves updated about the user experience. But that may very well be more than you should expect - even from a giant like Corsair ... or perhaps particularly from a giant. It is not a rant, but simply a sense of sadness over the current situation and the way too long distance between the end-user and the manufacturer.

[CyberAssault]

On 2/12/2023 at 8:07 AM, c-attack said:

Yes, I am sure there were dozens of possible explanations from probable to absurd.  This was a combined Windows/CUE task bar issue back in 2020 which was resolved long ago.  Unclear whether the original user who needed help was older software OS or CUE or was running additional software that interacts with the task bar.  Aside from cleaning up the installation of CUE on his/her end there is not a lot that can be done in a peer to peer support forum, hence the suggestion to contact Support to provide the necessary details to those that are in a position to analyze and resolve it.  However, it is ridiculous to assume it is an unreported widespread error and then do nothing on the user end.  Your argument there are numerous other far less likely but possible explanations is not very compelling since you offer none of merit, there are almost no technical details offered from any of the posters, and suggests you don't have much experience in resolving issues from people without technical backgrounds.  Regardless of the actual root cause of the issue, if you think initially treating this as a local issue before moving on to more complex origins that are not user side resolvable is a mistake, then you are not qualified to be dishing out your sermon.  

 

This is an example of a fallacy.  

 

I am amazed at your dedication to organize a Corsair owners group, collect everyone's software and hardware details, and then systematically poll the residents of three countries.  That is an amazing effort.  Make sure you pass those details on to Corsair Technical Support.  It's too bad you didn't join this forum until just now...  to post a wide ranging rant on a two year old post.  You are in the troubleshooting section of the forum.  It is for users to help other users with problems that are resolvable on their end and when they are not, to direct them to the place where they can continue troubleshooting efforts.  If you would like to post your thoughts on corporate guidance, best practices, feedback on specific Corsair gear, or your general opinion on whatever topic, the place to do so is here https://forum.corsair.com/forums/forum/236-corsair-icue/ .   The original poster surely had a real issue as did the others who posted after.  What advice are you giving them to solve their problem?  Don't do anything, just yell louder?

It was not resolved I've been experiencing this issue for 5 months now. Clean install and reinstall. There are missing taskbar options and finnicky crap going on, before & after windows 11 update. My H100i Cooler, ICUE Should have all its ******g Menu Options for the 270$ cooler I paid for with an LCD Screen. That's what I bought, I didn't buy it new....... for the software that controls it to take a dump. We need more updates and bug fixes. Tech Support was not helping either and it's a nightmare to submit another ticket. 

[CyberAssault]

On 2/12/2023 at 8:07 AM, c-attack said:

Yes, I am sure there were dozens of possible explanations from probable to absurd.  This was a combined Windows/CUE task bar issue back in 2020 which was resolved long ago.  Unclear whether the original user who needed help was older software OS or CUE or was running additional software that interacts with the task bar.  Aside from cleaning up the installation of CUE on his/her end there is not a lot that can be done in a peer to peer support forum, hence the suggestion to contact Support to provide the necessary details to those that are in a position to analyze and resolve it.  However, it is ridiculous to assume it is an unreported widespread error and then do nothing on the user end.  Your argument there are numerous other far less likely but possible explanations is not very compelling since you offer none of merit, there are almost no technical details offered from any of the posters, and suggests you don't have much experience in resolving issues from people without technical backgrounds.  Regardless of the actual root cause of the issue, if you think initially treating this as a local issue before moving on to more complex origins that are not user side resolvable is a mistake, then you are not qualified to be dishing out your sermon.  

 

This is an example of a fallacy.  

 

I am amazed at your dedication to organize a Corsair owners group, collect everyone's software and hardware details, and then systematically poll the residents of three countries.  That is an amazing effort.  Make sure you pass those details on to Corsair Technical Support.  It's too bad you didn't join this forum until just now...  to post a wide ranging rant on a two year old post.  You are in the troubleshooting section of the forum.  It is for users to help other users with problems that are resolvable on their end and when they are not, to direct them to the place where they can continue troubleshooting efforts.  If you would like to post your thoughts on corporate guidance, best practices, feedback on specific Corsair gear, or your general opinion on whatever topic, the place to do so is here https://forum.corsair.com/forums/forum/236-corsair-icue/ .   The original poster surely had a real issue as did the others who posted after.  What advice are you giving them to solve their problem?  Don't do anything, just yell louder?

I shouldn't have to pull up my Reg Editor just to get something to run right either. I bet it's more common than your thinking my guy I'm surprised there aren't more posts. I guess too many people put up with crap. Or maybe people don't want to make an account just to solve a software issue that isn't destroying their computer. Regardless, Enough people are saying they have the same issue.

[I_DON_LIKE_INVS_WINDOWS]

Hello,

The reason more people are not complaining about it should be obvious its because the nature of the issue is hard to identify that it is related to the iCUE software its a invisible window that blocks interaction with anything behind it. people will think it is just a strange issue like I have for likely months if not longer. I suddenly realized it was a problem when I randomly noticed it is the same area as the iCUE task manager popup and then the issue went away after closing it. Fix the issue instead of hiding the issue with making the window not visible that is so unbelievably lazy.