Windows 10: Cursor Deletes At Random

Need help ASAP!



My cursor will disappear at random. I have searched online for assistance and saw the advice of looking into cursor settings to ensure the "hide your cursor while typing" feature was not enabled but it still happens!


This will sometimes happen in Word Doc/Excel, has happened sometimes while in Outlook....and recently started to happen at random when attempting to open folders on my drives.


I've messed with the settings before....and it will stop for awhile but then will start / stop again at random! This has been going on for months!


PLEASE HELP ME

:)

 

Is there a key to delete character ahead of the cursor?

Hello Stephen,

As of the moment, deleting the characters next to the cursor is unavailable. You can only delete characters by moving the cursor to the right side. You can always send a suggestion via Feedback Hub app so that it can be added or included on the next update.

To send a feedback on your phone, you can follow the steps below:

• Go to All Apps, search for the Feedback
  Hub app.
• Open the menu icon at the top left side.
• Select Feedback, then at the top right side, tap the
  add button (+).
• Select Suggestion and fill up the box with the details of the feature you want to be added on Windows phone.
• Select the right category for the suggestion and then submit.

Should you need more help, feel free to ask the Community.

 

cursor dissappeared

Thank you both for your prompt replies, I tried all steps listed, some I had tries previously but I still tried them again, but still no cursor.

Do you have any other suggestions?

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.