Error 1 File 'Windows.props' not found. Visual Studio 2013 Premium











up vote
1
down vote

favorite












I'm getting the error Error 1 File 'Windows.props' not found. every time I try to build a JS Store app (Windows, Windows Phone or Universal).



I've been getting this error ever since i installed the 'Windows Phone 8.1 Emulator', I have tried restoring my PC to a previous state (a day before the installation), repairing multiple times, removing the Emulator, re-installing Visual Studio and I have also tried building on a different user account.



According to a few sources on the internet the windows.props file should be located in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1ReferencesCommonConfigurationNeutral




Its not located in that directory. But I did locate the Windows.props file in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1DesignTimeCommonConfigurationNeutral




There is a Stackoverflow question similar to this but I couldn't find an answer that helped me.



Here is the information contained in my registry



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhonev8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindows Phonev8.1



and



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhoneAppv8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1



The complete error is




C:Program Files
(x86)MSBuildMicrosoftVisualStudiov12.0AppxPackageMicrosoft.AppXPackage.Tar‌​gets(561,9):
error APPX1639: File 'Windows.props' not found. See
go.microsoft.com/fwlink/… for more information











share|improve this question
























  • @Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
    – aleks
    Jun 24 '14 at 15:35












  • Be sure you have VS2013 Update 2 installed
    – Ramhound
    Jun 24 '14 at 15:41










  • You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
    – Ramhound
    Jun 24 '14 at 15:57












  • @Ramhound what do you mean by "Place the file indicated by the current registry value"?
    – aleks
    Jun 24 '14 at 15:59












  • The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
    – Ramhound
    Jun 24 '14 at 16:03

















up vote
1
down vote

favorite












I'm getting the error Error 1 File 'Windows.props' not found. every time I try to build a JS Store app (Windows, Windows Phone or Universal).



I've been getting this error ever since i installed the 'Windows Phone 8.1 Emulator', I have tried restoring my PC to a previous state (a day before the installation), repairing multiple times, removing the Emulator, re-installing Visual Studio and I have also tried building on a different user account.



According to a few sources on the internet the windows.props file should be located in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1ReferencesCommonConfigurationNeutral




Its not located in that directory. But I did locate the Windows.props file in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1DesignTimeCommonConfigurationNeutral




There is a Stackoverflow question similar to this but I couldn't find an answer that helped me.



Here is the information contained in my registry



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhonev8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindows Phonev8.1



and



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhoneAppv8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1



The complete error is




C:Program Files
(x86)MSBuildMicrosoftVisualStudiov12.0AppxPackageMicrosoft.AppXPackage.Tar‌​gets(561,9):
error APPX1639: File 'Windows.props' not found. See
go.microsoft.com/fwlink/… for more information











share|improve this question
























  • @Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
    – aleks
    Jun 24 '14 at 15:35












  • Be sure you have VS2013 Update 2 installed
    – Ramhound
    Jun 24 '14 at 15:41










  • You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
    – Ramhound
    Jun 24 '14 at 15:57












  • @Ramhound what do you mean by "Place the file indicated by the current registry value"?
    – aleks
    Jun 24 '14 at 15:59












  • The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
    – Ramhound
    Jun 24 '14 at 16:03















up vote
1
down vote

favorite









up vote
1
down vote

favorite











I'm getting the error Error 1 File 'Windows.props' not found. every time I try to build a JS Store app (Windows, Windows Phone or Universal).



I've been getting this error ever since i installed the 'Windows Phone 8.1 Emulator', I have tried restoring my PC to a previous state (a day before the installation), repairing multiple times, removing the Emulator, re-installing Visual Studio and I have also tried building on a different user account.



According to a few sources on the internet the windows.props file should be located in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1ReferencesCommonConfigurationNeutral




Its not located in that directory. But I did locate the Windows.props file in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1DesignTimeCommonConfigurationNeutral




There is a Stackoverflow question similar to this but I couldn't find an answer that helped me.



Here is the information contained in my registry



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhonev8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindows Phonev8.1



and



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhoneAppv8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1



The complete error is




C:Program Files
(x86)MSBuildMicrosoftVisualStudiov12.0AppxPackageMicrosoft.AppXPackage.Tar‌​gets(561,9):
error APPX1639: File 'Windows.props' not found. See
go.microsoft.com/fwlink/… for more information











share|improve this question















I'm getting the error Error 1 File 'Windows.props' not found. every time I try to build a JS Store app (Windows, Windows Phone or Universal).



I've been getting this error ever since i installed the 'Windows Phone 8.1 Emulator', I have tried restoring my PC to a previous state (a day before the installation), repairing multiple times, removing the Emulator, re-installing Visual Studio and I have also tried building on a different user account.



According to a few sources on the internet the windows.props file should be located in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1ReferencesCommonConfigurationNeutral




Its not located in that directory. But I did locate the Windows.props file in the following directory.




C:Program Files (x86)Windows Phone
Kits8.1DesignTimeCommonConfigurationNeutral




There is a Stackoverflow question similar to this but I couldn't find an answer that helped me.



Here is the information contained in my registry



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhonev8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindows Phonev8.1



and



HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKsWindowsPhoneAppv8.1Install Path was set to C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1



The complete error is




C:Program Files
(x86)MSBuildMicrosoftVisualStudiov12.0AppxPackageMicrosoft.AppXPackage.Tar‌​gets(561,9):
error APPX1639: File 'Windows.props' not found. See
go.microsoft.com/fwlink/… for more information








windows windows-8 emulator windows-phone visual-studio-2013






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 23 '17 at 12:41









Community

1




1










asked Jun 24 '14 at 15:31









aleks

614




614












  • @Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
    – aleks
    Jun 24 '14 at 15:35












  • Be sure you have VS2013 Update 2 installed
    – Ramhound
    Jun 24 '14 at 15:41










  • You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
    – Ramhound
    Jun 24 '14 at 15:57












  • @Ramhound what do you mean by "Place the file indicated by the current registry value"?
    – aleks
    Jun 24 '14 at 15:59












  • The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
    – Ramhound
    Jun 24 '14 at 16:03




















  • @Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
    – aleks
    Jun 24 '14 at 15:35












  • Be sure you have VS2013 Update 2 installed
    – Ramhound
    Jun 24 '14 at 15:41










  • You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
    – Ramhound
    Jun 24 '14 at 15:57












  • @Ramhound what do you mean by "Place the file indicated by the current registry value"?
    – aleks
    Jun 24 '14 at 15:59












  • The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
    – Ramhound
    Jun 24 '14 at 16:03


















@Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
– aleks
Jun 24 '14 at 15:35






@Ramhound no the error only provides a <a hre="go.microsoft.com/fwlink/…>. I tried copying it from `C:Program Files (x86)Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral` but it still gives the same error.
– aleks
Jun 24 '14 at 15:35














Be sure you have VS2013 Update 2 installed
– Ramhound
Jun 24 '14 at 15:41




Be sure you have VS2013 Update 2 installed
– Ramhound
Jun 24 '14 at 15:41












You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
– Ramhound
Jun 24 '14 at 15:57






You have two options. Place the file indicated by the current registry value or change the registry value to the current location of the file. Can you please take 2-3 minutes and format the question so its not a huge block of text?
– Ramhound
Jun 24 '14 at 15:57














@Ramhound what do you mean by "Place the file indicated by the current registry value"?
– aleks
Jun 24 '14 at 15:59






@Ramhound what do you mean by "Place the file indicated by the current registry value"?
– aleks
Jun 24 '14 at 15:59














The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
– Ramhound
Jun 24 '14 at 16:03






The build script is attempting to locate the file in the following location C:Program Files (x86)Microsoft SDKsWindowsPhoneAppv8.1 and since its actually located in C:Program Files (x86) Windows Phone Kits8.1DesignTimeCommonConfigurationNeutral the build script fails. Using the verbose logging would have indicated this.
– Ramhound
Jun 24 '14 at 16:03












1 Answer
1






active

oldest

votes

















up vote
0
down vote













I faced same issues for Visual Studio 2013 Ultimate. Repairing VS fixed the problem. I believe this issue is caused because the updates doesn't get installed properly for unknown reasons.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f772845%2ferror-1-file-windows-props-not-found-visual-studio-2013-premium%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    I faced same issues for Visual Studio 2013 Ultimate. Repairing VS fixed the problem. I believe this issue is caused because the updates doesn't get installed properly for unknown reasons.






    share|improve this answer

























      up vote
      0
      down vote













      I faced same issues for Visual Studio 2013 Ultimate. Repairing VS fixed the problem. I believe this issue is caused because the updates doesn't get installed properly for unknown reasons.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        I faced same issues for Visual Studio 2013 Ultimate. Repairing VS fixed the problem. I believe this issue is caused because the updates doesn't get installed properly for unknown reasons.






        share|improve this answer












        I faced same issues for Visual Studio 2013 Ultimate. Repairing VS fixed the problem. I believe this issue is caused because the updates doesn't get installed properly for unknown reasons.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 22 '14 at 16:29









        Kishor Patil

        11




        11






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f772845%2ferror-1-file-windows-props-not-found-visual-studio-2013-premium%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            AnyDesk - Fatal Program Failure

            How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

            QoS: MAC-Priority for clients behind a repeater