PowerShell/WindowsCompatibility
Module that allows Windows PowerShell Modules to be used from PSCore6
PowerShellNOASSERTION
Issues
- 4
DISM commands not compatible
#87 opened by panos-coupa - 0
- 1
Applocker module not working correctly
#88 opened by jschpp - 6
- 5
Type conversion issue on setting $verboseFlag
#68 opened by theDonOfBran - 4
- 1
Powershell 7.0 bug
#85 opened by PhilMEFL - 4
The client cannot connect to the destination specified in the request (localhost)
#73 opened by rjmholt - 0
- 9
Unable to use Export-PFXCertificate one a certificate whose key IS marked exportable
#76 opened by scott1138 - 2
Merge with PowerShellGet
#39 opened by Ayanmullick - 2
Method invocation failed because [System.Management.Automation.PSModuleInfo] does not contain a method named 'Where'.
#82 opened by ianfallon - 1
- 2
- 0
Error during import in profile
#80 opened by MRSchexnayder - 0
- 0
- 1
- 3
- 4
- 0
Work with windows based modules that are installed in the PowerShell core setup
#71 opened by Sarafian - 0
Import-Module Proxy Command
#70 opened by JustinGrote - 0
- 0
When import modules from NeverClobberList, each call of the Import-WinModule adds '.WinModule' to the module name.
#64 opened by sethvs - 0
Need to ignore differences between "localhost" and the short/long values of (hostname)
#63 opened by jpsnover - 2
Set-Clipboard doesn't work
#54 opened by SteveL-MSFT - 1
- 6
- 0
Add-WindowsPSModulePath doesn't account for User PSModulePath environment variable.
#59 opened by sethvs - 0
Path is added even if specifying '[N] No' when using Add-WindowsPSModulePath -Confirm
#57 opened by sethvs - 2
Error with RC1 Import-WinModule when called from Linux PS 6.1 remoting to Windows PS 5.1
#52 opened by banyula - 2
Should expose -PSSession parameter
#55 opened by SteveL-MSFT - 3
Variables are not passed to Filter parameter of any cmdlet from ActiveDirectory module
#42 opened by kborowinski - 7
- 2
- 1
Critical Bug: Remote Sessions Fail
#23 opened by markekraus - 3
- 13
Install this module failed
#45 opened by chucklu - 1
Should we rename Add-WindowsPSModulePath function to Add-WinPSModulePath in order to maintain naming consistency?
#30 opened by sethvs - 0
Should we change the name of the session to include 'wincompat' and Computer Name it connects to?
#33 opened by sethvs - 0
Should we rename Add-WinFunction parameter -FunctionName to -Name and add FunctionName as alias?
#31 opened by sethvs - 3
What's in a name
#26 opened by AdilHindistan - 14
Module Name
#21 opened by markekraus - 9
- 6
Test failures on Windows PS 5.1
#6 opened by SteveL-MSFT - 3
Remove WCP assemblies
#17 opened by SteveL-MSFT - 0
non-Windows compatibility
#14 opened by SteveL-MSFT - 2
Enable methods on deserialized objects
#13 opened by SteveL-MSFT - 3
Aliases are too long
#2 opened by SteveL-MSFT