Apps (mail, news, weather and others) crashing in Build 16281

Hello,

A factor why your applications crashes is due to corrupted system files on your computer. We recommend that you run the System File Checker. System File Check is a utility available in Windows 10 that checks for system file corruption. If the issue isn't resolved by performing the SFC, kindly use DISM. DISM is used to troubleshoot errors that SFC can't resolve.

See this article: Using System File Checker in Windows 10 and follow the on-screen instructions. In the event that SFC wasn't able to resolve the issue, click on More info on System File Checker and go to DISM on the thread for the steps.

Keep us posted with the result.

Most of my Microsoft apps are broken after 16281 installed, including Store and Edge. 

When I run sfc /scannow, I get: 

Windows Resource Protection could not start the repair service.

I'm looking at DISM now, but wanted to post this in case I get to a point I can't recover from. 

DISM ended with the following:

C:\Users\TheJi> DISM.exe /Online /Cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.16281.1000

Image Version: 10.0.16281.1000

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

However, the log it produced is full of errors. Most ominous-appearing of those is this one:

2017-09-11 20:43:35, Info                  DISM   DISM Package Manager: PID=4456 TID=16520 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2017-09-11 20:43:35, Info                  DISM   DISM Package Manager: PID=4456 TID=16520 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2017-09-11 20:43:35, Info                  DISM   DISM Package Manager: PID=4456 TID=16520 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2017-09-11 20:43:35, Info                  DISM   DISM Package Manager: PID=4456 TID=16520 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
2017-09-11 20:44:32, Info                  DISM   DISM Package Manager: PID=4456 TID=260  Error in operation: (null) (CBS HRESULT=0x800f0821) - CCbsConUIHandler::Error
2017-09-11 20:44:32, Error                 DISM   DISM Package Manager: PID=4456 TID=16520 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0821)
2017-09-11 20:44:32, Error                 DISM   DISM Package Manager: PID=4456 TID=16520 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x800704c7)
2017-09-11 20:44:32, Error                 DISM   DISM Package Manager: PID=4456 TID=16520 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800704c7)
2017-09-11 20:44:32, Error                 DISM   DISM Package Manager: PID=4456 TID=16520 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800704c7)
2017-09-11 20:44:32, Info                  DISM   DISM Package Manager: PID=4456 TID=16520 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2017-09-11 20:44:32, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800704C7
2017-09-11 20:44:32, Info                  DISM   DISM Provider Store: PID=4456 TID=16520 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-09-11 20:44:32, Info                  DISM   DISM Provider Store: PID=4456 TID=16520 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-09-11 20:44:32, Info                  DISM   DISM Provider Store: PID=4456 TID=16520 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

I'm not exactly dead in the water, but I am concerned that the next update might put me at a point I can't recover from. Any advice would be helpful.

After running DISM.exe, I was able to use the vast majority of the apps that were not operational. There were a couple that I downloaded from the store that continued to open briefly and then close. 

I HAVE, HOWEVER, BEEN EXPERIENCING A BIGGER PROBLEMS WITH THE WINDOWS INSIDER UPDATE! As mentioned in my post above, my entire PC was RESET. This has occurred in 3 of 4 updates (16275, 16281 AND NOW 16288). Before taking the time to put the files back into place, download deleted apps, etc. I did take some screenshots of what my PC looks like after THIS UPDATE (16288)

Here is a list of what occurred:

1. File Explorer "RESET" with NONE of my old files transferred into the "new" file explorer. Instead they are found under Users, where I find a number of files containing the files that SHOULD have stayed in place during the update. Notice in the screenshot the variations on my Computer's name attached to these files. This, of course, also means that my lock screen and background photos did not display after the upgrade.

2. My OneDrive files are intact, but will have to be MOVED to the new file explorer in order to avoid having them sync to the new location, once I RESTART OneDrive. I learned this the hard way after my pc was reset with Build 16275.

3. ALL Apps and webpages have been unpinned from my taskbar.

4. Start Menu RESET.

5. Microsoft EDGE has been RESET  (including start pages) and the extensions had to be reactivated.

6. Some minor problems restarted my Office Applications.

7. Had to "verify" my account as if this were a new PC.

8.  Other minor problems, BUT THE BIGGEST PROBLEM IS THAT THE UPDATES ARE NOT LEAVING MY PC IN THE STATE IT WAS IN BEFORE THE UPDATE. 

This also happened with the computer, I maintain for my mother. I am on the fast ring and I keep hers on the slow ring. BUILD 16278 TOTALLY reset her computer and I ended up having to put all files back in place, etc.

I am not sure what the underlying problem is, but am hoping to get some helpful feedback. The attached screenshots show how my computer looks right now. I wanted to wait for a new build with the hopes that it would go smoothly without this type of disruption, but decided that if it occurred again, I would send screenshots, before putting everything back into place. Overall, with the exception of the few apps that I could not get to function, my PC functions well.

I also failed to mention that my PC is a Dell OptiPlex 760 (4 GB Ram--I need more! LOL, 1TB hard drive, dual core), Windows 10 64bit Pro). My other PC is a Dell OptiPlex 780 (4 GB Ram, 250 GB Hard Drive, Windows 10 64-Bit Pro). 

Edge browser has been total reset. Notice "You have a new extension." Furthermore, I don't have "My Feed" set for any news. Had to reset my start page and will later have to re-enter the pages that I have open when I open the Edge Browser.

Start Menu totally RESET! Software for my network printer had to be updated for some reason.

Desktop is reset. I NEVER have these on my desktop, opting to use the desktop shortcut on the taskbar.

I had to "verify" my account with my password. This did not occur during the two previous disruptive updates.

File Explore has, once again, been RESET. MY Files are safe on the PC, BUT NOT in the new File Explorer.

I have been an Insider since June 2015 with no problems and continue to enjoy the program. Just curious about the sudden disruptive updates for my PC. I have not read or heard of any other Insiders with this problem. I hope the screenshots will help some of you guys gain some insight into what may be happening.

I generally format my PC's twice per year and do a clean Windows Install. I am thinking that I may have to do one soon. LOL! Thank you for your assistance in advance.

Thanks for any feedback and/or suggestions you can provide.

You are having a more broad problem than I had, It's a bit of a long shot, but perhaps what I found might help you.

For several builds the UWP apps (store, mail, news, etc.) would not run on my system. If you tried to run them, basically nothing would happen - no window would open, etc. The tile would turn briefly black, and then return to normal.

The problem was specific to a user login. If I created another user and logged in, it could start the apps.

I eventually found a hint that c:\<user>\appdata\local\Microsoft\windows\notifications might be the issue. This turns out to be a cache database that is used by the UWP apps for posting notifications. Mine had become corrupted. The apps would see the corrupted database, and just exit. Copying that folder from another user on the machine finally fixed the problem, and it has not come back.

Given the other user-centric issues you are seeing with other MS tools, you might have additional corruption or deletions from c:\<user>\appdata\local\Microsoft\windows? There are lots of folders for various Microsoft tools in there, presumably storing the user's configuration and history for those apps. If you have a backup of that folder from before the problems started, and there are significant differences from what you see in the current folder, I would "very" carefully (i.e. a folder at a time, backing up the current in case you need to roll back) see if restoring pieces helps. BTW, to do that, you will probably need to be logged in as a different user, since many of those files are locked when you are logged in as that user.

Again, just offering this as a possible hint. I was certainly surprised that this actually fixed my problem.

 I just read through this thread and didn't see anything about backup.  So I'll just point out the very important need to back up anything you have on that system that you don't want to lose ASAP because with the strange things you're seeing, something possibly could make your system become totally unusable.  I hope that doesn't happen, but you know what they say about that ounce of prevention.  Two programs I've used a lot are Macrium Reflect and Easeus Todo Backup, both of which have free versions for non-commercial use.

 Good luck!

You are having a more broad problem than I had, It's a bit of a long shot, but perhaps what I found might help you.

For several builds the UWP apps (store, mail, news, etc.) would not run on my system. If you tried to run them, basically nothing would happen - no window would open, etc. The tile would turn briefly black, and then return to normal.

The problem was specific to a user login. If I created another user and logged in, it could start the apps.

I eventually found a hint that c:\<user>\appdata\local\Microsoft\windows\notifications might be the issue. This turns out to be a cache database that is used by the UWP apps for posting notifications. Mine had become corrupted. The apps would see the corrupted database, and just exit. Copying that folder from another user on the machine finally fixed the problem, and it has not come back.

Given the other user-centric issues you are seeing with other MS tools, you might have additional corruption or deletions from c:\<user>\appdata\local\Microsoft\windows? There are lots of folders for various Microsoft tools in there, presumably storing the user's configuration and history for those apps. If you have a backup of that folder from before the problems started, and there are significant differences from what you see in the current folder, I would "very" carefully (i.e. a folder at a time, backing up the current in case you need to roll back) see if restoring pieces helps. BTW, to do that, you will probably need to be logged in as a different user, since many of those files are locked when you are logged in as that user.

Again, just offering this as a possible hint. I was certainly surprised that this actually fixed my problem.

Thank you for your kind response. I certainly going to take your suggestions and see if any of them might work. If not, I am overdue for the formatting and clean installation of Windows 10. I probably will wait until I can get an IPO for the public release of the Fall Creators Update. I think this is necessary because I believe some errors can compound after multiple updates with new builds! Thank you very much for taking the time to provide some helpful comments!

 I just read through this thread and didn't see anything about backup.  So I'll just point out the very important need to back up anything you have on that system that you don't want to lose ASAP because with the strange things you're seeing, something possibly could make your system become totally unusable.  I hope that doesn't happen, but you know what they say about that ounce of prevention.  Two programs I've used a lot are Macrium Reflect and Easeus Todo Backup, both of which have free versions for non-commercial use.

 Good luck!

Thank you Hula_Baloo for the awesome feedback and suggestions. I am actually pretty good with computers and took for granted that most Insiders would know to back up their PC's. LOL! I have everything backed up and will probably just do a clean install once the Public ISOs are available for the Fall Creators Update. I generally do a clean install twice a year, which always gets rid of these quirks. I am, however, wondering if this is more a Window's problem since the computer I maintain for my mother on the slow ring experienced exactly the same problems when it was updated to build 16278. Thank you for some great backup sources. The more backups the better. Thank you again!

Hello,

A factor why your applications crashes is due to corrupted system files on your computer. We recommend that you run the System File Checker. System File Check is a utility available in Windows 10 that checks for system file corruption. If the issue isn't resolved by performing the SFC, kindly use DISM. DISM is used to troubleshoot errors that SFC can't resolve.

See this article: Using System File Checker in Windows 10 and follow the on-screen instructions. In the event that SFC wasn't able to resolve the issue, click on More info on System File Checker and go to DISM on the thread for the steps.

Keep us posted with the result.

Until Build 16275, I had no problems with updates on TWO Windows 10 PCs, as described in other parts of this thread. I have one on the FAST RING and one on the SLOW RING. On YESTERDAY, the PC on the SLOW RING updated to BUILD 16288 WITH THE EXACT SAME OUTCOME THAT I HAVE DESCRIBED ELSEWHERE. I cannot imagine that both, otherwise very diligently maintained PCs, could have the SAME OUTCOME UNLESS there is something going on with the BUILDS themselves. I noticed that there has been no KNOWN ISSUES shown with any of these updates. 

In any case, there is no need to post screenshots because the PC on the SLOW RING LOOKS EXACTLY as my FAST RING PC looked after numerous updates. The other problem that emerged with the PC on the SLOW RING is the cachepurge error with the Windows Store, so none of your store apps are functioning and, from what I've researched, there is no way to repair this without reinstalling the operating system.

I have run SFC /scannow and DISM.exe, which do not show any problems, which probably is true because, once I put the files back where they belong, the PCs function beautifully (I should not, however, have to do this after every new build), BUT these updates RESET every aspect of my PCs. Perhaps this is not a widespread enough problem to address, BUT as an Insider for over 2 years, I did expect a more thorough investigation of what I reported, some possible reasons (other than file corruption), and some possible solutions.

My recommendation to you all is that you RELEASE an ISO for every new build on the day that the build is released. Furthermore, with EACH build, we are given the option in Windows Update to allow the build to download and update or PCs as usual or to allow us to download the ISO.

As a final troubleshooting step, I called Verizon and had them do a check of my DSL line AND my modem. No problems were found. I, therefore, believe there is a problem, which may not have impacted most Insiders, but is nevertheless a problem with these builds. In 2 years, I have NEVER had this level of disruption with the installation of new builds.