If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
A strange thing happened with the latest Win10 update
Microsoft laid another update for Win10 1709 on us last week. I try to wait
a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. |
Ads |
#2
|
|||
|
|||
A strange thing happened with the latest Win10 update
On 4/27/2018 3:59 AM, Tim wrote:
Microsoft laid another update for Win10 1709 on us last week. I try to wait a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. None of the updates have affected any of my Logitech mice or any USB functions, so those particular problems appears to be yours. However, if what you need to do can be accomplished on some other OS, why not switch? -- best regards, Neil |
#3
|
|||
|
|||
A strange thing happened with the latest Win10 update
Tim wrote:
Microsoft laid another update for Win10 1709 on us last week. I try to wait a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. During the OS Upgrade to 1709, it will be reinstalling your 77MB copy of SetPoint. That's part of what the migration logic does - C:\Windows becomes C:\Windows.old and the OS installation process "reinstalls" stuff. Certain migrations aren't always done properly. For example, the RAMDisk on my Win10 setup usually gets "borked" and I have to do a quick "Repair Install" from Programs and Features to bring it back to life. Since the software in question is Logitech, and it's 77MB in size (for the purpose of making the two arrow buttons on the left, work on your trackball), what happened isn't particularly a surprise. That's a huge piece of software. You could remove SetPoint, before the 1804 Upgrade comes in, and see how an Upgrade install works with vanilla HID drivers (the Microsoft in-box drivers). Paul |
#4
|
|||
|
|||
A strange thing happened with the latest Win10 update
On 27/4/2018 3:59 PM, Tim wrote:
Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. That's why people want the option to disable automatic update!! Do you wanna work overtime because of a bad update from Micro$oft? Well... US Government doesn't give a dime about this! -- @~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!! / v \ Simplicity is Beauty! /( _ )\ May the Force and farces be with you! ^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3 不借貸! 不詐騙! 不*錢! 不援交! 不打交! 不打劫! 不自殺! 不求神! 請考慮綜援 (CSSA): http://www.swd.gov.hk/tc/index/site_...sub_addressesa |
#5
|
|||
|
|||
A strange thing happened with the latest Win10 update
On Fri, 27 Apr 2018 07:59:42 GMT, Tim wrote:
Microsoft laid another update for Win10 1709 on us last week. I try to wait a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. Their updates seem to be getting worse all the time. As some people here know, I re-installed Windows 10 the other day because I _believed_ that a driver issue caused my computer to behave as if the motherboard died. It turned out that Bitlocker was the issue. However, on the latest installation, after disabling Bitlocker and updating the driver properly to remedy the issue, Windows decided that my installation was no longer activated and refused to activate. It also refused to allow me to install Windows Store apps. None of this idiocy is necessarily the fault of an update, but I've been using Bitlocker for months and updating a graphics driver with it enabled only recently became an issue; it was always possible before. |
#6
|
|||
|
|||
A strange thing happened with the latest Win10 update
a.m wrote:
On Fri, 27 Apr 2018 07:59:42 GMT, Tim wrote: Microsoft laid another update for Win10 1709 on us last week. I try to wait a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. Their updates seem to be getting worse all the time. As some people here know, I re-installed Windows 10 the other day because I _believed_ that a driver issue caused my computer to behave as if the motherboard died. It turned out that Bitlocker was the issue. However, on the latest installation, after disabling Bitlocker and updating the driver properly to remedy the issue, Windows decided that my installation was no longer activated and refused to activate. It also refused to allow me to install Windows Store apps. None of this idiocy is necessarily the fault of an update, but I've been using Bitlocker for months and updating a graphics driver with it enabled only recently became an issue; it was always possible before. There's something in the Settings panel. https://support.microsoft.com/en-us/...ivation-errors On the older OSes, you might try Googling on "slui 3" and "slui 4". "slui 4" is phone activation. http://www.thewindowsclub.com/fix-wi...ailed-activate Tech Support for activation issues is supposed to be free. Some activation issues are caused by server overload, but "waiting" for stuff to fix itself, is hardly a good approach to a fast resolution. Paul |
#7
|
|||
|
|||
A strange thing happened with the latest Win10 update
On Fri, 27 Apr 2018 13:41:50 -0400, Paul
wrote: a.m wrote: On Fri, 27 Apr 2018 07:59:42 GMT, Tim wrote: Microsoft laid another update for Win10 1709 on us last week. I try to wait a week or so to see what went wrong (there's always something). But Monday I had to reboot for a different reason so the update got applied. Everything seemed to go ok until I went to use Windows again. My mouse stopped working. I have a Logitech M750 wireless trackball mouse that I consider to be almost perfect. Nothing. Nada. The system still saw the wireless dongle, but no mouse activity. I figured out the basic keyboard moves to let me read my email, but that was about it. So I picked up a plain vanilla $7 three button mouse to use while I got the M750 fixed/replaced. Ugh! Today I decided to try to troubleshoot a little before contacting Logitech. As part of that, I reloaded the Logitech driver. Wonderbah! Everything worked! All I can think of is that something in the update fubarred the driver to the point that it wouldn't work. That's not really surprising since all of the problems with this update seemed to affect USB things. I swear, if I wasn't so embedded into the Windows environment, I would be switching to Linux. I am going to test drive it again. I may switch anyway. Their updates seem to be getting worse all the time. As some people here know, I re-installed Windows 10 the other day because I _believed_ that a driver issue caused my computer to behave as if the motherboard died. It turned out that Bitlocker was the issue. However, on the latest installation, after disabling Bitlocker and updating the driver properly to remedy the issue, Windows decided that my installation was no longer activated and refused to activate. It also refused to allow me to install Windows Store apps. None of this idiocy is necessarily the fault of an update, but I've been using Bitlocker for months and updating a graphics driver with it enabled only recently became an issue; it was always possible before. There's something in the Settings panel. https://support.microsoft.com/en-us/...ivation-errors On the older OSes, you might try Googling on "slui 3" and "slui 4". "slui 4" is phone activation. http://www.thewindowsclub.com/fix-wi...ailed-activate Tech Support for activation issues is supposed to be free. Some activation issues are caused by server overload, but "waiting" for stuff to fix itself, is hardly a good approach to a fast resolution. slui.exe would work but slui.exe 4 refused to load. I think decrypting the Bitlocked drives corrupted something even though they suddenly allowed me to install the graphics driver with no issue. To say the least, I'm not bothering with Bitlocker on anything other than external drives anymore and I'm not even installing the Pro edition either. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|