Hi, Bitdefender seems to be blocking PowerShell on my system. I need to use it for legitimate purposes, but it gets automatically blocked or closed. How can I allow or unblock PowerShell through Bitdefender? Thanks in advance for your help!
Kindly follow the steps below:
The Scan scripts feature allows Bitdefender to scan PowerShell scripts and Office documents that may contain s.c.r.i.p.t based malware. Disabling this option can help prevent legitimate PowerShell use from being blocked.
If the issue persists, try adding PowerShell as an exclusion in your Bitdefender product:
1) Temporarily disable Bitdefender Protection: https://www.bitdefender.com/consumer/support/answer/28557/
2) Set exclusions in Bitdefender Antivirus: https://www.bitdefender.com/consumer/support/answer/13427/
3) Set exclusions in Bitdefender Advanced Threat Defense: https://www.bitdefender.com/consumer/support/answer/2393/
4) Re-enable real-time protection in Bitdefender.
If the issue still persists, kindly contact Bitdefender support by visiting https://www.bitdefender.com/consumer/support/help/
Select, How to's & Troubleshooting Bitdefender products→Troubleshooting→I don't know→Contact Support→ You will get the option of chat, call or email.
To get an immediate update, kindly use the chat option. Also, ensure that no ad blockers or privacy extensions are enabled in your web browser, as they may prevent the chat window from appearing.
Bitdefender support may request diagnostic logs and will guide you through the process of generating them.
Regards
Hi,
Thanks for your reply and instructions. I followed the steps and disabled the "Scan scripts" option under the Advanced tab, but unfortunately PowerShell is still being blocked or closes immediately after opening.
It seems like something else might still be interfering — could it be caused by Advanced Threat Defense or another protection module?
Machine : Windows 11
Shells concernés :
- Windows PowerShell 5.1
- PowerShell 7.x (pwsh)
STATUT : Résolu par configuration
1. Symptôme initial
PowerShell bloque lorsqu’il est invoqué depuis l’appel du terminal ou à partir de cmd.exe. La commande ne rend pas la main, même pour des instructions triviales.
La sortie n’apparaît qu’après Ctrl+C.
Exemples de commandes bloquantes (exécutées depuis cmd.exe) :
pwsh
pwsh -Command "Write-Output OK"
powershell -Command "Write-Output OK"
2. Diagnostic
Les tests AMSI montrent une interférence avec BitDefender.
Le module Advanced Threat Defense (ATD) de Bitdefender intercepte AMSI.
Cette interception provoque un deadlock lors de l’initialisation de PowerShell.
Antivirus et Menaces en ligne ne sont pas en cause.
4. Validation expérimentale
Après désactivation d’ATD et redémarrage (+++ OBLIGATOIRE) :
- PowerShell 5.1 : OK
- PowerShell 7 : OK
5. Configuration stable dans BitDefender pour permettre le fonctionnement de Powershell :
Protection/ouvrir Advenced Threat Defense/Parametres/Gérer les exceptions/Advanced Threat Defense/ Option des exceptions/
Exclure powershell.exe
Bitdefender Antivirus : Pas d’exception (bouton sur off)
Bitdefender Menaces en ligne : Pas d’exception (bouton sur off)
Bitdefender Advanced Threat Defense : Exception (bouton sur ON)
6. Conclusion
Il s’agit d’une incompatibilité fonctionnelle entre AMSI et Bitdefender ATD.
La configuration retenue est stable, reproductible et documentée.
