Windows 10: GetSystemMetricsSM_CMOUSEBUTTONS returning wrong value on Windows10 on RDP

If we call the Windows GetSystemMetrics function to find the number of buttons of the installed mouse, it alwaysreturns 2 if the function is called from a Remote Desktop session.


Our application needs 3 buttons to perform 3 different actions on graphic clients ILOG IlView based.However, the application only receives events for two buttons if executed on a Terminal Server/RDP session. But it works fine on a console session. The software detects only two buttons and the graphic library ignores events coming from the third one.


The detection is internally made by invoking GetSystemMetrics passing SM_CMOUSEBUTTONS as a parameter. The result varies between console and RDP sessions.


The problem happens only if the RDP session is executed on Windows 10, but not on Windows 7. No matter what Windows version is used on the client side.


int main int argc, char **argv


{


BOOL fResult = GetSystemMetricsSM_MOUSEPRESENT;

if fResult == 0
printf"No mouse installed.\n";
else
{
printf"Mouse installed.\n";

int nb = GetSystemMetricsSM_CMOUSEBUTTONS;
printf"The number of mouse buttons - %d\n", nb;
}
getche;
return 0;




}


The expected result on Windows 10 on a RDP session is greater than 2 if a 3-button mouse is being used. However it coming as is2, which is incorrect.

:)

 

Native Resolution wrong in Windows10 laptop


Hi, I assume you bought it 2nd hand. Did it come with Win 10?

As you're unsure about what you've got, I suggest you download and run
Hwinfo64
E.g.

 

RDP

Hi Nikki,

We can see here that you are having issues using (RDP) Remote Desktop Protocol on your computer. There are several reasons why you are experiencing this concern. To set your expectation, we will be doing some troubleshooting steps to isolate
this problem. Before we proceed, may we know the following:

• Any changes made on the computer prior to this concern?
• What troubleshooting steps have you tried so far?
• Is this the first time that you encountered this problem?
• When did you notice about this issue?
• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.

 

RDP

• Any changes made on the computer prior to this concern?
  
  Initially when we received the problem there wasn't any changes made on the computer since we couldn't figure out the problem, we upgraded the pc to windows 10. It fixed the problem momentarily and then it starts again. Then we re initiated the upgrade the
  same day I wrote this post and it was fixed again and then on today the issue is back

• What troubleshooting steps have you tried so far?
  
  In the past we would delete the MS Licensing Protocol folder as suggested by so many other posts and restart the RDP connection ad administrator to rebuild it. This time around it didn't fix anything. Like I said previously we've tried to upgrade the PC and
  the fix is temporal

• Is this the first time that you encountered this problem? No

• When did you notice about this issue? I'm not sure when it started because I haven't been on this project that long but I would say within the last month based on me. Based on other conversations this has happened in the past.

• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.
  
  Sure