![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 50%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
1,104 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 13%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
One big thing that you haven't mentioned is, did VS 16.8 also install the Windows 10 2004 SDK? Check under the Individual Component list to see if the SDK 10.0.19041.0 is installed.
This is important because the version of ucrtbased.dll that ends up being copied to System32 and SysWoW64 is from the latest installed Windows 10 SDK. This means that if you have two SDKs installed and the setup for the latest one failed somehow, then it is possible to not have these files in the locations that Windows would look in for executables.
I would honestly suggest that you just do a repair install for Visual Studio 2019 16.8. This will do a repair on all installed SDKs too.
