Thanks for the ping. Others already provided most of the information. To summarize, we don't produce a package for Microsoft.Win32.Registy any longer as the library became part of the Microsoft.NETCore.App shared framework. If you target .NETStandard and want to use Registry APIs, feel free to use the existing stable 5.0.0 version of the package.

This change was made as part of .NET 6 and you should be able to use the Registry API without referencing a package when targeting net6.0 or higher.

@ViktorHofer thanks for the feedback, our of curiosity, how does the net60 / net70 runtime accepts a reference from netstandard2.0 to Microsoft.Win32.Registy 5.0.0 (which is compiled against .NET Framework v4.61 AFAIK) and translates it to calls to net60 / net70 equivalent registry types?

The assembly version of the netstandard2.0/net461 asset in the Microsoft.Win32.Registry 5.0.0 package is 5.0.0.x. The assembly version of the Microsoft.Win32.Registry.dll that is part of the shared framework is 6.0.0.0 for the .NET 6 and 7.0.0.0 for the .NET 7 shared framework. The "conflict resolution" task is msbuild makes sure to pick the right assembly based on the assembly and file version.

In the example of .NET 6, the 6.0.0.0 Microsoft.Win32.Registry.dll assembly from the shared framework wins over the 5.0.0.0 netstandard2.0/Microsoft.Win32.Registry.dll from the nuget package.