- or
No existing idea results
- ~ No ideas found ~
2789 results found
-
Error algoritmo de firma en Adobe Reader y macOS con claves mixtas en la jerarquía de certificados
Error en Adobe Reader en macOS con el algoritmo de firma cuando el certificado tiene una clave distinta al de la CA emisora.
Adobe Reader en macOS cuando realiza una firma digital está seleccionando el algoritmo desde el campo del certificado "Signature Algorithm", este campo no se corresponde con la clave del certificado cuando la CA emisora tiene un clave diferente al del certificado emitido. Esto provoca que se solicite una firma de forma errónea, por ejemplo, que se solicite una firma ECDSA con un certificado con clave RSA.
La manera de reproducir este error, es disponer de un certificado para firmar con clave RSA emitido por una CA con clave EC cuya firma del certificado se ha realizado con el algoritmo ECDSA e intentar firmar en Adobe Reader en macOS con el certificado con clave RSA.
También se reproduce con algoritmos intercambiados, esto es, emitir un certificado con clave EC firmado por una CA con clave RSA.
En cualquiera de los dos casos Adobe solicita el algoritmo de firma basándose en la firma del certificado que no se corresponde con la clave del certificado y por tanto provocando un error en cualquier proveedor criptográfico que se esté usando.
Error en Adobe Reader en macOS con el algoritmo de firma cuando el certificado tiene una clave distinta al de la CA emisora.
Adobe Reader en macOS cuando realiza una firma digital está seleccionando el algoritmo desde el campo del certificado "Signature Algorithm", este campo no se corresponde con la clave del certificado cuando la CA emisora tiene un clave diferente al del certificado emitido. Esto provoca que se solicite una firma de forma errónea, por ejemplo, que se solicite una firma ECDSA con un certificado con clave RSA.
La manera de reproducir este error, es disponer de un certificado…
1 vote -
Move "Digitally Sign" (Certificates) to the top level of the side menu
Hello,
Currently, digitally signing a PDF document using a digital certificate in the new Adobe Acrobat Reader interface requires too many clicks (4 clicks in total):
Scroll down the left/right panel.
Click "View more".
Click "Use a certificate".
Click "Digitally sign".
As a frequent user who signs dozens of documents daily, this workflow is highly inefficient.
Feature Request:
Please bring the "Digitally Sign" or "Use a certificate" tool directly to the top-level tools panel (right or left sidebar) by default, as high as possible. This will allow users to initiate the digital signing process with just 1 click immediately after opening the document.
Thank you for considering this improvement to save time for all users.Hello,
Currently, digitally signing a PDF document using a digital certificate in the new Adobe Acrobat Reader interface requires too many clicks (4 clicks in total):
Scroll down the left/right panel.
Click "View more".
Click "Use a certificate".
Click "Digitally sign".
As a frequent user who signs dozens of documents daily, this workflow is highly inefficient.
Feature Request:
Please bring the "Digitally Sign" or "Use a certificate" tool directly to the top-level tools panel (right or left sidebar) by default, as high as possible. This will allow users to initiate the digital signing process with just 1 click immediately after…1 vote -
1 vote
-
1 vote
-
Allow users to use the modern Windows dialog for browsing for folders in Advanced Search
When using Advanced Search in Adobe Reader, users have to manually go through the folder tree to get to the desired folder to search. This is a problem for users with deeply nested folder trees, those who use folder shortcuts, and power users. The modern folder-browsing dialog in Windows allows users to paste a folder path, allowing the user to quickly select a folder. In case there is any confusion, the "modern" dialog I am referring to has the location bar.
1 vote -
「Adobe AcrobatをデフォルトのPDFアプリに設定」の通知が、デフォルトアプリに設定していても繰り返し表示される
バージョン 2026.001.21431 をWindows 11で利用しています。
「Adobe AcrobatをデフォルトのPDFアプリに設定」の通知が、デフォルトアプリに設定してからも繰り返し表示されます。一応、「環境設定」の「一般」で「Adobe AcrobatがデフォルトのPDFアプリケーションではない場合に通知」のチェックを外すことで通知が来ないようにはできるのですが、そもそもAdobe AcrobatがデフォルトのPDFアプリを判定する箇所にバグがあるのではないかと思い報告しました。1 vote -
Version 26.04.00 on iOS Bug
Version 26.04.00 on iPad causes the app to crash when filling in (some random, not all) empty fields. Crash does not occur when you fill in the field using a laptop or computer, only on the iPad and only on empty fields.
Same on multiple iPads with the same info:
- iPadOS Version: 26.4.1
- Model Name: iPad (9th Generation)
- Model Number: MK4E3X/A1 vote -
print pages field wrongly disabled for single page PDF
I want to print a single page document, but repeated so there are 2 or 4 copies per page. I would normally do this by setting the Pages field for 'Pages to Print' to e.g. "1, 1" for 2 copies per page. But that field is wrongly disabled, presumably because there's only one page in the document. The field should not be disabled, this is a valid use case.
1 vote -
Include the original comment along with the reply comment in email notifications
When a reviewer adds a Reply comment in adobe acrobat, a notification email is sent. The email includes a copy of the reply but it does not have the original comment. Most often the original comment is required for context, especially for large documents or when some time has passed since original comment was added.
For example, the Reply "Ok, thank you" Is useless with the original comment.
Forcing me to click the 'Go to comment' button is an unwanted additional step.1 vote -
Enhanced Functionality and Speed
Improving Adobe Reader with faster load times, a more intuitive interface, and additional editing tools would make reading and managing PDFs much smoother and more efficient.
1 vote -
Bug Report - Expanding exe package fails to extract msp file
When using the file from https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2500120756/AcroRdrDCx642500120756_MUI.exe
executing the command
.\AcroRdrDCx642500120756MUI.exe -sfxo"C:\Temp\Files" -sfx_neresults in a 0 byte AcroRdrDCx64Upd2500120756_MUI.msp file.
When running the extracted Setup.exe, the installer will fail with exit code 1636.Workaround is to open AcroRdrDCx642500120756_MUI.exe with 7zip and manually extract the msp file.
This was not an issue with AcroRdrDCx642500120577_MUI.exe
2 votes -
dating site
On which platform can I find a girl? Help please
1 vote -
PDF search function bug
In a scientific PDF with references, like [1], I cannot search for the string "[1]". It says it finds nothing.
The same search works however when using the Microsoft browser to view the same PDF.
Acrobat Reader [German language] version in attached file.
1 vote -
Bug Report: Acrobat Reader installer disables inheritance and overwrites ACL on .pdf\PersistentHandler, removing required Windows capability
Bug Report: Acrobat Reader installer disables inheritance and overwrites ACL on .pdf\PersistentHandler, removing required Windows capability SID → Windows 11 PDF full-text indexing breaks
Product / ComponentAdobe Acrobat Reader (latest version as of Jan 2026)
Installer / Update / Repair actions affecting Windows Search integration and registry ACLsOS / Environment
Windows 11 Pro (x64)
Windows Search indexing enabled and functioning correctly for other formats (e.g., .docx)
PDFs are text/OCR-enabled (text can be selected and copied)
Issue is reproducible on system A; system B (Windows 11, no prior Adobe install) indexes the same PDFs correctly
Summary
Installing (or repairing/updating) Adobe Acrobat Reader on Windows 11 Pro breaks Windows Explorer / Windows Search full-text indexing of PDF contents.
The failure is caused not only by registry value mappings, but by Acrobat modifying registry key permissions (security descriptor):
Acrobat disables permission inheritance on:
HKLM\SOFTWARE\Classes.pdf\PersistentHandler
Acrobat overwrites the ACL (DACL) to include only classic principals like:
SYSTEM, Administrators, Everyone
This process removes Windows default capability SID ACEs (notably a capability SID in the form S-1-15-3-…)
Windows Search’s SearchFilterHost.exe runs with that capability SID in its token (verified in Process Explorer as Group with flag “Capability”).
Once that SID is no longer granted ReadKey on the PersistentHandler registry key, SearchFilterHost.exe receives ACCESS DENIED and the PDF IFilter chain cannot be resolved/loaded.
Result: PDFs appear in the index (metadata indexed), but System.Search.Contents remains empty, and Explorer cannot find text inside PDFs.
Re-enabling inheritance (or restoring default ACL) immediately restores PDF full-text indexing.
Impact / Severity
High. Acrobat Reader installation can silently disable OS functionality:
Explorer / Start Menu search cannot find PDF content
Windows Search indexes PDF metadata only, not contents
Users may incorrectly assume PDF content indexing is broken or unreliable in Windows 11
Affects enterprise setups and forensic/search workflows heavily
Expected Behavior
After installing Acrobat Reader:
Windows Search / Explorer should continue to index PDF contents using the Windows built-in PDF filter (Windows.Data.Pdf.dll) or a compatible handler chain.
Acrobat should not modify registry key ACLs in a way that removes Windows-required capability SIDs.
PDF full-text search should continue working the same way as before installation.
Actual Behavior
After Acrobat Reader installation:
PDF contents are no longer searchable (while .docx continues working)
In the Windows Search index:
PDF file entries exist
System.Search.Contents is empty (no extracted text)
Process Monitor shows registry access failures:
SearchFilterHost.exe → RegOpenKey / RegQueryValue on .pdf\PersistentHandler results in ACCESS DENIED
Windows.Data.Pdf.dll is not loaded during PDF indexing attempts until permissions are fixed
Reproduction Steps (100% reproducible)
Baseline (works)Ensure Windows Search is enabled, and the folder containing PDFs is indexed.
Confirm that a given PDF has selectable/copyable text (OCR or embedded).
Confirm PDF full-text search works:
Explorer search finds terms inside PDF content
In Windows Search index, System.Search.Contents contains extracted text (or at least non-empty)
Confirm handler chain is present:
HKCR.pdf\PersistentHandler default value is {1AA9BF05-9A97-48C1-BA28-D9DCE795E93C}
HKLM\SOFTWARE\Classes\CLSID{1AA9BF05-…}\PersistentAddinsRegistered{89BCB740-6119-101A-BCB7-00DD010655AF} points to:
{6C337B26-3E38-4F98-813B-FBA18BAB64F5}{6C337B26-…}\InprocServer32 points to %SystemRoot%\System32\Windows.Data.Pdf.dll
Trigger (break indexing)
Install Adobe Acrobat Reader (latest version).
After install, check registry ACL of:
HKLM\SOFTWARE\Classes.pdf\PersistentHandler
Observe:
Inheritance disabled
DACL replaced/flattened with entries like:
SYSTEM
Administrators
Everyone
Missing capability SID entries (notably S-1-15-3-1024-… capability SID)
Observe failure
Copy a PDF into an indexed folder (or modify a PDF to trigger indexing).
Confirm:
Indexing occurs for metadata (System.ItemPathDisplay present in index)
But System.Search.Contents empty
Explorer cannot find content terms in the PDF
Evidence / Diagnostics
1) Registry key ACL change causes failureUser experiment:
When permissions on .pdf\PersistentHandler are set to inherit from parent .pdf, PDF content indexing works.
When inheritance is disabled and the capability SID ACE is removed, PDF indexing fails.
Adding back the capability SID (explicit allow ReadKey) or re-enabling inheritance restores indexing.
Minimal permission requirements observed:
SYSTEM + capability SID (S-1-15-3-…) required
Removing Users/Admins/CreatorOwner does not break indexing
Removing SYSTEM or the capability SID breaks indexing
2) Process token includes the capability SID (confirmed)
Using Process Explorer:
SearchFilterHost.exe → Properties → Security → Groups
The capability SID appears in Groups with Flag = “Capability”.
This demonstrates that Windows Search components rely on capability SIDs in access checks.
3) ProcMon shows access denied
In Process Monitor during PDF indexing attempt after Acrobat installation:
SearchFilterHost.exe
Registry open/query on .pdf\PersistentHandler yields ACCESS DENIED
Stack shows impersonation-related frames (e.g., kernel path mentions dereferencing impersonation token)
After fixing ACL inheritance, access succeeds and:
Windows.Data.Pdf.dll becomes visible/loaded in the indexing chain
PDF full-text indexing works again
4) Why SYSTEM alone is insufficient
Even when DACL includes SYSTEM FullControl, access can still fail due to Windows token restrictions / capability gating:
Access may require both:
standard SID authorization AND
capability / restricted SID set authorization
This matches observed behavior: SYSTEM alone does not restore indexing if capability SID ACE is missing.
Root Cause
The Acrobat Reader installer (or update/repair routine):
modifies security descriptors (ACLs) of the registry key HKLM\SOFTWARE\Classes.pdf\PersistentHandler
disables inheritance
rewrites DACL to contain only classic principals (SYSTEM/Admin/Everyone)
thereby removing default Windows capability SIDs such as S-1-15-3-1024-…
Windows Search indexing host (SearchFilterHost.exe) includes that SID with flag “Capability” and requires ReadKey
result: SearchFilterHost cannot read PersistentHandler → cannot resolve filter chain → cannot extract contents
This is a permissions regression introduced by Acrobat install behavior.
Workaround / Fix
Immediate workaround (manual)Restore default Windows ACL by re-enabling inheritance:
regedit
Navigate to: HKLM\SOFTWARE\Classes.pdf\PersistentHandler
Permissions → Advanced
Enable inheritance
Apply
PDF full-text indexing resumes immediately after next indexing cycle.
Alternative workaround
If inheritance must remain disabled:
Add explicit allow ReadKey ACE for:
Capability SID: S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681
Ensure SYSTEM also retains ReadKey
Recommendation to Adobe Engineering
Do not modify security descriptors for .pdf\PersistentHandler unless absolutely necessary.
If ACL changes must be made:
preserve inherited ACEs (do not disable inheritance)
do not remove “unknown” SIDs (capability SIDs)
If Acrobat registers its own handler chain, it should do so by updating values, not rewriting registry permissions.
Add a regression test:
install Acrobat on clean Windows 11
ensure PDF System.Search.Contents extraction still works under Windows Search
verify capability SIDs remain present in ACLs
Additional Notes
On a second Windows 11 system (no prior Adobe install), PDF full-text indexing works correctly with the same PDF files.
The issue is independent of PDF content (OCR/text selection works; document is new and created from Word).
Microsoft documentation indicates capability SIDs are legitimate and commonly used; they should not be removed from ACLs.
Bug Report: Acrobat Reader installer disables inheritance and overwrites ACL on .pdf\PersistentHandler, removing required Windows capability SID → Windows 11 PDF full-text indexing breaks
Product / ComponentAdobe Acrobat Reader (latest version as of Jan 2026)
Installer / Update / Repair actions affecting Windows Search integration and registry ACLsOS / Environment
Windows 11 Pro (x64)
Windows Search indexing enabled and functioning correctly for other formats (e.g., .docx)
PDFs are text/OCR-enabled (text can be selected and copied)
Issue is reproducible on system A; system B (Windows 11, no prior Adobe install) indexes the same PDFs correctly
Summary
Installing…
2 votes -
1 vote
-
Allow Admins to see the usage reports for SSO users for Adobe Reader and Adobe Acrobat.
My users are SSO'd via an access package from our Microsoft tenant. While being able to access reports there are an option, it's usually tedious to get. If I could get a report/ audit log from within the Admin Console for Adobe, that would save me so much time. I could see: which applications my users signed into (Adobe Reader, Acrobat, InDesign, etc., the frequency of the use of the app, and last login activity. If I could also see common errors my users get, that would be so helpful!!
1 vote -
Your latest update to Adobe Reader does not support Custom Forms properly.
Your latest update to Adobe Reader does not support Custom Forms properly.
1 vote -
Curious Learning Method
I’m really glad I found this forum and this discussion in particular, as it turned out to be much more helpful than I expected. It gave me a better understanding of how people approach AI tutorshttps://www.reddit.com/r/languagelearning/comments/1quufm1/curious_learning_method/ , and what actually works in real learning situations. I appreciate how different opinions are shared openly, from skepticism to positive experiences, which makes the conversation feel honest and useful. It also helped me rethink my own approach and consider trying new tools more thoughtfully. Overall, this was a great read, and I’d definitely recommend others explore this thread if they’re interested in language learning.
I’m really glad I found this forum and this discussion in particular, as it turned out to be much more helpful than I expected. It gave me a better understanding of how people approach AI tutorshttps://www.reddit.com/r/languagelearning/comments/1quufm1/curious_learning_method/ , and what actually works in real learning situations. I appreciate how different opinions are shared openly, from skepticism to positive experiences, which makes the conversation feel honest and useful. It also helped me rethink my own approach and consider trying new tools more thoughtfully. Overall, this was a great read, and I’d definitely recommend others explore this thread if they’re interested in…
1 vote -
drag menu bar
I frequently move windows between screens and it's really frustrating how little of the menu bar it is possible to use to drag Adobe from one screen to another, without first maximising the window to find a sufficient gap between the "+Create" button and the Help button. There appear to be a lot of gaps between/around the buttons, especially between the "Sign In" and the minimise window button, or between the Menu and the Home buttons, but the only place you can drag the window around from is the small gap between "+Create" and Help. This is really annoying if it happens to be off screen! Please increase the amount of the menu bar that can be used to drag the window around!
I frequently move windows between screens and it's really frustrating how little of the menu bar it is possible to use to drag Adobe from one screen to another, without first maximising the window to find a sufficient gap between the "+Create" button and the Help button. There appear to be a lot of gaps between/around the buttons, especially between the "Sign In" and the minimise window button, or between the Menu and the Home buttons, but the only place you can drag the window around from is the small gap between "+Create" and Help. This is really annoying if…
1 vote -
Medical salon
Hello! I am currently looking for a medical spa that offers personalized skin care treatments. I would like to find a place that tailors treatments to the specific needs of my skin, rather than just offering standard masks. I am interested in professional medical treatments, a relaxing atmosphere, and attentive service. Can you tell me where I can find such a medical spa?
1 vote
- Don't see your idea?