Windows update broke code signing, documentation is entirely defective

### Type of issue

Code doesn't work

### Description

The latest Windows update has broken code signing and the documentation is incomplete.

My code is confgured to sign assemblies with a code signing key:
[assembly: System.Reflection.AssemblyKeyName("SigningKeyDeveloper")]

Code which worked fine before Windows update now fails:
Error signing output with public key from container 'SigningKeyDeveloper' -- Keyset does not exist (Exception from HRESULT: 0x80090016)

The key still exists in the store:
sn -i fred.snk SigningKeyDeveloper

The problem here might well be that the code signing scheme is essentially unfinished and there are separate key stores for 32 and 64 bit windows. But here is the thing, there is absolutely no way to know which mode anything is operating in. Do I have the 32 or 64 bit console? No idea and no way to find out.

Similarly, how do I list out the keys to see why something is failing? Again, no explanation.

Most of the documentation doesn't even mention this issue.

So I am going to be turning off windows update and seeing if I can back out the last update because my working system has been broken trying to install features that are of zero value to me.

### Page URL

https://learn.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name

### Content source URL

https://github.com/dotnet/docs/blob/main/docs/standard/assembly/sign-strong-name.md

### Document Version Independent Id

73c57596-00af-2739-b206-bcbea262fcbb

### Article author

@IEvangelist

### Metadata

* ID: f94526da-6739-ad3b-c0eb-48652e70a062
* Service: **dotnet-fundamentals**

[Related Issues](https://github.com/dotnet/docs/issues?q=is%3Aissue+is%3Aopen+73c57596-00af-2739-b206-bcbea262fcbb)