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
|
|||
|
|||
Another 1803 problem - Cursor arrow slow to appear
I don't normally shut my computer down when I have finished using it.
Instead, I have set it so that after a short period of non-use it goes to sleep. Until recently, all I have had to do to wake it is waggle the wireless mouse, wait a few seconds for the computer to wake up, and after the login screen and box appears I log in. All this has changed since the 1803 update. Now, when I want to wake up the computer, I can waggle the mouse until I am blue in the face and the only response is blinking green light from the mouse as it tries to connect to its receiver. For variety the mouse periodically blinks red, presumably telling me that the brand new battery has been dragged down to a low voltage. What I now have to do to wake up the computer is hit the space bar on the keyboard (once will do) and wait for what now seems to be a slightly longer term for the computer to start. Then the log in screen pops up but without the log in box. What is worse is that the screen has no cursor arrow with which to provoke the login. Fortunately, hitting the space bar causes the login box to appear with a cursor bar at a position which allows me to start typing. So I type in my password, hit return and voila! The screens have pictures and icons etc but still no cursor arrow. In the meantime the green light on the mouse is going bonkers. From this point I have tried all sorts of things in an attempt to bring up the cursor arrow but without success. All that seems to work is waiting for several minutes until the cursor arrow decides to appear of its own accord, somewhere on the screen. There appears to be no pattern in where it appears. The wireless keyboard and mouse are a matched pair by Logitech. They share a common receiver plugged into a USB port on one of my monitors about 1 foot (30 cm) away. At first I thought it was a simple USB problem but the fact that the keyboard is ready and waiting while the mouse defies all attempts to make it work suggests it is something which has changed in Windows settings which only affects the mouse. I'm out of my depth in Windows at this level and I would be grateful to anyone who can help me make my mouse to come to life as soon as I waggle it. -- Regards, Eric Stevens |
#2
|
|||
|
|||
Another 1803 problem - Cursor arrow slow to appear
Eric Stevens wrote:
I don't normally shut my computer down when I have finished using it. Instead, I have set it so that after a short period of non-use it goes to sleep. Until recently, all I have had to do to wake it is waggle the wireless mouse, wait a few seconds for the computer to wake up, and after the login screen and box appears I log in. All this has changed since the 1803 update. Now, when I want to wake up the computer, I can waggle the mouse until I am blue in the face and the only response is blinking green light from the mouse as it tries to connect to its receiver. For variety the mouse periodically blinks red, presumably telling me that the brand new battery has been dragged down to a low voltage. What I now have to do to wake up the computer is hit the space bar on the keyboard (once will do) and wait for what now seems to be a slightly longer term for the computer to start. Then the log in screen pops up but without the log in box. What is worse is that the screen has no cursor arrow with which to provoke the login. Fortunately, hitting the space bar causes the login box to appear with a cursor bar at a position which allows me to start typing. So I type in my password, hit return and voila! The screens have pictures and icons etc but still no cursor arrow. In the meantime the green light on the mouse is going bonkers. From this point I have tried all sorts of things in an attempt to bring up the cursor arrow but without success. All that seems to work is waiting for several minutes until the cursor arrow decides to appear of its own accord, somewhere on the screen. There appears to be no pattern in where it appears. The wireless keyboard and mouse are a matched pair by Logitech. They share a common receiver plugged into a USB port on one of my monitors about 1 foot (30 cm) away. At first I thought it was a simple USB problem but the fact that the keyboard is ready and waiting while the mouse defies all attempts to make it work suggests it is something which has changed in Windows settings which only affects the mouse. I'm out of my depth in Windows at this level and I would be grateful to anyone who can help me make my mouse to come to life as soon as I waggle it. In Device Manager, do Properties on all the affected visible items on your fully running system. Check whether the tick box for "Allow the computer to turn off this device to save power" has been switched on by accident. https://s33.postimg.cc/hqp6vo2xb/Device_Manager.gif The "powercfg" command, in an Administrator Command prompt, also has information about this stuff. https://www.howtogeek.com/122954/how...-accidentally/ powercfg -devicequery wake_armed Between Powercfg and Reliability Monitor, there's some real improvements in Windows 10 with regard to easy visibility of what's going on. Compared to say, WinXP. HTH, Paul |
#3
|
|||
|
|||
Another 1803 problem - Cursor arrow slow to appear
On Thu, 19 Jul 2018 00:35:04 -0400, Paul
wrote: Eric Stevens wrote: I don't normally shut my computer down when I have finished using it. Instead, I have set it so that after a short period of non-use it goes to sleep. Until recently, all I have had to do to wake it is waggle the wireless mouse, wait a few seconds for the computer to wake up, and after the login screen and box appears I log in. All this has changed since the 1803 update. Now, when I want to wake up the computer, I can waggle the mouse until I am blue in the face and the only response is blinking green light from the mouse as it tries to connect to its receiver. For variety the mouse periodically blinks red, presumably telling me that the brand new battery has been dragged down to a low voltage. What I now have to do to wake up the computer is hit the space bar on the keyboard (once will do) and wait for what now seems to be a slightly longer term for the computer to start. Then the log in screen pops up but without the log in box. What is worse is that the screen has no cursor arrow with which to provoke the login. Fortunately, hitting the space bar causes the login box to appear with a cursor bar at a position which allows me to start typing. So I type in my password, hit return and voila! The screens have pictures and icons etc but still no cursor arrow. In the meantime the green light on the mouse is going bonkers. From this point I have tried all sorts of things in an attempt to bring up the cursor arrow but without success. All that seems to work is waiting for several minutes until the cursor arrow decides to appear of its own accord, somewhere on the screen. There appears to be no pattern in where it appears. The wireless keyboard and mouse are a matched pair by Logitech. They share a common receiver plugged into a USB port on one of my monitors about 1 foot (30 cm) away. At first I thought it was a simple USB problem but the fact that the keyboard is ready and waiting while the mouse defies all attempts to make it work suggests it is something which has changed in Windows settings which only affects the mouse. I'm out of my depth in Windows at this level and I would be grateful to anyone who can help me make my mouse to come to life as soon as I waggle it. In Device Manager, do Properties on all the affected visible items on your fully running system. Check whether the tick box for "Allow the computer to turn off this device to save power" has been switched on by accident. https://s33.postimg.cc/hqp6vo2xb/Device_Manager.gif I have checked this and as far as I can see anything related to mouse and keyboard is allowed to wake the computer. The "powercfg" command, in an Administrator Command prompt, also has information about this stuff. https://www.howtogeek.com/122954/how...-accidentally/ powercfg -devicequery wake_armed I tried that and here is what I got back: C:\WINDOWS\system32powercfg -devicequery wake_armed Logitech HID-compliant Unifying keyboard Logitech HID-compliant Unifying Mouse HID-compliant mouse Intel(R) Ethernet Connection (2) I218-V HID Keyboard Device Between Powercfg and Reliability Monitor, there's some real improvements in Windows 10 with regard to easy visibility of what's going on. Compared to say, WinXP. The only problem is that I lack the underlying information required to make sense of it. -- Regards, Eric Stevens |
Thread Tools | |
Display Modes | Rate This Thread |
|
|