alerickson
alerickson
@aavdberg I was waiting for a response to Justin's comment above. Are you running as admin?
For that, please open an issue on the [PowerShell](https://GitHub.com/PowerShell/PowerShell) repo.
@aavdberg for the time being if you want a workaround you can update $env:PSModulePath to have the old documents folder prioritized on the path: ` $env:PSModulePath = "; $env:PSModulePath"`
@aavdberg, yup that'll work... the previous default documents path was: `C:\Users\\Documents\PowerShell\Modules`
Ah okay, in that case as a workaround you can use `Save-Module -Destination ` This will install to the path specified.
@it-praktyk @daxian-dbw that's not an issue I've seen before. As a work around, you can always use Save-Module and specify the module directory as the -path to install to.
@daxian-dbw Yes, please transfer to PowerShellGet. It looks like PSGet tries to open a file to test whether the module is in use that's failing. @it-praktyk can you try running...
@iSazonov I'm pretty confident `Save-Module -Path ` would be a suitable workaround. @it-praktyk could you let us know if this does in fact work for you?
@avishnyakov thanks for the extensive testing and suggestions! I highly agree with the suggestion to move onto docker containers.
@avishnyakov the build itself is not broken, they're flakey pester tests that need to be updated. But you're right, this should be addressed and we'll get to this in the...