Anam Navied

@BohrenAn we completely understand the frustration with this PowerShellGet V2 behavior. We are working on PowerShellGet V3 to be less confusing and handle such scenarios better. If you try finding...

@BohrenAn PSGet 2.2.5 (and its cmdlet Install-Module) defaults to CurrentUser for PowerShell5 and 7. Lower versions of PSGet may not default to CurrentUser.

This issue should be resolved via #1627 . If you still see an issue with this please feel free to comment and I can re-open, thanks @JustinGrote !

@MFunction96 thanks for sharing this info, we'll investigate into this.

@tgrader thanks for reaching out! I noticed that you are using `Install-Package` (which comes from PackageManagement). Could you use `Install-Module` (which comes from PowerShellGet V2). Also, are the packages `jQuery`...

@travisgr thanks for trying this scenario out with PSGet V3. We're working to add better nupkg integration for packages like these which have neither .psd1 nor .ps1 file. These files...

@dolauli sorry for the delayed response. We're aware of this issue and are working to resolve it

@fabricesemti80 looking at the [link you posted in the Stack Overflow post](https://forge.puppet.com/modules/dsc/powershellget) > Usage section > the example recommends that installation policy is case sensitive and should be `trusted` or...

@zp-zpanda thanks for reaching out and my apologies for the late response. Could you try again, our email system got fixed within the last week. In the meantime I'll also...

@pbafna03 @seanmcne @mikenelson-io thanks for reaching out. We are looking into this and working to resolve it, but don't have a definitive timeframe for the solution at the moment.