[SOLVED] Unable to update Windows 10 or view Windows Features

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth

And if you can find the following files on the failed boot drive it would be great.
Rich (BB code): 
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat
Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
Packages\Microsoft-Windows-LanguageFeatures-Fonts-Cans-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat
Packages\Microsoft-Windows-LanguageFeatures-Fonts-Cans-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
Packages\WindowsDevicePortal-Desktop-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\WindowsDevicePortal-Desktop-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\WindowsDevicePortal-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\WindowsDevicePortal-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
 

Attachments

Code: 
PS C:\WINDOWS\system32> DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.3803

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I might have good news about the failed boot drive! I did some properly heinous tomfoolery with combining old systems and managed to cobble together something that worked well enough to let me see the contents of that drive, and initial assessment is that only the boot sector of that drive has failed, and I exported the packages folder onto the server already, so I'll take a look as soon as I post this reply. Other than that, I'm taking a forensic image of the drive to hopefully recover anything that might have been deleted.
 

Attachments

Found:
Code: 
Packages\Microsoft-Windows-LanguageFeatures-Fonts-Cans-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat
Packages\Microsoft-Windows-LanguageFeatures-Fonts-Cans-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat
Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum

Still missing:
Code: 
Packages\WindowsDevicePortal-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\WindowsDevicePortal-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\WindowsDevicePortal-Desktop-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\WindowsDevicePortal-Desktop-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.5193.mum
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.19041.5193.cat
Packages\Microsoft-OneCore-DeveloperMode-Desktop-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.19041.5193.mum

I have to check to see if something happened with the imaging, but for now this is what I got.
 
Great, the remaining components (19041.5193 / 19045.5193) are all related to an specific insider build. I've installed that one on a VM, but it was a clean install withoout those FOD packages. So it should be an option to setup an VM with a previous build, and to update that VM with all the FOD packages to the insider version (5193), attached you will find the UUPDump files to create an ISO for this build.

Note: this build (19045.5194) also contain files for (19045.5193).

That said, now we have replaced most of the missing packages you can also try an in-place-upgrade to see what happens?
 

Attachments

Before I proceed, I should make sure I'm understanding you correctly. You are suggesting I try performing an in-place upgrade to the latest version of Windows 10 rather than fiddling around with a virtual machine to get those remaining few packages?
 
The_Meme said:
You are suggesting I try performing an in-place upgrade to the latest version of Windows 10 rather than fiddling around with a virtual machine to get those remaining few packages?
Click to expand...
Yes I woould try this first after making a full system image, maybe an in-place-upgrade with the latest ISO will bypass (all) the remaining issues.
 
For no reason other than to occupy myself while I waited for your reply, I checked to see if anything had changed with regard to the visibility of the items in the "Turn Windows features on or off" dialog. This is certainly an interesting thing to see.
1751196405349.webp
The break in the middle is a result of the window being captured across multiple screens, so that's not anything I'm worried about.

If you recall my initial post in this thread, I mentioned that there were two of most entries for the brief period before it disappeared entirely. Now there are three of several entries and two of most other entries.

How should I feel about this? While it is indicative of progress, and does technically resolve one of the issues, I also feel that this behavior hints at another issue.
 
Last edited:
I should also mention that I haven't actually done anything with the files I found (see post #44) other than copy them into a random folder in my documents. Should I perform DISM with that folder as the source?
 
The_Meme said:
This is certainly an interesting thing to see.
Click to expand...
Yes, we've replaced a large number of packages (cat/mum pairs) and that's why the OptionalFeatures window is working again.

The_Meme said:
Should I perform DISM with that folder as the source?
Click to expand...
Yes, or create an SFCFix.zip file to restore them as explained here: Troubleshooting 0x800f081f / 0x800f0982 Error

Then I would perform an in-place-upgrade which should be work to get this system stable again.
 
Alright, I'll go ahead and do that. What would be your suggested method for making the full system image?
 
If Macrium Reflect would be the ideal, I actually happen to have kept mine from a while ago (the copyright in the About section states "2006-2023") and thus still have the free version.
 
Backing up now. It will be fun figuring out how to make enough space available for the whole backup while it's actively running, but if the program is estimating correctly then I should have about a day and a half to solve that puzzle. Thank you for all of your help so far! I'm very surprised at how similar this process is to what I did about 6 months ago trying to fix it myself. To that point, I had actually downloaded the 5193/5194 update materials from uupdump the other day when I mentioned possibly taking the rest of the work off your hands. I just didn't really trust that I would know what to do with them.
 
Last edited:
You're welcome and fixing (badly) damaged machine could be very complex, and sourcing files for preview / insider versions doesn't make it easier too! Especially when Microsoft releases multiple versions of the same KB number? And that is certainly a needle in a hay stack for specific updates when they are pulled from the update catalog and you can find nothing for the build number of the missing component...
 
The backup is taking longer than expected, but hopefully will be done within 24 hours. I may have to live with just backing up the boot drive until I am able to expand the capacity of the server. That should be fine, yeah?
 
I've finally gotten around to doing an in-place upgrade of Windows. I'll let you know how it goes. Currently it's at 26%.
 
I think it completed the update, but my version number has not changed.

Code: 
PS C:\WINDOWS\system32> DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.3803

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

Despite it reporting no errors, I'm attaching the CBS.log.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top