Hi @Titus Tolbert (Sr. Dev Operation, Hoka corp)
Thank you for posting your question in the Microsoft Q&A forum.
Based on the symptoms you described, this aligns with the known issue under investigation for SharePoint Server Subscription Edition post-September 2025 CU (KB5002784), as noted in Stefan Gossner's summary and related discussions. No full resolution is available yet, but Microsoft recommends opening a support ticket for escalation, with a potential fix targeted in the October 2025 CU.
While waiting for an official fix, here are some mitigations you may try:
1.Rename file extension or compress into ZIP before upload:
Temporarily rename the .pdf extension (e.g., to .pdfx or .doc) prior to upload, then revert post-upload if needed. Alternatively, compress the PDF into a .zip archive for upload and extract it server-side via workflows or user action. This helps bypass AMSI-triggered crashes.
2.Exclude .pdf extensions from SharePoint Antivirus scans
In Central Administration > Security > Manage antivirus settings, add pdf under Exclude these file extensions from the scan (comma-separated if adding others). Save and run a full scan job to propagate.
Please note: this exclusion applies only to SharePoint-integrated antivirus scanning, not to OS-level Defender AMSI. Depending on your configuration, it may or may not fully mitigate the crash.
The registry-based AMSI workaround should not be used, because it is unsupported and undocumented. Microsoft has not released any official guidance or registry key to disable AMSI scanning for PDFs in SharePoint. Implementing such changes may lead to system instability or introduce unsupported behavior and should not be used in production environments.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.