After I installed Visual Studio 2022 (Version 17.12.4) the Visual Studio 2019 issue described above was fixed.