This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
It spent around 5 hours downloading updates, and then started an in-place upgrade.
The in-place upgrade failed. Windows 10 could not be installed, so it reverted to the previous condition.
0x800F0830 - 0x20003
An error occured in INSTALL_UPDATES so the install failed in the SAFE_OS phase.
Hmm. I wonder how many of my own 3 hours were used doing that, but at least mine was successful. Anyway...
(1) Make a Windows System Image Backup.
It makes a backup of all the Windows partitions required to boot & run Windows: EFI, Recovery, MSR, & Windows (C:). If you've got additional partition(s), they will also be offered for inclusion. Make it at "START, Settings, Update & Security, Backup, Go to backup & Restore (Win 7)", & make the Repair Disc or ask Cortana for Recovery Drive to put it on USB. Then see...
How to restore a Windows 10 system image to an existing or larger storage device
https://www.winhelp.us/restore-a-system-image-in-windows-7.html
Restore a System Image Backup in Windows 7, 8, 8.1 and 10
Note: That is an informative 3rd-party site, but I know nothing (good or bad) about any downloads or links that are there (or anywhere else).
If your external hard drive (or the internal one I guess) is a Seagate or Maxtor, there will be a free version of Acronis True Image at their site. Seagate calls it DiscWizard. Macrium Reflect, AOMEI Backupper & others also offer free versions of their image makers. These 3rd-party apps are quicker, make more compact images, & are more flexible in use. But the Windows version works in under 15 minutes on my small & uncomplicated system. I must add, DiscWizard's Bootable Media (to restore an image when Windows won't boot) requires a Mouse to operate. Plug one in, & it is instantly recognized.
(2) If we take the error message at its word, it could work to simply bypass the quality updates during the in-place upgrade (or over-install), as kriegalex reports in here...
"We couldn't install Windows 10" 0x800F0830
Wasn't there a box to uncheck for that? Afterwards, of course, go to Windows Update & do take them in.
(3) But may as well do these 10 quick fixes first, but skip QF #9...
https://docs.microsoft.com/en-us/windows/deployment/upgrade/quick-fixes
Quick Fixes
(a) QF #2 took 12+ hours to run on my 1TB HDD first time. Two subsequent runs, took 3.5 hours apiece.
(b) For QF #8, what is your System Model in MSInfo32 (ask Search or Cortana)? That can be BINGed for a site specific to it. Current BIOS version is also in MSInfo32.
"(1) Make a Windows System Image Backup."
And presumably do a restore too? So instead of an in-place upgrade which you thought might have a chance of working, you want to restore an installation which we already know isn't working? Why?
"(2) If we take the error message at its word, it could work to simply bypass the quality updates during the in-place upgrade (or over-install), as kriegalex reports in here..."
I did another in-place upgrade to SP build 239. This time I set it not to download updates, and I removed my second hard drive. The in-place upgrade succeeded but the result is the same as before.
17 applications still say they were presented by Microsoft Corporation and have various sizes and installation dates, but no names and I can't guess what the applications are. Microsoft Store is not one of them. Microsoft Store is still listed by name. But still Microsoft Store does not open.
"(3) But may as well do these 10 quick fixes first, but skip QF #9..."
'1. Remove nonessential external hardware, such as docks and USB devices.'
That would be my second internal SATA hard drive. I did.
'2. Check the system drive for errors and attempt repairs.'
I've checked the system event log to see if it reported any bad blocks found on my hard drives. It didn't.
'3. Run the Windows Update troubleshooter.'
I've done that numerous times. It didn't help.
'4. Attempt to restore and repair system files.'
We already discussed that, right?
'5. Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update.'
Yes, I do that all the time too. If in the middle of working on something then I delay these, but during this discussion I've done lots of reboots. The same updates get installed too, except that if I let the updates install as part of the in-place upgrade then the in-place upgrade fails.
'6. Temporarily uninstall non-Microsoft antivirus software.'
Malware Bytes? Sorry, I didn't uninstall it.
'7. Uninstall all nonessential software.'
Microsoft Store? Actually I did, which can be done from the command line. And then I reinstalled it. But it still doesn't work. I don't know what the other 17 are.
I did not uninstall Microsoft Word, Acrobat Reader, drivers, etc. Those are essential and they work. They aren't Store apps so they work. They survive the in-place upgrade too.
'8. Update firmware and drivers.'
Done a long time ago. Dell Precision M6500, BIOS A10. By the way, 3 other computers with the same model and same version of Windows 10 1903 do work, and this one did work until it stopped working, so I don't think the firmware and drivers are the reason why Microsoft Store stopped working.
'9. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.'
As you and I agreed, I did try that before and the upgrade process failed, so I tried not doing it this time and the upgrade process succeeded but the non-working apps are still non-working.
'10. Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.'
591 GB free.
(1) A Windows system image backup is useful in case things get worse. Unexpected new problems can be undone. But it's best to make one when things are running well. It freezes the goodness in place.
(2) Sadly, that computer was never supported by Dell beyond Windows 7. You've got the latest BIOS, but it is old. Any Win 10 drivers will have to be supplied by MSFT or by component manufacturers. But I doubt the current problem is driver related.
(3) A pity the in-place upgrade was not a cure, even run as you had to do. Looks like most of the quality updates came in anyway afterwards. But the latest one is...
https://support.microsoft.com/en-us/help/4505903
July 26, 2019—KB4505903 (OS Build 18362.267)
Has it come in yet? It does a lot, but I don't see it directly mentions your issue.
(4) One thing an in-place install will not cure is a settings issue...
(a) Do you see anything in MalwareBytes' settings that could affect this - maybe it does something with the firewall or blocks access to system folders?
(b) Windows Pro edition has more control over settings than Home edition. Ask Cortana or Search for GPEdit. Look for something inside that affects Windows features. I believe I've read - if you seek to limit Window's ability to snoop too much - it will react badly & turn off features.
(c) Have you installed & used other registry tweakers, like CCleaner? Same problem as with GPEdit.
(d) Ask Cortana or search for "Reliability History". Does it show the Store apps are trying to come in, but failing? We could try BINGing some of that.
(5) Consider...
(a) Make a system image backup, which can undo the following.
(b) Create, say, 100 GB of unallocated space.
(c) Clean install Windows into it, which takes less 1/2 hour.
This establishes a dual-boot (which is easily reversed two ways). You'll have a new menu at boot for which to choose. If the new instance of Windows works well, it proves the rottenness in the current installation is not a game-ender. Then...
(d) Make a separate backup of user files, including 3rd-party raw downloads.
(e) Repeat the clean install - this time wiping the rotten instance - but read Greg's...
Clean Install Windows 10
That contains every possible consideration preparatory to & post a clean install. The reason I say to repeat it (instead of just removing the rotten instance) is to get all the partitions right. The rotten one has kept the Recovery Partition, for one thing.
We already know that clean installs have Store applications working. My reason for not doing a clean install is that I want to keep my non-Store applications working as they are, with settings that have been working and continue to work.
Yes this PC and its latest BIOS and drivers are old. They're old when clean installs are working. They're old on 3 other PCs of the same model where upgraded installs continue to work.
Yes, KB4505903 was installed again after the in-place upgrade. It also had been installed before being removed by the in-place upgrade, though it had not been easy to get it installed due to repeated failures. After the in-place upgrade, KB4505903 installs immediately.
I do not see anything in Malware Bytes settings that could prevent Store applications from installing. Also Malware Bytes doesn't prevent non-Store applications from installing, though I don't have a problem with non-Store applications anyway. Windows itself has an option which I have not set and Windows itself also doesn't prevent non-Store applications from installing.
A few years ago I used GPEdit to make Windows Update notify me before downloading and installing updates, the same as used to be available as an option in Windows 7 and XP, so that I can be aware and save my work before rebooting. I manually let Windows Update install all updates.
I have not tried CCleaner.
Yes, Reliability History shows that the following Windows Updates failed. There are duplicates in the list. The number of failing applicatinos is likely greater than this.
9NBLGGH4LS1F-Microsoft.StorePurchaseApp
9PK21VDD7LD9-Microsoft.NET.Native.Framework.2.1
9MZ8BK1XV75W-Microsoft.NET.Native.Runtime.2.1
9NBLGGH4LS1F-Microsoft.StorePurchaseApp
9PK21VDD7LD9-Microsoft.NET.Native.Framework.2.1
9MZ8BK1XV75W-Microsoft.NET.Native.Runtime.2.1
9WZDNCRD1HKW-Microsoft.XboxIdentityProvider
9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE
9PK21VDD7LD9-Microsoft.NET.Native.Framework.2.1
9MZ8BK1XV75W-Microsoft.NET.Native.Runtime.2.1
9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE
9PK21VDD7LD9-Microsoft.NET.Native.Framework.2.1
9MZ8BK1XV75W-Microsoft.NET.Native.Runtime.2.1
9WZDNCRFJ3PR-MICROSOFT.WINDOWSALARMS
9NBNPFNSWTGB-Microsoft.UI.Xaml.2.1
9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO
9WZDNCRFHVN5-MICROSOFT.WINDOWSCALCULATOR
9NBNPFNSWTGB-Microsoft.UI.Xaml.2.1
To repeat, you do not need to tell me that a clean install might work; I already know that it does. The question is whether Microsoft can fix an existing install that Microsoft screwed up. The existence of tools like sfc and dism suggests that Microsoft intended to let some kinds of breakage be repaired.
