Get-SecretInfo: The specified module '...\Microsoft.PowerShell.SecretStore' was not loaded because no valid module file was found in any module directory. about secretmanagement HOT 4 OPEN

Thank you rkeithhill. I was receiving the same error. I had looked around for a few hours for the file which held the string to that path which was being used but which was no longer correct to reach the SecretStore module. And the "vaultinfo" file was where the data was.

It seems that, in your case and mine, the problem with the path to the SecretStore module occurred because, at some time point after installation of the Microsoft SecretStore, the path to the special \Documents\ (aka "MyDocuments") folder in Windows was changed, and the contents of the \Documents\ folder moved to the new location. So, the folder which contains the SecretStore module was moved to that new location.

And for the SecretStore, Microsoft had used an algorithm such that the path listed in the "vaultinfo" file contains a string which pointed to the location of the Documents special folder at the time of installation of the Microsoft SecretStore.

So, I suggest that, in the next version of SecretStore, Microsoft change the algorithm so that the path listed in the "vaultinfo" file will contain a string which points to the Documents special folder. That way the path can be found at runtime, rather than at installation of the SecretStore module.

from secretmanagement.

Hmm,

 > Get-SecretVault | fl *

Name            : BuiltInLocalVault
ModuleName      : SecretManagement.JustinGrote.CredMan
ModulePath      : C:\Program Files (x86)\Universal\Modules\SecretManagement.JustinGrote.CredMan
Description     :
VaultParameters : {}
IsDefault       : False

Name            : LocalStore
ModuleName      : Microsoft.PowerShell.SecretStore
ModulePath      : C:\Users\hillr\Documents\PowerShell\Modules\Microsoft.PowerShell.SecretStore
Description     :
VaultParameters : {}
IsDefault       : True

Name            : PSUSecretStore
ModuleName      : Microsoft.PowerShell.SecretStore
ModulePath      : C:\Users\hillr\OneDrive - Keysight
                  Technologies\Documents\PowerShell\Modules\Microsoft.PowerShell.SecretStore
Description     :
VaultParameters : {}
IsDefault       : False

from secretmanagement.

OK, edited this file "$HOME\AppData\Local\Microsoft\PowerShell\secretmanagement\secretvaultregistry\vaultinfo" to fix the bogus old (pre-OneDrive migration) path and now the annoying error is gone.

from secretmanagement.

Also, I'm hoping a future version of PowerShell moves modules out of Documents\PowerShell\Modules into a $HOME\AppData\Local folder. That would have prevented this problem from occurring.

from secretmanagement.