Developer technologies | Universal Windows Platform (UWP)
A Microsoft platform for building and publishing apps for Windows devices.
error APPX3217: SDK folder containing 'UAP.props' for 'UAP 10.0.17763.0' cannot be located.
![](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(256, 0%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
Hong
1,456
Reputation points
Building a UWP app with VS 2022 fails with the following error:
C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets(1131,5): error APPX3217: SDK folder containing 'UAP.props' for 'UAP 10.0.17763.0' cannot be located. See http://go.microsoft.com/fwlink/?LinkID=798187 for more information.
When I try to install Windows 10 SDK, version 1809 (10.0.17763.0), I get the following error:
Could anyone offer a tip on how to remedy this?
Developer technologies | Universal Windows Platform (UWP)
{count} votes
-
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2023-06-05T09:00:42.2633333+00:00 Could you reproduce this issue from a blank UWP project? Please try in a Blank project and confirm if this is an issue about the VS environment.
-
Hong 1,456 Reputation points
2023-06-06T12:22:47.0566667+00:00 I have another UWP app that builds without any problem.
I updated VS from 17.5.5 to 17.6.2. This error is gone but other errors showed up immediately after the update.
-
Anonymous
2023-06-08T02:13:50.49+00:00 This seems to be a Visual Studio issue. Since you've raised feedback in the VS DC, and VS engineers are checking this, please focus on that feedback.
Sign in to comment
Sign in to answer