Numlock keeps coming back on all of the time

[Yousuf Khan[_2_]]

My laptop's numlock key keeps getting reactivated whenever it reawakens
from sleep or from a reboot. It's annoying, where can I change that
behaviour? Obviously that never happened under Windows 7.

Yousuf Khan

[Mike Swift]

In article >, Yousuf Khan
> writes
>My laptop's numlock key keeps getting reactivated whenever it reawakens
>from sleep or from a reboot. It's annoying, where can I change that
>behaviour? Obviously that never happened under Windows 7.

I'm getting similar, mine is switched off randomly when I fire up the
computer so I can't enter my pin to log in until I switch the number
lock on, no great deal, just annoying.

Mike

--
Michael Swift We do not regard Englishmen as foreigners.
Kirkheaton We look on them only as rather mad Norwegians.
Yorkshire Halvard Lange

[. . .winston[_2_]]

Yousuf Khan wrote on 08/18/2015 3:02 PM:
> My laptop's numlock key keeps getting reactivated whenever it reawakens
> from sleep or from a reboot. It's annoying, where can I change that
> behaviour? Obviously that never happened under Windows 7.
>
> Yousuf Khan

I had the opposite occur on the Win10 Insider Build (the latest and prior)
- Numlock while enabled in the BIOS/UEFI was off when reaching the
Desktop user profile. Eventually, the symptom disappeared.


--
...winston
msft mvp windows experience

[Yousuf Khan[_2_]]

On 18/08/2015 7:25 PM, Mike Swift wrote:
> In article >, Yousuf Khan
> > writes
>> My laptop's numlock key keeps getting reactivated whenever it reawakens
>> from sleep or from a reboot. It's annoying, where can I change that
>> behaviour? Obviously that never happened under Windows 7.
>
> I'm getting similar, mine is switched off randomly when I fire up the
> computer so I can't enter my pin to log in until I switch the number
> lock on, no great deal, just annoying.

In my case, there is no specific numlock key on my laptop's keyboard, it
shares duty with one of the F-number keys (F11 in this case), and you
have to hold down the "Fn" key followed by the F11 to get it pressed.
And it's not always an easy task to find either of these keys in the
dark either. It's not a lit keyboard.

Yousuf Khan

[Yousuf Khan[_2_]]

On 18/08/2015 9:32 PM, . . .winston wrote:
> I had the opposite occur on the Win10 Insider Build (the latest and prior)
> - Numlock while enabled in the BIOS/UEFI was off when reaching the
> Desktop user profile. Eventually, the symptom disappeared.

Do you think that if the problem just went away on its own, that it
maybe a known issue with Win 10, that Microsoft simply hasn't fixed yet?
That perhaps a specific bug fix might be coming? I did install this Win
10 prematurely, I didn't wait for my "invitation" to join Win 10 to
arrive yet, I just downloaded the media and upgraded it that way. Should
I maybe go back to Win 7 and let it wait until it's ready to be upgraded
by the invitation? I've had nothing but numerous little niggling hitches
ever since installing this thing. In another thread, I mentioned having
a not working entirely proper touchpad.

Yousuf Khan

[. . .winston[_2_]]

Yousuf Khan wrote on 08/19/2015 12:42 AM:
> On 18/08/2015 9:32 PM, . . .winston wrote:
>> I had the opposite occur on the Win10 Insider Build (the latest and
>> prior)
>> - Numlock while enabled in the BIOS/UEFI was off when reaching the
>> Desktop user profile. Eventually, the symptom disappeared.
>
> Do you think that if the problem just went away on its own, that it
> maybe a known issue with Win 10, that Microsoft simply hasn't fixed yet?
> That perhaps a specific bug fix might be coming? I did install this Win
> 10 prematurely, I didn't wait for my "invitation" to join Win 10 to
> arrive yet, I just downloaded the media and upgraded it that way. Should
> I maybe go back to Win 7 and let it wait until it's ready to be upgraded
> by the invitation? I've had nothing but numerous little niggling hitches
> ever since installing this thing. In another thread, I mentioned having
> a not working entirely proper touchpad.
>
> Yousuf Khan

Don't know the answer on why it 'went away' at this time.

I initially thought it could be hardware related
- for the Insider Build device (on which it occurred is an Acer i3
Intel chip BIOS/EFI laptop) I've a replaceable identical size HD that is
running Win10 Pro on that same device. Numlock functions per its
configuration (On or Off) on each start/restart...thus the only
difference between each drive running Win10 is the HD manufacturer (WD
vs. Seagate) and the o/s (Insider 10525 vs RTM 10240).

.....but since Numlock now functions on each it doesn't appear (in my
case) to be related to Win10 RTM 10240.

The Win 10 bits when upgrading a qualifying o/s are the same no matter
how one upgrades (Windows Update or using the Win10 available media)

Windows Update (on both - Insider Build and Win10 RTM, remember same
device, different replaceable HD) both previously (circa July 29th/30th)
had a Synaptics Touch Pad driver pushed down via Windows Update.



--
...winston
msft mvp windows experience

[A.M]

On 2015-08-18 3:02 PM, Yousuf Khan wrote:
> My laptop's numlock key keeps getting reactivated whenever it reawakens
> from sleep or from a reboot. It's annoying, where can I change that
> behaviour? Obviously that never happened under Windows 7.

What kind of keyboard?


--
A.M

Hillary for Prison 2016!!

[Yousuf Khan[_2_]]

On 19/08/2015 1:40 PM, A.M wrote:
> On 2015-08-18 3:02 PM, Yousuf Khan wrote:
>> My laptop's numlock key keeps getting reactivated whenever it reawakens
>> from sleep or from a reboot. It's annoying, where can I change that
>> behaviour? Obviously that never happened under Windows 7.
>
> What kind of keyboard?

Just a laptop keyboard. What do you mean?

Yousuf Khan

[Yousuf Khan[_2_]]

On 19/08/2015 1:44 AM, . . .winston wrote:
> ....but since Numlock now functions on each it doesn't appear (in my
> case) to be related to Win10 RTM 10240.
>
> The Win 10 bits when upgrading a qualifying o/s are the same no matter
> how one upgrades (Windows Update or using the Win10 available media)
>
> Windows Update (on both - Insider Build and Win10 RTM, remember same
> device, different replaceable HD) both previously (circa July 29th/30th)
> had a Synaptics Touch Pad driver pushed down via Windows Update.

I'm also having a problem with a Synaptics touchpad driver. I've now
reverted back to Win 7 on the laptop, but I'm wondering if I had removed
the existing Synaptics driver, then would Win 10 have installed its own
version? Synaptics seems to have way too many versions of its driver
floating around. Each OEM seems to have their own custom versions of it,
but they don't seem to do anything different from each other. Why not
just standardize on one Synaptics version?

Yousuf Khan

[. . .winston[_2_]]

Yousuf Khan wrote on 08/20/2015 10:59 AM:
> On 19/08/2015 1:44 AM, . . .winston wrote:
>> ....but since Numlock now functions on each it doesn't appear (in my
>> case) to be related to Win10 RTM 10240.
>>
>> The Win 10 bits when upgrading a qualifying o/s are the same no matter
>> how one upgrades (Windows Update or using the Win10 available media)
>>
>> Windows Update (on both - Insider Build and Win10 RTM, remember same
>> device, different replaceable HD) both previously (circa July 29th/30th)
>> had a Synaptics Touch Pad driver pushed down via Windows Update.
>
> I'm also having a problem with a Synaptics touchpad driver. I've now
> reverted back to Win 7 on the laptop, but I'm wondering if I had removed
> the existing Synaptics driver, then would Win 10 have installed its own
> version? Synaptics seems to have way too many versions of its driver
> floating around. Each OEM seems to have their own custom versions of it,
> but they don't seem to do anything different from each other. Why not
> just standardize on one Synaptics version?
>
> Yousuf Khan

On my device..the Synaptics driver functioned on 8.1 prior to upgrading
to 10, after installing 10, and again after installing the touch pad
driver offered in Windows Update.



--
...winston
msft mvp windows experience