Skip to content

Settings and activity

11 results found

  1. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    I'm unsure about versions preceding last current one v24.002.20687 I've started re-using again, but as of now inside Acrobat Reader DC MUI Preferences -> Documents there's a 'Remember last state of the All Tools pane when opening documents' that works fine and since after I enabled it allowed me to avoid seeing that pane every time I open Acrobat Reader DC.

  2. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    I'm unsure about versions preceding last current one v24.002.20687 I've started re-using again, but as of now inside Acrobat Reader DC MUI Preferences -> Documents there's a 'Remember last state of the All Tools pane when opening documents' that works fine and since after I enabled it allowed me to avoid seeing that pane every time I open Acrobat Reader DC.

  3. 21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    I'm unsure about versions preceding last current one v24.002.20687 that I've started re-using again, but as of now inside Acrobat Reader DC MUI Preferences -> Documents there's a 'Remember last state of the All Tools pane when opening documents' that works fine and since after I enabled it allowed me to avoid seeing that pane every time I open Acrobat Reader DC.

  4. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    I'm unsure about versions preceding last current one v24.002.20687 I've started re-using again, but as of now inside Acrobat Reader DC MUI Preferences -> Documents there's a 'Remember last state of the All Tools pane when opening documents' that works fine and since after I enabled it allowed me to avoid seeing that pane every time I open Acrobat Reader DC.

  5. 24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    I'm unsure about versions preceding last current one v24.002.20687 I've started re-using again, but as of now inside Acrobat Reader DC MUI Preferences -> Documents there's a 'Remember last state of the All Tools pane when opening documents' that works fine and since after I enabled it allowed me to avoid seeing that pane every time I open Acrobat Reader DC.

  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rob Mer commented  · 

    As of now inside Adobe own technical article 'Print PDFs' <https://helpx.adobe.com/reader/using/print-pdfs.html> this paragraph clearly explains that:
    "The printer driver controls the options, not Adobe Acrobat or Adobe Reader. Check your printer documentation to see what features your printer supports."
    And also additional "Note: There could be a scenario when a printer actually supports duplex printing and this option does not appear in the Print dialog box. In such cases, open the printer properties to directly access this option from printer preferences."
    So chances are that lost option for duplex printing might just have depended from last update in same printer driver, or rather that user might have even been unable to notice/verify that default printer was no more same one used in the past. Theoretically if considered printer was a network one that was changed recently, he would have simply received automatically new driver on his client and maybe a logon script might have even set such new printer as default without his proper awareness.

  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer shared this idea  · 
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer shared this idea  · 
  9. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rob Mer commented  · 

    After some more investigation I also did for another bug I've commented, I've also been able to verify that current Adobe technical article I've initially considered as a knowledgeable reference indeed contains partially invalid details. On my client Adobe Acrobat Reader was initially installed from its OEM (Dell) and so I guess they used some Adobe own approved setup method. During years I constantly continued to upgrade it until Reader XI MUI, that I later upgraded to Acrobat Reader DC v15.023.20070, then immediately to v17.009.20044 and then, sometime later, to v18.011.20055 and since its version continued to upgrade until current v24.002.20687 I believe that Adobe article "Acrobat Reader migration to 64-bit" needs more corrections because since registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Installer\ do not exist, it doesn't even consider that Acrobat Reader DC MUI (32bit) when installed on an x64 bit OS will instead just use a very different registry key path (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\DC\Installer\) that I correctly found and that is populated with lot of registry values but not with 'SCAPackageLevel' that is described in above mentioned technical article and does not even exists.
    This also confirms that error described into this bug should also not be related with missing registry keys (a doubt I had since I verified that my OS registry was missing completely missing HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ registry key path, so above mentioned errors may not be caused from an unexplicable deletion that indeed never happened. 0:-)

    An error occurred while saving the comment
    Rob Mer commented  · 

    Update: After manually restarting BITS service and 'Adobe Acrobat Update Service' (=AdobeARMservice, so armsvc.exe) once more I awaited for next scheduled run to see if anything changed. But, unfortunately same issue continued again (see effects in AdobeARM_207ter.log as always from %SystemRoot%\Temp), so I decided to see if activating a manual update from within Adobe Reader DC could work.
    And this time update started correctly and then completed fine (see contents of AdobeARM_208bis.log at the end where it's possible to see that this time '... Command Line: ...' line is indeed not empty and with all needed arguments so I hope all this really helped to avoid past errors I described in previous posts).

    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    After some more investigations I did on my client (also from same AdobeARM_196.log I already uploaded) I found that both same "NtReadVirtualMemory unicode_path failed, error: -2147483635" (corresponding to 0xFFFFFFFF8000000d) and also "NtReadVirtualMemory read_peb failed, error: -1073741790" (corresponding to 0xFFFFFFFFc0000022) were also temporarily only experienced on 3/28 right during last upgrade to Acrobat Reader v24.001.20629 that I still have and then also on 04/03 that I thought was 1st earlier evidence.
    Now according to Bing Copilot additional help I decided to ask for, both error messages correspond to constant STATUS_ACCESS_DENIED in Windows OS but for current AdobeARM.exe v1.824.460.1067 main problem is that when currently finding 1st error (more frequent) or 2nd one (less frequent) is now not really adding into own log more additional details that might better help an end user really figure out or understand why they're being logged.
    So, I would really hope that a next ARM release in future might better be able to log more conditions about own status when both situations may happen again so to possibly help an end user like me, or even Adobe yourself (because I also saw that you do seem to often self-get back a copy of my logs when "Command Line: /ArmElevate /CollectFiles /Svc /USER:<myAlias> /SESSIONID:1").
    P.S. May all this be anyhow related to AdobeARM.exe only starting with an empty "Command Line: " but anyway "Using registered preference AUTO_ALL", or even with some other unclear situation related to BITS service own status that is used by AdobeARM when downloading own files ?
    I'm saying this because in the past, right before upgrade to Acrobat Reader v24.001.20629 really succeeded I noticed some other BITS related errors (also from AdobeARM_196.log I included before) which I tried to possibly solve by manually forcing BITS to restart before next scheduled AdobeARM occurrence was going to take place:
    "...
    [2024-03-28 19:36:40:0400] ARMDownloader:: BITS_Job GetError() error: -2145386481
    [2024-03-28 19:36:40:0400] ARMDownloader:: BG_JOB_STATE_CONNECTING: errorCount1
    [2024-03-28 19:36:40:0450] all BITs attempts failed
    [2024-03-28 19:36:40:0450] Error Code: -2145386481
    [2024-03-28 19:36:40:0450] ** Setting Error Condition: 140000
    [2024-03-28 19:36:40:0913] BITs failed, download manifest Job is not in Transferred state
    [2024-03-28 19:36:48:0591] valid after BB download: C:\Users\<myAlias>\AppData\Local\Adobe\ARM\S\ArmManifest3.msi
    [2024-03-28 19:36:48:0697] Newer version ARM update is not available
    ..."

    An error occurred while saving the comment
    Rob Mer commented  · 

    Because after some more investigation I was also able to find all downloaded files already reported initially into C:\ProgramData\Adobe\ARM\Reader_24.001.20629 folder, my next step now will be to soon try to manually execute AcroRdrDCUpd2400120643_MUI_incr.msp and then AcroRdrDCUpd2400220687_MUI.msp only to see if manual installation complete correctly (but because I'm unsure what ReaderDCManifest3.msi may do and yesterday I found no reference details on it).

    An error occurred while saving the comment
    Rob Mer commented  · 

    As you can see from initially enclosed AdobeARM.log issue seems to have started on 04/05 and I casually noticed it because I saw that AdobeARM.exe was remaining in memory more time that expected. But in reality, this issue indeed started on 04/03 as you can see from a previous copy of same file I had saved on same day and before AdobeARM.log on 04/05 even reset his size after it had grown too much (reaching 3.57MiB).

    Rob Mer shared this idea  · 
  10. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rob Mer commented  · 

    After more investigation I've been able to do I verified that current Adobe technical article I've initially considered as a knowledgeable reference indeed contains partially invalid details. On my client Adobe Acrobat Reader was initially installed from its OEM (Dell) and so I guess they used some Adobe own approved setup method. During years I constantly continued to upgrade it until Reader XI MUI, that I later upgraded to Acrobat Reader DC v15.023.20070, then immediately to v17.009.20044 and then, sometime later, to v18.011.20055 and since its version continued to upgrade until current v24.002.20687 I believe that Adobe article "Acrobat Reader migration to 64-bit" needs more corrections because since registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Installer\ do not exist, it doesn't even consider that Acrobat Reader DC MUI (32bit) when installed on an x64 bit OS will instead just use a very different registry key path (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\DC\Installer\) that I correctly found and that is populated with lot of registry values but not with 'SCAPackageLevel' that is described in above mentioned technical article and does not even exists.

    An error occurred while saving the comment
    Rob Mer commented  · 

    Because of additional investigations I also did for another bug I opened some days ago, so through another technical article 'Acrobat Reader migration to 64-bit' <https://helpx.adobe.com/acrobat/kb/about-acrobat-reader-dc-migration-to-64-bit.html>, and more specifically because of 'How to identify if Acrobat 64-bit or Acrobat Reader 64-bit is installed' section contents, I've learned that presence of one of those applications can be easily detected via a dedicated Registry key value 'SCAPackageLevel' to be found into following registry path HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Installer\ .
    Because of this it is very likely that at least 2 other similar and very specific registry key values should also probably already exist to also quickly indicate presence of Adobe Acrobat (32bit) rather than Adobe Acrobat Reader (32bit) and also of its currently installed version number.
    And basically, it also seems that if for any unexpected reason, it's impossible to read contents of such involved registry key values indicating presence of Adobe Acrobat (32bit) rather than Adobe Acrobat Reader (32bit) and/or also of its currently installed version, then proper installation of 'Adobe Reader Extended Asian Language Font Pack' v23.008.20421 (32bit) via FontPack2300820421XtdAlfLang_DC.msi file will just fail with above reported error message.
    And this is what has happened on my laptop where unfortunately today , I've been able to verify that registry path and key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ currently exists no more for unexpected and unclear reasons.
    Nevertheless I do have Adobe Acrobat Reader DC MUI v24.001.20629 already installed on my laptop with Windows 7 SP1 x64 Ultimate and only earlier this morning I was able to manually update it to what should be latest/current v24.002.20687 (if interested to find additional details on other related difficulties that I've also already experienced during such upgrade process then pls also just see the other bug I opened <https://acrobat.uservoice.com/forums/926812-acrobat-reader-for-windows-and-mac/suggestions/48247154-bug-adobearm-v1-824-460-1067-getting-stuck-in-mem>).
    Now, back to this issue, while it can obviously be difficult to understand how, when and why HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ registry key may have disappeared it is also true that 'Adobe Acrobat Reader MUI' installation presence was also already detectable via HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-FFFF-7B44-AC0F074E4100} registry path and via 'DisplayName' containing 'Adobe Acrobat Reader MUI' string and 'DisplayVersion' (both REG_SZ) containing '24.002.20687' string.
    And similarly, obviously if needed, previous presence of 'Extended Asian Language font pack for Adobe Acrobat Reader DC' (from 'DisplayName' REG_SZ value) and '15.007.20033' (from 'DisplayVersion' REG_SZ value) might have been verified via registry path HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-2530-0000-AC0F074E4100} , together with 'Spelling Dictionaries Support For Adobe Acrobat Reader DC' (into 'DisplayName' REG_SZ value) and '15.007.20033' (from 'DisplayVersion' REG_SZ value) via registry path HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-5464-3428-AC0F074E4100}.

    Rob Mer shared this idea  · 
  11. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rob Mer supported this idea  · 
    An error occurred while saving the comment
    Rob Mer commented  · 

    FWIW since ITMT multiple installers have already been made available from Adobe site <https://helpx.adobe.com/acrobat/kb/windows-font-packs-32-bit-reader.html> then maybe this entry might even be definitely closed ...
    P.S. Also, since this user now appears as 'Anonymous' chances are that he/she may even already self-solved this issue time ago, before or after deciding to delete own profile from here and even using one of those more updated installers (that I also believe have already been released from quite some time, for instance I've even been able to check that article was 1st published in February 2021 ;-) ).