In the recent pwps_dab (22.214.171.124 and above) module updates I have run into an issue installing / upgrading the module in the 32 bit ISE. I am not aware of any changes to my computer that would be causing the issue. I am running the ISE as admin.
Here is the output I get from the install-module attempt.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.VERBOSE: The -Repository parameter was not specified. PowerShellGet will use all of the registered repositories.VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.VERBOSE: The specified Location is 'www.powershellgallery.com/.../' and PackageManagementProvider is 'NuGet'.VERBOSE: Searching repository 'www.powershellgallery.com/.../FindPackagesById() for ''.VERBOSE: Total package yield:'1' for the specified package 'pwps_dab'.VERBOSE: Performing the operation "Install-Module" on target "Version '126.96.36.199' of module 'pwps_dab'".VERBOSE: The installation scope is specified to be 'AllUsers'.VERBOSE: The specified module will be installed in 'C:\Program Files (x86)\WindowsPowerShell\Modules'.VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.VERBOSE: Downloading module 'pwps_dab' with version '188.8.131.52' from the repository 'https://www.powershellgallery.com/api/v2/'.VERBOSE: Searching repository 'www.powershellgallery.com/.../FindPackagesById() for ''.VERBOSE: InstallPackage' - name='pwps_dab', version='184.108.40.206',destination='C:\Users\3830a\AppData\Local\Temp\1540773918'VERBOSE: DownloadPackage' - name='pwps_dab', version='220.127.116.11',destination='C:\Users\3830a\AppData\Local\Temp\1540773918\pwps_dab\pwps_dab.nupkg', uri='www.powershellgallery.com/.../1.10.5'VERBOSE: Downloading 'www.powershellgallery.com/.../1.10.5'.VERBOSE: Completed downloading 'www.powershellgallery.com/.../1.10.5'.VERBOSE: Completed downloading 'pwps_dab'.VERBOSE: Hash for package 'pwps_dab' does not match hash provided from the server.VERBOSE: InstallPackageLocal' - name='pwps_dab', version='18.104.22.168',destination='C:\Users\3830a\AppData\Local\Temp\1540773918'PackageManagement\Install-Package : Access is deniedAt C:\Program Files (x86)\WindowsPowerShell\Modules\PowerShellGet\22.214.171.124\PSModule.psm1:1772 char:21+ ... $null = PackageManagement\Install-Package @PSBoundParameters+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Packag e], Exception + FullyQualifiedErrorId : System.UnauthorizedAccessException,Microsoft.PowerShell.Commands.GetChildItemCom mand,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage
I am still able to get it installed in the 64 bit ISE though I have not used that version.
My suggestion is to run uninstall-module pwps_dab -AllVersions -Force from your 32 bit session and then run the same thing from your 64-bit session. If you don't have good module hygiene, you can end up with a lot of versions since we're releasing so often. That can lead to unintended problems. I suggest only doing the install from a 64-bit session. Then, you get one installation (in Program Files\WindowsPowershell) that can be used by both 32-bit and 64-bit PowerShell.
What is it that's keeping you from using 64-bit all the time? We are trying to incorporate some of the more useful features from PWPS so that you will have them available in 64-bit. Kind of changes our original scoping (don't bother to replicate functionality from PWPS), but I think that's OK.
I have done the uninstall on the 32 bit versions but not the 64 so I will give that a try. There is probably nothing keeping me from going to the 64bit version. I started on the 32 bit and used the pwps commandlets on my early scripts so that is really the only reason that I have stayed on it.
Thanks for your help...