Set-Secret and Get-SecretStoreConfiguration throws an exception as a normal user about secretstore

[swinster]

Looks like rebooting might have resolved this

[PaulHigin]

I am not clear on the repro steps. Did you install the modules and vaults under two accounts, one admin and one not? I have tested this without any problems. The type initializer exception suggests you have two different versions of SecretStore or SecretManagement. During preview, each version is incompatible with the other. So be sure and uninstall the old versions before you install the new.

[swinster]

Hey @PaulHigin. Installation of the modules were under a single users account, but from an elevated PS window, then re-run under the normal user context. No previous modules were install, only the last releases of SecretStore or SecretManagement. TBH, I managed to get something similar to happen on two other machines as well.

[PaulHigin]

@swinster One other thing that may result in type initializer error is if you installed onto a Windows machine without netstandard2.0. PowerShell 7+ will include the needed binaries, but if you are running WindowsPowerShell, the netstandard binaries will not be there by default. Installing PowerShell 7+ will include them or you can get it from netstandard.library package from nuget.org.

[swinster]

Was using the latest version of PS7....

[PaulHigin]

I am changing how the module binaries are built, targeting net461 framework rather than netstandard2.0. This should improve compatibility with PS7 and PS5.1. This may solve your issue since the exception above is thrown during store file creation, and may be related to the access control API compatibility issue my change addresses.

[PaulHigin]

Implemented in preview4 changes.