What is in the LabVIEW 2023 Q3 Patch 4?

[Frozen]

---

@_Bryan wrote:

---

@tst wrote:

---

@_Bryan wrote:

No idea.

I did a search and found your post though.......  We are having an issue on a Windows 11 desktop computer where the mouse is moving around and clicking things.  They say it is happening even without a mouse plugged in.  

---

My guess would be that this is Windows recognizing a connected device as a mouse and interpreting its data as mouse commands. Before USB was common, Windows would try to automatically recognize what kind of device you have plugged in based on various heuristics (Plug and Play). While USB is no longer new, I wouldn't be surprised if Windows 11 still has this code in it and people using programs written in LV are far more likely than the average user to plug in some relatively rare device to a serial port. Disconnecting whatever they have plugged in is a good way to test this.

---

The fun part is that 2 new computers are having the same issue, one is a primary and the other is a backup computer.  The computer uses a mouse, keyboard, monitor and an ethernet DAQ device.  It was written in LabVIEW 2023 Q3 and the only code for the mouse is to change the pointer into a busy icon when checking for the attached DAQ and then goes back to Normal.  So for a test I am going to remove that code and see what happens.  But the other new computers with 2023 Q3 code have not shown the same issue. 

Our IT department can't figure out what is happening and running out of ideas on how to fix it.  So I am just wondering if LabVIEW could possibly be causing it somehow, but I have not found anything.  So I am starting to reach for anything strange at this point.

---

Maybe a bad touch screen?

[_Bryan]

---

@Frozen wrote:

---

@_Bryan wrote:

---

@tst wrote:

---

@_Bryan wrote:

No idea.

I did a search and found your post though.......  We are having an issue on a Windows 11 desktop computer where the mouse is moving around and clicking things.  They say it is happening even without a mouse plugged in.  

---

My guess would be that this is Windows recognizing a connected device as a mouse and interpreting its data as mouse commands. Before USB was common, Windows would try to automatically recognize what kind of device you have plugged in based on various heuristics (Plug and Play). While USB is no longer new, I wouldn't be surprised if Windows 11 still has this code in it and people using programs written in LV are far more likely than the average user to plug in some relatively rare device to a serial port. Disconnecting whatever they have plugged in is a good way to test this.

---

The fun part is that 2 new computers are having the same issue, one is a primary and the other is a backup computer.  The computer uses a mouse, keyboard, monitor and an ethernet DAQ device.  It was written in LabVIEW 2023 Q3 and the only code for the mouse is to change the pointer into a busy icon when checking for the attached DAQ and then goes back to Normal.  So for a test I am going to remove that code and see what happens.  But the other new computers with 2023 Q3 code have not shown the same issue. 

Our IT department can't figure out what is happening and running out of ideas on how to fix it.  So I am just wondering if LabVIEW could possibly be causing it somehow, but I have not found anything.  So I am starting to reach for anything strange at this point.

---

Maybe a bad touch screen?

---

It is a desktop computer.  

I think the original computer had a touchscreen that was disabled because everyone ended up touching it when pointing at the screen.  I am waiting to hear back what monitor is currently connected.

I always thought the touchscreen monitors needed a USB connection to operate as a touchscreen.  So I figured the monitor would not matter without the USB.  But it is worth looking into. 

[NIquist]

Maybe AI is already taking over??? 

"I have no mouse and I must scream"  😱

[tst]

---

@_Bryan wrote:

---

The computer uses a mouse, keyboard, monitor and an ethernet DAQ device. 

---

I suppose it's also possible this could happen with an Ethernet device, but I have only heard of it with devices connected directly to the PC (serial, parallel, etc.).

I would suggest opening Device Manager on that PC and seeing if there's an unexpected mouse in the list.

[_Bryan]

---

@tst wrote:

---

@_Bryan wrote:

---

The computer uses a mouse, keyboard, monitor and an ethernet DAQ device. 

---

I suppose it's also possible this could happen with an Ethernet device, but I have only heard of it with devices connected directly to the PC (serial, parallel, etc.).

I would suggest opening Device Manager on that PC and seeing if there's an unexpected mouse in the list.

---

I can't connect to it remotely, but the IT guys on site say they have gone though the device manager already.  Along with the usual update everything approach.  Microsoft had a page full of troubleshooting steps that they say have not helped.  I think the only thing they have not tried yet is a new profile. 

But I am not sure if new profiles will help since it has happened on the primary and backup computer.  So it has to be something common to both of the computers.  I also asked them to try another keyboard since we are now looking for something really strange.

Thanks for the help though.

[rolfk]

Some computers have a strange serial port in their device manager that is some sort of management device interface for the TPM or similar chipset embedded security management engine. Maybe that acts up and makes Windows believe it sees a mouse/touch panel on that serial port?

I never managed to capture it with VISA as some service in Windows seems to normally claim it at startup.

[_Bryan]

---

@_Bryan wrote:

---

@Frozen wrote:

---

@_Bryan wrote:

---

@tst wrote:

---

@_Bryan wrote:

No idea.

I did a search and found your post though.......  We are having an issue on a Windows 11 desktop computer where the mouse is moving around and clicking things.  They say it is happening even without a mouse plugged in.  

---

My guess would be that this is Windows recognizing a connected device as a mouse and interpreting its data as mouse commands. Before USB was common, Windows would try to automatically recognize what kind of device you have plugged in based on various heuristics (Plug and Play). While USB is no longer new, I wouldn't be surprised if Windows 11 still has this code in it and people using programs written in LV are far more likely than the average user to plug in some relatively rare device to a serial port. Disconnecting whatever they have plugged in is a good way to test this.

---

The fun part is that 2 new computers are having the same issue, one is a primary and the other is a backup computer.  The computer uses a mouse, keyboard, monitor and an ethernet DAQ device.  It was written in LabVIEW 2023 Q3 and the only code for the mouse is to change the pointer into a busy icon when checking for the attached DAQ and then goes back to Normal.  So for a test I am going to remove that code and see what happens.  But the other new computers with 2023 Q3 code have not shown the same issue. 

Our IT department can't figure out what is happening and running out of ideas on how to fix it.  So I am just wondering if LabVIEW could possibly be causing it somehow, but I have not found anything.  So I am starting to reach for anything strange at this point.

---

Maybe a bad touch screen?

---

It is a desktop computer.  

I think the original computer had a touchscreen that was disabled because everyone ended up touching it when pointing at the screen.  I am waiting to hear back what monitor is currently connected.

I always thought the touchscreen monitors needed a USB connection to operate as a touchscreen.  So I figured the monitor would not matter without the USB.  But it is worth looking into. 

---

A very possible winner winner chicken dinner!

It turns out that the touchscreen monitor was still attached to the system.  I had IT swap it out last week, IT did not even realize it was a touchscreen and as of Friday they were not having any mouse issues.  I should know by the end of the week if it was the monitor causing the issue.

Thanks to everyone for the help with suggestions.     

[Intaris]

---

@Frozen wrote:

---

---

Maybe a bad touch screen?

---

I will not lie. I thought this was a bit of a crazy suggestion at the time but well..... spot on.

I suppose sometimes crazy situations can use a crazy suggestion. Kudos.