toggle quoted messageShow quoted text
Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:
- Restart with all add-ons disabled.
- Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.
If OneCore comes up, restart NVDA with partial add-on functionality. To do so:
- Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
- Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
- After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
- As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
- To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.
If this does not help, reinstall NVDA from scratch.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Gary Metzler
Sent: Thursday, November 28, 2019 8:58 AM
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
When I press nvda shift plus 6 it says windows 8 64 bit. I hope this helps.
You may need to manually type these lines into Python Console.
Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version.
What I did was copy and paste the lines just as Joseph typed them.
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."
On 2019-11-28 10:23 AM, Gary Metzler wrote:
After I enter each line I get the error win version not defined.
I hope this helps.
Hmmm, you get “False” when you’ve got 1909… Let’s try this method:
- Go back to Python Console (Control+NVDA+Z).
- Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):
NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.
I did what you suggested and I get a false response.
That’s strange. Let’s try:
- Open Python Console (Control+NVDA+Z).
- Type the following as exactly as I tell you:
Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.
I got the add on manually but, when I went to install it it said I was using an older version of windows.
Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.
I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.
I’m sorry to say I am getting the error not compatible with this version of windows. I am using windows 10 1909 and the latest nvda.
In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.
A few important notes:
- Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
- A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.