Windows 10: Windows 10 v1607: Logitech TRB-22 Wireless Trackman Problems...

It appears that my recent update to W10 v1607 has screwed up my Logitech trackman (arguably the best mouse ever made, but stupidly discontinued by Logitech.) Every time I boot up or restart from Sleep, I have to press the trackman's reset button. Otherwise, there is no cursor. Furthermore, although I get the cursor working, if I stop using the mouse for a short time while typing text, the cursor freezes and I have to push the reset again to get things working. I believe that this malfunction is related to v1607 and has adversely effected other devices (eg, cams) as is now being reported in various forums. Any suggestions on how to handle this issue?

Until Microsoft fixes this issue, perhaps it would be best to roll back the 1607 update to the previous version of W10 that was on my computer? But, I'm a little shaky about doing this. Can it be done easily without causing further problems, and how?

:)

 

windows 10 not recognizing keyboard and trackball drivers or acknowledging connections

These are the things that do not work now with the Windows 10 Pro OS machine, a rebuilt Dell Inspiron 3668, which I received 1/30/2018. All of them did work when I first set it up and installed the drivers.

Logitech Trackman Marble M/N: MO1047

Fellowes Smart Design Keyboard with Microban KU 9938

Dell USB corded mouse CANCES 3181 NMB 3181 (came with the Desktop)

Dell USB corded keyboard DP/N 0644G3 (came with the Desktop)

This USB corded accessory does work:

Logitech Webcam Pro 9000 for Business ( I just checked and the controls are now missing on the screen. This issue was previously resolved by downloading a new driver. The OS may be starting to not read this driver now.)

These are Bluetooth-enabled devices that are plugged into the USB ports, and they work:

Sennheiser BTD 500 USB (Bluetooth dongle)

Logitech Wireless Touch Keyboard K-400r

I appreciate your help.

 

Compatibility Windows 10 and Logitech Wireless Keyboard

I am on my third Logitech wireless keyboard and mouse (courtesy of Logitech) since I got a new computer with Windows 7 and immediately upgraded to Windows 10. I have no end of problems with letters and numbers I've typed not showing up on a document,
or letters/numbers missing in a string after 10 seconds of typing, or letters double typing. If I use the keyboard and mouse on a Windows 7 computer, I have no such problems. Help! Is there a basic incompatibility between the Logitech wireless keyboard
and Windows 10? Logitech has given up on me.

 

After the 10 update....have you tried uninstalling and reinstalling software/driver package for that mouse?

Cordless Optical TrackMan - Logitech Support

 

Did the uninstall and the reinstall (V. 6.67.83,) and now when Setpoint is opened, it doesn't show the screens that allow for the TRB-22 to be programed. In fact, it doesn't show any mouse controls...just the Tools tab. I have tried downloading from several sources, but all to no avail as the programs only opened up with the Tools tab and nothing about TRB-22 settings???

 

From what I heard MS should be sending out a fix for all those types of issue's sometime in Sept. Just don't know when in Sept. *Confused
I think Logitech should be sending out a fix for THEIR software.....but guess not.

 

Can't wait for the fix, as I can't stand using a "regular" mouse. I guess it would be better to wait rather than rolling back to a previous W10 version???

 

Thats up to you, but I would wait if it was me. That AU messed up my logitech Web Cam software, but any other software can use my web cam just fine.....just not Logitech's OWN software. *Mad

BTY My logitech wireless keyboard and mouse software have no problems .....but don't think we use the same version's

 

@flycaster
Here is a screenshot of my logitech setpoint.....maybe it IS the same version as yours *Rolleyes



This works just fine for me.

 

2nd screenshot @flycaster
Seems our mice do use the same software....

 

Wonder if you are running your windows 10 with the latest updates installed??

 

Yeah, 1607, and that is when I think the troubles started...as others have noted elsewhere. Everything I have dl'd and opened from Setpoint 6.67.83, it has failed to give me a My Muse tab. It only comes up with a Tools tab. I have tried dl'ing from difference sites and I have dl'd the Smart install and the full 64-bit install...all to no avail. BTW, no viruses or untoward elements have been detected on the computer.

 

I have the RB22 too , and will be most unhappy when it dies, it is great for those with RSI issues, I wish I had one for each of my systems....

I have also found the nothing on all tabs except the Tools tab , a few times with recent Setpoint SW versions, but currently I have it on a Non-AU system and I am back on version 6.30.41 (driver ver. 5.30.67) to get all the Options again.

I also own the MX2 Mouse (Wifi/Bluetooth) but it's Options software ,seems to screwup the Setpoint stuff especially if you install the Options SW 1st on a system , in my experience, ymmv.

KB

 

Several Logitech M570 wireless trackballs here running with no issues. I don't use the Setpoint software though. I don't need any of those functions. If I need to link or unlink device I just install the Unifying software. I use Logitech Keyboards and trackballs exclusively. They all work with the stock Windows supplied drivers.

 

I moved my RB22 over to my AU.83 system and it is seen fine on 6.67.83 (driver 5.90.41) on the PS2 port , the system also has a Marble Mouse on the USB Port, no problem with it and both seen in Setpoint as you would expect.

If I remember rightly I initially had issues in win 10 and went back to Setpoint V6.30_x64 to get the mouse Tab and correct images to show up. That system was the one I installed Options for the MX2 on 1st and could not get SetPoint to recognize anything , so I had to uninstall Options altogether.

Yes they all work fine with the M$ Drivers too but it limits the programmable buttons and the scroll wheel etc, which is the only reason to use the Logitech Software I find.

KB