Monday, 24 August 2015

Fix The Server Stumbled with Error 0x801901F7 in Windows 10

So Windows Store can seem to work for you in Windows 10? Sure you are here just because of that. Windows 10 Users may get to see The Server stumbled and the under that shows the Error code 0x801901F7. This Happens everytime you try and launch Windows Store.

One may Assume this is because of the Microsoft Servers, no doubt they will be overloaded and thus the error. This really can be the case but there are few things that you can do on your own to Solve this Windows Store Error 0x801901F7 in Windows 10.

Fix The Server Stumbled with Error 0x801901F7
Snapshot of  Error 0x801901F7 in Windows Store

We will be listing All possible ways to fix this error, All the below mentioned methods might just not work for everyone but worth a try. Lets See how to solve this issue.

Solving Windows Store Error 0x801901F7

Following are the 3 Different Ways which must help you to get rid of this error in your windows 10. We are parting the 3 methods in to 2. Basic and Advance. We will Start with Basic Method First and then jump on to Advance methods if it doesn't help you.

Basic Method to Fix Error Code 0x801901F7

Method 1: Resetting Windows Store Cache.

Most of the time Clearing or Resetting the Cache helps. Doesn't works always but we prefer this to be done first before moving to some advance methods which are mentioned below

To Reset Windows Store cache please follow below Simple Steps
  • Open up RUN by searching or pressing "Windows Key + R" 
  • Type "wsreset.exe" and press Enter or Click on OK.
  • Windows Store will Open up automatically along with a command prompt.
  • This Resets Windows store and you might see it Loading as it should be.

This method might work but if it fails to solve Error 0x801901F7 then follow below Methods.

Advance Methods to Fix Error Code 0x801901F7

Method 2: Delete Windows Store Database File.

So in this Method we will be Deleting the Database file for Windows Store. This file is located on your C Drive or the drive where your Operating System is Installed.

Steps 1: Navigate to C:\Windows\SoftwareDistribution\DataStore\DataStore.edb 

Step 2: Delete DataStore.edb file from there.

Step 3: Now Open Windows Store and see if you still get Error code 0x801901F7
The Datastore.edb file that we deleted will be automatically created once you perform Step 3 which is launching Windows Store.

If you still cant get this error away then Close Windows Store and Reboot your PC then Launch Windows Store Again.

Method 3: Tweaking Windows Update Properties.

Perform the steps mentioned in this method if above mentioned Methods Fails. We will be Tweaking couple of things in Windows Updates to see if that helps.
  1. Open Task manager by right clicking on Task bar, then click on Task Manager.
  2. Jump to Services Tab, Click on Open Services at very bottom of the Window.
  3. Now a new Window will Pop up, Scroll down & Find "Windows Update" from the list.
  4. Double click on Windows update to open up its Properties.
  5. Now from Startup type Dropdown, select Automatic as shown in Below Picture. Click on Apply, Start and then Ok.

Now Just one more step, Reset Windows Store again (Refer to method 1 for Steps). This should fix your Windows Store Error that shows The Server Stumbled with 0x801901F7 Error Code.

So these were all 3 Methods that can Possibly Fix the issue for you. Please let us know which method helped you with this problem in Comments below.


  1. Replies
    1. Awesome Sumit, Thanks for letting us know about this. Helps others.

  2. method 3 worked for me too.thanks a lot

  3. Thanks you so much. You save my day :)

  4. On method 3 once you press apply and service status says running is it supposed to take a long time? I pressed it 20 mins ago and it still says running

  5. i'm on a WSUS server and as soon as I disable HKLM\Software\policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer (put to 0 instead of 1), it works for me. But i don't want to disable the WSUS to make the Windows Store works...

    1. This did the trick for me and further investigations proposed I have to do more on WSUS end to rectify the issue. Cheers for the post.

  6. You are the savior. Last method works for me. Thanks

  7. Number 3...I have been looking for a solution for ages...thanks a lot, I think you are the only one who came up with a solution that works

  8. 3 is awesome, works like a charm, thanks for help

  9. yeah yeah man! method 3 works for me

  10. method 3 work for me also