Error code 0x80131500 visual studio 2019

So recently, i have reinstalled windows, and now i have windows 10, i did some optimization, and installed some of my games, and apps, then i installed Visual Studio Community 2019, then i decided to

So recently, i have reinstalled windows, and now i have windows 10, i did some optimization, and installed some of my games, and apps, then i installed Visual Studio Community 2019, then i decided to create a new game, since i was bored, but when i tried to load the Designer file (Form1.vb [Designer]) it said IntelliSense finished initializing, but an error occurred while trying to load the document, and with the error code: 0x80131500, i tried disabling fast preview, and i tried relaunching, no luck. I haven’t found other solutions. And i put my projects in DesktopMy DocsVisual Studio ProjectsVisual BasicGameTest (Name of the game)

What do i do?

asked Mar 10, 2021 at 13:41

ridhomblr's user avatar

1

I thought the only way was to reset my PC and reinstall visual studio, but then I thought of resetting visual studio and it helped.
The error is basically due to some errors in importing the files. So I tried to reset the vs settings by simply going over to

tools>import and export settings>reset all setings>general

and hit next.

answered May 12, 2021 at 13:20

MATRIX LLC's user avatar

i just logged out from my account and it works for me

answered Apr 4, 2021 at 11:23

gega abzianidze's user avatar

1

When creating the new project as the .NET framework , you have to select the .NET Core 5 as the targeted framework. Do Not choose .NET Core 3.1 (Long Term Used).
Hope this gonna work For you!

answered Mar 26, 2021 at 5:09

Nethmi Perera's user avatar

simply close the designer tab and press shift+f7
it will load refresh.

answered Nov 19, 2021 at 15:06

Savita maan's user avatar

Open your visual studio —-> open your project ——> go to your solution explorer and double click on your prject —> change Target framework To (net472)——> again go to your solution explorer and click right on your project and click on properties and change target framework to 4.7.2
Restart visual studio
That will successfully and work with me and will work with you

answered Jan 7, 2022 at 1:52

Feras Abo Aloun's user avatar

1

  • Remove From My Forums
  • Question

  • Because I did see only an empty ssis toolboxI tried to reinstall SSIS Version 3.4 and I got an error and following protokol:

    [0A70:1AA8][2020-03-04T18:45:56]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: .DownloadsMicrosoft.DataTools.IntegrationServices.exe, cmdline: »
    [0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable ‘ProductVersionVar’ to value ‘15.0.2000.71’
    [0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable ‘ReleaseVersion’ to value ‘3.4’
    [0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable ‘LicenseTermsUrl’ to value ‘https://go.microsoft.com/fwlink/?LinkID=853828&clcid=’
    [0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable ‘PreviewStatementUrl’ to value

    ../ some lines I had to delete because of size / ..

    [27A0:0C4C][2020-03-04T18:47:31]i301: Applying execute package: SSAS_AMO2016, action: Repair, path: C:ProgramDataPackage Cache{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14payloadSQL_AS_AMO2016.msi, arguments: ‘ ARPSYSTEMCOMPONENT=»1″ MSIFASTINSTALL=»7″‘
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 47
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 24, Overall progress: 48
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 37, Overall progress: 49
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 63, Overall progress: 51
    [0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 76, Overall progress: 52
    [0A70:1AA8][2020-03-04T18:47:32]i000: MainViewModel.OnPackageActionProgress: Percent completed: 89, Overall progress: 53
    [0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server 2016 Analysis Management Objects (id: SSAS_AMO2016)
    [0A70:1AA8][2020-03-04T18:47:40]i319: Applied execute package: SSAS_AMO2016, result: 0x0, restart: None
    [27A0:0C4C][2020-03-04T18:47:40]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {97A881AD-5134-4CD2-A6A8-371C83E5622B}, package: SSAS_AMO2016
    [27A0:0C4C][2020-03-04T18:47:40]i323: Registering package dependency provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, version: 13.1.4561.14, package: SSAS_OLEDB2016
    [0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
    [27A0:0C4C][2020-03-04T18:47:40]i301: Applying execute package: SSAS_OLEDB2016, action: Repair, path: C:ProgramDataPackage Cache{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14payloadSQL_AS_OLEDB2016.msi, arguments: ‘ ARPSYSTEMCOMPONENT=»1″
    MSIFASTINSTALL=»7″‘
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 55
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 28, Overall progress: 56
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 41, Overall progress: 57
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 54, Overall progress: 58
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 67, Overall progress: 59
    [0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 80, Overall progress: 60
    [0A70:1AA8][2020-03-04T18:47:42]i000: MainViewModel.OnPackageActionProgress: Percent completed: 95, Overall progress: 61
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
    [0A70:1AA8][2020-03-04T18:47:45]i319: Applied execute package: SSAS_OLEDB2016, result: 0x0, restart: None
    [27A0:0C4C][2020-03-04T18:47:45]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, package: SSAS_OLEDB2016
    [27A0:0C4C][2020-03-04T18:47:45]i323: Registering package dependency provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, version: 14.0.3002.563, package: SSDTISSingleton140
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
    [27A0:0C4C][2020-03-04T18:47:45]i301: Applying execute package: SSDTISSingleton140, action: Repair, path: C:ProgramDataPackage Cache{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563payloadSSDTISSingleton140.msi, arguments: ‘ MSIFASTINSTALL=»7″‘
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 62
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 63
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 64
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 48, Overall progress: 65
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 66
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 73, Overall progress: 67
    [0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 84, Overall progress: 68
    [0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageActionProgress: Percent completed: 98, Overall progress: 69
    [0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
    [0A70:1AA8][2020-03-04T18:47:46]i319: Applied execute package: SSDTISSingleton140, result: 0x0, restart: None
    [27A0:0C4C][2020-03-04T18:47:46]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, package: SSDTISSingleton140
    [27A0:0C4C][2020-03-04T18:47:46]i323: Registering package dependency provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, version: 15.0.2000.71, package: SSDTISSingleton
    [0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
    [27A0:0C4C][2020-03-04T18:47:46]i301: Applying execute package: SSDTISSingleton, action: Repair, path: C:ProgramDataPackage Cache{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71payloadSSDTISSingleton.msi, arguments: ‘ MSIFASTINSTALL=»7″‘
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 70
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 71
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 72
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 56, Overall progress: 73
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 74
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 75, Overall progress: 75
    [0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 88, Overall progress: 76
    [0A70:1AA8][2020-03-04T18:47:51]i000: BootstrapperEngineDataModel.OnExecutePackageComplete: Package requires a restart but it has not been initiated yet.
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
    [0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: SSDTISSingleton, result: 0x0, restart: Required
    [27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, package: SSDTISSingleton
    [27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsixPreInstall, version: 1.0.0.0, package: ISVsixPreInstall
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
    [27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsixPreInstall, action: Install, path: C:ProgramDataPackage Cache2FC1517AABA51C6B742AD49998003E7910042F0EISVsixPreInstall.exe, arguments: ‘»C:ProgramDataPackage Cache2FC1517AABA51C6B742AD49998003E7910042F0EISVsixPreInstall.exe»
    /instanceIds:»33f63265″ /log:».AppDataLocalTempSsdtisSetupMicrosoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log»‘
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 80
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 84
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
    [0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: ISVsixPreInstall, result: 0x0, restart: None
    [27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package: ISVsixPreInstall
    [27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsix, version: 1.0.0.0, package: ISVsix
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
    [27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsix, action: Install, path: C:ProgramDataPackage Cache15160B731819F56D87A626F9A2777550340022D7VSIXBootstrapper.exe, arguments: ‘»C:ProgramDataPackage Cache15160B731819F56D87A626F9A2777550340022D7VSIXBootstrapper.exe»
    /q /admin /instanceIds:»33f63265″ /logFile:».AppDataLocalTempSsdtisSetupMicrosoft.DataTools.IntegrationServices_20200304184556_11_ISVsix.log» «payloadMicrosoft.DataTools.IntegrationServices.vsix»‘
    [0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 88
    [27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Process returned error: 0x80131500
    [27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
    [0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to configure per-machine EXE package.
    [0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
    [0A70:1AA8][2020-03-04T18:48:10]i319: Applied execute package: ISVsix, result: 0x80131500, restart: None
    [0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
    [27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsix, package: ISVsix
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsix, from path: C:ProgramDataPackage Cache15160B731819F56D87A626F9A2777550340022D7
    [27A0:0C4C][2020-03-04T18:48:10]i326: Removed dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package ISVsixPreInstall
    [0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
    [0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 92
    [27A0:0C4C][2020-03-04T18:48:10]i301: Applying rollback package: ISVsixPreInstall, action: Uninstall, path: C:ProgramDataPackage Cache2FC1517AABA51C6B742AD49998003E7910042F0EISVsixPreInstall.exe, arguments: ‘»C:ProgramDataPackage Cache2FC1517AABA51C6B742AD49998003E7910042F0EISVsixPreInstall.exe»
    /instanceIds:»33f63265″ /log:».AppDataLocalTempSsdtisSetupMicrosoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log» /u’
    [0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
    [0A70:1AA8][2020-03-04T18:48:10]i319: Applied rollback package: ISVsixPreInstall, result: 0x0, restart: None
    [27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsixPreInstall, package: ISVsixPreInstall
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsixPreInstall, from path: C:ProgramDataPackage Cache2FC1517AABA51C6B742AD49998003E7910042F0E
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton, from path: C:ProgramDataPackage Cache{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton140, from path: C:ProgramDataPackage Cache{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_OLEDB2016, from path: C:ProgramDataPackage Cache{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2016, from path: C:ProgramDataPackage Cache{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2014, from path: C:ProgramDataPackage Cache{76CBDC35-0752-4B5A-83E8-49A741BD42BC}v12.2.5626.31
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2012, from path: C:ProgramDataPackage Cache{53086A62-13F3-4FC5-AA41-211FD74340B3}v11.4.7001.0
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2016, from path: C:ProgramDataPackage Cache{1F86F7A6-BCC6-49C4-8033-785993FA6331}v13.1.4561.14
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2014, from path: C:ProgramDataPackage Cache{07001141-C74D-47ED-B03D-892C7EF00E3D}v12.2.5626.31
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2012, from path: C:ProgramDataPackage Cache{DB97C76B-9116-42C5-8814-0041856EB9E6}v11.4.7001.0
    [27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: VCRedist2010, from path: C:ProgramDataPackage Cache28C54491BE70C38C97849C3D8CFBFDD0D3C515CB
    [0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
    [0A70:1AA8][2020-03-04T18:48:10]i000: BootstrapperEngineDataModel.OnApplyComplete: Bundle requires a restart but it has not been initiated yet.
    [0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:Usersobresl01AppDataLocalTempdd_VSIXInstaller_20200303165453_2594.log …
    [0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:54:53, which is too old. Skip processing.
    [0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:Usersobresl01AppDataLocalTempdd_VSIXInstaller_20200303165453_2f54.log …
    [0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:57:04, which is too old. Skip processing.
    [0A70:1AA8][2020-03-04T18:48:10]e000: MainViewModel.OnBundleAction: Bundle action failed: Unknown error (0x80131500) (0x80131500)
    [0A70:1AA8][2020-03-04T18:48:10]i399: Apply complete, result: 0x80131500, restart: Required, ba requested restart:  No
    [0A70:0C04][2020-03-04T18:48:17]i000: MainViewModel.OpenUrl: Opening url: .AppDataLocalTempSsdtisSetupMicrosoft.DataTools.IntegrationServices_20200304184556.log

    Somebody can help?

    regards

    Olaf


    olaf870

    • Moved by

      Thursday, March 5, 2020 2:00 AM
      more appropriate

Answers

  • Thank you Mona,

    the install package SSIS 3.4 seems to have a defect with VS 2019.

    I tried to remove the installation of SSIS 3.4, but it failed too. Now I installed SSIS 3.3 over 3.4 and now VS 2019 can open SSIS-Projects again.

    Thanks

    regard Olaf


    olaf870

    • Marked as answer by
      olaf870
      Thursday, March 5, 2020 11:04 AM

Как исправить ошибку 0x80131500 в Microsoft StoreОдна из самых распространенных ошибок в магазине приложений Windows 11 и Windows 10 — ошибка с кодом 0x80131500. Причины ошибки могут быть разными, но проблему обычно сравнительно легко решить.

В этой инструкции подробно о способах исправить ошибку «Код: 0x80131500» в Microsoft Store различными способами, начиная с простых и часто срабатывающих, заканчивая более сложными.

Средство устранения неполадок Microsoft Store

Первый способ редко срабатывает, но начать рекомендую именно с него. Попробуйте использовать встроенное средство устранения неполадок Microsoft Store. Для этого:

  1. В Windows 11 перейдите в Параметры — Система — Устранение неполадок — Другие средства устранения неполадок.
  2. В Windows 10 перейдите в Параметры — Обновление и безопасность — Устранение неполадок — Дополнительные средства устранения неполадок.
  3. Запустите средство устранения неполадок «Приложения из Магазина Windows». Устранение неполадок приложения из Магазина Windows
  4. Следуйте указаниям мастера устранения неполадок для поиска и попытки автоматического исправления найденных ошибок. Средство устранения неполадок исправило ошибки Microsoft Store

Если какие-либо ошибки были исправлены, попробуйте перезапустить Microsoft Store и проверить, появляется ли ошибка с кодом 0x80131500 снова.

Очистка кэша и сброс Microsoft Store

Следующий метод — очистка кэша и сброс приложения Microsoft Store. Выполните следующие шаги:

  1. Перейдите в Параметры — Приложения — приложения и возможности.
  2. Найдите Microsoft Store в списке приложений, нажмите по трем точкам справа и выберите «Дополнительные параметры». Открыть дополнительные параметры Microsoft Store
  3. Используйте кнопки «Исправить» и «Сбросить» в разделе сброса приложения. Исправление и сброс Microsoft Store
  4. Нажмите правой кнопкой мыши по кнопке «Пуск», выберите пункт «Выполнить», введите wsreset.exe и нажмите Enter. На некоторое время появится пустое окно консоли, затем оно закроется и Microsoft Store будет запущен автоматически.

После повторного запуска Microsoft Store проверьте, была ли решена проблема.

Решение проблем с доступом к серверам Майкрософт

Причиной ошибки 0x80131500 в Microsoft Store могут быть те или иные проблемы при попытке доступа к соответствующим серверам Майкрософт. Что можно попробовать:

  1. При наличии стороннего антивируса или файрволла попробуйте временно отключить их и проверить, была ли решена проблема.
  2. Если вы использовали какие-либо сторонние утилиты для отключения обновлений Windows, отключения телеметрии и подобных задач, они могли заблокировать доступ к серверам Майкрософт. Попробуйте сбросить настройки брандмауэра Windows и восстановить файл hosts — из него потребуется удалить все строки, блокирующие доступ к серверам.
  3. Если вы используете сервисы VPN/прокси, проверьте, сохраняется ли ошибка, если их отключить. Отключите автоматическое определение параметров прокси-сервера (подробнее: Как отключить прокси-сервер Windows 10).
  4. Проверьте, исчезает ли ошибка, если настроить популярные публичные DNS в Windows, здесь могут помочь статьи: Как изменить DNS в Windows 11, Как изменить DNS-сервер в Windows 10.
  5. Включите TLS 1.2 и TLS 1.3, если они отключены. Для этого можно зайти в Панель управления, открыть «Свойства браузера» (или нажать клавиши Win+R и ввести inetcpl.cpl), включить соответствующие пункты и применить настройки. Включение TLS 1.2 в Windows

Перерегистрация или переустановка Microsoft Store

Для исправления ошибки можно попробовать выполнить переустановку приложения Microsoft Store, для этого:

  1. Запустите PowerShell или Windows Терминал (с открытой консолью PowerShell) от имени Администратора. Сделать это можно через контекстное меню кнопки «Пуск».
  2. Введите следующую команду и нажмите Enter
    Get-AppxPackage *windowsstore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppxManifest.xml"}

После выполнения команды закройте окно PowerShell и проверьте работу Microsoft Store.

Также можно попробовать удалить и повторно установить Microsoft Store (под свою ответственность, возможны проблемы). Для этого используем по порядку следующие две команды:

Get-AppxPackage -allusers *windowsstore* | Remove-AppxPackage
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

Если предлагаемые методы не помогли, обратите внимание на следующие возможные варианты решения:

  1. Проверьте настройки даты, времени и часового пояса в Windows, убедитесь, что они настроены правильно. Установите правильный регион в параметрах Windows. Исправить дату, время и регион в параметрах Windows
  2. В службах Windows (Win+Rservices.msc) найдите «Фоновая интеллектуальная служба передачи (BITS)», дважды нажмите по ней и, если в «Тип запуска» установлено «Отключена», измените на «Вручную» и примените настройки. Исправление службы BITS в Windows
  3. Используйте точки восстановления системы на дату, когда ошибка 0x80131500 не появлялась. Подробнее: Точки восстановления Windows 11, Точки восстановления Windows 10.
  4. Выполните проверку и восстановление целостности системных файлов. Как восстановить системные файлы Windows 11, Как восстановить системные файлы Windows 10.
  5. Можно попробовать создать новую учетную запись Windows (Как создать пользователя Windows 10, большинство способов аналогичны и в Windows 11), зайти под ним и проверить, появляется ли ошибка в магазине приложений под новым пользователем.
  6. Попробуйте выполнить сброс сетевых настроек. Как сбросить сетевые настройки Windows 11, Как сбросить сетевые настройки Windows 10.

К сожалению, точную причину ошибки 0x80131500 в Microsoft Store бывает сложно установить. Однако, один из предложенных выше методов обычно помогает решить проблему и вернуть работоспособность магазина приложений Windows.

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

Comments

@murali2020kris

Steps to reproduce

  1. Download https://dotnetcli.blob.core.windows.net/dotnet/beta/Binaries/Latest/dotnet-dev-centos-x64.latest.tar.gz
  2. Unpack tar file
  3. Set DOTNET_HOME as unzipped folder. [usr/share/dotnet]
  4. Change permission settings for unzipped folder dotnet
  5. run dotnet -version

Expected behavior

Should give version number

Actual behavior

Gives error message Failed to initialize
Failed to initialize CoreCLR, HRESULT: 0x80131500

Environment data

dotnet --version output:
Failed to initialize CoreCLR, HRESULT: 0x80131500

@ellismg

Have you installed dependent packages like icu and libunwind?

@murali2020kris

@ellismg Thank you so much. icu was missing. It works now.

@ellismg

@Bundas

Hey, I have the same error. I have icu and libundwind installed. What else could be the problem?

I am running Ubuntu 16.04 @ellismg @murali2020kris

@decompiled

@Bundas I am also having the same issue with 16.04 with icu and libundwind.

@ellismg

Support for 16.04 will come at RTM.

@vstoykov

I also has the same problem. I’m trying it on Fedora 23 (downloaded Centos binaries).

I know that Fedora is not listed in supported distributions but I just wanted to try. Probably the reason for error is the same as for Ubuntu 16.04 (version of the icu is newer in Fedora 23 and Ubuntu 16.04, compared to Debian 8, CentOS 7 and Ubuntu 14.04)

@robert-sandor

For Ubuntu 16.04, installing libicu52 from trusty-security seems to fix the problem.

@ghost

For Fedora you can copy necessary libs from: ftp://195.220.108.108/linux/centos/7.2.1511/os/x86_64/Packages/libicu-50.1.2-15.el7.x86_64.rpm package to your /lib/lib64

@SoftHippo

Any ideas for this in OpenSUSE Leap? I’ve installed the package icu and libicu52_1 and get this same issue.

@icebreaker

You can find out what is missing by running:

find /opt/dotnet -name '*.so' -type f -print | xargs ldd | grep 'not found'

Replace /opt/dotnet with the directory you «un-tarred» the tar ball to.

capric8416, sphildreth, nivla, j-dc, carzpurzkey, molaie, leoroos, rindeal, diegosouza, pacholik, and 24 more reacted with thumbs up emoji
p-h, jmathew, anandav, and romandvoskin reacted with hooray emoji

@SoftHippo

Thanks @icebreaker

It appears I’m still missing libicu53 (seems unavailable for Leap, though I have libicu52) and liblldb.so.3.5.0 (I have 3.7.0 installed)

Are these particular versions required?

@kamathba

Same problem on Fedora 24, with the following library versions:
libunwind-1.1-11.fc24.x86_64
libicu-56.1-4.fc24.x86_64

SemaiCZE, sphildreth, abstractj, ybod, lu4nx, monkey2000, eliskovets, gusennan, vukovinski, jpitchardu, and erindru reacted with thumbs up emoji

@capric8416

openSUSE Tumbleweed:
sudo find /opt/dotnet -name ‘*.so’ -type f -print | xargs ldd | grep ‘not found’
liblldb.so.3.5.0 => not found # liblldb.so.3.8 found
libicuuc.so.53.1 => not found # libicuuc.so.57.1 found
libicui18n.so.53.1 => not found # libicui18n.so.57.1 found
liblttng-ust.so.0 => not found # not found

@ghost

kamathba, on fedora 24 you need libicu from fedora 23. Try that package: mirror.yandex.ru/fedora/linux/releases/23/Workstation/x86_64/os/Packages/l/libicu-54.1-5.fc23.x86_64.rpm

@3rdey3

Arch Linux

$ sudo find /opt/dotnet -name '*.so' -type f -print | xargs ldd | grep 'not found'
/opt/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.Net.Http.Native.so: /usr/lib/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /opt/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.Net.Http.Native.so)
    libicuuc.so.52 => not found
    libicui18n.so.52 => not found
    liblldb-3.6.so => not found
    liblttng-ust.so.0 => not found

$ pacman -Q icu libunwind curl 
icu 57.1-1
libunwind 1.1-3
curl 7.49.1-1

@SoftHippo

Okay, I don’t think it’s so productive if we all just post our missing dependencies here. We need to find out if they require those particular versions for every distribution, or if a specific version per distribution is needed, or if it simply doesn’t work on some distributions (I don’t think I’ve seen a successful OpenSUSE or Arch install yet). Any ideas?

@watzon

Had the same problem running Kali linux. Turned out that I had a newer version of libicu and libicu-dev installed (v55 I believe) and dotnet wanted version 52. All I had to do was go to the debian repos and find libicu52 and libicu52-dev and install them

@vanthome

Gentoo User here. I have 57.1 of libicu installed. @iDev0urer did downgrading to 55.x help in your case?

@heavendragon

Opensuse 42.1 finally success after install libicu from this https://software.opensuse.org/package/libicu53_1
but still failed to initialize code, error «Segmentation fault» during dotnet new, dotnet restore(Opensuse 42.1, kernel 4.6.x)
No problem on kernel 4.1.21-14-default

@SoftHippo

@heavendragon Interesting; I installed the rpm from that link (and its one dependency for which it asked) and it runs fine for me. dotnet new, restore, and run all worked as expected. Getting into this some more tomorrow.

(also on Opensuse 42.1, much earlier kernel though)

@watzon

@vanthome I downgraded to v52 and now it works. At the very least I’m not getting that error when typing dotnet --help and dotnet --version anymore. I haven’t tried doing anything else with it yet

@tgoncuoglu

here are some specifics: OS is Fedora 24 with libunwind/libicu installed (f24 has icu at version 56.1 and libunwind at version 1.11). I’m getting above mentioned error. Downgrading to f23 libicu is not an option because of dependencies involved: qt5-qtbase, among others. No can do. So in the end, it seems dotnet requires a specific icu version, ie v52.

@kamathba

I was able to get it working on Fedora 24 by building/installing libicu v52 from source and installing liblldb /libunwind using yum

@sphildreth

On Fedora 24 I installed ftp://195.220.108.108/linux/fedora/linux/releases/23/Everything/x86_64/os/Packages/l/libicu-54.1-5.fc23.x86_64.rpm and «dotnet -version» worked.

@mickaelistria

Another way to get it running on Fedora 24 and other distros using too recent ICU (provided to me by @scela)

  1. download libicu-54.1-5.fc23.x86_64.rpm from wherver ( eg http://mirror.yandex.ru/fedora/linux/releases/23/Workstation/x86_64/os/Packages/l/libicu-54.1-5.fc23.x86_64.rpm )
  2. open it with archive manager, go to ./usr/lib64 and extract all the .so files to ~/oldicu
  3. now execute: LD_LIBRARY_PATH=~/oldicu/:$LD_LIBRARY_PATH dotnet instead of invoking directly dotnet.

This has the advantage of not forcing installation of older icu (which can lead to other issues for package requiring newer icu). Also I imagine this would work with any Linux distribution facing this issue. You can also tweak your .bashrc to define alias dotnet=LD_LIBRARY_PATH=~/oldicu/:$LD_LIBRARY_PATH dotnet, but since alias aren’t inherited, it’s not working when running scripts, so one had to use source script.sh instead of ./script.sh if they want to take advantage of their alias.

mrmeek, tathanhdinh, kevinlang, jlederman, josephbales, shawnanastasio, TuntematonSotilas, rizkytahara, jpitchardu, mikob, and anandav reacted with thumbs up emoji
anandav reacted with hooray emoji

@mrmeek

I was able to dotnet new, restore, and run on OpenSUSE 42.1 by downloading and installing the dependency for libicu53_1: https://software.opensuse.org/package/libicu53_1-ledata (this just copies libicudt531.dat to/usr/share/icu/53.1), and using the technique mickaelistria described such that I can leave the default 52_1 install alone. Thanks mickaelistria!

BTW, Kernel v4.1.20-11-default

@molaie

for debian stretch users, there is more than just libicu52.
I added this line to sources.list (/etc/apt/sources.list)
deb http://ftp.de.debian.org/debian/ jessie main
then :
apt-get update
finally:
apt-get -t jessie install libicu52
apt-get install libssl1.0.0
in this point, the command by @icebreaker gives this output:

    root@yspdebian:~# find /opt/dotnet -name '*.so' -type f -print | xargs ldd | grep 'not found'`

    liblldb-3.6.so => not found

    liblttng-ust.so.0 => not found

finally, work is done by :
apt-get install liblttng-ust0 and apt-get install liblldb-3.6

and now, i have this error:

ahmad@yspdebian:~/oldicu$ dotnet new
Welcome to .NET Core!
---------------------
Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs.
Telemetry
--------------
The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include commandline arguments. The data is collected by Microsoft and shared with the community.
You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shell.
You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.
Configuring...
-------------------
A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take up to a minute to complete and will only happen once.
Decompressing 100% 4369 ms
Expanding 0%Segmentation fault

version is:

ahmad@yspdebian:~/oldicu$ dotnet --version
1.0.0-preview2-003121

and

ahmad@yspdebian:~/oldicu$ dotnet --info
.NET Command Line Tools (1.0.0-preview2-003121)

Product Information:
 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     debian
 OS Version:  
 OS Platform: Linux
 RID:         debian.-x64

@ellismg

There was a bug in 1.0.0 that manifested itself in this way on newer kernels (IIRC it was 4.6.0+) . We fixed the bug see (dotnet/coreclr#6027) but I don’t think the fix has flowed to any of the binary packages.

We will release this fix as part of a 1.0.1 release, but we don’t know the exact date of that release yet. If you want to try the following, it should probably address your issue.

  1. Download https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.debian.8-x64.Microsoft.NETCore.Runtime.CoreCLR/1.0.4
  2. Unzip it to some folder (otherwise it will litter files over whatever folder you extract it in).
  3. copy all the files in runtimes/debian.8-x64/native/ to /opt/dotnet/shared/Microsoft.NETCore.App/1.0.0/ (replacing the versions that already exist there).

Give it another whirl after this.

@TuntematonSotilas

I am on Fedora 24 : I use a script(SH) wich force LD_LIBRARY_PATH, works good for dotnet run. Now I am lost in Visual Studio Code : where do I configure the path of .NET CLI ?

@nibbles-

Just upgraded to Fedora25 (libicu 57.1) and now it is broken again

@TheRealPiotrP

@DustinCampbell can you comment on

I am on Fedora 24 : I use a script(SH) wich force LD_LIBRARY_PATH, works good for dotnet run. Now I am lost in Visual Studio Code : where do I configure the path of .NET CLI ?

@ellismg any updates on this issue? Seems like it’s still affecting a bunch of folks…

@ellismg

any updates on this issue? Seems like it’s still affecting a bunch of folks…

We took fixes for vNext (they didn’t make it in for 1.1) that should help here. Basically we added a mode where we can compile in a way such that we’ll «roll forward» to newer ICUs. I believe the plan is to cut over to that mode as the default before vNext for the binaries that we build and distribute.

In the mean time, you can install an older version of libicu or if it’s possible to override the version of the CLI that VSCode uses to use a local copy of .NET Core, we have scripts that will let you rebuild the relevant native components.

When I last looked, it was unclear if VSCode was deploying their stuff as shared framework apps or standalone. Either way, we can do the rebuilds. If VS Code is just using the shared framework, we have scripts now that can automate the rebuilding. If they publish their tools standalone, then folks will have to rebuild «by hand».

There may also be problems with some other native components (specifically Crypto and HTTP) but you hit the ICU issues first, since globalization is used early in app startup.

@DustinCampbell

@GBatault: If I understand, you have a script that sets LD_LIBRARY_PATH and launches ‘dotnet’? If so, putting this script on your path and naming it ‘dotnet’ should get various commnads in VS Code that depend on the .NET CLI working.

@TuntematonSotilas

@DustinCampbell Tanks for the trick : So what I did today : I use my .bashrc to add an alias : dotnet='LD_LIBRARY_PATH=~/oldicu/:$LD_LIBRARY_PATH dotnet'

But still the error on launching VS Code :
The .NET CLI tools cannot be located. .NET Core debugging will not be enabled. Make sure .NET CLI tools are installed and are on the path.

@DustinCampbell

@gregg-miskelly

@GBatault I don’t know enough about how node spawns processes to say for sure if bash aliases will apply or not. Did you try starting VS Code from a bash prompt with the alias set? I would imagine you could at least make a dotnet file which is really a bash script that could work.

For reference, all the debugger does is run dotnet --info (see link).

@TuntematonSotilas

@gregg-miskelly Tanks, seems to work like this : Create a srcipt shell to launch VS Code with : LD_LIBRARY_PATH=~/oldicu/:$LD_LIBRARY_PATH code

@tamashiketsu

I’m currently struggling with a ICU installation, these libs are missing:

-       liblttng-ust.so.0 => not found
- 	libicuuc.so.50 => not found
- 	libicui18n.so.50 => not found
- 	libcrypto.so.10 => not found
- 	libssl.so.10 => not found
- 	liblldb.so => not found
- 	liblttng-ust.so.0 => not found
- 	libicuuc.so.50 => not found
- 	libicui18n.so.50 => not found
- 	liblldb.so => not found
- 	libcrypto.so.10 => not found
- 	libssl.so.10 => not found

And when I try to install any of them

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package liblttng-ust.so.0
E: Couldn't find any package by glob 'liblttng-ust.so.0'
E: Couldn't find any package by regex 'liblttng-ust.so.0'

@jpitchardu

@acastaner

Downloaded version 1.0.4 (also tried with 1.1), followed all the instructions from https://www.microsoft.com/net/core#linuxfedora (although I’m using Fedora 25) and I get the same error:

[acastaner@localhost ~]$ dotnet --version
Failed to initialize CoreCLR, HRESULT: 0x80131500

I’m apparently missing dependencies

[acastaner@localhost ~]$ find /opt/dotnet -name '*.so' -type f -print | xargs ldd | grep 'not found'
	libicuuc.so.56 => not found
	libicui18n.so.56 => not found
	liblldb.so.3.8.0 => not found

So it seems that contrary to the statements in this issue the problem seems to still exist? Is there a planned fix rather than the provided workarounds?

@ellismg

It is fixed in master now, if you download 2.0 nightlies from dotnet/cli things should work.

There are no plans to back port the changes to 1.0 or 1.1.

@gforceg

@ellismg, when does 2.0 drop? I’d like to use a version of the CLI that is recommended for production environments. I’d also like to develop on Fedora 25.

How do I find out where the CLI is looking for these libs? I wonder if I can make a symlink to the (newer) versions I have installed.

@gforceg

@ellismg

@ellismg, when does 2.0 drop? I’d like to use a version of the CLI that is recommended for production environments. I’d also like to develop on Fedora 25.

The Roadmap says Q3 of this year.

How do I find out where the CLI is looking for these libs? I wonder if I can make a symlink to the (newer) versions I have installed.

To answer the question, although I now see you’ve fixed the issue, CoreCLR just does normal probing like any other application would to find these libraries, so that will usually be configured with ldconfig. The problem with making a symlink (vs downloading the libraries as you did) is that ICU decorates function exports with a version number (so instead of an export named «foo» on ICU 51 and 52 it’s named «foo_51» and «foo_52» on the two versions) so you need to install a matching version.

.NET Core 1.1 does support Fedora 24 in production, so that’s always an option if you need to stick with Fedora and also want to be in a supported place. I would encourage you to kick the ties on some of the newer 2.0 builds, while we still have time to address any feedback you’ll find.

@knocte

thanks @mmisztal1980 , that has solved the issue for me in Ubuntu 16.04.

@gideondsouza

Ok, this still exists for me on Fedora 25. I have libicu and I have libunwind. When I installed them with dnf it says it’s already installed.

Any clues or pointers?

@mickaelistria

@ellismg

@gideondsouza Which version of the CLI are you trying to install?

@gforceg

@gideondsouza I’m also running Fedora 25, but I had to install the version of libicu used by Fedora 24 for the CLI to work. (libicu v 56).

@daddykotex

On Ubuntu 16.04, I had:

find /opt/dotnet -name '*.so' -type f -print | xargs ldd | grep 'not found'
	libicuuc.so.52 => not found
	libicui18n.so.52 => not found
	liblldb-3.6.so => not found
	libicuuc.so.52 => not found
	libicui18n.so.52 => not found
	liblldb-3.6.so => not found

so I did:

sudo echo "deb http://security.ubuntu.com/ubuntu trusty-security main" >> /etc/apt/sources.list
sudo apt-get update && sudo apt-get install libicu52 liblldb-3.6

And could:

dotnet --info.NET Command Line Tools (1.0.4)

Product Information:
 Version:            1.0.4
 Commit SHA-1 hash:  af1e6684fd

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  16.04
 OS Platform: Linux
 RID:         ubuntu.16.04-x64
 Base Path:   /opt/dotnet/sdk/1.0.4

@agrcrobles

On Ubuntu 16.04 I ended up symlinking libicuuc.so.52 libicui18n.so.52 from opt to usr/lib as a workaround, I am still looking for a better way to do it though.

@sunnystormy

Is there a reason dotnet Core isn’t being built with the latest packages from Debian? libicu52 and liblldb-3.6, for example, are several generations behind. I don’t want to have to necro old packages just to get this to run.

—EDIT—

Everything works if you download it from the main github page here. It doesn’t work if you download it using the commands from the https://www.microsoft.com/net/core#linuxdebian website. Perhaps that should be updated?

@knocte

Perhaps that should be updated?

@sunnystormy what should be updated? Maybe you want to create a PR since this issue is marked as closed (not sure why though).

@sunnystormy

@knocte Good point. I’ll create a new ticket with the contents of the second part of my post.

@msftgits
msftgits

transferred this issue from dotnet/cli

Jan 31, 2020

Содержание

  1. Как исправить ошибку 0x80131500 в Microsoft Store
  2. Средство устранения неполадок Microsoft Store
  3. Очистка кэша и сброс Microsoft Store
  4. Решение проблем с доступом к серверам Майкрософт
  5. Перерегистрация или переустановка Microsoft Store
  6. Другие способы исправить ошибку 0x80131500
  7. question
  8. How can i fix VS 2019 Error Code: 0x80131500 IntelliSense finished initializing, but an error occurred when attempting to load the document.
  9. 6 Answers
  10. Error code 0x80131500 visual studio 2019
  11. Microsoft Store Error Code 0x80131500: Try These 9 Solutions
  12. Get Microsoft Store running in minutes with our solutions
  13. What causes the code: 0x80131500 error in Microsoft Store?
  14. How can I fix the 0x80131500 error on Windows 10?
  15. 1. Reconfigure Internet properties
  16. 2. Set the date, time, and region correctly
  17. 3. Change the language to English
  18. 4. Update Microsoft Store
  19. 5. Check the services
  20. 6. Reset the Microsoft Store app
  21. 7. Reinstall Microsoft Store
  22. 8. Disable your antivirus and firewall
  23. 9. Replace your wireless adapter

Как исправить ошибку 0x80131500 в Microsoft Store

Одна из самых распространенных ошибок в магазине приложений Windows 11 и Windows 10 — ошибка с кодом 0x80131500. Причины ошибки могут быть разными, но проблему обычно сравнительно легко решить.

В этой инструкции подробно о способах исправить ошибку «Код: 0x80131500» в Microsoft Store различными способами, начиная с простых и часто срабатывающих, заканчивая более сложными.

Средство устранения неполадок Microsoft Store

Первый способ редко срабатывает, но начать рекомендую именно с него. Попробуйте использовать встроенное средство устранения неполадок Microsoft Store. Для этого:

  1. В Windows 11 перейдите в Параметры — Система — Устранение неполадок — Другие средства устранения неполадок.
  2. В Windows 10 перейдите в Параметры — Обновление и безопасность — Устранение неполадок — Дополнительные средства устранения неполадок.
  3. Запустите средство устранения неполадок «Приложения из Магазина Windows».
  4. Следуйте указаниям мастера устранения неполадок для поиска и попытки автоматического исправления найденных ошибок.

Если какие-либо ошибки были исправлены, попробуйте перезапустить Microsoft Store и проверить, появляется ли ошибка с кодом 0x80131500 снова.

Очистка кэша и сброс Microsoft Store

Следующий метод — очистка кэша и сброс приложения Microsoft Store. Выполните следующие шаги:

  1. Перейдите в Параметры — Приложения — приложения и возможности.
  2. Найдите Microsoft Store в списке приложений, нажмите по трем точкам справа и выберите «Дополнительные параметры».
  3. Используйте кнопки «Исправить» и «Сбросить» в разделе сброса приложения.
  4. Нажмите правой кнопкой мыши по кнопке «Пуск», выберите пункт «Выполнить», введите wsreset.exe и нажмите Enter. На некоторое время появится пустое окно консоли, затем оно закроется и Microsoft Store будет запущен автоматически.

После повторного запуска Microsoft Store проверьте, была ли решена проблема.

Решение проблем с доступом к серверам Майкрософт

Причиной ошибки 0x80131500 в Microsoft Store могут быть те или иные проблемы при попытке доступа к соответствующим серверам Майкрософт. Что можно попробовать:

  1. При наличии стороннего антивируса или файрволла попробуйте временно отключить их и проверить, была ли решена проблема.
  2. Если вы использовали какие-либо сторонние утилиты для отключения обновлений Windows, отключения телеметрии и подобных задач, они могли заблокировать доступ к серверам Майкрософт. Попробуйте сбросить настройки брандмауэра Windows и восстановить файл hosts — из него потребуется удалить все строки, блокирующие доступ к серверам.
  3. Если вы используете сервисы VPN/прокси, проверьте, сохраняется ли ошибка, если их отключить. Отключите автоматическое определение параметров прокси-сервера (подробнее: Как отключить прокси-сервер Windows 10).
  4. Проверьте, исчезает ли ошибка, если настроить популярные публичные DNS в Windows, здесь могут помочь статьи: Как изменить DNS в Windows 11, Как изменить DNS-сервер в Windows 10.
  5. Включите TLS 1.2 и TLS 1.3, если они отключены. Для этого можно зайти в Панель управления, открыть «Свойства браузера» (или нажать клавиши Win+R и ввести inetcpl.cpl), включить соответствующие пункты и применить настройки.

Перерегистрация или переустановка Microsoft Store

Для исправления ошибки можно попробовать выполнить переустановку приложения Microsoft Store, для этого:

  1. Запустите PowerShell или Windows Терминал (с открытой консолью PowerShell) от имени Администратора. Сделать это можно через контекстное меню кнопки «Пуск».
  2. Введите следующую команду и нажмите Enter

После выполнения команды закройте окно PowerShell и проверьте работу Microsoft Store.

Также можно попробовать удалить и повторно установить Microsoft Store (под свою ответственность, возможны проблемы). Для этого используем по порядку следующие две команды:

Другие способы исправить ошибку 0x80131500

Если предлагаемые методы не помогли, обратите внимание на следующие возможные варианты решения:

  1. Проверьте настройки даты, времени и часового пояса в Windows, убедитесь, что они настроены правильно. Установите правильный регион в параметрах Windows.
  2. В службах Windows (Win+Rservices.msc) найдите «Фоновая интеллектуальная служба передачи (BITS)», дважды нажмите по ней и, если в «Тип запуска» установлено «Отключена», измените на «Вручную» и примените настройки.
  3. Используйте точки восстановления системы на дату, когда ошибка 0x80131500 не появлялась. Подробнее: Точки восстановления Windows 11, Точки восстановления Windows 10.
  4. Выполните проверку и восстановление целостности системных файлов. Как восстановить системные файлы Windows 11, Как восстановить системные файлы Windows 10.
  5. Можно попробовать создать новую учетную запись Windows (Как создать пользователя Windows 10, большинство способов аналогичны и в Windows 11), зайти под ним и проверить, появляется ли ошибка в магазине приложений под новым пользователем.
  6. Попробуйте выполнить сброс сетевых настроек. Как сбросить сетевые настройки Windows 11, Как сбросить сетевые настройки Windows 10.

К сожалению, точную причину ошибки 0x80131500 в Microsoft Store бывает сложно установить. Однако, один из предложенных выше методов обычно помогает решить проблему и вернуть работоспособность магазина приложений Windows.

Источник

question

How can i fix VS 2019 Error Code: 0x80131500 IntelliSense finished initializing, but an error occurred when attempting to load the document.

Occurred: After Finished Create New Project.

Visual Studio 2019 [ 16.9.4 ]

Tried:
1. Use Repair in Visual Studio Installer.
2. Re Installed Visual Studio

I have error like you . But i still fixed error and use it .
Step 1 : coppy file contain content create new file
Step2 : start run file new and old file
if you don’t see form1.cs.design in new file
step3 : close file form1.cs.design by select X like picture

step 4 : on view tab on menu select DESIGN and run

6 Answers

Welcome to Microsoft Q&A!

Could you tell me what your project type is? Which target framework of your project are you using? .NET Core or .NET Framework?

You can try the following workarounds:
1. Create a new project and check if the error occurs in specific project or not.
2. Use the command: devenv /safemode to run your Visual Studio in safe mode.
3. Delete the hidden .vs , bin and obj folders in the project folder.

If the answer is helpful, please click «Accept Answer» and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Источник

Error code 0x80131500 visual studio 2019

// TestComObject.cpp : Defines the entry point for the console application.
//

#include «stdafx.h»
#include
#include

int _tmain(int argc, _TCHAR* argv[])
<
HRESULT hr;

CoInitialize( NULL );
Ncr_AS_ASWebOfficeInterface::IPosLogRemoteData *remoteData;

hr = CoCreateInstance( __uuidof( Ncr_AS_ASWebOfficeInterface::PosLogRemoteData ), NULL, CLSCTX_SERVER,
__uuidof( Ncr_AS_ASWebOfficeInterface::IPosLogRemoteData ), (void **)&remoteData );

cout Release();
remoteData = NULL;
>

IClassFactory *cls;
hr = CoGetClassObject( __uuidof( Ncr_AS_ASWebOfficeInterface::PosLogRemoteData ), CLSCTX_SERVER, NULL, IID_IClassFactory, (void **)&cls );
cout CreateInstance( NULL, __uuidof( Ncr_AS_ASWebOfficeInterface::IPosLogRemoteData ), (void **)&remoteData );
cls->Release();
cout Release();
>

CoUninitialize();
return 0;
>

using System;
using System.Runtime.InteropServices;
using System.IO;
using System.Xml;
using NCR.WO.Common.DataProcessor;

namespace Ncr.AS.ASWebOfficeInterface
<
///
/// This class provides the methods needed to send data to the Web Office data processing service.
///
[ClassInterface( ClassInterfaceType.None ), ComVisible( true )]
public sealed class PosLogRemoteData : IPosLogRemoteData, IDisposable
<
///
/// Web Office interface object
///
private ProcessRemoteData _woProcessor;

///
/// Initialize any persistant data structures
///
public PosLogRemoteData()
<
_woProcessor = new ProcessRemoteData(«WOTransactionRecorder»);
>

// .. trimmed for brevity

Output from TestComObject

>TestComObject
CoCreateInstance returned 0x80131500
CoGetClassObject returned 0x0
ClassFactory::CreateInstance returned 0x80131500

That said, I did manage to dig into this a bit further yesterday evening. It appears that the assembly that the ProcessRemoteData object is in has been changed (it is provided by a third party) and it appears that the new version number is

Источник

Microsoft Store Error Code 0x80131500: Try These 9 Solutions

Get Microsoft Store running in minutes with our solutions

  • 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.

  1. Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here) .
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues affecting your computer’s security and performance

  • Restoro has been downloaded by 0 readers this month.

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 error 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

Users also reported the following problems:

  • 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.

Given below are the solutions for the error Code: 0x80131500 in Microsoft Store that worked for most users.

How can I fix the 0x80131500 error on Windows 10?

Let’s first try a few quick solutions before heading over to the slightly complex ones.

  1. Restart the computer
  2. Update Windows to the latest available version
  3. 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

  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
    • Use TLS 1.3: Check
  4. Once done click on OK to save the changed then reboot the computer for these to apply.

This is one of the methods that worked for most users and fixed the Code: 0x80131500 for good. So, do try it.

2. Set the date, time, and region correctly

  1. Press Windows + I to open Settings and select Time & Language.
  2. 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.
  3. Now, manually choose the correct date and time and click on Change.
  4. 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.

3. Change the language to English

  1. Press Windows + I to open Settings, then click on Time & Langauge.
  2. Navigate to the Language tab from the left and select English (United States) from the Windows display language dropdown menu.

4. Update Microsoft Store

  1. Type Microsoft Store in the Search bar, and then click on the relevant search result.
  2. Click on the Library icon near the bottom-left.
  3. Now, click on the Get updates button.
  4. 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

  1. Press the Windows key + R , type services.msc, and then press Enter or click OK.
  2. Locate the Background Intelligent Transfer Service and then double-click it.
  3. Set Automatic as the Startup type and then hit the Start button below. Now, click the Apply and OK buttons to acknowledge the change.
  4. Do the same for the Windows Update service.

6. Reset the Microsoft Store app

  1. Press Windows + I to open Settings, and then click on Apps.
  2. Locate and select Microsoft Store, and then click on Advanced options.
  3. Click on the Reset button.
  4. Again, click Reset in the confirmation prompt.

After the Microsoft Store reset is complete, you shouldn’t come across Code: 0x80131500.

Read more about this topic

7. Reinstall Microsoft Store

  1. Type cmd in the Search tab, then click on Run as administrator to start Command Prompt with full privileges.
  2. Paste the following command to remove the Microsoft Store apps package and then hit Enter : Get-AppxPackage -allusers *WindowsStore* | Remove-AppxPackage
  3. Now, execute the following command to reinstall it: Get-AppxPackage -allusers *WindowsStore* | Foreach

8. Disable your antivirus and firewall

  1. Type Security on the Search tab, and then select Windows Security from the results.
  2. Click on Virus & threat protection.
  3. 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.

Expert tip:

SPONSORED

Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

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 completely , be sure to check out the best uninstaller software you can use right now.

IfIf 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

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 this topic, reach for the comments section below.

Источник

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 December 8, 2022

Reviewed by
Vlad Turiceanu

Vlad Turiceanu

Passionate about technology, Windows, and everything that has a power button, he spent most of his time developing new skills and learning more about the tech world. Coming… read more

  • 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.

fix error code: 0x80131500 in Microsoft Store

XINSTALL BY CLICKING THE DOWNLOAD FILE

To fix various PC problems, we recommend Restoro PC Repair Tool:
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:

  1. Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues affecting your computer’s security and performance
  • Restoro has been downloaded by 0 readers this month.

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?

In this article

  • 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.

  1. Restart the computer
  2. Update Windows to the latest available version
  3. 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.

Internet options to fix code: 0x80131500

2. Navigate to the Advanced tab, and then scroll down to the bottom of the Settings list.

0x80131500-windows-10

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

reconfigure settings to fix code: 0x80131500

4. Once done, click on OK to save the changes then reboot the computer for these to apply.

0x80131500-windows-10

2. Set the date, time, and region correctly

  1. Press Windows + I to open Settings and select Time & Language.time & language
  2. 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.change time to fix code: 0x80131500
  3. Now, manually choose the correct date and time and click on Change.set time
  4. Finally, choose the correct Time zone from the dropdown menu, which corresponds to your region.time zone

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

  1. Press Windows + I to open Settings, then click on Time & Langauge.time & language
  2. Navigate to the Language tab from the left and select English (United States) from the Windows display language dropdown menu.set english to fix code: 0x80131500

4. Update Microsoft Store

  1. Type Microsoft Store in the Search bar, and then click on the relevant search result.microsoft store
  2. Click on the Library icon near the bottom-left.Library
  3. Now, click on the Get updates button.get updates to fix code: 0x80131500
  4. If there’s an update for Microsoft Store, it should now install automatically.update

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

  1. Press the Windows key + R, type services.msc, and then press Enter or click OK.
  2. Locate the Background Intelligent Transfer Service and then double-click it.
  3. Set Automatic as the Startup type and then hit the Start button below. Now, click the Apply and OK buttons to acknowledge the change.
  4. Do the same for the Windows Update service.

6. Reset the Microsoft Store app

  1. Press Windows + I to open Settings, and then click on Apps.apps
  2. Locate and select Microsoft Store, and then click on Advanced options.advanced options
  3. Click on the Reset button.reset to fix code: 0x80131500
  4. Again, click Reset in the confirmation prompt.reset

Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

After the Microsoft Store reset is complete, you shouldn’t come across Code: 0x80131500.

Read more about this topic

  • Windows Update Components Must be Repaired: 4 Easy Solutions
  • 0x80248007: How to Fix This Error Code in 8 Steps
  • HP Laptop Camera Is Not Working: 5 Quick Ways to Fix It
  • Reset Epson Ink Pad with This Approved Method

7. Reinstall Microsoft Store

  1. Type cmd in the Search tab, then click on Run as administrator to start Command Prompt with full privileges.Command Prompt
  2. Paste the following command to remove the Microsoft Store apps package and then hit Enter: Get-AppxPackage -allusers *WindowsStore* | Remove-AppxPackage
  3. 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

  1. Type Security on the Search tab, and then select Windows Security from the results.
  2. Click on Virus & threat protection.
  3. 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.

newsletter icon

Newsletter

Image 1

Table of Contents

  • Introduction
  • Background
  • Error Numbers
    • 8013150a
    • 80131515
    • 80131522
    • 80070002
    • 80004002
    • 80004005
    • 80070057
    • 80131500
    • 80131018
  • References
  • Summary
  • History

Introduction

In this article, I have tried to cover some of the possible solutions for error numbers that we face with Visual Studio add-in exceptions.

These errors can happen during development or post installation.

I have put my time and efforts on all of my articles. Please don’t forget to mark your votes, suggestions and feedback to improve the quality of this and upcoming articles.

You might be interested in my article on Visual Studio Add-in — Web Search. Please click here to check my other articles.

Background

While working with Web Search add-in for Visual Studio, I made some notes on add-in error numbers to troubleshoot Visual Studio add-ins. I thought of sharing these notes for the developer community to make life easier while working with Visual Studio add-ins.

If you found any other solutions for any of the problems mentioned here, please let me know.

Error numbers throws some light on the exception occurred. By using error numbers, we can identify the root cause of the problem.

80131515

Image 2

I got this 80131515 error when I tried to run Web Search add-in from a network location, and I made it work after applying the first solution from this post.

How to Resolve 80131515 Issue

This error comes when we run an add-in files from a network location as the DLL runs from a network location has less permission.

To resolve this issue, we need add loadFromRemoteSources element to the devenv.exe.config file.

Open (with admin rights) the devenv.exe.config file from the below location:

C:Program FilesMicrosoft Visual Studio 10.0Common7IDEdevenv.exe.config 

or:

C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDEdevenv.exe.config  

and add loadFromRemoteSources element with «true» value, like below:

<configuration>
   <runtime>
      <loadFromRemoteSources enabled="true"/>
   </runtime>
</configuration>   

Sometimes, the windows tag the downloaded files as «the file comes from a different location» to apply more restrictions on them. The simple solution is to unblock the downloaded zip file or DLL file.

To unblock the file, just right click on the file (zip/dll/setup), go to ‘Properties‘, then select ‘General‘ tab, then click on the ‘Unblock‘ button. Refer to the below screenshot:

Image 3

If you found any other solution to resolve this issue, please let me know.

80131522

Visual Studio Add-in Troubleshooting, Error Number 80131522 - Shemeer

This error comes when the namespace and/or class name of the connect class specified in the .AddIn file doesn’t match the actual one declared in the source code.

If you look at the below image, the actual Namespace is WebSearch2012.

Image 5

but in the .AddIn the Namespace is mentioned as WebSearch, that’s why it caused the error 80131522.

Image 6

If you found any other solution to resolve this issue, please let me know.

80070002

Image 7

The 80070002 error is caused mostly by two reasons:

  1. The AddIn DLL mentioned in the assembly tag is missing (not valid), or
  2. The AddIn references a DLL that cannot be found.

If you found any other solution to resolve this issue, please let me know.

8013150a

Image 8

This error is due to the lack of permission to the AddIn DLL. This happens when we run AddIn from a network location.

The best and simple solution is to Copy the AddIn to a Local folder and add that folder in the folder list of Addins:

  • Go to Tools->Options.
  • Select Environment.
  • Go to Add in / Macro security tab.
  • Click Add-> select the local folder where you have copied the AddIn file and AddIn DLL.

Image 9

If you found any other solution to resolve this 8013150a issue, please let me know.

80004002

Image 10

The 80004002 error is because the Assembly is not COM visible.

Image 11

I got this error only when I compiled WebSearch with the above code. If the System.Runtime.InteropServices.ComVisible is not mentioned, then its default by True.

Ensure that Connect class is Public and that you have the ComVisible(True) applied at assembly level, or at least at class level.

80004005

Image 12

80004005 is due to invalid file specified in <Assembly> tag:

Image 13

Make sure that the file exits in the specified path mentioned in <Assembly> tag.

If you found any other solution to resolve this issue, please let me know.

80070057

Image 14

This error has probably happened because an Exception occured inside the Add-in code.

Which Exception? Where?

Any unhandled error inside OnConnection method of an add-in class will cause the add-in to be removed from Visual Studio.

The Error Number 80070057 says that an ArgumentException has occurred inside the OnConnection method of Add-in class (mainly Connect class).

Solution

Handling the ArgumentException inside the OnConnection method will resolve this issue.

If you are using any third party add-ins, then you should get the latest add-in component (DLL) with the fix for this bug.

If you found any other solution to resolve this issue, please let me know.

80131018

Image 15

This is due to an unknown file specified in the <Assembly> tag.

Image 16

80131500

Visual Studio Add-in Troubleshooting, Error Number 80131500 - Shemeer

This error has probably happened because an Exception occured inside the Add-in code.

Any unhandled error inside OnConnection method of an add-in class will cause the add-in to be removed from Visual Studio.

The Error Number 80131500 says that an unhandled Exception has occurred inside the OnConnection method of Add-in class (mainly Connect class).

Solution

Expect the un-expected errors Smile | <img src= .

Handling the Exception inside the OnConnection method will resolve this issue.

If you are using any third party add-ins, then you should get the latest add-in component (DLL) with the fix for this bug.

If you found any other solution to resolve this issue, please let me know.

References

  • MZTools

Web Search

You might be interested in my article on Visual Studio Add-in — Web Search.

Web Search - Visual Studio Add-in , Search (Google, Yahoo, MSDN, Code Project, Stack Overflow and more...) for the selected text/item - Shemeer NS

Summary

In this article, I have tried to explain some of the common errors with Visual Studio Add-in with multiple solutions, I hope you have enjoyed this article and got some value addition to your knowledge.

I have put my time and efforts on all of my articles, please don’t forget to mark your votes, suggestions and feedback to improve the quality of this and upcoming articles.

History

  • 23rd September, 2012: Initial version

Ошибка 0x80131500 в Windows 10 возникает при открытии магазина Microsoft Store. В сообщении говорится о невозможности загрузки страницы, код при этом указывается в самом низу страницы, маленьким шрифтом. Появляется такого рода проблема достаточно часто, исправить ее можно несколькими способами. Вот об этом я сегодня и расскажу. И вдобавок перечислю основные причины возникновения ошибки 0x80131500.

Проблема с кодом 0x80131500 в Windows 10 может появляться по нескольким причинам:

  • появление багов в работе Магазина Windows,
  • некорректные настройки времени и даты,
  • нестабильное подключение к сети Интернет,
  • проблемы с DNS-сервером.

Способы устранения неполадки

В зависимости от корня проблемы можно использовать несколько способов ее устранения. Если же причина неизвестна, предлагаю воспользоваться следующими инструкциями, причем идти в строго указанной последовательности, от одного способа к другому.

Изменение сетевого подключения

Для начала я попробую изменить тип сетевого подключения – если у меня соединение с сетью Интернет осуществляется по Wi-FI, тогда перехожу на проводной. И наоборот. Можно также попробовать подключиться к другой точке доступа, например, при возможности раздать трафик с мобильного подключения.

Изменение конфигураций DNS

Проблема может быть решена и изменением DNS-настроек. В таком случае сначала я открываю «Параметры», кликнув по иконке с изображением шестеренки в левой части меню «Пуск» или нажав на сочетание Win + I. Перехожу в категорию «Сеть и Интернет», во вкладке «Состояние» есть ссылка «Настройка параметров адаптера» — жму по ней.

Как поменять DNS-адрес и решить проблему с кодом 0x80131500

В «Параметрах» системы открываю настройки параметров адаптера

Откроется новое окно, в нем я выбираю активное подключение и жму по нему дважды левой кнопкой мыши для вызова окна «Состояние». В нем будет кнопка «Свойства» — нажимаю на нее.

Как открыть свойства, изменить адрес DNS-сервера и устранить ошибку 0x80131500 в Windows 10

Открываю раздел с отображением состояния активного интернет-подключения и перехожу к «Свойствам»

В первой же вкладке «Сеть» в списке компонентов есть пункт «IP версии 4 (TCP/IPv4)», по нему я кликаю левой кнопкой дважды для открытия свойств.

Изменение настроек DNS-сервера как способ устранения ошибки 0x80131500

Теперь открываю свойства пункта «IP версии 4 (TCP/IPv4)»

DNS-адрес в компьютере по умолчанию всегда получается автоматически, но можно установить его по умолчанию. В новом открывшемся окне я отмечаю пункт «Использовать следующие адреса DNS-серверов», затем в двух нижних полях ввожу такие значения:

  • На предпочитаемый DNS-сервер – 8.8.8.8;
  • На альтернативный DNS-сервер – 8.8.4.4;

Это бесплатные публичные серверы компании Google, они используются для ускорения загрузки сайтов и препятствуют сбору данных.

Применяю изменения нажатием на кнопку ОК, закрываю все окна и перезагружаю компьютер. Затем проверяю, работает ли теперь магазин Windows.

Изменение адресов DNS-серверов и исправление ошибки 0x80131500

Ввожу данные значения в указанные поля и применяю изменения

Если данный способ не помог устранить проблему, опять открываю те же окна и отмечаю элемент «Получить адрес DNS-сервера автоматически», т.е. возвращаю все измененные параметры в исходное состояние.

Изменение настроек даты и времени

Из-за неправильно установленных даты и времени в работе Microsoft Store тоже могут появляться ошибки. Для исправления ситуации я захожу в «Параметры», нажав на комбинацию Win + I, после открываю категорию «Время и язык». Откроется вкладка «Дата и время», в ней будет тумблер «Установить время автоматически». Если он отключен, я переключаю его, затем жму по кнопке «Синхронизировать». Можно также попробовать поменять часовой пояс, а после посмотреть, загрузился ли Магазин.

Как устранить ошибку 0x80131500 в Windows 10 изменением даты и времени

Переключаю тумблер на автоматическую установку времени и активирую синхронизацию

Запуск средства устранения неполадок

В «Параметрах» системы есть специальный инструмент, с помощью которого можно искать и устранять неполадки. Для начала я открываю соответствующий раздел – жму на комбинацию Win + I.

После этого перехожу в раздел «Обновление и безопасность», там уже открываю вкладку «Устранение неполадок». Выбираю пункт «Приложения из Магазина Windows», жму на появившуюся кнопку, в результате откроется новое окно и начнется сканирование.

Как исправить ошибку 0x80131500 в Windows 10 через «Параметры»

Запускаю средство устранения неполадок в компьютере

При наличии каких-либо неполадок система предоставит информацию и несколько способов их устранения. После применения исправлений обязательно перезагружаю компьютер и проверяю, не исчезла ли данная проблема.

Удаление кэша Магазина

Можно попробовать удалить кэш Microsoft Store. Для этого сначала я открываю «Проводник» и следую данному пути C:UsersUserAppDataLocalPackages (могу просто ввести его в адресной строке). Нахожу папку с названием Microsoft.WindowsStore 8wekyb3d8bbwe (оно может отличаться). Открываю ее, удаляю все содержимое и перезагружаю компьютер. Затем запускаю Магазин и проверяю его работу.

Сброс приложения Microsoft Store

Если предыдущий способ не сработал, попробую сбросить настройки магазина Windows. Открываю окно «Выполнить» нажатием на сочетание клавиш Win + R, затем в поле ввожу запрос wsreset.exe и активирую его нажатием на кнопку ОК.

После окончания обязательно перезагружаю компьютер и проверяю магазин.

Создание новой учетной записи

В некоторых случаях может помочь создание новой учетной записи в компьютере. Для этого я вновь захожу в «Параметры», только на этот раз открываю категорию «Учетные записи». Перехожу во вкладку «Семья и другие пользователи» и в разделе «Другие пользователи» жму на элемент «Добавить пользователя для этого компьютера».

Как создать новую учетную запись в компьютере

Можно создать нового пользователя, для этого следую указанной последовательности

Откроется окно с настройкой учетных записей. Если нет желания создавать новый аккаунт Microsoft и привязывать его, можно обойтись и без него. В таком случае в новом окне я жму сначала на ссылку «У меня нет данных для входа этого человека». Затем система предложит создать новую учетную запись, и под полем, где обычно вводится  электронный адрес, появятся три ссылки. Третья – «Добавить пользователя без учетной записи Майкрософт». Я жму по ней.

Создание нового пользователя без привязки к аккаунту Microsoft

Можно создать новую учетную запись Microsoft и привязать ее к аккаунту. А можно и обойтись без этого, нажав на эту ссылку и добавив пользователя без привязки к аккаунту

В следующем окне я ввожу имя для нового пользователя и, если нужно, пароль. После нажатия на кнопку «Далее» на компьютере создастся новая учетная запись. Теперь можно выходить из своего аккаунта и переходить в новый профиль. Там проверяю работу Магазина Windows.

Как создать нового пользователя в Windows 10

Ввожу имя для нового пользователя, установку пароля можно пропустить, оставив поля пустыми

Повторная регистрация Microsoft Store

Последний, крайний способ устранения ошибки 0x80131500 в Windows 10 – перерегистрация Магазина Windows. Мне необходимо сначала открыть консоль Windows PowerShell, а сделать это можно несколькими способами. Один из них – нажать на сочетание клавиш Win + X, затем в списке выбрать пункт «Windows PowerShell (администратор)». Именно с правами админа, иначе ничего не сработает.

Как устранить ошибку 0x80131500 в Windows 10 с помощью PowerShell

Вот таким способом я могу быстро открыть Windows PowerShell с правами администратора

В новом окне ввожу вот такой запрос:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

Его можно скопировать и вставить прямо со страницы, затем активировать, нажав на кнопку Enter.

Если данная команда не сработает, можно попробовать вставить другую, аналогичного содержания, но немного иного вида:

Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

Если и после этого программа выдает ошибку, рекомендую последовательно вводить следующие запросы:

  • PowerShell –ExecutionPolicy Unrestricted
  • $manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + ‘AppxManifest.xml’ ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest
  • Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

Последняя в этой серии дублирует вторую команду, которую я указала. Она точно так же повторно регистрирует Microsoft Store в компьютере. Не забываю про перезагрузку и тест приложения.

Заключение

Ошибка с кодом 0x80131500 в Windows 10 появляется при открытии Microsoft Store. Причины на то могут быть разными – от нестабильного интернет-подключения до наличия серьезных ошибок в работе приложения. Данный тип неполадки, вне зависимости от ее корня, можно устранить с помощью встроенных в систему средств, не прибегая к сторонним утилитам. Если причины неизвестны, лучше следовать указанной в инструкции последовательности до тех пор, пока проблема не будет устранена.

Загрузка ... Загрузка …

Post Views: 6 935

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Error code 0x800f0922
  • Error code 0x800f081e
  • Error code 0x800b0109 windows 7
  • Error code 0x800b0101
  • Error code 0x800b0100 windows 10 что делать

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии