Hmmm my issue was with the current stable, but things work as expected now. It could be a cert issue and I do have the latest windows 10 updates including optionals, chrome, and edge,

Well maybe its propergation of the new certs. Not only does it still work but updates for nvda and nvda addons work now. So you may have to wait for things to update themselves.

I move we hold Joseph hostage. I'm joking of corse. He rocks! Wow! Happy Friday all. Sarah Alawami, owner of TFFP. . For more info go to our website. . to subscribe to the feed click here Our

Hi, The root cause was discovered by Lukasz Golonka in August 2021 - it turns out NVDA was assuming the internals of certificate related errors was the same between Python 2 and 3 when in fact it

Joseph: Your solution worked perfectly. Now, I need to go around and update all of my NVDA installations. I have several so it will take a while. I don't know about the rest of the

Yup. Unfortunately, still the same thing happening here. Running windows 10 with NVDA version 2021.2.

That worked perfectly for me.

Hi all, A possible workaround found: looks like it might be indeed NVDA. The following suggested workaround is applicable for NVDA 2021.2 or older and/or if you are running alpha snapshots released

Neither the update addon's under the tool menu of the NVDA UI nor the check for updates under the help menu work for me on my Win 10 system running latest version of NVDA.

Hi all, According to an NVDA code contributor, this issue should be resolved in alpha builds (2021.3 unless NV Access decides to backport this sooner). I'll do something about this issue from Add-on

Not necessarily. When this certificate expired yesterday some sights were not affected but softwares were. I speak from experience as yesterday I was having loads of issues, luckelly not at work, at

Chris, If you happen to have a GitHub account, and could do as Joseph asked and snag logs from your machine when it's working, and add a comment and attach those, it might help. I just did this on my

Its both in the nvda help menu check for nvda update and the tools menu check for addon updates Currently I can check for both addon updates and nvda update without an error And others have

Hi, Also, if possible, please attach log fragments to the GitHub issue just created. For best results, do: See if you do receive error messages when you check for NVDA and/or add-on updates. Restart

- To the group membership: Note the above well. This is an example where adding comments to a ticket giving additional information about occurrences of this behavior will probably be pivotal to

Hi, Tracking as a major issue - I have asked add-ons community about this issue. We can't detect patterns here as it shows up on some systems but not others. Cheers, Joseph

GitHub Issue Created: Manual attempts to update NVDA, or NVDA Add-Ons, is throwing error messages -- Brian - Windows 10, 64-Bit, Version 21H1, Build 19043 Nothing in all the world is more

Greetings, I wanted to follow up to share my findings/solution to the volume reduction of the remote computer audio while using MS RDP. The local computer was detecting the communications of the MS

I’ve done more checking and I found an odd thing. I have recent portable copies of NVDA. One of them gives a proper update message when I run the updater. Another one generates the error message.

And for additional information and clarity, I am also getting an error message when I attempt to check for updates to NVDA itself from the Help submenu. But, the error messages are distinct for each