F5F Stay Refreshed Software Operating Systems Screen display and magnification tools appear repeatedly on Windows 10

Screen display and magnification tools appear repeatedly on Windows 10

Screen display and magnification tools appear repeatedly on Windows 10

T
theboodboody
Junior Member
47
03-22-2016, 03:05 AM
#1
Previously, while away from my computer, my brother accessed accessibility options on the lock screen, which included the magnifier, onscreen keyboard, and narrator. These features appeared repeatedly during boot, login, and when prompts asked for confirmation to make changes. I was able to prevent the narrator from opening but couldn't stop the onscreen keyboard or magnifier, even though I increased the magnification to 100%. This behavior has persisted for roughly a month. Anyone know the cause or how to resolve it?
T
theboodboody
03-22-2016, 03:05 AM #1

Previously, while away from my computer, my brother accessed accessibility options on the lock screen, which included the magnifier, onscreen keyboard, and narrator. These features appeared repeatedly during boot, login, and when prompts asked for confirmation to make changes. I was able to prevent the narrator from opening but couldn't stop the onscreen keyboard or magnifier, even though I increased the magnification to 100%. This behavior has persisted for roughly a month. Anyone know the cause or how to resolve it?

S
swaggy_sandy10
Junior Member
2
03-25-2016, 06:28 PM
#2
Check the Control Panel (Ease of Access Center) and see if anything is enabled.
S
swaggy_sandy10
03-25-2016, 06:28 PM #2

Check the Control Panel (Ease of Access Center) and see if anything is enabled.

I
Its_Mizz
Member
55
04-01-2016, 09:14 AM
#3
Settings>Ease of Access>Narrator>Disable "Narrator" and "Start Narrator Completely".
Settings>Ease of Access>Magnifier>Disable "Turn on Magnifier".
I
Its_Mizz
04-01-2016, 09:14 AM #3

Settings>Ease of Access>Narrator>Disable "Narrator" and "Start Narrator Completely".
Settings>Ease of Access>Magnifier>Disable "Turn on Magnifier".

X
57
04-01-2016, 09:44 AM
#4
I’ve completed that task. Nothing is set up to suggest they will act this way.
X
XxExotic_PvPxX
04-01-2016, 09:44 AM #4

I’ve completed that task. Nothing is set up to suggest they will act this way.

W
Woody_JuX
Member
130
04-03-2016, 02:48 AM
#5
I addressed the narrator issue previously; I believe that was my approach. Now I’ve stopped the magnifier from activating, though the keyboard remains the main problem, with its settings quite restricted.
W
Woody_JuX
04-03-2016, 02:48 AM #5

I addressed the narrator issue previously; I believe that was my approach. Now I’ve stopped the magnifier from activating, though the keyboard remains the main problem, with its settings quite restricted.

S
sweetkitty101
Junior Member
15
04-03-2016, 07:04 AM
#6
Try to outdo your sibling and get him to reinstall everything. Those adjustments likely restored the previous state.
S
sweetkitty101
04-03-2016, 07:04 AM #6

Try to outdo your sibling and get him to reinstall everything. Those adjustments likely restored the previous state.

S
sst04
Member
208
04-03-2016, 05:53 PM
#7
Tomorrow I’ll start a Win10VM and explore what I can discover
S
sst04
04-03-2016, 05:53 PM #7

Tomorrow I’ll start a Win10VM and explore what I can discover

P
PeterTopp
Junior Member
1
04-04-2016, 06:00 PM
#8
I understand, I’ve adjusted the setup so the keyboard appears only when needed, but it’s still not working as expected. With around 500GB of games and files, I don’t want to risk losing everything by reinstalling everything due to a simple keyboard issue.
P
PeterTopp
04-04-2016, 06:00 PM #8

I understand, I’ve adjusted the setup so the keyboard appears only when needed, but it’s still not working as expected. With around 500GB of games and files, I don’t want to risk losing everything by reinstalling everything due to a simple keyboard issue.

K
KR4TOS
Member
193
04-07-2016, 07:14 PM
#9
I understand your point. It's unclear what your brother did, but the VM acted as expected, sorry...
K
KR4TOS
04-07-2016, 07:14 PM #9

I understand your point. It's unclear what your brother did, but the VM acted as expected, sorry...