Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / PowerShell/WindowsCompatibility issues and pull requests
#89 - Get-ADUser Fails To Import When In a WhatIf Context
Issue -
State: open - Opened by aolszowka over 3 years ago
#88 - Applocker module not working correctly
Issue -
State: closed - Opened by jschpp almost 4 years ago
- 1 comment
#87 - DISM commands not compatible
Issue -
State: open - Opened by panos-coupa almost 4 years ago
- 4 comments
#86 - Update LICENSE.txt so that it's recognized as MIT
Pull Request -
State: open - Opened by xtqqczze about 4 years ago
#85 - Powershell 7.0 bug
Issue -
State: open - Opened by PhilMEFL about 4 years ago
- 1 comment
#84 - IISAdministration does not work on PowerShell 7.
Issue -
State: open - Opened by PeterHodges15 about 4 years ago
- 6 comments
#83 - Windows Server's Deduplication powershell commands are kinda buggy
Issue -
State: open - Opened by Evengard over 4 years ago
#82 - Method invocation failed because [System.Management.Automation.PSModuleInfo] does not contain a method named 'Where'.
Issue -
State: open - Opened by ianfallon over 4 years ago
- 2 comments
#81 - [Discussion] Future of this project (AKA Is it dead?)
Issue -
State: closed - Opened by OranguTech almost 5 years ago
- 1 comment
#80 - Error during import in profile
Issue -
State: open - Opened by MRSchexnayder about 5 years ago
#79 - IIS WebAdministration does not load properly via Windows Compatibility
Issue -
State: open - Opened by doctordns about 5 years ago
- 2 comments
#78 - Can not install Docker package with PowerShell 7.
Issue -
State: open - Opened by doctordns about 5 years ago
#77 - BestPractices module does not load with Wndows Compatibility module
Issue -
State: open - Opened by doctordns about 5 years ago
#76 - Unable to use Export-PFXCertificate one a certificate whose key IS marked exportable
Issue -
State: open - Opened by scott1138 about 5 years ago
- 9 comments
#75 - fixing issue-63
Pull Request -
State: open - Opened by Medve01 over 5 years ago
- 3 comments
#74 - ADDSDeployment module does not load - cannot create DCs
Issue -
State: open - Opened by doctordns over 5 years ago
- 1 comment
#73 - The client cannot connect to the destination specified in the request (localhost)
Issue -
State: open - Opened by rjmholt over 5 years ago
- 4 comments
#72 - Import-WinModule returns error with `Get-WebRequest`
Issue -
State: closed - Opened by DanAtkinson over 5 years ago
- 4 comments
Labels: bug
#71 - Work with windows based modules that are installed in the PowerShell core setup
Issue -
State: open - Opened by Sarafian over 5 years ago
#70 - Import-Module Proxy Command
Issue -
State: open - Opened by JustinGrote over 5 years ago
#69 - Adding empty CmdletsToExport to module manifest
Pull Request -
State: open - Opened by powercode over 5 years ago
#68 - Type conversion issue on setting $verboseFlag
Issue -
State: open - Opened by theDonOfBran over 5 years ago
- 5 comments
#67 - Add-WindowsPSModulePath is modified by background runspace
Issue -
State: open - Opened by jdhitsolutions over 5 years ago
#66 - Set-Location generates an error but still works
Issue -
State: open - Opened by jdhitsolutions over 5 years ago
- 3 comments
#65 - Fix adding '.WinModule' with every execution of Import-WinModule command if the module is from NeverClobberList
Pull Request -
State: open - Opened by sethvs almost 6 years ago
#64 - When import modules from NeverClobberList, each call of the Import-WinModule adds '.WinModule' to the module name.
Issue -
State: open - Opened by sethvs almost 6 years ago
#63 - Need to ignore differences between "localhost" and the short/long values of (hostname)
Issue -
State: open - Opened by jpsnover almost 6 years ago
#62 - Add-WindowsPSModulePath adds empty entries in certain cases.
Issue -
State: open - Opened by gwojan almost 6 years ago
- 1 comment
Labels: bug
#61 - Updates for release, bug fix for #56
Pull Request -
State: closed - Opened by BrucePay almost 6 years ago
#60 - Add User PSModulePath environment variable to Add-WindowsPSModulePath function.
Pull Request -
State: closed - Opened by sethvs almost 6 years ago
#59 - Add-WindowsPSModulePath doesn't account for User PSModulePath environment variable.
Issue -
State: closed - Opened by sethvs almost 6 years ago
#58 - Fix ShouldProcess for Add-WindowsPSModulePath
Pull Request -
State: closed - Opened by sethvs almost 6 years ago
#57 - Path is added even if specifying '[N] No' when using Add-WindowsPSModulePath -Confirm
Issue -
State: closed - Opened by sethvs almost 6 years ago
#56 - Error when importing a windows module in $profile using 1.0.0.rc1
Issue -
State: closed - Opened by KaylorDave almost 6 years ago
- 6 comments
Labels: question
#55 - Should expose -PSSession parameter
Issue -
State: open - Opened by SteveL-MSFT almost 6 years ago
- 2 comments
Labels: enhancement
#54 - Set-Clipboard doesn't work
Issue -
State: closed - Opened by SteveL-MSFT almost 6 years ago
- 2 comments
Labels: bug
#53 - Support for non-Windows OS & target host in Environment variable
Pull Request -
State: open - Opened by jhoneill almost 6 years ago
#52 - Error with RC1 Import-WinModule when called from Linux PS 6.1 remoting to Windows PS 5.1
Issue -
State: open - Opened by banyula almost 6 years ago
- 2 comments
Labels: enhancement
#51 - Update Add-WinFunction in QuickStart.md
Pull Request -
State: closed - Opened by tommymaynard almost 6 years ago
#50 - fixed up version number and tags in the manifest
Pull Request -
State: closed - Opened by BrucePay almost 6 years ago
#49 - Test fixes, minor cleanup and preparations for RC
Pull Request -
State: closed - Opened by BrucePay about 6 years ago
#48 - New-EventLog didn't output the error message in powershell 6.1
Issue -
State: closed - Opened by chucklu about 6 years ago
- 2 comments
Labels: discussion
#47 - Added code so the current directory will be tracked in the compat session.
Pull Request -
State: closed - Opened by BrucePay about 6 years ago
#46 - How can I check if I have installed this module successfully?
Issue -
State: closed - Opened by chucklu about 6 years ago
- 3 comments
#45 - Install this module failed
Issue -
State: closed - Opened by chucklu about 6 years ago
- 13 comments
Labels: discussion
#44 - Rename the ProjectUri
Pull Request -
State: closed - Opened by alexandair about 6 years ago
#43 - Fix a typo in WindowsCompatibility.md
Pull Request -
State: closed - Opened by alexandair about 6 years ago
- 1 comment
#42 - Variables are not passed to Filter parameter of any cmdlet from ActiveDirectory module
Issue -
State: open - Opened by kborowinski about 6 years ago
- 3 comments
#41 - Add Add-WinPSModulePath alias.
Pull Request -
State: closed - Opened by sethvs about 6 years ago
#40 - Fix for #23. Session management was broken.
Pull Request -
State: closed - Opened by BrucePay about 6 years ago
#39 - Merge with PowerShellGet
Issue -
State: closed - Opened by Ayanmullick over 6 years ago
- 2 comments
Labels: discussion
#38 - Unable to use NTFSSecurity Module via Import-WinModule
Issue -
State: open - Opened by pldmgg over 6 years ago
- 7 comments
#37 - Problem with DnsServer module and CimSession (de)serialization
Issue -
State: closed - Opened by rmbolger over 6 years ago
- 4 comments
#36 - Update help for Import-WinModule function
Pull Request -
State: closed - Opened by sethvs over 6 years ago
#35 - Fix path in Description for Copy-WinModule.
Pull Request -
State: closed - Opened by sethvs over 6 years ago
#34 - Change name of the session being created to include 'wincompat' and Computer Name it connects to.
Pull Request -
State: closed - Opened by sethvs over 6 years ago
#33 - Should we change the name of the session to include 'wincompat' and Computer Name it connects to?
Issue -
State: closed - Opened by sethvs over 6 years ago
#32 - Rename FunctionName parameter to Name and add FunctionName parameter as an alias.
Pull Request -
State: closed - Opened by sethvs over 6 years ago
#31 - Should we rename Add-WinFunction parameter -FunctionName to -Name and add FunctionName as alias?
Issue -
State: closed - Opened by sethvs over 6 years ago
#30 - Should we rename Add-WindowsPSModulePath function to Add-WinPSModulePath in order to maintain naming consistency?
Issue -
State: closed - Opened by sethvs over 6 years ago
- 1 comment
#29 - Remove 'Program Files' module path from Add-WindowsPSModulePath function
Pull Request -
State: closed - Opened by sethvs over 6 years ago
- 4 comments
#28 - Installing WindowsCompatibility using PS5+
Pull Request -
State: closed - Opened by jwmoss over 6 years ago
- 2 comments
#27 - Add Installation Docs
Pull Request -
State: closed - Opened by markekraus over 6 years ago
- 1 comment
#26 - What's in a name
Issue -
State: open - Opened by AdilHindistan over 6 years ago
- 3 comments
Labels: discussion
#25 - Rename Module to WindowsCompatibility
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#24 - Add More Documentation
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#23 - Critical Bug: Remote Sessions Fail
Issue -
State: closed - Opened by markekraus over 6 years ago
- 1 comment
Labels: bug
#22 - Remove Dotnet CLI Pre-req
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#21 - Module Name
Issue -
State: closed - Opened by markekraus over 6 years ago
- 14 comments
Labels: discussion
#20 - Set required (minimum) PowerShell version to be 6.0
Pull Request -
State: closed - Opened by BrucePay over 6 years ago
#19 - Add Module Rename Hack
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#18 - Remove WCP and Make Core Only
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#17 - Remove WCP assemblies
Issue -
State: closed - Opened by SteveL-MSFT over 6 years ago
- 3 comments
#16 - Fixes for the Compatibility session commands and tests for Desktop
Pull Request -
State: closed - Opened by BrucePay over 6 years ago
- 2 comments
#15 - Fixed spelling of otherExcludedAssemblies
Pull Request -
State: closed - Opened by weloytty over 6 years ago
- 1 comment
#14 - non-Windows compatibility
Issue -
State: open - Opened by SteveL-MSFT over 6 years ago
Labels: enhancement
#13 - Enable methods on deserialized objects
Issue -
State: open - Opened by SteveL-MSFT over 6 years ago
- 2 comments
Labels: enhancement
#12 - Fix use of Windows Compat Pack
Pull Request -
State: closed - Opened by SteveL-MSFT over 6 years ago
#11 - Disabled the ability to do Import-WinModule Microsoft.PowerShell.Management module
Pull Request -
State: closed - Opened by BrucePay over 6 years ago
- 2 comments
#10 - Move CBH to external help with PlatyPS
Pull Request -
State: closed - Opened by markekraus over 6 years ago
- 1 comment
#9 - update readme
Pull Request -
State: closed - Opened by SteveL-MSFT over 6 years ago
#8 - Enable module to work on Windows PowerShell 5.1
Pull Request -
State: closed - Opened by SteveL-MSFT over 6 years ago
- 2 comments
#7 - Tabcomplete no longer works after running CompatibilitySession.Tests.ps1
Issue -
State: closed - Opened by SteveL-MSFT over 6 years ago
- 9 comments
Labels: bug
#6 - Test failures on Windows PS 5.1
Issue -
State: closed - Opened by SteveL-MSFT over 6 years ago
- 6 comments
Labels: bug
#5 - Removed the command aliases from the module, manifest and tests
Pull Request -
State: closed - Opened by BrucePay over 6 years ago
#4 - Integrate Windows Compatibility Pack
Pull Request -
State: closed - Opened by markekraus over 6 years ago
#3 - Add Add-WindowsPSModulePath cmdlet and test
Pull Request -
State: closed - Opened by SteveL-MSFT over 6 years ago
#2 - Aliases are too long
Issue -
State: closed - Opened by SteveL-MSFT over 6 years ago
- 3 comments
#1 - First version of the Compatibility Session commands
Pull Request -
State: closed - Opened by BrucePay over 6 years ago
- 4 comments