adobe reader 64 bit does not work with NVDA


enes sarıbaş
 

Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?


enes sarıbaş
 

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156

On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?


Christopher Duffley
 

Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







enes sarıbaş
 

Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







Christopher Duffley
 

OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







enes sarıbaş
 

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







Gene
 

This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
 
Gene

-----Original Message-----
Sent: Thursday, October 07, 2021 9:56 AM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.
 
Thanks,
 
Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971
 
12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş mailto:enes.saribas@... wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?
 
Thanks,
 
Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971
 
12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş mailto:enes.saribas@... wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







Rui Fontes
 

Downgrading, I don't believe...

But, you can remove the 64-bit version and install the 32-bit version.


It gaves always an error when starting, but it works...


Rui Fontes


Às 15:56 de 07/10/2021, enes sarıbaş escreveu:

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?







 

On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit), Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit), 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


enes sarıbaş
 

Hi Brian,

I very much went against this advice, and installed 64 bit versions of file compression, format conversion, and office software etc.Even browsers, I was one of the early upgraders to Firefox 64 bit. Until Reader 64 bit, I had no issues whatsoever with 64 bit software.  Nor did I see any advice with Mozilla, Microsoft etc against choosing a 64 bit version.


On 10/7/2021 7:29 PM, Brian Vogel wrote:
On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit), Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit), 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Gene
 

In the early days of 64 bit Firefox, I don’t recall hearing about performance problems with the browser, but there were not many 64 bit add-ons so switching meant that you were losing one of the important reasons a lot of people used Firefox.
 
Gene

-----Original Message-----
Sent: Thursday, October 07, 2021 1:01 PM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 

Hi Brian,

I very much went against this advice, and installed 64 bit versions of file compression, format conversion, and office software etc.Even browsers, I was one of the early upgraders to Firefox 64 bit. Until Reader 64 bit, I had no issues whatsoever with 64 bit software.  Nor did I see any advice with Mozilla, Microsoft etc against choosing a 64 bit version.

 

On 10/7/2021 7:29 PM, Brian Vogel wrote:
On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11.
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit), Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit), 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


 

enes,

       I can say, with absolute certainty, that at one point (probably in the past) Microsoft explicitly instructed to use the 32-bit version of Office unless you needed something that could not be had without the 64-bit.

        But, my statement is about what we techs "on the ground" routinely advise, particularly after an issue has reared its ugly head with a 64-bit version of anything.  For lots of stuff I still just install the 32-bit because it's the "most focused upon" in the development cycles at the moment.  That's definitely going to change, and I wish it had changed ages ago, but there has always been a need to keep the 32-bit stuff "in tip top shape" since it can run under a 32-bit and 64-bit version of Windows.

        There's lots of 64-bit software, I'd say most of it, that you won't have a single, solitary problem with.  But if you are, or suspect you might based upon reports such as those made in this topic, and a 32-bit version exists, then nuke the 64-bit install and then install the 32-bit version.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


enes sarıbaş
 

Hi Brian,

Going 64 bit is really benefitial for certain types of software, for example file compression software, antiviruses etc that use lots of memory and CPU cycles.  I will get around to nuking 64 bit reader, but I wish it had worked especially since Quentin on this list earlier had said he had no issues.

On 10/7/2021 9:49 PM, Brian Vogel wrote:
enes,

       I can say, with absolute certainty, that at one point (probably in the past) Microsoft explicitly instructed to use the 32-bit version of Office unless you needed something that could not be had without the 64-bit.

        But, my statement is about what we techs "on the ground" routinely advise, particularly after an issue has reared its ugly head with a 64-bit version of anything.  For lots of stuff I still just install the 32-bit because it's the "most focused upon" in the development cycles at the moment.  That's definitely going to change, and I wish it had changed ages ago, but there has always been a need to keep the 32-bit stuff "in tip top shape" since it can run under a 32-bit and 64-bit version of Windows.

        There's lots of 64-bit software, I'd say most of it, that you won't have a single, solitary problem with.  But if you are, or suspect you might based upon reports such as those made in this topic, and a 32-bit version exists, then nuke the 64-bit install and then install the 32-bit version.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


benmoxey@...
 

Hi Enes

 

I typically always install 64 bit versions of Apps when available with no problem, but have noticed some stability issues with Adobe Reader DC 64 and NVDA. I run the 32 bit version on my work machine and it’s smooth sailing.

 

If you want to try the 32 bit version and see if it resolves your issue, remove your current install and download the 32 bit version from the below link. This page will let you choose, rather than Adobe detecting your system and automatically giving you the 64 bit option. Choose the version that simply states it’s “for Windows”. This is the 32 bit one you want.

 

Adobe Acrobat Reader DC Install for all versions

 

Interested to know if others have noticed instability with the 64 bit version.

 

All the best.

 

Ben

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of enes saribas
Sent: Friday, 8 October 2021 1:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA

 

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:

OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

 

Thanks,

 

Christopher Duffley

Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com

Cell: +1 (603) 851-6971

 

12 Pro Max


On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:

Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

 

Thanks,

 

Christopher Duffley

Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com

Cell: +1 (603) 851-6971

 

12 Pro Max


On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:

Hi all,

 

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?

 






 

I did once but who knows.

Adobe reader just updated again.

Sadly it seems adobe reader likes to update itself you may if you root about can get a 32 bit adobe reader but yeah its done this before.

For a while its been ok.

Still is ok.

This is  what you may want to do.

1.  open the document then imediately alt tab away, do it again.

Wait till its finnished processing.

push up arrow, it should ding.

Hit alt tab again, and keep doing that till the document appears.

Now this will work with online documents, but I have had documents which just don't work so well due to how they are constructed.

For those I use balabolka but they can run together.

In general any coded web documents do not crash and most documents should be ok but yeah there are issues some times.

On 8/10/2021 1:05 am, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?





.


Gene
 

I really like using browsers for PDF documents.  I can’t comment in general; I mostly use Edge but other browsers may work well.  Edge opens documents much faster than Adobe.  I don’t read PDF documents much but from the little I do, it seems to me that Edge usually renders them as well as Adobe.
 
Gene

-----Original Message-----
Sent: Thursday, October 07, 2021 10:30 PM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 
I did once but who knows.

Adobe reader just updated again.

Sadly it seems adobe reader likes to update itself you may if you root
about can get a 32 bit adobe reader but yeah its done this before.

For a while its been ok.

Still is ok.

This is  what you may want to do.

1.  open the document then imediately alt tab away, do it again.

Wait till its finnished processing.

push up arrow, it should ding.

Hit alt tab again, and keep doing that till the document appears.

Now this will work with online documents, but I have had documents which
just don't work so well due to how they are constructed.

For those I use balabolka but they can run together.

In general any coded web documents do not crash and most documents
should be ok but yeah there are issues some times.



On 8/10/2021 1:05 am, enes sarıbaş wrote:
> Hi all,
>
> I am running latest windows 10 21h1, with NVDA latest alpha build   as
> of this writing.   Adobe reader 64 bit doesn't work at all.  When
> clicking on a document, it becomes unresponsive, and exits adobe
> reader within 30 seconds with no error message.  Is anyone else
> experiencing this?
>
>
>
>
>
>
> .





 

To be honest jean with the latest version of firefox 93.0, if I download a bunch of files or if say I go to a site like amd, then maybe another one like skype and then try to download a file the dialog will come up but firefox will crash and I have to end it.

That doesn't mean I can't complete my tasks, but its been like that since I loaded 93.


Its not uber badd as it will work to view things but it can get a bit annoying at times.

I really need to report this to mozilla.



On 8/10/2021 7:42 am, Gene wrote:
In the early days of 64 bit Firefox, I don’t recall hearing about performance problems with the browser, but there were not many 64 bit add-ons so switching meant that you were losing one of the important reasons a lot of people used Firefox.
 
Gene
-----Original Message-----
Sent: Thursday, October 07, 2021 1:01 PM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 

Hi Brian,

I very much went against this advice, and installed 64 bit versions of file compression, format conversion, and office software etc.Even browsers, I was one of the early upgraders to Firefox 64 bit. Until Reader 64 bit, I had no issues whatsoever with 64 bit software.  Nor did I see any advice with Mozilla, Microsoft etc against choosing a 64 bit version.

 

On 10/7/2021 7:29 PM, Brian Vogel wrote:
On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11.
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit), Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit), 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


tim
 

Think you guys got off the point.

He didn't say the 64 bit din't work with windows 10 it was NVDA it didn't work with.

So far with win 11 you can still run 32 bit. However, Microsoft did state that after 11 32 bit useage would be dropping off just like internet explorer. Then even NVDA will need a complete rewrite to 64 bit seeing how its only 32 bit now.

On 10/7/2021 3:34 PM, enes sarıbaş wrote:

Hi Brian,

Going 64 bit is really benefitial for certain types of software, for example file compression software, antiviruses etc that use lots of memory and CPU cycles.  I will get around to nuking 64 bit reader, but I wish it had worked especially since Quentin on this list earlier had said he had no issues.

On 10/7/2021 9:49 PM, Brian Vogel wrote:
enes,

       I can say, with absolute certainty, that at one point (probably in the past) Microsoft explicitly instructed to use the 32-bit version of Office unless you needed something that could not be had without the 64-bit.

        But, my statement is about what we techs "on the ground" routinely advise, particularly after an issue has reared its ugly head with a 64-bit version of anything.  For lots of stuff I still just install the 32-bit because it's the "most focused upon" in the development cycles at the moment.  That's definitely going to change, and I wish it had changed ages ago, but there has always been a need to keep the 32-bit stuff "in tip top shape" since it can run under a 32-bit and 64-bit version of Windows.

        There's lots of 64-bit software, I'd say most of it, that you won't have a single, solitary problem with.  But if you are, or suspect you might based upon reports such as those made in this topic, and a 32-bit version exists, then nuke the 64-bit install and then install the 32-bit version.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Sarah k Alawami
 

Have you tried launching it with narrator running only, if it crashes then this is an adobe issue and should be taken up with the company, if they even care about such things.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of enes saribas
Sent: Thursday, October 7, 2021 5:08 AM
To: nvda@nvda.groups.io; nvda@nvda.groups.io
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp,
registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build as
of this writing. Adobe reader 64 bit doesn't work at all. When
clicking on a document, it becomes unresponsive, and exits adobe
reader within 30 seconds with no error message. Is anyone else
experiencing this?


enes sarıbaş
 

I haven't trie that, but I am 100% sure it is an NVDA issue, due to the log I posted, and NVDA causing app to exit.

On 10/8/2021 6:50 PM, Sarah k Alawami wrote:
Have you tried launching it with narrator running only, if it crashes then this is an adobe issue and should be taken up with the company, if they even care about such things.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of enes saribas
Sent: Thursday, October 7, 2021 5:08 AM
To: nvda@nvda.groups.io; nvda@nvda.groups.io
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp,
registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build as
of this writing. Adobe reader 64 bit doesn't work at all. When
clicking on a document, it becomes unresponsive, and exits adobe
reader within 30 seconds with no error message. Is anyone else
experiencing this?