Make the Chocolatey refreshenv part of Powershell. Manipulating environment variables is very difficult without it.

pnputil provides the PublishedName property. This can come in handy in rare cases where Windows does not properly register and unregister a driver.

This is what I am looking for:

Microsoft PnP Utility

Adding driver package: cnp60ma64.inf
Driver package added successfully.
Published Name: oem20.inf <---- need this
Driver package installed.

Total driver packages: 1
Added driver packages: 1

Unfortunately, the printmanagement cmdlet does not provide this functionality when adding or enumerating driver objects. Add-WindowsDriver and Get-WindowsDriver do, but you can only use Add-WindowsDriver on offline images at the moment.

Is there any plan to enhance or change this?

In Windows Explorer there are two columns available: "Date modified" and "Date". I've tried both setting the .LastWriteTime and .CreationTime for files and it changes the date in the "Date Modified" column, but does not change the "Date" column.

Is there a way to modify the "Date" column in Windows Explorer using Powershell scripting? I basically want to create a "touch" command that will affect BOTH "Date modified" and "Date" columns in Windows Explorer.

Thanks!

in the WebAdministration module, the commandlet "new-WebApplication" fails if the physicalPath is a UNC location.

AppCmd.exe and the .NET lib Microsoft.Web.Administration do not have this limitation.

Trying to configure Static mapping using an ExternalIPAddress other than 0.0.0.0
Get us this message:
"Add-NetNatStaticMapping : The process cannot access the file because it is being used by another process."
Even though the IP address and port is mapped in "NetNatExternalAddress".

C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript&#39;
Find-Package : A parameter cannot be found that matches parameter name 'ScriptSourceLocation'.
At line:1 char:37
+ Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://ww ...
+ ~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : InvalidArgument: (:) [Find-Package], ParameterBindingException

+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

PS 21:22 C:\src
C:>$PSVersionTable

Name Value

PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript&#39;
Find-Package : A parameter cannot be found that matches parameter name 'ScriptSourceLocation'.
At line:1 char:37
+ Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://ww ...
+ ~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : InvalidArgument: (:) [Find-Package], ParameterBindingException

+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

PS 21:22 C:\src
C:>$PSVersionTable

Name Value

PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

There is the time that we need to open more than one PowerShell windows at a time and run different CMDLETs for different purposes.
So if there is the option to show up the purposes of different PS window, it will greatly help us distinguish and find out the currently required PS window.

It would be great to have not only in-window progress bar for my scripts, but the green bar filling up my taskbar as I can see in Copy and other operations. It may be just something like -taskbar... parameter, maybe additionally fitted with ProgressState.

The Remove-PrinterDriver cmdlet currently does not offer a -Force option. This becomes a problem when there are network printers mapped via Group Policy that use the driver. When this is the case, PowerShell will return a "The specified driver is in use by one or more printers" error.

PnPUtil offers the ability to force delete a driver even if it is in use. PowerShell's Remove-PrinterDriver cmdlet should offer the same behavior (clearly it is possible).

I'm attempting to run an executable remotely on a machine that needs updating. Whenever the exe is called, Antimalware Service Executable pops up on the remote machine for a moment, and then nothing else happens.

Code is attached. Unsure if this is user error/known issue/isolated bug

I'm attempting to run an executable remotely on a machine that needs updating. Whenever the exe is called, Antimalware Service Executable pops up on the remote machine for a moment, and then nothing else happens.

Code is attached. Unsure if this is user error/known issue/isolated bug

I want to look a few lines of a large file, but Get-Content with -Head and -Tail option still reports insufficient memory issue.

Get-ADcomputer -filter 'Name -like "SRV_*"' -Properties ProtectedFromAccidentalDeletion | Set-ADObject -ProtectedfromaccidentialDeletion $false

Get-ADcomputer -filter 'Name -like "SRV_*"' -Properties ProtectedFromAccidentalDeletion | Set-ADComputer -ProtectedfromaccidentialDeletion $false

Set-ADComputer : Es wurde kein Parameter gefunden, der dem Parameternamen
"ProtectedfromaccidentialDeletion" entspricht.
In Zeile:1 Zeichen:106
+ ... Set-ADComputer -ProtectedfromaccidentialDeletion $false
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : InvalidArgument: (:) [Set-ADComputer], Parameter

BindingException

+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.ActiveDirectory

.Management.Commands.SetADComputer

The following causes sleep to not sleep at all

Start-Sleep -Seconds 0.5

Seems anything < 1.0 is considered to be zero

Cannot change Temp folder path used for Exchange Online Power-Shell Module (With MFA) imports. How do we change the path from using the temp folder

New-SMBShare -Temporary should remove the share after a reboot but that's nothing happening

Reproducibility: always.

1) Set display scaling not at 100%
2) Start new PS and PS ISE sessions
3) Run:
Add-Type -AssemblyName System.Windows.Forms
4) Notice difference when running in PS ISE to PS standard

PS ISE takes no notice of display scaling and reports screen resolution. PS does take notice of display scaling and reports virtual screen resolution, e.g. 1920x1080 for a 3840x2160 screen with 200% scaling.

$PSVersionTable:
PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Windows 10 Pro v1903 OS Build 18362.418