This $ENV:PATH holds the value of your current PATH settings. This variable can be updated in your current PowerShell terminal :
$ENV:PATH="$ENV:PATH;C:\Program Files (x86)\Notepad++"
You can also retrieve the current value with the following cmdlet Get-ItemProperty :
Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH
To make this change permanently, open up a new PowerShell terminal as Administrator (using runas) :
$oldpath = (Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH).Path
$newpath = "$oldpath;C:\Program Files (x86)\Notepad++"
Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH -Value $newpath
Now, just log out of your current Windows session to take this change into account
NB : Tested successfully on Windows 10
A special syntax for the Filter parameter is required for some Active Directory PowerShell cmdlets such as Get-ADUser to get the expected result.
This article explains perfectly how to properly handle it : http://www.powershellish.com/blog/2015-11-17-ad-filter
While upgrading your Debian Stretch, you can come up with this message :
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915
This has been referenced as a bug :
If you can’t upgrade to Debian Buster, there is a possible workaround
Otherwise, after switching to Buster, the available version of firmware-misc-nonfree provides the missing firmwares.
hardinfo used on the command line displays the following message error :
sh: 1: /lib/libc.so.6: not found
This is a non-blocking issue as report can be generated successfully.
This error is referenced as a confirmed bug both in Debian and Ubuntu.
Windows PowerShell Syntax Plugin provides Syntax coloring, indenting and filetype detection for Windows PowerShell.
It is available at :
If you use Pathogen, just extract into your bundle folder.
If not, just set up Pathogen as follows below :
Additional actions to make it work on Windows 7 :
cd C:\Program Files (x86)\Vim\vimfiles
Install pathogen.vim in C:\Program Files (x86)\Vim\vimfiles\autoload
To enable Pathogen, add this to your gvimrc :
filetype plugin indent on
On Windows 7/10, the gvimrc file must be named as _gvimrc and located in one of the folders :
$HOME points to your home directory in Windows 7 and $VIM points to your directory where Vim/gVim have been installed.
The personal initialization files are searched in the order specified above
and only the first one that is found is read.
This plugin is now enabled. Enjoy !
At boot time, the following message can pop up :
WARNING : Failed to connect to lvmetad. Falling back to device scanning
This message is displayed, whether running Debian stable or Debian testing.
To get rid of this message, disable lvmetad in /etc/lvm/lvm.conf
Update the initramfs for the current kernel your system uses :
update-initramfs -k $(uname -r) -u; sync
Reboot your system and you’re done !
Ubuntu workaround for this issue
This issue has already been reported in the Debian bug tracking system : #846946