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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-07-29T22:36:47+00:00

    Licence verification is that the computer has a digital licence.  This is as it should be, having been upgraded from Windows 7 four years ago.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-07-29T22:43:52+00:00

    I accidentally closed the Control Panel applet that showed Maintenance was running.  When I opened that Control Panel applet again, it showed that Maintenance is not running.

    The Application event log shows that three Defrag operations completed normally.  I guess Maintenance doesn't try to defrag the two recovery partitions that Windows 10's installer created.

    I don't see any other evidence of what Maintenance did.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-07-29T22:44:01+00:00

    Thanks for the feedback on the tutorial which has tens of thousands of uses. I made changes in the Startups and Maintenance sections based on your feedback.

    As I explain in the tutorial, DISM only repairs the integrity of the install.wim image used to check the System files by. The actual repair of System Files is done by SFC which should be run up to 3 separate times to see if it can repair the files, and if not move on to the Repair Upgrade, by installing the Media Creation Tool from this link http://windows.microsoft.com/en-us/windows-10/m... choosing Download Tool Now, install the tool, open it and choose Upgrade this PC Now. This will save your files and apps while bringing you up to the latest version by the most stable method. It will also bring all of your Updates current and solve most problems since it reinstalls Windows.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. 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