toggle quoted messageShow quoted text
Not having a go at you Ian, but just in general can people please not say things like: "Windows 10 machine with the latest build Windows 10". It's really not as helpful as it seems. My computer refused to do updates for about six months last year - it was just a glitch, but it never gave me an error message unless I looked on the update screen - I could easily have assumed I had "the latest build", when it fact I could have been two major versions behind. Also Microsoft release different builds to different users - with their major builds they stagger them so it can take three months before it is rolled out around the world, no matter how many times a particular use hits "check for updates". Even then, because of various things including the exact hardware your machine has, or even a feature Microsoft want to roll out to half the users, they might roll out a major build but two slightly different versions with it being completely random who gets one and who gets the other. That is why I ask for the specific build number - in general but also in this case. If this is a bug which has crept back into Windows, even just practically, we can't go to Microsoft and say "a user has reported it in the latest build" - they'll need to know the exact build - and even before that - if other users come forward and say they can replicate it and they're all on the same build, and other users can't and they're on a newer build, it's likely it's been fixed (or conversely if they're all on older builds, it's likely it's a new bug crept in) - and all of those users might be on "the latest build" (they can get).
Again, not picking on you or anyone, just trying to explain why it is really very helpful if you could please provide which build number you are using when reporting something (and the more the better - if it's a problem you're having opening a document in Word, then the version of Windows, NVDA and Office could all be useful).
I get this on my Windows 10 machine with the latest build Windows 10 but the solution is to press any key are you just press the enter key and then your password box shows up mind you I have two accounts on my machine
And I see this is normal behaviour as I think but I can’t see it but I think the screen shows the date when you beat the machine then you have to click somewhere and that gives you your logon screens as I can’t see I can’t give you the exact reason but it’s been happening ever since I’ve had Windows 10 I don’t see it as a problem as it’s more a quirk of the operating system I mean you’ve got it least it talking to you solution press enter and then go ahead regards Ian
On 12 Jan 2021, at 2:24 pm, Quentin Christensen <quentin@...
Which build of Windows are you using? We saw this issue a couple of years ago, but I hadn't heard of it happening recently.
You can get your build by opening "winver" - press the windows key, type winver and press enter.
What's happening is your lock screen is getting in the way. Try hitting the control key or some other key, and you should get jumped into your regular login screen.
----- Original Message -----
From: "Bob Cavanaugh" <cavbob1993@...>
Date: Mon, 11 Jan 2021 21:54:15 -0800
Subject: [nvda] possible issue with NVDA on the Windows 10 log-on screen
> Hi everyone,
> I'm not sure what's causing this, but there seems to be an intermitant
> issue with NVDA on the log-on screen of Windows 10. Yesterday was a
> frustrating morning for me computer-wise, requiring several restarts.
> After one such restart, NVDA just kept speaking the first letter of my
> password after typing it several times. Usually it speaks that letter
> once, then the password box comes up and I can type normally. Why the
> log-on screen behaves this way I'm not sure, but it's something I've
> gotten used to having Windows 10 for 3 and a half years. Once in a
> while however, NVDA doesn't want to focus on anything on the log-on
> screen. I tab around and it doesn't speak. So, I fire up Narrator,
> which usually causes both screen readers to speak at the same time,
> and from then on NVDA also works properly. I'm not sure if there's
> anything the developers can do to track this down and fix it, but if
> there is I'd like to see it done.
Training and Support Manager
Training and Support Manager