Use DISM to Repair Windows 10 Image  

Alex 3 said:

I'm sorry about that - I attached the file incorrectly to my last post. Here it is: sfcdetails.txt

Alex

I took a quick look at the file. It looks like you have a bunch of corrupt Default Store App components. Like Email, Calendar, Messaging, etc. Take a look at this tutorial, it may be able to fix it up for you. After running the steps, re-do a SFC /SCANNOW to see results.

Reinstall and Re-register Apps in Windows 10 Windows 10 Performance Maintenance Tutorials



Anybody else with any ideas, chime in! :)

Alex 3 said:

I'm sorry about that - I attached the file incorrectly to my last post. Here it is: sfcdetails.txt

Alex

Code:

2017-06-25 05:52:11, Info                  CSI    000054c6 [SR] Repairing 1 components
2017-06-25 05:52:11, Info                  CSI    000054c7 [SR] Beginning Verify and Repair transaction
2017-06-25 05:52:11, Info                  CSI    000054c9 [SR] Cannot repair member file [l:22]'Windows Foreground.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054cb [SR] Cannot repair member file [l:33]'Windows Notify System Generic.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054cd [SR] Cannot repair member file [l:22]'Windows Background.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054cf [SR] Cannot repair member file [l:27]'Windows Notify Calendar.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054d1 [SR] Cannot repair member file [l:28]'Windows Notify Messaging.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054d3 [SR] Cannot repair member file [l:24]'Windows Notify Email.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054d6 [SR] Cannot repair member file [l:22]'Windows Foreground.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054d7 [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054d9 [SR] Cannot repair member file [l:33]'Windows Notify System Generic.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054da [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054dc [SR] Cannot repair member file [l:22]'Windows Background.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054dd [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054df [SR] Cannot repair member file [l:27]'Windows Notify Calendar.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054e0 [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054e2 [SR] Cannot repair member file [l:28]'Windows Notify Messaging.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054e3 [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054e5 [SR] Cannot repair member file [l:24]'Windows Notify Email.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-25 05:52:11, Info                  CSI    000054e6 [SR] This component was referenced by [l:175]'Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia-Deployment'
2017-06-25 05:52:11, Info                  CSI    000054e9 [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Foreground.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054ec [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Notify System Generic.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054ef [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Background.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054f2 [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Notify Calendar.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054f5 [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Notify Messaging.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054f8 [SR] Could not reproject corrupted file \??\C:\windows\Media\Windows Notify Email.wav; source file in store is also corrupted
2017-06-25 05:52:11, Info                  CSI    000054fb [SR] Repair complete
2017-06-25 05:52:11, Info                  CSI    000054fc [SR] Committing transaction
2017-06-25 05:52:11, Info                  CSI    00005501 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Looking at the original attachment:
The hash mismatches are nothing to worry about. But it looks like there are a bunch of problem sounds?

Did we try the Dism /Online /Cleanup-Image /ScanHealth, Dism /Online /Cleanup-Image /RestoreHealth? Maybe the tool from Kyhi would be easiest?
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

I would also get rid of all OEM bloatware - that just causes problems.

Hello Alex, :)

I looked at your latest SFC details, and it's showing as mismatches for shell .wav sound files as simrick posted above.

Did you modify or copy them from another source?

As long as they are working, these are really nothing to worry about though.

If all else fails, a repair install should be able to fix them if you really want to pursue it.

Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

Brink said:

Hello Alex, :)

I looked at your latest SFC details, and it's showing as mismatches for shell .wav sound files as simrick posted above.

Did you modify or copy them from another source?

As long as they are working, these are really nothing to worry about though.

If all else fails, a repair install should be able to fix them if you really want to pursue it.

Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

Agreed. That was my next thought too.

Alex, you've got two super experts on this stuff looking now. I suspected as I said earlier that they were probably mostly harmless. I, too, agree a repair with an ISO would go a long way.

Alex 3 said:

Hi simrick and thank you.

Last week I ran both dism commands and I ran them again a short time ago using the tool that you linked to (which is amazingly convenient, by the way). Oddly, both in the past and again now, /scanhealth reports that a correction was made, /restorehealth doesn't report any issue, but /scannow still fails.



Hi Brink, thank you very much too.

I did not modify or copy the problem files from any other source. I am working on my dad's new HP Envy and noticed the problem during the initial setup. I then restored the computer to stock using the factory recovery image on the ssd and /scannow reported the same error.

During the past week, after failing with the usual dism command fixes and failing to correct the problem by pointing dism to a mounted Windows 10 iso, I tried doing an in-place Windows 10 upgrade but /scannow still failed.

I then did a refresh with keeping data and /scannow failed.

I then did a reset without keeping any data and /scannow passed. This led me to believe that the HP factory recovery image on the ssd was faulty, so I contacted HP and they sent me a new recovery on a usb. I restored the machine using the HP usb recovery image and /scannow failed.

I've obviously spent more time than I should have on trying to figure out why the stock recovery isn't working. Given what's gone on so far, the only thing that I can come up with is that HP may have defective recovery images for this model (product number: Y0F94AV).

Based on what I've mentioned, do you and simrick recommend that I start setting the machine up after performing a reset (which previously led to a passing /scannow test) or do you recommend using a Windows 10 iso to format the drive and start completely from scratch?

One general question - when it comes to installing drivers after performing a clean install (or even a reset), do you recommend using the drivers on the manufacturer's website for a machine or letting Windows find drivers via Windows Update?
Thanks again for taking the time to help me. I really appreciate it.

Alex

@Alex 3

Alex, The statement above about the RESET....I don't recall seeing that posted before, but I could have missed it, probably did. If a reset did in fact give you a clean sfc /scannow, that is good. A RESET is virtually the same as a clean install, in your case (because the system is brand new), it is a clean install. It is, in fact, a step or two cleaner than an in-place repair. After a successful RESET (MS not HP), the HP Recovery partition and data is virtually worthless. It contains the OS they installed, plus plus tons of bloatware. It can be deleted. Any HP specific apps you may want/need can be downloaded from their support site, without taking the "candy". It appears to me that the RESET option you have already tried successfully is the option you should use. Your choice, of course.

As far as the drivers.....initially, I would go with what MS, thru Windows Update, downloads and installs. They have made it thru WHQL. If there are any specific issues, then an HP driver. HP should have a support site where it can detect and recommend HP specific drivers, similar to what Dell does.

And backup, backup, backup........

TC