MS Build Tools installed but Xamarin won't Update

I have installed build tools 2013, 2015 Update 3 and 2017, but when I try install Xamarin 4.3.609 Beta (or even current Stable to do a re-install) from VS 2015 Community Update 3 I get:
_"This setup requires Microsoft Build Tools 2015 package to be installed for this installation to continue."
I have uninstalled and re-installed VS2015, the Build tools, Xamarin (I can only re-install this through the VS2015 installer), tried with only 2015, and only with 2015 and 2013, and have run the VS2015 repair.

The Build Tools 2015 package is detected as per below line from the log in MonoDevelop4.0\Cache folder:
MSI (c) (F0:24) [09:34:28:419]: PROPERTY CHANGE: Adding MSBUILDTOOLS2015_VERSION property. Its value is '2.0'.
MSI (c) (F0:24) [09:34:28:419]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\MSBuild\15.0 3: 2

I need to update Xamarin so I can resolve another issue that was fixed in later release, has anyone resolved the above issue before?


  • AlanClarkAlanClark USForum Administrator, Xamarin Team Xamurai

    @MarcelSaturnyne Could you try running VS2015 as administrator and see if you still have the same issue?

  • @AlanClark Thank you for the reply, I forgot to mention that I did try running the VS 2015 IDE as Administrator in my previous steps.

    I have however resolved the issue this morning. Just because you run the IDE as Admin does not mean the IDE will execute the MSI as an Admin.

    What ended up working for me was to open a Command Prompt as an Administrator and run the below two commands:

    cd %LocalAppData%\MonoDevelop-4.0\Cache\TempDownload msiexec.exe /i CEEB6A85-3EE8-4027-8DDA-747947CA970D-40300609.msi

    This then breaks Xamarin completely however, and one has to perform a repair by double clicking the .msi as a normal user and following the prompts.

    This has allowed me to get past the MS Build Tools not found error successfully and VS2015 reports the correct, updated, Xamarin version.

    I do hope that the above steps won't be my ongoing upgrade path :)

Sign In or Register to comment.