Microsoft Store: Something happened on our end error [FIX]

• Something happened on our end. Waiting a bit might help error in Microsoft Store might be caused by a faulty Internet connection.
• Running the Windows troubleshooter should help you see what’s leading to the Microsoft Store Something happened on our end issue.
• In some cases, the local cache might prevent the app from launching.
• Resetting the MS Store app is always a good idea, to start fresh.

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.

Microsoft Store is one of the pre-installed Windows 10 apps. Some users have stated that a Something happened on our end error message pops up when they try launching the app.

The full error message states: Try that again. Something happened on our end. Waiting a bit might help. Consequently, the MS Store doesn’t open.

To fix it, start by running Windows Store Apps Troubleshooter. That should resolve the halt or at least give you a better insight into what’s causing it.

If the issue persists, reset the MS Store app and check Buy and Download Xbox Live settings. Read in detail about each solution below.

How do I fix Something happened on our end in Microsoft Store?

1. Run the Windows Store Apps troubleshooter

1. Press the Windows key + S hotkey to open Cortana’s search box in Windows 10.
2. Enter troubleshoot in the text box, and click Troubleshoot settings.
3. Scroll down to and select Windows Store Apps.
4. Press the Run this troubleshooter button to open the Windows Store Apps troubleshooter.
5. Then go through the troubleshooter’s potential resolutions.

Some users have confirmed that troubleshooter resolved the error for them.

2. Reset the MS Store app

1. Press the Windows key + X hotkey and click Run.
2. Enter wsreset.exe in Run’s Open box.
3. Press the OK button.
4. A blank Command Prompt window will then open while resetting MS Store. Thereafter, the MS Store app might open.

3. Check the Buy and Download Xbox Live setting

1. Log in to the Xbox Live website and open the settings.
2. Select the XBOX One Online Safety tab.
3. Select the Only Free radio button for the Buy and Download option.

Adjusting the Buy and Download Xbox Live setting is another resolution that has fixed the Try that again error for some users.

4. Clear the LocalCache folder

1. Open Run by pressing the Windows key + R hotkey.
2. Input %localappdata% in Run and click OK to open File Explorer.
3. Open the Packages >Microsoft.WindowsStore_8wekyb3d8bbwe, and LocalCache folders from there.
4. Press the Ctrl + A hotkey to select all content within the LocalCache folder.
5. Press the Delete button.

A corrupted LocalCache folder can be the source for various Microsoft Store errors. So, clearing that folder is a potential resolution for the Something happened on our end error.

Those are some of the confirmed resolutions for the above-mentioned error. Should you know other fixes, don’t hesitate to share them with us.

How to Delete Cookies in Microsoft Edge

Windows Update or Upgrade Error 0XC1900103

Windows 10 Activation Error Code 0xC004F012

What Does IMY Mean?

What Does AFK Mean?

What Does ICYDK Mean?

What Does ICYMI Mean?

What Does IDK Mean?

What Does ROTFLMAO, ROFL, or ROTF Mean?

What Does IRL Mean?

How to Fix Microsoft Store — Try That Again

Published by Timothy Tibbetts on 04/08/2020

In this tutorial, we look at fixing the Microsoft Store error — Try that again. Page could not be loaded. Please try again later.

TIP : Hard to fix Windows Problems? Repair/Restore Missing Windows OS Files Damaged by Malware with a few clicks

The first three steps below should resolve this error for most people.

Video — How to Fix Microsoft Store — Try That Again

1: Check the Microsoft Store Install Service

Press the Windows Key + S and type in services.msc.

Find the Microsoft Store Install Service and double=click,

If Disabled, change it to Automatic, click Start and click OK.

2: Run the Windows Store Apps Troubleshooter

To get to the Troubleshooters, go to Settings > Updates & Security > Troubleshoot.

Click on Windows Store Apps and click on Run the troubleshooter.

If you’ve never used a troubleshooter before, they contain a list of known Windows 10 fixes. Here’s a video tutorial on using troubleshooters:

3: Clear the Store Cache

One of the easier and complete fixes is to delete the Store cache. In this video, we walk you through the steps:

Press the Windows Key + R and type in WSReset.exe.

A blank Command Prompt window should appear for about 30 seconds and automatically load the Store.

If you receive the error message again, please try WSReset.exe a second time.

4: Reset the Store in Settings

Press the Windows Key + R and type in ms-settings:appsfeatures.

Click on Microsoft Store > Advanced Options > Reset.

5: Clear the LocalCache Folder

Press the Windows Key + R and type in %localappdata%.

Open Microsoft.WindowsStore_8wekyb3d8bbwe > LocalCache.

Press CTRL + A to delete all the files in the LocalCache folder.

6: Reinstall the Windows Store

App Store: «Try that again Page could not be loaded. Please try again later.»

HELP! I AM connected to the internet and I have a very strong connection. My Google Chrome works absolutely fine when I tried to search something, but the Microsoft Store app isn’t working. This is very strange because it has never happened to me before. In fact, Microsoft have a new logo so it might be bugs and slow-downs. The codes are above, help me please! But my question to you is: How do I fix this?

The list of things I’ve tried:

Restarting my laptop

Refreshing my laptop

Closed the Store and opened it again

Troubleshooted problems for WiFi

Checked www.fast.com and I have a really good connection!

Turned my WiFi off and back on again

If you know ANYTHING, please help me

Start by running the Windows Store Apps troubleshooter.

Open Start > Settings > Update & security > Troubleshoot
Scroll down to the bottom
Click Windows Store Apps

Click Run the troubleshooter

When complete try opening the Store again.

Also check if the Store works in another user account.

Press Windows key + R
Type: wsreset.exe
Hit Enter

Do this a couple times then try launching the Store again.

Your Antivirus might be interfering with the Store, try disabling it ‘temporarily’ to see if it launches.

Check Windows Update and install the latest updates. Sometimes Microsoft releases infrastructure fixes for the Store through Windows Update.

You can also try resetting the store app using the following instructions:

If that does not work, try resetting the software distribution folder:
Before carrying out this procedure, disconnect from the Internet. That means turning off Wi-Fi and disconnecting from a wired connection. If you don’t, Windows 10 will indicate some files are in use and cannot be modified or the command will be non-responsive. Also, you should restart your computer after disconnecting from the Internet. The easiest way to do it is to enable Airplane mode from the Action Center — Windows key + X.

1. Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” from the menu.

2. Stop the BITS, Cryptographic, MSI Installer and the Windows Update Services. To do this, type the following commands at a command prompt. Press the “ENTER” key after you type each command.

net stop wuauserv

net stop cryptSvc

net stop msiserver

3. Now rename the SoftwareDistribution and Catroot2 folder. You can do this by typing the following commands in the Command Prompt. Press the “ENTER” key after you type each command.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 Catroot2.old

4. Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Typethe following commands in the Command Prompt for this. Press the ENTER key after you type each command.

net start wuauserv

net start cryptSvc

net start msiserver

5. Type Exit in the Command Prompt to close it and then restart the computer.

If you need more help, please continue to engage with us. We want to help you through this.

21 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Try that again windows store

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Pro 10.0.10586 build 10586 Fully updated from WSUS, joined to domain.

«try that again something went wrong» error code 0x800706D9 on attempts to install any apps from microsoft store. Problem is on multiple desktops here, persists with windows firewall service or antivirus services running or stopped and launched by a user in local admins group. Any ideas?

Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 6/23/2016 3:48:13 PM
Event ID: 44
Task Category: Windows Update Agent
Level: Information
Keywords: Started,Download
User: SYSTEM
Computer: *
Description:
Windows Update started downloading an update.

Tons of errors similar to this logged during the transaction:

Log Name: Application
Source: Windows Error Reporting
Date: 6/23/2016 3:48:17 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: *
Description:
Fault bucket 126526281078, type 5
Event Name: StoreAgentDownloadFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: WSAcquisition
P2: 800706d9
P3: 10586
P4: 420
P5: Windows.Desktop
P6: 8
P7:
P8:
P9:
P10:

Log Name: Application
Source: Windows Error Reporting
Date: 6/23/2016 3:48:16 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: *
Description:
Fault bucket 126519901698, type 5
Event Name: StoreAgentDownloadFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: WSAutoUpdate
P2: 800706d9
P3: 10586
P4: 420
P5: Windows.Desktop
P6: B
P7:
P8:
P9:
P10:

All replies

Using DISM Command:

I) Press Windows + x on your keyboard.

ii) Select Command prompt (Admin) to open Administrator Command Prompt .

iii) In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:
dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth

Using sfc /scannow

a. Click on Start button and type cmd in search box.

b. Right-click on Command Prompt and select Run as administrator.

c. Type the following command and hit Enter.

sfc /scannow

Run Power shell Command:

1. Open the Task manager. Here’s a tip: Press CTRL+Shift+ESC.
2. Click File > Run New Task
3. Make sure you have a check mark beside “Create this task with administrative privileges”
4. Type Powershell

Type the following in the Powershell prompt:

Get-AppXPackage -AllUsers | Foreach

S.Sengupta, Windows Experience MVP

• Proposed as answer by Rick_Li Microsoft contingent staff Friday, June 24, 2016 2:17 AM

Please refer to S.Sengupta’s suggestion to have a try at first.
For Store Application issue, here are some general solutions you could try at least.
1: Reset Windows store by run wsreset.exe.
2: Register Store state using the following command in Powershell:
Get-AppXPackage | Foreach
3: If you get any third part security app installed on your computer, please try to install app under Clean boot since it will sometimes block the installation.
How to perform a clean boot
http://support.microsoft.com/kb/929135
4: Check if we can install this app on another user account, please create a new one and connect to your Microsoft account then.

In addition, I notice that this issue occurs on multiple domain joined computers, there is a possibility that this issue is caused by some specific domain policy settings.
We could remove one machine that has this issue from domain, then restart and logon with a local user account to have a test.

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact tnmff@microsoft.com

made it through these with no problem:
dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
sfc /scannow
wsreset.exe

pages of results similar to below when running the powershell from administrator prompt, same results whether windows firewall service is started or stopped from services.msc. have not yet tried on another machine off domain, will have to set one up for testing.

Add-AppxPackage : Deployment failed with HRESULT: 0x80073D0A, The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall
service and try again. (Exception from HRESULT: 0x80073D0A)
NOTE: For additional information, look for [ActivityId] e41778f5-cd9e-0001-3ad8-17e49ecdd101 in the Event Log or use the command line Get-AppxLog -ActivityID
e41778f5-cd9e-0001-3ad8-17e49ecdd101
At line:1 char:38
+ . | Foreach +

+ CategoryInfo : NotSpecified: (C:\Program File. ppXManifest.xml:String) [Add-AppxPackage], Exception
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Log Name: Application
Source: Windows Error Reporting
Date: 6/24/2016 9:09:05 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: *
Description:
Fault bucket 126519930766, type 5
Event Name: AppxDeploymentFailureBlue
Response: Not available
Cab Id: 0

Problem signature:
P1: 80073D06
P2: 3
P3: 0
P4: NONE
P5: 10.0.10586.420
P6: 0
P7:
P8:
P9:
P10:

How about the issue, is there anything to update?

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact tnmff@microsoft.com

I have this same exact issue but enabling Storage Service does NOT work for me.

For one, it was already enabled. I restarted my PC in the last 12 hours, still with this issue, and since the Storage Service was already running, I restarted it. Still same problem.

I am on Win 10 Pro on a 2-month old Dell G3.

Version is 1803 Build 17134.228
Microsoft Windows [Version 10.0.17134.228]

Wow, this is a really poor suggestion. Basically this says «I have no idea how to fix this but just try this shotgun-blast, restore everything to scratch and see if it might just happen to work.»

It’s like the doctor saying, «Oh, your toe hurts? Well the fix for that is we cut off your leg, then guaranteed the toe doesn’t hurt anymore.»

What kind of system engineering is this? So poor — in the absence of any other information from Microsoft on this error, which as a reminder is an error reported as «Something went wrong. » (how much worse can programming be? Answer=none), much to my regret I tried your shotgun blast and all I got was a bunch of junk like solitaire and netflix and other junk restored which I had already deleted and do not want.

So, this «solution», not only does it NOT fix the problem it makes a bunch of things WORSE because it altered specific configurations that were already made for business reasons.

As someone who has worked many years as a programmer, I can readily state that anyone who codes crap like «Something went wrong» when they failed to catch an error should be reassigned to building maintenance or something that doesn’t involve enterprise software. Yechh!

What I would like to see Microsoft do to provide a constructive solution is the following:
1. Document what services and their states are required for the Microsoft Store to work.
2. Document what port/protocols are required for the Microsoft Store to work.
3. Document what files and their permission s are required for the Microsoft Store to execute successfully.

Then we could check all the criteria and make precision changes that correct the issue without causing a bunch of other worse problems.

Without fixing this I cannot spend any money in the Microsoft Store and will have to rely on Steam or something else instead. $$$

Finally, I know MSFT has a strict hiring regimen but it’s incomprehensible that code gets out the door without needed try. catch statements. And this is new code, ugh.