Windows store not launching event id error 10001

I updated the windows store yesterday night, after the update completed the windows store would not launch anymore. I checked the event viewer and I would get the following error every time I try to open the store:

Unable to start a DCOM Server: Microsoft.WindowsStore_11712.1001.13.0_x64__8wekyb3d8bbwe!App as Unavailable/Unavailable. The error:"2"Happened while starting this command:"C:\Program Files\WindowsApps\Microsoft.WindowsStore_11712.1001.13.0_x64__8wekyb3d8bbwe\WinStore.App.exe" -ServerName:App.AppXc75wvwned5vhz4xyxxecvgdjhdkgsdza.mca

I've tried the following to try to fix the issue:

1: tried wsreset.exe but I would get the error: Windows cannot find 'ms-windows-store:PurgeCaches'

2: sfc /scannow but found not integrity violations and the store is still not opening

3: used the DISM command line but found no corruption

4: created a new user profile and still the store will not open

5: uninstalled and reinstalled the windows store via powershell

I'm really stumped here and don't know what else to do. I've never had this issue before till the last windows store update from last night. Hopefully someone can help me with this problem. Thanks in advance

Hi Ken

Thank you for the links and suggestion. I managed to find the culprit of why I was getting the error. I was in the process of doing the in-place upgrade following the instructions on the link that you provided. As I got to the step to disable my security software, I first disabled Kaspersky and as I was about to disable Zemana Antilogger I happen to click on the quarantine section, and to my surprise the windows store folder and store exe. was in quarantine.

I restored the windows store folder and the store was up and running again. It's strange that I got no type of notification that it was quarantined by Zemana at all. I've never had that happen before, I've gotten false postives by Zemana before and I normally get a notification. Also what I find strange is why Zemana would quarantine the store folder, I'm guessing it had something to do with the store update. Again thank you very much for the suggestion and links, it helped me stumble on the culprit of the error.