Rob Reynolds

> If you're new to choco, especially if you've used package managers on other platforms, the first 10 times you have to spawn a new admin PS session to run...

> then close my original powershell window and reopen it so the new app shows up on the path. Why would you do this? Do you know about `refreshenv`? 

https://chocolatey.org/docs/troubleshooting#i-cant-get-the-powershell-tab-completion-working There is a small documentation bug with the next item where the profile installation is: ~~~powershell # Chocolatey profile $ChocolateyProfile = "$env:ChocolateyInstall\helpers\chocolateyProfile.psm1" if (Test-Path($ChocolateyProfile)) { Import-Module "$ChocolateyProfile" } ~~~...

> I have never seen that snippet get added to one of my profile scripts, on any machine, ever. And what about when a new PowerShell version is installed? This...

> IMO it should, but that's a bit of a different issue It used to. However that had its own set of issues related to VMs, Vagrant, and Virtualbox.

https://github.com/chocolatey/choco/issues/834 is where the issue is documented, #833 is where we did the work for exclusion rules.

@FranklinYu here's the problem - chocolateyBeforeModify.ps1 comes from the INSTALLED (aka OLDER version) of the package. If it is bad or wrong, the only way to fix this is to...

This is likely to go over to open source

@qzo I like that as well. We want some for existing known types and then also the ability for someone to add an ini type file for particular ones

Sounds like a good idea. Have added this to up for grabs.