0x80070057 - Cannot Manually Update Store Apps

[Mighty Joe]

Hello folks,

As the title states, I am unable to manually update apps in the Store. Currently, the apps in question are: the Microsoft Store itself, Cortana, and VP9 Video Extensions. In the Store, the error message I receive is "Something happened on our end." In my Reliability Monitor, the error message is
"Installation Failure: Windows failed to install the following update with error 0x80070057: 9NFFX4SZZ23L-Microsoft.549981C3F5F10."

Although the Problem Details state "Failed Windows Update," the 0x80070057 error appears to be independent of Windows Update because I have been able to receive standard Windows Updates and this is has me quite confused.

Based on the app history in my Revo Uninstaller, It looks like my system was running smooth up to 3/8/22 because on that date, it shows I was able to receive a few app updates without having to enter the store and do it manually. I got no new app updates from 3/8 on up until 4/11 when Cortana updated and on 4/12 when Mail and Calendar updated but the Store gives some conflicting information re: which apps updated and on which date. So I would say it was a few weeks ago when I started to notice the issue.

I have tried the usual steps (in safe mode/safe mode with networking, where possible) with no luck or with no errors/corruption found:
1. error check on my C drive
2. DISM.exe /Online /Cleanup-Image /Restorehealth
3. cleared Software Distribution Downloads and Cache
4. Windows Update troubleshooter
5. Windows Store Apps troubleshooter
6. wsreset
7. sfcfix
8. setupdiag (crashed/would not open) This is probably significant.

For a while, the Store would open, then close quickly but somewhere along the way, things improved to where I am at least able to open the Store and have it remain open.

Additionally, I tried to enter various commands I read about online to reregister my apps, I received many error messages in red. I didn't make note of the specifics. And in my Event Viewer, re: trying to update Cortana, KERNELBASE.dll is listed as the faulting module. Application Error 1000.

I fear if this issue isn't solved, any morning now I am going to wake up to a BSOD. Any assistance you can provide will be greatly appreciated. Thank you so much for your consideration!

 

[xrobwx71]

Obviously, the things you tried didn't fix it for you but what were the results of the fixes you tried 1-8. Did you receive any messages (errors) after running each one?

Are you up to date on Windows Update?

Hit start and type Powershell, then right-click on PowerShell and run as administrator. In the window that opens, please copy and paste this get-appxpackage -allusers and hit enter.

In your next post, please post answers to my questions above and in the content of the PowerShell output, look for Microsoft.WindowsStore. Under this, you'll see PackageFullName.

Mine looks like this:

PackageFullName : Microsoft.WindowsStore_22203.1401.21.0_x64__8wekyb3d8bbwe

Copy and paste yours in along with your next post as well. You'll need to use CTRL+C to copy.

 

[x BlueRobot]

In addition to what @xrobwx71 has mentioned, could you please provide your CBS log folder? It should be available in the following directory path:

%systemroot%\Logs\CBS

Although the Problem Details state "Failed Windows Update," the 0x80070057 error appears to be independent of Windows Update because I have been able to receive standard Windows Updates and this is has me quite confused.

Like optional features and language packs, I assume the store apps are delivered as update packages as well.

 

[Mighty Joe]

I greatly apologize for the delayed reply. I typically get e-mails when there are responses to a thread I start but I never did in this case.

Here is the package full name: Microsoft.WindowsStore_22202.1402.0.0_x64__8wekyb3d8bbwe. My most recent CBS log has been uploaded for your review.

Other than what I mentioned, there were no specific errors when I tried the steps 1 to 8. All the checks came back clean.

Since the date I posted the thread, I've continued to try and work on it and found a corrupted permission in my WindowsApps folder (this was obviously not picked up by the various checks). It came about when I took ownership of the folder, I'm sure, so I deleted the corrupted permission and reestablished TrustedInstaller as the owner but I don't think it fully worked because I neglected to check the boxes related to inheritance and child objects.

The file Windows\Winstore\Appxmanifest.xml remains missing. That could be the main culprit.

Thank you again

 

[ubuysa]

The only 'error' of significance that I can see in your CBS.log is this one:

2022-05-02 10:59:01, Info                  CBS    Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I confess that I don't know exactly what that signifies (note that it's only an informational message) but it does reference the store and is probably related to the manifest file you're missing.

Take a look in the folder C:\Windows\LiveKernelReports, the Windows kernel does sometimes write minidumps on the fly (without crashing) to here, so if there are any relevant ones in here (check the timestamp) then upload them.

 

[Mighty Joe]

Thank you for bringing that error to my attention, ubuysa. I don't understand why the SFC /scannow reported no integrity violations if there is in fact corruption as the log indicates.

The Live KernelReports folder contains only an empty folder called WATCHDOG.

 

[x BlueRobot]

I confess that I don't know exactly what that signifies (note that it's only an informational message) but it does reference the store and is probably related to the manifest file you're missing.

It's not significant at all. It just means that it's attempted to set a registry value which doesn't exist.

2022-05-02 10:59:01, Info                  CBS    Ensure CBS corruption flag is clear
2022-05-02 10:59:01, Info                  CBS    Ensure WCP corruption flag is clear
2022-05-02 10:59:01, Info                  CBS    All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2022-05-02 10:59:01, Info                  CBS    Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I don't understand why the SFC /scannow reported no integrity violations if there is in fact corruption as the log indicates.

There's two reasons really: SFC does not check for registry corruption and only checks for payload files; there is no corruption detected by DISM hence why it's attempting to clear those corruption flags in your registry.

The file Windows\Winstore\Appxmanifest.xml remains missing. That could be the main culprit.

Have you tried Step 3 of this guide?

Solved: Windows Store Does Not Open - Missing PurgeCaches - MajorGeeks

Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.XML

 

[Mighty Joe]

Enclosed is the error from Step 3 of the Major Geeks solution.

Step 4 - I was unable to copy the output but there was "access is denied" everywhere, ending in "successfully processed 6524 files; failed processing 8523 files." Wsreset gave me the same "purge caches" error ("try reinstalling the application to fix the problem.")

I also have those weird *ms-resource:AppName* entries at the bottom of my start menu.

 

[x BlueRobot]

Sorry, the command should have been the following:

Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml

It will probably fail though and state that the path does not exist.

 

[Mighty Joe]

Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml

Failed exactly the way you predicted.

 

[x BlueRobot]

What might be useful is to get a Process Monitor trace while you attempt to update one of the store apps. Please see instructions below:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating one of the store apps just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

 

[Mighty Joe]

The way I tried to update apps in the past was through the Store. But I cannot open the Store.

 

[Mighty Joe]

The way I tried to update apps in the past was through the Store. But I cannot open the Store.

Hope you'll excuse the bump.

If there are any logs you'd like me to upload for your review, I'm happy to do so. Would like to get this resolved without doing a Windows 10 reset.

Thank you again.

 

[Mighty Joe]

What might be useful is to get a Process Monitor trace while you attempt to update one of the store apps. Please see instructions below:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating one of the store apps just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or

What might be useful is to get a Process Monitor trace while you attempt to update one of the store apps. Please see instructions below:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating one of the store apps just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

This isn't exactly what you asked for but I thought I would try this on an app that opens but quickly closes in hopes you may be able to pinpoint the crash. Thank you.

Logfile.zip
OneDrive or WeTransfer.

 

[Mighty Joe]

What might be useful is to get a Process Monitor trace while you attempt to update one of the store apps. Please see instructions below:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating one of the store apps just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

This isn't exactly what you asked for but I thought I'd try this on an app that opens but quickly closes in hopes you can pinpoint the crash. Thank you again.
Logfile.zip