Hello there! I was working on a project of mine and came across some abnormal behavior using beeep's windows notify feature. Running a compiled binary using the beeep.Notify function I noticed that the system's PowerShell profile was being executed when it shouldn't have been. After some hunting, I figured out that beeep was using PowerShell commands for some functionality but without specifying the -NoProfile argument. As the goal of the line was to simply capture the output of the Get-StartApps command I figured it wouldn't hurt to add in the NoProfile arg and would prevent any unexpected outputs/behavior.
gen2brain
commented
3 years ago
Hello there! I was working on a project of mine and came across some abnormal behavior using beeep's windows notify feature. Running a compiled binary using the beeep.Notify function I noticed that the system's PowerShell profile was being executed when it shouldn't have been. After some hunting, I figured out that beeep was using PowerShell commands for some functionality but without specifying the -NoProfile argument. As the goal of the line was to simply capture the output of the Get-StartApps command I figured it wouldn't hurt to add in the NoProfile arg and would prevent any unexpected outputs/behavior.