I’m trying to install the new Visual Studio 2017 RC on one on my machines.
The first attempt failed during download because of not enough free disc space. After that each try of install it again results in following error/excpetion:
2016-11-17T16:50:08 : Error : Failed to get installed product summaries. [installerId: SetupEngine, error: JsonReaderException at bei Newtonsoft.Json.JsonTextReader.ReadStringIntoBuffer(Char quote)
bei Newtonsoft.Json.JsonTextReader.ParseString(Char quote, ReadType readType)
bei Newtonsoft.Json.JsonTextReader.ReadStringValue(ReadType readType)
bei Newtonsoft.Json.JsonTextReader.ReadAsString()
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType(JsonReader reader, JsonContract contract, Boolean hasConverter)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
bei Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
bei Newtonsoft.Json.JsonSerializer.Deserialize[T](JsonReader reader)
bei Microsoft.VisualStudio.Setup.Serialization.ModelSerializer`1.Deserialize(TextReader reader)
bei Microsoft.VisualStudio.Setup.Cache.InstanceRepository.GetInstance()
bei Microsoft.VisualStudio.Setup.Cache.CacheRepository.<GetInstances>d__25.MoveNext()
bei Microsoft.VisualStudio.Setup.InstalledProductsProviderService.GetInstalledProductSummariesImpl()
bei Microsoft.VisualStudio.Setup.InstalledProductsProviderService.GetInstalledProductSummaries()]
I already tried:
- download and run the installer again
- manual delete C:\Program Files (x86)\Microsoft Visual Studio*
- removed already new installed components (Core Framework, Win SDK etc.)
- uninstalled Visual Studio 15 Preview
I assume that somehow the installer can’t get the information which products are already installed. One line before the excpetion:
2016-11-17T16:50:08 : Verbose : Getting product summaries. [installerId: SetupEngine]
I already know that failed Visual Studio installations sometimes are so messed up that only a OS reinstall solves the problem. But before I do this maybe someone has a solution or hint — basically its «just» a json parsing problem …
- Remove From My Forums
-
Question
-
i need urgent guidance on the error code i got just after installing my Visual studio 2015.I am actually a new user of Visual Studio and missed my .NET training practical as a result of being unable to create name for new project.I tried typing a name
initially but got a prompt with »Visual Studio 2015 Error — General Exception (Exception From HRESULT: 0x80131500)
«please i need help urgently
All replies
-
Hi wiseglend,
What do you mean by «name for new project»?
Please provide the name you have typed.
____________
Ashidacchi -
Hi wiseglend,
Welcome to the MSDN forum.
Do you meet the same error message when you try to create other project types?
Refer to the error message, please have a look at this similar issue:
Visual Studio 2013 > New project > unspecified error (exception from hresult: 0x80004005 (e_fail))
and have a try with the following:- Please run VS 2015 as administrator and create a new project
- Go to Control Panel-Programs and Features, right click the VS 2015, choose Change-Repair to repair VS 2015
- Go to Documents directory and right click each folder, check if they are encrypted by default or not. If so, please uncheck the encrypted option.
- Go to the VS 2015 installation folder like C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE and open cmd to run the command: devenv /safemode to run VS with safe mode, then create new project to test.
Best regards,
Sara
MSDN Community Support
Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
MSDN Support, feel free to contact MSDNFSF@microsoft.com.-
Proposed as answer by
Tuesday, May 9, 2017 9:56 AM
- Please run VS 2015 as administrator and create a new project
- Remove From My Forums
-
Question
-
Attempting to install SSDT 15.7 into a version of Visual Studio Team Explorer 15.7.3 Fails with ‘Unknown Error 0x80131500’. I have opened up the following
issue on the Developer Community site over a month ago and there has not been a hint of feedback.
What is the deal? Will this ever be fixed?
-
Edited by
Art Gola
Monday, June 11, 2018 5:34 PM
-
Edited by
All replies
-
Hi Art Gola,
Thanks for your posting on MSDN forum.
As of now, you can try to install SSDT 15.7 on VS 2017 15.6.7 which available
hereAs far as I know, the SSDT on VS 2017 15.7.X always fails.
For more information, please have a check following discussion:
SSDT cannot install onto 15.7 version of Visual Studio
This issue will be fixed in a future Visual Studio update, if you can’t wait for that the workaround is to completely uninstall Visual Studio and install an older version, e.g. 15.6.7.
Thanks for your understanding and support.
Regards,
Pirlo Zhang
MSDN Community Support
Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
MSDN Support, feel free to contact MSDNFSF@microsoft.com.-
Edited by
Pirlo Zhang
Tuesday, June 12, 2018 9:43 AM
-
Edited by
-
Pirlo:
The 15.7 release of SSDT resolved the installation of SSDT into existing instances of Visual Studio Enterprise. However, I believe there is a separate problem installing into Team Explorer instances. In the link I posted, it appears that with a Visual Studio
Team Explorer install, there is a dependency missing when SSDT attempts to install. -
> As of now, you can try to install SSDT 15.7 on VS 2017 15.6.7 which available here
> As far as I know, the SSDT on VS 2017 15.7.X always fails.Eleven months later… is there any update on this?
> This issue will be fixed in a future Visual Studio update, if you can’t wait for that the workaround
> is to completely uninstall Visual Studio and install an older version, e.g. 15.6.7.Hilarious !!
-
I’m on Visual Studio 16.4.1
I downloaded SSIS from here :
https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
It says this version/installer is for Visual Studio 2019.
But I get the same installer error as above : Unknown Error 0x80131500
Get Microsoft Store back up and running thanks to our expert tips
by Milan Stanojevic
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more
Updated on
- To fix this issue, you should disable certain antivirus and firewall features.
- Changing regional settings can positively affect this error by removing it.
- You can also create a new user account and move all your files to the new one.
The Microsoft Store is an integral part of Windows 10 and 11 since it allows you to download many applications easily. Unfortunately, many users reported Code: 0x80131500 while trying to use Microsoft Store, so today, we’ll show you how to fix it.
The Microsoft Store error code 0x80131500 is highly complex owing to the vast number of underlying causes, which makes it difficult to identify the one in your case. However, troubleshooting will be more streamlined if you have a thorough understanding.
So, to find out all about the error Code: 0x80131500 and the practical solutions, read the following sections.
What causes the code: 0x80131500 error in Microsoft Store?
Here are some of the common reasons that trigger the error Code: 0x80131500 in the Microsoft store:
- Misconfigured Microsoft Store setting
- Incomplete installation of Microsoft Store
- Running an outdated version of the Microsoft Store
- Corrupt app cache
- Issues with the network settings
- Incorrect date and time or regions set on the computer
- Third-party apps, usually antivirus, conflicting with Microsoft Store
Given below are the solutions for the error Code: 0x80131500 in Microsoft Store that worked for most users.
How do I fix the Microsoft Store error code 0x80131500?
- What causes the code: 0x80131500 error in Microsoft Store?
- How do I fix the Microsoft Store error code 0x80131500?
- 1. Reconfigure Internet properties
- 2. Set the date, time, and region correctly
- 3. Change the language to English
- 4. Update Microsoft Store
- 5. Check the services
- 6. Reset the Microsoft Store app
- 7. Reinstall Microsoft Store
- 8. Disable your antivirus and firewall
- 9. Replace your wireless adapter
Let’s first try a few quick solutions before heading over to the slightly complex ones.
- Restart the computer
- Update Windows to the latest available version
- Check the Internet connection and make sure you are receiving a decent speed
If these don’t work, here are the ones that worked for most:
1. Reconfigure Internet properties
This is one of the methods that worked for most users and fixed the Code: 0x80131500 for good. So, do try it. It describes how you can reconfigure the Internet properties correctly with every detail you need, as shown below.
1. Type Internet Options in the Search bar, then click on the relevant search result.
2. Navigate to the Advanced tab, and then scroll down to the bottom of the Settings list.
3. Now, reconfigure the following entries:
- Use SSL 3.0: Uncheck
- Use TLS 1.0: Uncheck
- Use TLS 1.1: Uncheck
- Use TLS 1.2: Check
4. Once done, click on OK to save the changes then reboot the computer for these to apply.
2. Set the date, time, and region correctly
- Press Windows + I to open Settings and select Time & Language.
- If you see an incorrect time here, turn off the toggle for Set time automatically and then click on the Change button under Set the date and time manually.
- Now, manually choose the correct date and time and click on Change.
- Finally, choose the correct Time zone from the dropdown menu, which corresponds to your region.
Once done, restart the computer, and the error with Microsoft Store should be fixed. Also, some users suggested choosing the United States as the region did the trick. So, you might try that as well, then check whether the Microsoft Store error code 0x80131500 is gone.
3. Change the language to English
- Press Windows + I to open Settings, then click on Time & Langauge.
- Navigate to the Language tab from the left and select English (United States) from the Windows display language dropdown menu.
4. Update Microsoft Store
- Type Microsoft Store in the Search bar, and then click on the relevant search result.
- Click on the Library icon near the bottom-left.
- Now, click on the Get updates button.
- If there’s an update for Microsoft Store, it should now install automatically.
Many managed to fix Code: 0x80131500 in Microsoft Store by simply updating the app. However, one user encountered the error after reinstalling a previous iteration of the OS. So, if that’s the case with you, this method may work.
5. Check the services
- Press the Windows key + R, type services.msc, and then press Enter or click OK.
- Locate the Background Intelligent Transfer Service and then double-click it.
- Set Automatic as the Startup type and then hit the Start button below. Now, click the Apply and OK buttons to acknowledge the change.
- Do the same for the Windows Update service.
6. Reset the Microsoft Store app
- Press Windows + I to open Settings, and then click on Apps.
- Locate and select Microsoft Store, and then click on Advanced options.
- Click on the Reset button.
- Again, click Reset in the confirmation prompt.
After the Microsoft Store reset is complete, you shouldn’t come across Code: 0x80131500.
- Error Authenticating With Venmo: 6 Ways to Fix it
- Fix: Internet Speed is Fast, but Video Calls are Slow
- Fix: MSI Afterburner Failed to Start Scanning
- Windows 11 Keeps Chiming? Stop it in 8 Steps
7. Reinstall Microsoft Store
- Type cmd in the Search tab, then click on Run as administrator to start Command Prompt with full privileges.
- Paste the following command to remove the Microsoft Store apps package and then hit Enter:
Get-AppxPackage -allusers *WindowsStore* | Remove-AppxPackage
- Now, execute the following command to reinstall it:
Get-AppxPackage -allusers *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
8. Disable your antivirus and firewall
- Type Security on the Search tab, and then select Windows Security from the results.
- Click on Virus & threat protection.
- If you don’t have a third-party antivirus, turn off the protection. If you have one, click on Open app or open it individually and disable its protection.
Sometimes the Code: 0x80131500 error can appear due to your antivirus or firewall that may block some apps, and you will need to disable it.
However, the issue can persist even after you disable your antivirus, in which case uninstalling the program is the only viable solution.
If you’re using any antivirus solution to remove it from your PC altogether, be sure to check out the best uninstaller software you can use right now.
Plus, if removing the antivirus solves the problem, you should consider switching to a different antivirus. There are many great antivirus solutions available.
We recommend you try an antivirus that offers comprehensive security and online privacy, multi-platform protection, keeps your banking secure, and protects your IoT and webcam.
ESET Internet Security doesn’t interfere with the Microsoft Store and offers intelligent security protection for your PC. So it’s worth giving it a chance, and you won’t be disappointed.
9. Replace your wireless adapter
A few users reported problematic wireless adapter caused this issue adapter. In addition, even though the Internet connection works without problems, users reported problems with the Microsoft Store.
After switching to a different wireless adapter, the issue was fixed, so you might want to try that.
If you don’t have a replacement in mind, you should definitely consider the Wireless USB Wi-Fi Adapter for PC. It has a dual antenna and a top speed of 1200Mbps working in the 802.11AC standard.
- Increased signal with the Dual High Gain Wi-Fi Antenna
- Ultra-fast AC1200 wireless adapter speed
- Super USB 3.0 Wi-Fi adapter for desktop PCs
- 7×24 hours technical support
- Occupies a lot of space
Users also reported the following problems related to the Microsoft Store:
- 0x80131505 Windows 10 Store – This error usually appears when trying to access Microsoft Store, and some issues with your internet connection most likely cause it.
- The server stumbled error code 0x80131500 – It’s just a variation in the message received, so the solutions below will surely fix it. However, it is usually caused by issues connecting with the servers, which could be a problem from your ISP.
- Microsoft Store problems – If you’re having Microsoft Store problems, you might be able to fix this problem by running the Microsoft Store troubleshooter.
- Visual Studio error code: 0x80131500 – This means that you cannot access the Microsoft server or there are issues with the SQL server.
Running into the error Code: 0x80131500 can be really frustrating, especially if you constantly use the Microsoft Store for your favorite apps. But the solutions here are all tried and tested and should get things fixed on your computer.
Also, find the best offline games on Microsoft Store you should download today!
As always, for more suggestions or other questions on the topic of the Microsoft Store error code 0x80131500, reach for the comments section below.
Hi,
First install attempt with the Sphere:
Platform: Windows 10
Installed VS2019 Community products below:
Microsoft Visual Studio Community 2019 Version 16.2.1
VisualStudio.16.Release/16.2.1+29201.188
Microsoft .NET Framework Version 4.7.03056
Installed Version: Community
Visual C++ 2019 00435-60000-00000-AA583
ASP.NET and Web Tools 2019 16.2.290.48383
C# Tools 3.2.0-beta4-19359-03+15b43b33901c88f68ef43f8314b5a2457716780d
IntelliCode Extension 1.0
Microsoft JVM Debugger 1.0
Microsoft MI-Based Debugger 1.0
Microsoft Visual C++ Wizards 1.0
Microsoft Visual Studio VC Package 1.0
NuGet Package Manager 5.2.0
ProjectServicesPackage Extension 1.0
Test Adapter for Boost.Test 1.0
Test Adapter for Google Test 1.0
Visual Basic Tools 3.2.0-beta4-19359-03+15b43b33901c88f68ef43f8314b5a2457716780d
Visual Studio Code Debug Adapter Host Package 1.0
Visual Studio Tools for CMake 1.0
Visual Studio Tools for CMake 1.0
Connected to Sphere OK — COM ports showing OK
Install of SDK fails with error 0x80131500
Log text follows — thanks for any help
[113C:1820][2019-08-07T10:36:08]i001: Burn v3.11.0.1701, Windows v10.0 (Build 17134: Service Pack 0), path: C:\Users\Frank\AppData\Local\Temp{15903CBC-F8F5-409E-A4D6-D83FAAC4FA89}.cr\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe
[113C:1820][2019-08-07T10:36:08]i000: Initializing string variable ‘MbaNetfxPackageId’ to value ‘netfxfullredist_43’
[113C:1820][2019-08-07T10:36:08]i000: Initializing string variable ‘vsixQuiet’ to value ‘yes’
[113C:1820][2019-08-07T10:36:08]i009: Command Line: ‘-burn.clean.room=C:\Users\Frank\Downloads\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe -burn.filehandle.attached=568 -burn.filehandle.self=636’
[113C:1820][2019-08-07T10:36:08]i000: Setting string variable ‘WixBundleOriginalSource’ to value ‘C:\Users\Frank\Downloads\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe’
[113C:1820][2019-08-07T10:36:08]i000: Setting string variable ‘WixBundleOriginalSourceFolder’ to value ‘C:\Users\Frank\Downloads’
[113C:1820][2019-08-07T10:36:08]i000: Setting string variable ‘WixBundleLog’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608.log’
[113C:1820][2019-08-07T10:36:08]i052: Condition ‘(VersionNT >= v6.1)’ evaluates to true.
[113C:1820][2019-08-07T10:36:08]i000: Setting string variable ‘WixBundleName’ to value ‘Azure Sphere SDK Preview for Visual Studio’
[113C:1820][2019-08-07T10:36:08]i000: Setting string variable ‘WixBundleManufacturer’ to value ‘Microsoft Corporation’
[113C:0844][2019-08-07T10:36:09]i000: Setting numeric variable ‘WixStdBALanguageId’ to value 1033
[113C:0844][2019-08-07T10:36:09]i000: Setting version variable ‘WixBundleFileVersion’ to value ‘19.5.4.54816’
[113C:0844][2019-08-07T10:36:09]i000: Visual Studio Instance: Microsoft.VisualStudio.Product.SQL, Version 15.9.28307.770
[113C:0844][2019-08-07T10:36:09]i000: Visual Studio Instance: Microsoft.VisualStudio.Product.Community, Version 16.2.29201.188
[113C:0844][2019-08-07T10:36:09]i000: Setting numeric variable ‘VS2019_16_0_P2_Available’ to value 1
[113C:0844][2019-08-07T10:36:09]i000: Setting numeric variable ‘VS2019_16_0_4_Available’ to value 1
[113C:1820][2019-08-07T10:36:09]i100: Detect begin, 11 packages
[113C:1820][2019-08-07T10:36:09]i000: Product or related product not found: {D0C37DF0-56F6-4D80-BDFC-74EEB20F578D}
[113C:1820][2019-08-07T10:36:09]i000: Setting version variable ‘installedExtensionVersion’ to value ‘0.0.0.0’
[113C:1820][2019-08-07T10:36:09]i000: Setting string variable ‘WindowsBuildNumber’ to value ‘17134’
[113C:1820][2019-08-07T10:36:09]i000: Setting string variable ‘NETFRAMEWORK45’ to value ‘461808’
[113C:1820][2019-08-07T10:36:09]i000: Setting version variable ‘vsixInstallerVersion’ to value ‘16.2.3073.13146’
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘NETFRAMEWORK45 >= 461808’ evaluates to true.
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘NOT (WixBundleAction = 3 AND WixBundleUILevel = 1)’ evaluates to true.
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘NOT (WixBundleAction = 3 AND WixBundleUILevel = 1)’ evaluates to true.
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘(WixBundleAction=3) AND (NOT WixBundleUILevel=1)’ evaluates to false.
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘(WixBundleAction=3) AND (NOT WixBundleUILevel=1)’ evaluates to false.
[113C:1820][2019-08-07T10:36:09]i101: Detected package: NetFx472Redist, state: Present, cached: None
[113C:1820][2019-08-07T10:36:09]i101: Detected package: ConnectedServiceLegacyUninstallQuiet, state: Present, cached: None
[113C:1820][2019-08-07T10:36:09]i101: Detected package: ConnectedServiceUninstallQuietV16, state: Present, cached: None
[113C:1820][2019-08-07T10:36:09]i101: Detected package: VSExtensionVSIXV15, state: Absent, cached: None
[113C:1820][2019-08-07T10:36:09]i101: Detected package: VSExtensionVSIXV16, state: Absent, cached: None
[113C:1820][2019-08-07T10:36:09]i101: Detected package: TapDriverInstaller, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i101: Detected package: AzureSphereCore, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i101: Detected package: SlipService, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i101: Detected package: Sysroot_index0, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i101: Detected package: Sysroot_index1, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i101: Detected package: Sysroot_index2, state: Absent, cached: Complete
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘WindowsBuildNumber >= 14393’ evaluates to true.
[113C:1820][2019-08-07T10:36:09]i052: Condition ‘VS2017_15_9_Available OR VS2019_16_0_4_Available’ evaluates to true.
[113C:1820][2019-08-07T10:36:09]i199: Detect complete, result: 0x0
[113C:0844][2019-08-07T10:36:11]i000: Setting numeric variable ‘EulaAcceptCheckbox’ to value 1
[113C:0844][2019-08-07T10:36:13]i000: Setting numeric variable ‘EulaAcceptCheckbox’ to value 1
[113C:1820][2019-08-07T10:36:13]i200: Plan begin, 11 packages, action: Install
[113C:1820][2019-08-07T10:36:13]w321: Skipping dependency registration on package with no dependency providers: NetFx472Redist
[113C:1820][2019-08-07T10:36:13]w321: Skipping dependency registration on package with no dependency providers: ConnectedServiceLegacyUninstallQuiet
[113C:1820][2019-08-07T10:36:13]w321: Skipping dependency registration on package with no dependency providers: ConnectedServiceUninstallQuietV16
[113C:1820][2019-08-07T10:36:13]w321: Skipping dependency registration on package with no dependency providers: VSExtensionVSIXV15
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_VSExtensionVSIXV15’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_000_VSExtensionVSIXV15.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_VSExtensionVSIXV15’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_000_VSExtensionVSIXV15_rollback.log’
[113C:1820][2019-08-07T10:36:13]w321: Skipping dependency registration on package with no dependency providers: VSExtensionVSIXV16
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_VSExtensionVSIXV16’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_001_VSExtensionVSIXV16.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_VSExtensionVSIXV16’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_001_VSExtensionVSIXV16_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_TapDriverInstaller’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_002_TapDriverInstaller_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_TapDriverInstaller’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_002_TapDriverInstaller.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_AzureSphereCore’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_003_AzureSphereCore_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_AzureSphereCore’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_003_AzureSphereCore.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_SlipService’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_004_SlipService_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_SlipService’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_004_SlipService.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_Sysroot_index0’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_005_Sysroot_index0_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_Sysroot_index0’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_005_Sysroot_index0.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_Sysroot_index1’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_006_Sysroot_index1_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_Sysroot_index1’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_006_Sysroot_index1.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleRollbackLog_Sysroot_index2’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_007_Sysroot_index2_rollback.log’
[113C:1820][2019-08-07T10:36:13]i000: Setting string variable ‘WixBundleLog_Sysroot_index2’ to value ‘C:\Users\Frank\AppData\Local\Temp\dd_VC_AzureSphere_20190807103608_007_Sysroot_index2.log’
[113C:1820][2019-08-07T10:36:13]i201: Planned package: NetFx472Redist, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[113C:1820][2019-08-07T10:36:13]i201: Planned package: ConnectedServiceLegacyUninstallQuiet, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[113C:1820][2019-08-07T10:36:13]i201: Planned package: ConnectedServiceUninstallQuietV16, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[113C:1820][2019-08-07T10:36:13]i201: Planned package: VSExtensionVSIXV15, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[113C:1820][2019-08-07T10:36:13]i201: Planned package: VSExtensionVSIXV16, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[113C:1820][2019-08-07T10:36:13]i201: Planned package: TapDriverInstaller, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i201: Planned package: AzureSphereCore, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i201: Planned package: SlipService, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i201: Planned package: Sysroot_index0, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i201: Planned package: Sysroot_index1, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i201: Planned package: Sysroot_index2, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[113C:1820][2019-08-07T10:36:13]i299: Plan complete, result: 0x0
[113C:1820][2019-08-07T10:36:13]i300: Apply begin
[113C:1820][2019-08-07T10:36:13]i010: Launching elevated engine process.
[113C:1820][2019-08-07T10:36:15]i011: Launched elevated engine process.
[113C:1820][2019-08-07T10:36:15]i012: Connected to elevated engine.
[1DF0:22C8][2019-08-07T10:36:15]i358: Pausing automatic updates.
[1DF0:22C8][2019-08-07T10:36:15]i359: Paused automatic updates.
[1DF0:22C8][2019-08-07T10:36:15]i360: Creating a system restore point.
[1DF0:22C8][2019-08-07T10:36:16]i361: Created a system restore point.
[1DF0:22C8][2019-08-07T10:36:16]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, options: 0x7, disable resume: No
[1DF0:22C8][2019-08-07T10:36:16]i000: Caching bundle from: ‘C:\Users\Frank\AppData\Local\Temp{D2CBDC0B-7057-4ECF-BA72-7298F7910F33}.be\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe’ to: ‘C:\ProgramData\Package Cache{afaa4203-0409-4e16-ad86-0c52321dc834}\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe’
[1DF0:22C8][2019-08-07T10:36:16]i320: Registering bundle dependency provider: {afaa4203-0409-4e16-ad86-0c52321dc834}, version: 19.5.4.54816
[1DF0:22C8][2019-08-07T10:36:16]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: Active, restart initiated: No, disable resume: No
[1DF0:0C24][2019-08-07T10:36:16]i305: Verified acquired payload: VSExtensionVSIXV15 at path: C:\ProgramData\Package Cache.unverified\VSExtensionVSIXV15, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe.
[1DF0:0C24][2019-08-07T10:36:16]i305: Verified acquired payload: pay4F357484EB30226D85A1F8D7990E3A62 at path: C:\ProgramData\Package Cache.unverified\pay4F357484EB30226D85A1F8D7990E3A62, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: pay604BC1C19D2A4CFD8C3B77865142EA44 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe.
[1DF0:0C24][2019-08-07T10:36:16]i305: Verified acquired payload: pay7A13C3CF128AFA2EF560FFF6492A76EB at path: C:\ProgramData\Package Cache.unverified\pay7A13C3CF128AFA2EF560FFF6492A76EB, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V16.vsix.
[1DF0:22C8][2019-08-07T10:36:16]i052: Condition ‘(vsixQuiet = «yes») OR (WixBundleUILevel=2)’ evaluates to true.
[1DF0:22C8][2019-08-07T10:36:16]i301: Applying execute package: VSExtensionVSIXV15, action: Install, path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe, arguments: ‘»C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe» /admin /shutdownprocesses «Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix» /q’
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: VSExtensionVSIXV16 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: pay4F357484EB30226D85A1F8D7990E3A62 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: pay604BC1C19D2A4CFD8C3B77865142EA44 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\VSIXBootstrapper.exe.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: pay7A13C3CF128AFA2EF560FFF6492A76EB at path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V16.vsix.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: TapDriverInstaller at path: C:\ProgramData\Package Cache{BF7D823B-6E5F-433B-9C85-E9EECB1124BC}v2.2.0\packages\TapDriverInstaller\TapDriverInstaller.msi.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: AzureSphereCore at path: C:\ProgramData\Package Cache{DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}v19.05.4.53731\packages\AzureSphereCore\AzureSphereCore.msi.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: SlipService at path: C:\ProgramData\Package Cache{15D970F1-2AB1-4553-94E0-12DEC338AF1F}v19.5.4.53731\packages\SlipService\Azure Sphere Device Communication Service.msi.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: Sysroot_index0 at path: C:\ProgramData\Package Cache{CB7B85C6-65E4-4313-B137-1CD5A66D52E3}v19.02.3.59866\Sysroot0.msi.
[1DF0:0C24][2019-08-07T10:36:16]i304: Verified existing payload: Sysroot_index1 at path: C:\ProgramData\Package Cache{F5C48017-9F0C-4496-A7F3-F7575F918838}v19.05.4.44931\Sysroot1.msi.
[1DF0:0C24][2019-08-07T10:36:17]i304: Verified existing payload: Sysroot_index2 at path: C:\ProgramData\Package Cache{992C25E5-6E67-4B8C-99A7-692329CE45D6}v19.05.4.44935\Sysroot2.msi.
[1DF0:22C8][2019-08-07T10:36:45]e000: Error 0x80131500: Process returned error: 0x80131500
[1DF0:22C8][2019-08-07T10:36:45]e000: Error 0x80131500: Failed to execute EXE package.
[113C:1820][2019-08-07T10:36:45]e000: Error 0x80131500: Failed to configure per-machine EXE package.
[113C:1820][2019-08-07T10:36:45]i319: Applied execute package: VSExtensionVSIXV15, result: 0x80131500, restart: None
[113C:1820][2019-08-07T10:36:45]e000: Error 0x80131500: Failed to execute EXE package.
[1DF0:22C8][2019-08-07T10:36:45]i351: Removing cached package: VSExtensionVSIXV15, from path: C:\ProgramData\Package Cache\VSIXBootstrapper.19.5.4.54816
[1DF0:22C8][2019-08-07T10:36:45]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: None, restart: None, disable resume: No
[1DF0:22C8][2019-08-07T10:36:45]i330: Removed bundle dependency provider: {afaa4203-0409-4e16-ad86-0c52321dc834}
[1DF0:22C8][2019-08-07T10:36:45]i352: Removing cached bundle: {afaa4203-0409-4e16-ad86-0c52321dc834}, from path: C:\ProgramData\Package Cache{afaa4203-0409-4e16-ad86-0c52321dc834}
[1DF0:22C8][2019-08-07T10:36:45]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: None, restart initiated: No, disable resume: No
[113C:1820][2019-08-07T10:36:45]i399: Apply complete, result: 0x80131500, restart: None, ba requested restart: No