How to Stop Adobe Add-Ins from reinstalling in Outlook

Forum|Forum|2 years ago
July 24, 2023
3 replies
14290 views

I do not use Adobe ASdd-Ins in Outlook, I find they interfere with my ability to add attachments, and generally slow Outlook down to the point it is almost unusable. I have opened Outlook as an administrator and unistalled the Adobe Add-Ins on a few occaisons. A few days later, Outlook will again start to run slowly, freeze when adding attachments and Adobe Cloud reappers. The Add-Ins are reinstalling by themslves, and I am tiored of it. How do I prevent this? I am really fed up with Adobe!

J

Jonas37202835537o

Participant

OSB! this is only working as a Intune Script.

I found a way to check if the add-in is installed and remove it, if it exist this is done by a remediate script.

I work in IT and therfore this script is made as a remediation script to be pushed out to multiple machines.

Detect-RegistryKey.ps1:

# Define the registry key to check
$registryKey = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Addins\PdfmOutlook.PDFMOutlook"

# Check if the registry key exists
if (Test-Path $registryKey) {
Write-Output "Registry key found: $registryKey"
} else {
Write-Output "Registry key not found: $registryKey"
}

# Define the file path to check
$filePath = "C:\Program Files\Adobe\Acrobat DC\PDFMaker\Mail\Outlook\x64\SendAsLinkAddin.dll"

# Check if the file exists
if (Test-Path $filePath) {
Write-Output "File exists: $filePath"
} else {
Write-Output "File does not exist: $filePath"
}

Remediate-RegistryKey.ps1:

# Define the registry key to delete
$registryKey = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Addins\PdfmOutlook.PDFMOutlook"

# Check if the registry key exists
if (Test-Path $registryKey) {
# Delete the registry key
Remove-Item -Path $registryKey -Force
Write-Output "Deleted registry key: $registryKey"
} else {
Write-Output "Registry key not found: $registryKey. No action taken."
}

# Define the file path to delete
$filePath = "C:\Program Files\Adobe\Acrobat DC\PDFMaker\Mail\Outlook\x64\SendAsLinkAddin.dll"

# Check if the file exists
if (Test-Path $filePath) {
# Delete the file
Remove-Item $filePath -Force
Write-Output "Deleted file: $filePath"
} else {
Write-Output "File not found: $filePath"
}

C

ClockworkMuppet

Participant

I killed it by making a text doc and renaming it to SendAsLinkAddin.dll, then removing any system ability to modify it (only administrators can modify or delete it in security) and set it to read only then stuck it in here to replace the current file C:\Program Files\Adobe\Acrobat DC\PDFMaker\Mail\Outlook\x64

Working so far. None of the other solutions involving registry or anythiing else has worked, it always waits a while then reinstalls using conventional methods.

G

gregory_4604

Participant

Surely Adobe should see this is a big and painful problem and is very damaging to its brand (certainly it annoys the hell out of me) and JUST FIX IT!

D

Dennis33657103pcr6

Participant

Yeah, this is really frustrating. I just got off with Adobe support and the only way they were able to work around this was to delete the plugin within Outlook and then turn off the Adobe Pro DC automatic updates. The automatic updates will reinstall the plugin everytime and you are back to square one. One can manually update the product then and then delete the plugin but at least one knows when the plugin is reinstalled.