3D Spacemouse no longer works after Win 11 update 25H2

[MartinKB]

Hello,

After updating to Windows 11 25H2, the SpaceMouse is no longer recognized or connected in HP Z RGS.

I’ve already installed the new version 26.6.0.9951, but unfortunately that didn’t help either.

Additionally, “Enable Remote USB” and “Enable Clipboard” are grayed out and cannot be enabled.

Are there any other settings I can check?

Thank you very much

Martin

[KellyRGS]

Hello 

Can you tell me what SpaceMouse you are using? Are you using Windows 11 25H2 on both sender and receiver?  If so, when you installed both sender and receiver did you do any custom installation settings such as not installing Remote USB, or installing it as local only, or did you just use the installer and default settings on both? 

3DConnexion devices are not automatically remoted, you probably already know this, but when the device is plugged into the Receiver before the connection and then the connection is made, to remote it, you need to unplug the device and plug it back in to remote it.  The Sender and Receiver should have the appropriate 3DConnexion driver installed as well.  When you end the session, and want to use the device locally at the Receiver you need to unplug the device and plug it back in to bring it back.  

If a Windows Receiver, you can automate this process by setting up a registry setting which is covered in the User Guide under the Remote USB section.  Section starts at page 73 in the attached User Guide.

We did have two 3DConnexion devices that RGS was blocking some time ago and we did fix that with a property in the rgsenderconfig file.  Those two devices were the SpaceMouse Enterprise and the Wireless CAD Mouse.  To change that property, you need to open a text editor with admin privileges, remove the # and change the property from zero to one, save the file, do not perform a SaveAs, and then restart the sender service for the change to take effect.  The rgsenderconfig file is located at Program Files/HP/Remote Graphics Sender.

## Cause the Sender local display to blank and local keyboard and mouse
## input to block when primary user is connected.
# Rgsender.IsBlankScreenAndBlockInputEnabled=1
## Disable Input blocking. This setting specifically overrides the
## IsBlankScreenAndBlockInputEnabled setting for input blocking. This
## allows a user to enable screen blanking and allow input.
# Rgsender.DisableInputBlocking=0

Happy to do some testing as I have all of the 3DConnexion devices and see what I can do.  If the device is a discontinued one, that might make things a little more difficult.

Kelly

I am an HP employee.

[MartinKB]

Hi Kelly,

Thank you very much for your reply.

We use both the SpaceMous Pro and the SpaceMous Wireless 🙂
I was just a little surprised because everything worked perfectly before the update to Windows 11 25H2.
We’ve now adjusted the following settings on both .... the sender AND the receiver.

Sender:
## Cause the sender’s local display to go blank and block local keyboard and mouse
## input when the primary user is connected.
Rgsender.IsBlankScreenAndBlockInputEnabled=1
## Disable input blocking. This setting specifically overrides the
## IsBlankScreenAndBlockInputEnabled setting for input blocking. This
## allows a user to enable screen blanking while still allowing input.
Rgsender.DisableInputBlocking=1

## Remote Clipboard
Rgsender.Clipboard.IsEnabled=1

Receiver:
##### USB properties:
Rgreceiver.Usb.IsMutable=1
Rgreceiver.Usb.IsEnabled=1

## Sender session connection number to activate USB
Rgreceiver.Usb.ActiveSession=1

With these settings, the SpaceMouse works again.

Unfortunately, the clipboard still isn’t working.

Thank you very much for your help.
Best regards,
Martin

[KellyRGS]

What is the issue with clipboard that you are experiencing?  Copying and pasting text or an image?  RGS does not allow for copying and pasting files or multiple images at a time.  Is clipboard enabled in both sender and receiver?

I saw on the 3DConnexion forum that some of the older devices lost support in Windows 11, so I thought maybe that could be the problem, but glad you are back up and running with those devices.

Kelly

[MartinKB]

Hi Kelly,

Sorry for the late reply.

I can't copy any text.

“Enable Remote Clipboard” is grayed out and can't be enabled at all.

Thank you very much & best regards,
Martin

[KellyRGS]

Hello Martin

How did you install the sender and receiver?  Installer and customizing it or just using the defaults which should include Remote USB and Clipboard.  Or did you use command line to install the sender and receiver?  If so, if you did not include the clipboard option in the command line installation, that would prevent clipboard from working.

Windows to Windows environment for RGS?

In your settings for the sender, you show Clipboard being uncommented and enabled (set to 1).  If this was done after the sender was installed, my guess is that it was since the # is usually still there on a default installation, you would need to save the change, and restart the sender service to have the change take effect.  

On the receiver side, what does the property look like in the rgrecevierconfig file?  I always install clipboard by default on both sender and receiver.  If this is set to zero (Rgreceiver.Clipboard.IsEnabled) then it was not included in the installation.  If turning on the property, saving the change, make sure you use text editor with admin privileges, and then close the receiver and relaunch.  See if clipboard is then enabled.  

##### Clipboard properties:
# Rgreceiver.Clipboard.IsMutable=1
# Rgreceiver.Clipboard.IsEnabled=1

## List of clipboard format types allowed to be transferred between Sender
## and Receiver. The property string is a regular expression. Wildcard
## matching (globbing) is not supported.
# Rgreceiver.Clipboard.FilterString=|1|7|8|13|16|17|Ole Private Data|Object Descriptor|Link Source Descriptor|HTML Format|Rich Text Format|XML Spreadsheet|

Sometimes un-installing the sender and/or receiver, depends on whether or not both did not get the clipboard enabled, and then installing them again should resolve the issue.  

Kelly