Microsoft Store and various apps don't work in Windows 10 version 1903

Anonymous
2019-07-29T01:52:34+00:00

Since old threads tend to get locked, not allowing more replies, let me say to anyone who comes here from a Google search:

It doesn't look like this problem is going to get solved.  It looks like the Windows installation has to be scrapped and a new clean install from scratch has to be done, followed by reinstalling all applications and repeating all settings of all applications etc.

===

Here's the original question:

Microsoft Store and around a dozen other applications don't run.  I tried a lot of things including doing an in-place upgrade from Windows 10 1903 to Windows 10 1903 keeping all files and apps.  What it kept was the inability of these applications to run.

Start - Settings - Applications shows around a dozen unnamed applications attributed to Microsoft Corporation.  However, Microsoft Store itself is not one of these.  Microsoft Store is displayed in the list of applications, but doesn't have any size (not 0 bytes, but no size displayed at all), and was updated 2019/06/04.

The command wsreset gives an error message.  The specified device, path, or file cannot be accessed.  There is a possibility that the item can't be accessed because of a permissions problem.  However, I've observed that the Windows folder doesn't contain the subfolder needed by Microsoft Store.  The in-place reinstallation of Windows 10 1903 did not create the necessary subfolders.

sfc /scannnow etc. also do not create the necessary subfolders.

This PC originally ran Windows 7 Pro Japanese and subsequently Windows 10 Pro Japanese.  No other language version has ever been installed on this PC.

Windows for home | Windows 10 | Microsoft Store

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

100 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kapil Arya 38,466 Reputation points Volunteer Moderator
    2020-07-14T14:12:50+00:00

    Hello,

    Try to re-register apps. Perform these steps:

    1. Search for Windows PowerShell using Cortana or Windows Search.
    2. From results, right click on Windows PowerShell and select Run as administrator.
    3. Then type following command and press Enter key:

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

    Let the command complete.

    1. Close Windows PowerShell and see if the issue is resolved now.

    If issue still persists, we can try creating a new user account from User Accounts window. Press Windows + R, type netplwiz command, click OK. In the User Accounts window, click Add and create new account. 

    In case if nothing helps, we can perform repair upgrade:

    https://www.kapilarya.com/how-to-repair-windows-10-using-in-place-upgrade

    Hope this helps! 

    Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-07-29T23:08:38+00:00

    There's a maximum of 60,000 characters per reply in this forum but the forum says "something went wrong" even when I split CBS.log into portions.  Anyway, I will try to post the portions of CBS.log that pertain to the latest execution of sfc/scannow

    Timestamps are Canadian Eastern Daylight Time because I moved back from Japan.

    2019-07-29 18:56:41, Info                  CBS    TI: --- Initializing Trusted Installer ---

    [If I delete the rest of CBS.log, will this forum let me post again?]

    [No, I can edit this reply, but I can't add any more replies.]

    "I didn't ask for cbs log. Did you try running SFC 3 separate times to see if it will repair the files? What specific verbatim errors do you get?"

    You're in luck because this forum won't let me post the rest of cbs.log. 

    システム スキャンの検証フェーズを開始しています。

    検証 100% が完了しました。

    Windows リソース保護により、破損したファイルが見つかりましたが、それらは正常に修復されました。

    オンライン修復の場合、詳細は次の場所にある CBS ログ ファイルに含まれています

    windir\ Logs\CBS\CBS.log (たとえば C:\Windows\Logs\CBS\CBS.log)。オフライン修復の場合、

    詳細は /OFFLOGFILE フラグによって指定したログ ファイルに含まれています。

    C:\WINDOWS\system32>

    Verification completed 100%.  Damaged files were found in Windows resource protection but they were properly repaired.  If an online repair was performed, details are in cbs.log.

    ===

    This forum still won't let me add new replies, so here's my reply to PCR.

    "Well, what language is on the Installation media you used for the over-install...?..."

    As stated in the original posting, Japanese.  This PC never had any other language version installed on it.

    "(1) Insert the USB media (or mount the .iso) & note its letter."

    The DVD drive has letter R.  (I usually change it from D, and upgrade-in-place remembers that I assigned letter R.)

    "DISM  /Get-WimInfo  /WimFile:E:\Sources\Install.esd  /Index:6"

    DISM  /Get-WimInfo  /WimFile:R:\Sources\Install.esd  /Index:6

    R:\Sources\Install.esd doesn't exist.  The error message is:

    エラー: 87

    コマンドの処理中にエラーが発生しました。

    コマンド ライン引数が有効であることを確認してください。詳細については、ログ ファイルを確認してください。

    DISM ログ ファイルは C:\WINDOWS\Logs\DISM\dism.log にあります

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-07-29T22:54:38+00:00

    That sounds good. Well, what language is on the Installation media you used for the over-install...?...

    (1) Insert the USB media (or mount the .iso) & note its letter.

         Use  your letter in the following command (instead of mine).

    (2) At an Administrator Command Prompt, enter...

    DISM  /Get-WimInfo  /WimFile:E:\Sources\Install.esd  /Index:6

    Microsoft Windows [Version 10.0.18362.267]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>DISM  /Get-WimInfo  /WimFile:E:\Sources\Install.esd  /Index:6

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Details for image : E:\Sources\Install.esd

    Index : 6

    Name : Windows 10 Pro

    Description : Windows 10 Pro

    Size : 14,506,477,853 bytes

    WIM Bootable : No

    Architecture : x64

    Hal : <undefined>

    Version : 10.0.18362

    ServicePack Build : 175

    ServicePack Level : 0

    Edition : Professional

    Installation : Client

    ProductType : WinNT

    ProductSuite : Terminal Server

    System Root : WINDOWS

    Directories : 19798

    Files : 90136

    Created : 6/11/2019 - 9:37:17 PM

    Modified : 7/9/2019 - 10:05:58 PM

    Languages :

            en-US (Default)

    The operation completed successfully.

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-07-29T22:19:27+00:00

    Check whether Windows is activated at "START, Settings, Update & Security, Activation". I know some features will become unusable, if it is not activated.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-07-29T02:59:05+00:00

    There is no reinstall option that saves your files and apps besides a Repair Upgrade which is what you just did with Verison 1903. I only suggested that you do a Clean Install so you'd have an install that wouldn't suffer these problems.

     I would try re-registering again as that's the only repair we have directly addressing those Store apps condiition. 

    If you want to try to repair it further then go over this checklist to make sure the install is set up correctly, optimized for best performance, and any needed repairs get done:  http://answers.microsoft.com/en-us/windows/wiki/windows\_10-performance/windows-10-performance-and-install-integrity/75529fd4-fac7-4653-893a-dd8cd4b4db00

    Start with Step 4 to turn off Startup freeloaders which can conflict and cause issues, then Step 7 to check for infection the most thorough way, then step 10 to check for damaged System Files, and also Step 16 to test a new Local Admin account.  Then continue with the other steps to go over your install most thoroughly.

    Was this answer helpful?

    0 comments