• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Loss of mouse cursor - attn. : Jose Jeswin

Turns out that the NVidia version is already that latest one you recommended. I've just had another 'random' mouse cursor loss, with CTRL ALT DEL ineffective.
 
On a number of occasions now, I have lost the mouse cursor; and CTRL ALT DEL was ineffective. Rebooting is enough to fix the problem 'for the rest of the day'. It occurs soon after the first bootup of the day, and often when replying to an email (in Windows Live mail) or to a forum thread (in Firefox v50). Telling me that they are both obsolete programs does NOT advance my cause - after all, those programs serve me OK for the rest of the day.
There a setting in the mouse control panel to hide the cursor when you’re typing. Have you tried turning it off?

E35ADA5B-F7A1-4842-B04E-D16113C58A2F.png

What happens with the setting for pushing the CTRL key for locating the mouse pointer?
 
Last edited:
I had not hidden the cursor when typing, but the setting was already for that. The recent failure was NOT during typing.
Pressing CTRL briefly creates concentric circles around the cursor.
 
I had not hidden the cursor when typing, but the setting was already for that.
It’s turned on by default. I thought turning it off would change the issue with the missing cursor. I’ve had a failing graphics card or drivers cause artifacts or the missing cursor.
 
'why you won't upgrade your operating system and Firefox' - I have done so, and told you I even used it 'a little while ago' for an app that requires more RAM than x32 allows - I have it available for when I need it.
'unless you have a very special use case, which seems unlikely. Do you?' I do. I have a vast amount of 'documentation' in WordPerfectforDOS that is easier to access from my retro system than from the x64. WordPerfectforDOS is a text editor that has a unique (and valuable) function called UNDELETE, which is JUST that, and not the UNDO that other programs offer. It also has a KEY-TRIGGERED 'switch documents' function, that is also unique, and which I value. If if can not do something in WordPerfectforDOS which MSWORD can, then I use MSWORD.
The old Firefox allows me to continue to run a very functional video downloader, which a later Firefox will not let me.
The features for which you recommend the latest software and hardware are of no interest to me, whereas the 'old ones' are.

My 64bit system can not 'see' an external HDD with software backups, which my 32bit has no trouble in accessing.
The mail system of Win10 is not TO ME as user-friendly as the obsolete Windows Live Mail which can no longer be installed.

I have tried to install that NVidea driver on a clone of my system - to see first whether it would succeed before 'contaminating' my actual system. Partway through the installation, it gave a popup saying "No suitable graphics devices found", yet continued on till the end. So I do not know if it got installed. There is probably somewhere that I can check that, and you might be able to tell me where to look.

Turns out that the NVidia version is already that latest one you recommended. I've just had another 'random' mouse cursor loss, with CTRL ALT DEL ineffective.
Ok, so it looks like you have a special case for running 32-bit Windows as the functionality of some old programs is important to you and I can understand that.

I've got a similar situation with Personal Accounts from 2009. The user interface on it and realtime updates as data is entered are way better than the latest versions which have had the interface neutered significantly and are hence much more awkward to use. They have more features overall, but this is the one thing I don't want to compromise on so I stay with this old classic. Luckily, it still runs perfectly on the very latest 64-bit Windows 10, so I don't have to make compromises like running it in a VM etc. The time it starts giving problems, I'll consider my options.

Testing on your system is a bit of a basket case given the kind of setup that you have and that no graphics hardware error is very suggestive of a failing card, so you need to do something else. I advise you to grab a spare SSD / HDD and install Windows 10 64-bit on it fresh (unplug all other drives first) and run all the updates. Then, install the latest 466.77 on it and see if it works properly. If it still doesn't, then you have a bad graphics card I'm afraid, so will need to buy a new one.

If it works properly, then I suggest installing the free VMWare, then installing the 32-bit version of W10 in a virtual machine and then all your special apps. You have plenty of memory to give the VM a decent amount of RAM, like 8GB. This way, you get a stable system without giving up anything, greater convenience in accessing your apps and will have a proper cursor.

Even if the card doesn't work properly, then I recommend setting up this arrangement as it's better than what you have now. Of course, don't get rid of your old installs until you're 100% sure that everything is working properly and that all data and settings have been transferred over. It's not a quick job.

Good luck and let us know how you get on.
 
Last edited:
'I advise you to grab a spare SSD / HDD and install Windows 10 64-bit on it fresh' I already have an x64V21h1 on SSD - but only use it when I need to - that is even less, now that an upgrade to Bluestacks has enabled running Signal in x32. I WILL upgrade x64's NVidia to v466.77 (if it's not already at that version). Testing is difficult because the loss of mouse cursor is, as far as I know, totally random, and requires much time spent using it - I don't have a long-duration need for x64.

I would be quite interested in running the x323 in a virtual machine if I could clone it in to that. Starting from scratch is out of the question, since I have been tweaking x32 and its programs for years. That would be too massive a job for so little reward.
 
'I advise you to grab a spare SSD / HDD and install Windows 10 64-bit on it fresh' I already have an x64V21h1 on SSD - but only use it when I need to - that is even less, now that an upgrade to Bluestacks has enabled running Signal in x32. I WILL upgrade x64's NVidia to v466.77 (if it's not already at that version). Testing is difficult because the loss of mouse cursor is, as far as I know, totally random, and requires much time spent using it - I don't have a long-duration need for x64.

I would be quite interested in running the x323 in a virtual machine if I could clone it in to that. Starting from scratch is out of the question, since I have been tweaking x32 and its programs for years. That would be too massive a job for so little reward.
in all honesty, those tweaks you've done are likely what led to the cursor breaking.

It's always best to run as close to stock as possible to avoid this exact situation - you have problems you cant fix that are unique with mystery causes, and you cant/dont want to clean install because of all those tweaks.
 
'I advise you to grab a spare SSD / HDD and install Windows 10 64-bit on it fresh' I already have an x64V21h1 on SSD - but only use it when I need to - that is even less, now that an upgrade to Bluestacks has enabled running Signal in x32. I WILL upgrade x64's NVidia to v466.77 (if it's not already at that version). Testing is difficult because the loss of mouse cursor is, as far as I know, totally random, and requires much time spent using it - I don't have a long-duration need for x64.

I would be quite interested in running the x323 in a virtual machine if I could clone it in to that. Starting from scratch is out of the question, since I have been tweaking x32 and its programs for years. That would be too massive a job for so little reward.
I still maintain that you should go for a setup similar to what I suggested. There are tools out there that can convert an installation into one that can run in a VM, avoiding that rebuild. I don't know any off the top of my head, but it can be done - others might be able to chip in with suggestions. You've got a very awkward problem here, as Mussels said:

in all honesty, those tweaks you've done are likely what led to the cursor breaking.

So putting that install in a VM might be one way to get around having to redo everything, not least because it uses its own generic video driver which will be much more stable.

Note that your original installation is untouched, as it's simply cloned into a VM. Again, everything stays as it is until you're happy that the new setup is working for you. There's no shortcut to putting in the time on this one if you're serious about fixing this problem, sorry.
 
I'm looking forward to seeing here a suggestion of what VM program accepts a clone into it. Experimenting has its merits, but I would like to be sure that I can succeed before I start on this.

Before actually going through the motions of installing the v477.66 NVidia Graphic Card driver from 2018 in the 64bits system, I tried to find out what version is already installed. Control Panel has a 'dead' entry for NVidia; Device Manager's Display Adapter shows a v27.21.14 from 20/09/20, so that is more recent than the v477.66

Although BIOS precedes Windows, booting was delayed by one SSD (which shows for 342bit SSD) not appearing when the 64bit SSD is connected.
Also an external drive that shows without hesitation in 32bits Explorer, is not seen by 64bits Explorer.
 
Indeed, this is why you need a clean W10 64-bit install to test the card out on. Doing anything less than what I suggested is just pissing in the wind. It's not more recent than 477.66, because it's the latest. Not sure how you equate that other version number to it, lol. There's no connection.

Have a Google for converting an OS install to a VM image, as I don't think suggestions are going to be very forthcoming, but it can be done.
 
I simply quoted the figures that Device Manager showed in the Properties of the Display Adapter - Driver details. I have already asked the Microsoft Community AND GOT A REPLY about a VM machine. They told me there is a native one in Windows Features. It requires enablement in BIOS - I am hamstrung by the fact that the various methods that Google has suggested for accessing BIOS do not work. I CAN NOT ACCESS BIOS, so I can not even change the boot sequence.
It requires : Second Level Address Translation (SLAT) and (?) CPU support for VM Monitor Mode Extension - features which mine may or may not have.
 
I think some recommendations in this thread are pretty overkill. Kinda like tearing down the house because a door is squeaking. :)

@OP: I have personally a similar problem like you, but it isn't affecting my mouse, it's affecting my keyboard. It also only happens (randomly) when trying post a comment at TPU forums. Haven't noticed it somewhere else happening. The way it goes: logging in, trying to write a comment, and all keys stopped working before the first letter is drawn. ESC does nothing. Keyboard from there also doesn't work anymore in the Explorer or Windows search bar. Only the task manager can still be opened with STRG+ALT+DEL. It only happens (randomly) once a day & is fixed after reboot.

I suspect it either a Windows bug, a bug in Firefox or there is some shady thing going on on the TPU servers. The warning message from some weeks ago after login @tPU about hacked user accounts comes to my mind. Maybe the admins should have a look into it. It's pretty annoying, but I personally wouldn't pu too much into it. Reinstalling Win is too much imo. Most likely it's a Windows or Firefox
bug, which will get fixed by an update.

For the info, I am running a stock office machine, bios, OS, drivers & software up to date. No fancy mods.

Rig: LENOVO M700 Tiny
Keyboard: TurtleBeach Impact 500 (stock Windows drivers)
OS: Win10 Pro (20H2) x64
Kaspersky AV: no detections
MBam: no detections
Spybot: no detections
Browser: Firefox (89.0 / x64)
 
I think some recommendations in this thread are pretty overkill. Kinda like tearing down the house because a door is squeaking. :)

@OP: I have personally a similar problem like you, but it isn't affecting my mouse, it's affecting my keyboard. It also only happens (randomly) when trying post a comment at TPU forums. Haven't noticed it somewhere else happening. The way it goes: logging in, trying to write a comment, and all keys stopped working before the first letter is drawn. ESC does nothing. Keyboard from there also doesn't work anymore in the Explorer or Windows search bar. Only the task manager can still be opened with STRG+ALT+DEL. It only happens (randomly) once a day & is fixed after reboot.

I suspect it either a Windows bug, a bug in Firefox or there is some shady thing going on on the TPU servers. The warning message from some weeks ago after login @tPU about hacked user accounts comes to my mind. Maybe the admins should have a look into it. It's pretty annoying, but I personally wouldn't pu too much into it. Reinstalling Win is too much imo. Most likely it's a Windows or Firefox
bug, which will get fixed by an update.

For the info, I am running a stock office machine, bios, OS, drivers & software up to date. No fancy mods.

Rig: LENOVO M700 Tiny
Keyboard: TurtleBeach Impact 500 (stock Windows drivers)
OS: Win10 Pro (20H2) x64
Kaspersky AV: no detections
MBam: no detections
Spybot: no detections
Browser: Firefox (89.0 / x64)
Did you try disabling hardware acceleration in firefox?...

this setting..
View attachment disable-hardware-acceleration-in-Firefox-and-Chrome.webp
 
The only time I have ever seen this , and more than once is with memory clocked high on a Ryzen system, after doing enough to heat the pc and memory up a v soft hang occurred, no input noticed by the pc etc until rebooted.
Lowering the memory solved it and I haven't had it since.
Your problems might not be this but I thought I would chime in for your consideration.
 
same here for the last 1 week...tried using .jpg and .png image files...not tried with .bmp files...will see if it works or not..
 
A number of posts have appeared without me being alerted to them. I can not follow their content.
There is a suggestion to do something about Firefox - I think that would be more relevant if the problem occurred in Firefox, but I do NOT think that is the case.
There is also the suggestion to lower the RAM. This x32 system is limited to using 4Gb, but I do have 14Gb installed, as I also run the x64 system occasionally.
 
Back
Top