Well I seemed to recall this was the case for an earlier reporter and was

just trying to find some common denominator. Could it be somehow related,

but who knows. Otherwise as nothing has changed could the mismatch of not

selected in the temp copy mean that it gets configured when setting it up to

use the same shortcut and copies the settings incorrectly somewhere?

Brian

bglists@...

Sent via blueyonder.

Please address personal email to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

----- Original Message -----

From: "Chris" <chrismedley@...>

To: <nvda@nvda.groups.io>

Sent: Thursday, November 30, 2017 11:45 AM

Subject: Re: [nvda] installing 2017-4 RC3

This happened to me when i installed rc2

And i use caps lock as the nvda key along with insert

But i don’t see the significance of this though

From: Brian's Mail list account via Groups.Io

Sent: 30 November 2017 10:23

To: nvda@nvda.groups.io

Subject: Re: [nvda] installing 2017-4 RC3

As a matter of interest do you use caps lock as the nvda key?

Brian

bglists@...

Sent via blueyonder.

Please address personal email to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

----- Original Message -----

From: "Don H" <lmddh50@...>

To: <nvda@nvda.groups.io>

Sent: Thursday, November 30, 2017 1:00 AM

Subject: [nvda] installing 2017-4 RC3

> Used the check for updates under the help of the NVDA UI.  Installed RC 3

> over RC2.  For some reason during the update the Windows 10 settings

> screen opened and was showing the settings for Narrator.  Never seen this

> happen before.  Doesn't seem to have caused any issues with the update

> just strange that it happened.

> 

> 

> 

>