# Compiler identification problem (VS2022)

**URL:** https://discourse.cmake.org/t/compiler-identification-problem-vs2022/5149
**Category:** Usage
**Tags:** os:windows
**Created:** [March 2, 2022, 5:17pm UTC](https://discourse.cmake.org/t/compiler-identification-problem-vs2022/5149 "2022-03-02T17:17:17Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![hyperz](https://discourse.cmake.org/user_avatar/discourse.cmake.org/hyperz/32/2239_2.png) [@hyperz](https://discourse.cmake.org/u/hyperz)
#### Post date: [March 4, 2022, 9:00am UTC](https://discourse.cmake.org/t/compiler-identification-problem-vs2022/5149/6 "2022-03-04T09:00:57Z")

</div>

Today I installed a new version of Windows SDK through VS installer. Everything started working.

I think there is a problem with SDK 10.0.19041.0 which is the default SDK for VS 2022. When using this SDK compiler doesn’t get complete library paths so it fails when looking for ucrtd.lib. I can see that $(WindowsSDK\_LibraryPath\_x64) misses ucrt directory. Installation of new SDK fixes this. It looks like a msbuild’s internal SDK-detection problem.

---

_[View the full topic](https://discourse.cmake.org/t/compiler-identification-problem-vs2022/5149)._