Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not find SDK "Microsoft.VCLibs.Desktop, Version=14.0". #837

Closed
SwimmingTiger opened this issue May 15, 2019 · 8 comments
Closed

Could not find SDK "Microsoft.VCLibs.Desktop, Version=14.0". #837

SwimmingTiger opened this issue May 15, 2019 · 8 comments

Comments

@SwimmingTiger
Copy link

SwimmingTiger commented May 15, 2019

Your Windows build number

Windows 10 version 1903 build 18895.1000

What you're doing and what's happening

Got this error:
Error MSB3774 Could not find SDK "Microsoft.VCLibs.Desktop, Version=14.0". OpenConsolePackage C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets 266

I have exhausted all possible solutions:

  • Build with VS2017 (the same error)
  • Build with VS2019 Preview 3 (the same error)
  • Retarget platform toolset to v142 (the same error)
  • Install any components that may be missing (the same error)
  • Install the VS2015 platform toolset (v140) (the same error)
  • Switch system language from Chinese to English (the same error)
  • Switch system code page to UTF-8 (beta) (the same error)
  • Switch system code page to English-US (the same error)
  • Clone and rebuild many times (the same error)
  • Modify any possible version settings (the same error)

Screenshot (1)

What's wrong / what should be happening instead

Why does a VS2017 (v141) project require VCLibs 14.0 (v140)? And the error message points to the file from Visual Studio itself. I think this is beyond my understanding.

Wish a Visual Studio expert will tell me what happened.

I think this is a problem specific to this project. I can build a UWP Demo project normally. I can also build the earlier commits (58ec472 and earlier).

Screenshot (2)

@SwimmingTiger
Copy link
Author

Try installing VS2015 but it requires 8GB of disk space with C/C++ support. I don't think this is a reasonable solution.

Annotation 2019-05-16 070650

@SwimmingTiger
Copy link
Author

SwimmingTiger commented May 15, 2019

It seems that VCLibs 14.0 is there:

Annotation 2019-05-16 071736

But I always get the error.

@SwimmingTiger
Copy link
Author

Build with command (.\tools\razzle.cmd bcz) will get the same error:

Annotation 2019-05-16 072646

Tried both x64 Native Tools Command Prompt for VS 2017 and x64 Native Tools Command Prompt for VS 2019.

@binarycrusader
Copy link
Member

I've just built the latest gate tip with the latest VS2017 without issue. Can you provide screenshots showing what the Visual Studio Installer shows as installed?

For example, on my system:
image

image

If you run "git status" from the command line in the source directory, does it show any changes?

Have you tried creating a new repository clone?

@oising
Copy link
Collaborator

oising commented May 16, 2019

Just an FYI @SwimmingTiger -- v142 requires v141, but this dependency is hidden from you and is automatically installed. I'd imagine v141 may have a dependency on parts of v140. So installing VS 2015 is not the correct interpretation here.

@binarycrusader
Copy link
Member

See also #565.

@SwimmingTiger
Copy link
Author

@binarycrusader I have the same components as you in VS2017, except IntelliTrace (the community version does not have this feature, this should not matter).

I also installed the same components as #565 in VS2019, but I still have this error.
This should be considered as a new issue. If it doesn't happen to you, maybe it only happens on Windows 10 version 1903 build 18895.1000?

Screenshot (3)

@SwimmingTiger
Copy link
Author

SwimmingTiger commented May 16, 2019

Eventually I solved the problem by "Repair" my VS2017. I noticed that a new directory Microsoft.VCLibs.Desktop.110 was added to C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs (it didn't exist before. I didn't add or remove any components).

Annotation 2019-05-16 070650

This repair also solved the same build problem in VS2019 (I didn't repair VS2019, just repaired VS2017). I guess these files are shared components of all Visual Studio and were corrupted when I uninstalled VS2017 (at that time, I just wanted to keep VS2019) and were not reinstalled correctly after I reinstalled VS2017.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants