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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-08-01T04:38:01+00:00

    My own DISM.log is peppered with errors such as you've shown. Those must be normal & don't relate to the problem at hand. I got output from that DISM command that did show the characteristics of Install.esd including its language.

    However, I do get an error 87 when I use an invalid index number. Let us see your index numbers.

    (a) Ensure it is an Administrator Command Prompt.

    (b) Ensure you use your own letter.

    (c) It's the same DISM but without specifying an index number.

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

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

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

    Index : 1

    Name : Windows 10 Home

    Description : Windows 10 Home

    Size : 14,229,531,906 bytes

    Index : 2

    Name : Windows 10 Home N

    Description : Windows 10 Home N

    Size : 13,421,299,617 bytes

    Index : 3

    Name : Windows 10 Home Single Language

    Description : Windows 10 Home Single Language

    Size : 14,228,939,169 bytes

    Index : 4

    Name : Windows 10 Education

    Description : Windows 10 Education

    Size : 14,506,333,120 bytes

    Index : 5

    Name : Windows 10 Education N

    Description : Windows 10 Education N

    Size : 13,698,295,738 bytes

    Index : 6

    Name : Windows 10 Pro

    Description : Windows 10 Pro

    Size : 14,506,477,853 bytes

    Index : 7

    Name : Windows 10 Pro N

    Description : Windows 10 Pro N

    Size : 13,698,681,806 bytes

    The operation completed successfully

    If it fails to work, use CTRL-A & CTRL-C to copy the full contents of the Command Prompt & post it. Also post the full contents of the bottom of the DISM log between <----- Starting Dism.exe session -----> & <----- Ending Dism.exe session ----->. Mine is below, & the errors in it did not prevent the outpu.

    If it works, then use the proper index number in the original command. But I don't know why yours should be different.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE:

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=4

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.18362.1

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Executing command line: DISM   /Get-WimInfo  /WimFile:E:\Sources\Install.esd

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Connecting to the provider located at C:\WINDOWS\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-08-01 00:20:52, Warning               DISM   DISM Provider Store: PID=2296 TID=7856 Failed to load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Connecting to the provider located at C:\WINDOWS\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Connecting to the provider located at C:\WINDOWS\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Connecting to the provider located at C:\WINDOWS\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-08-01 00:20:52, Info                  DISM   DISM Provider Store: PID=2296 TID=7856 Connecting to the provider located at C:\WINDOWS\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-08-01 00:20:52, Warning               DISM   DISM Provider Store: PID=2296 TID=7856 Failed to load the provider: C:\WINDOWS\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE:

    2019-08-01 00:20:52, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-07-31T14:44:03+00:00

    "The last Installation DVD I made was of 1803."

    I believe you.  The installation DVD for 1903 has a similar root directory.  Let's continue.

    "Inside D:\Sources, I do see Install.esd."

    You're right.  Using File Explorer, inside R:\Source, I also see install.esd.  I wonder what happened the previous time.

    "(1) Are you sure your letter is R:?"

    Yes, I've been doing that for 22 years.  In Windows 95, when I attached a PCMCIS-SCSI adapter and SCSI hard disk, I wanted to let Windows assign drive letter D (and E etc.) so I changed the CD drive to R.

    "(3) Was it an Administrator Command Prompt...?..."

    I sure hope non-administrators wouldn't be able to write C:\WINDOWS\Logs\DISM\dism.log.  Let's see today's results.

    2019-07-31 10:23:12, Warning               DISM   DISM Provider Store: PID=1528 TID=12724 Failed to load the provider: C:\Windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-07-31 10:23:12, Info                  DISM   DISM FFU Provider: PID=1528 TID=12724 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

    [1528] [0x8007007b] FIOReadFileIntoBuffer:(1381): ファイル名、ディレクトリ名、またはボリューム ラベルの構文が間違っています。

    [1528] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

    [1528] [0xc142011c] WIMGetMountedImageHandle:(2897)

    2019-07-31 10:23:12, Info                  DISM   DISM WIM Provider: PID=1528 TID=12724 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

    2019-07-31 10:23:12, Info                  DISM   DISM VHD Provider: PID=1528 TID=12724 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2019-07-31 10:23:12, Info                  DISM   DISM FFU Provider: PID=1528 TID=12724 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

    2019-07-31 10:23:12, Info                  DISM   DISM Imaging Provider: PID=1528 TID=12724 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

    2019-07-31 10:23:12, Info                  DISM   DISM VHD Provider: PID=1528 TID=12724 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2019-07-31 10:23:12, Info                  DISM   DISM Imaging Provider: PID=1528 TID=12724 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

    [1528] [0x8007007b] FIOReadFileIntoBuffer:(1381): ファイル名、ディレクトリ名、またはボリューム ラベルの構文が間違っています。

    [1528] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

    [1528] [0xc142011c] WIMGetMountedImageHandle:(2897)

    Syntax error in file name, directory name, or volume name.  It says in English that C:\ isn't recognized.  That's weird, Windows is booted from C:.  I stopped assigning drive letters other than C: to Windows installations more than 10 years ago.

    2019-07-31 10:23:14, Error                 DISM   DISM Driver Manager: PID=3388 TID=5196 Error, file not found 'oem13.inf'. - CDriverManager::OpenPackageByFile(hr:0x80070002)

    2019-07-31 10:23:16, Error                 DISM   DISM Driver Manager: PID=3388 TID=3404 Error, file not found 'oem18.inf'. - CDriverManager::OpenPackageByFile(hr:0x80070002)

    2019-07-31 10:23:17, Error                 DISM   DISM Driver Manager: PID=3388 TID=3404 Error, file not found 'oem0.inf'. - CDriverManager::OpenPackageByFile(hr:0x80070002)

    Huh.  Microsoft now uses those oem__.inf files for other things besides drivers provided by hardware manufacturers.  I'd expect oem0.inf to be a Microsoft thing installed before Windows setup even starts looking at hardware.

    2019-07-31 10:28:27, Error                 DISM   DISM WIM Provider: PID=7592 TID=9624 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:3481 - CWimManager::InternalOpGetImages(hr:0x80070057)

    2019-07-31 10:28:27, Error                 DISM   DISM WIM Provider: PID=7592 TID=9624 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4268 - CWimManager::InternalCmdGetImages(hr:0x80070057)

    2019-07-31 10:28:27, Error                 DISM   DISM WIM Provider: PID=7592 TID=9624 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x80070057)

    2019-07-31 10:28:27, Error                 DISM   DISM WIM Provider: PID=7592 TID=9624 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2122 - CWimManager::ExecuteCmdLine(hr:0x80070057)

    2019-07-31 10:28:27, Error                 DISM   DISM.EXE: WimManager processed the command line but failed. HRESULT=80070057

    2019-07-31 10:28:27, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    2019-07-31 10:28:27, Info                  DISM   DISM.EXE:

    2019-07-31 10:28:27, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

    "It is important to know that the Language of the Installation media is the same as that of your installed Windows, as seen at  "START, Settings, Time & Language, Language"..."

    Yes, it's always been Japanese on this PC.  When moving to Canada I changed geographic settings for location and time zone, but the Windows version and GUI are still Japanese, and the installation DVD is still Japanese.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-07-31T00:04:23+00:00

    The last Installation DVD I made was of 1803. Here is its root directory...

    Inside D:\Sources, I do see Install.esd.

    (1) Are you sure your letter is R:?

    (2) Right-click the R: drive in File Explorer,

         & select "Open", & check that the file (Install.esd) is there (in Sources).

    (3) Was it an Administrator Command Prompt...?...

         Ask Cortana or Search for "CMD", & click "Run as Administrator".

    (4) It looks like you entered the command right,

         but copy/paste this into it, if R: is right...

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

    It is important to know that the Language of the Installation media is the same as that of your installed Windows, as seen at  "START, Settings, Time & Language, Language"...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-07-30T17:20:35+00:00

    My reply to Greg Carmack gave the output of sfc /scannow and my rough translation of that output.  That was the reason I started posting cbs.log before Mr. Carmack told me not to.

    My reply to PCR was the output of dism.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-07-30T16:48:52+00:00

    Was that result of DISM or System File Checker? I cannot read Japanesel.

    If it's DISM then run SFC /scannow up to 3 separate times until it fixes System files.  If not move on to Repair Upgrade.

    Was this answer helpful?

    0 comments