Page 52 of 55 FirstFirst ... 2425051525354 ... LastLast
  1.    25 Jun 2017 #510
    Join Date : Jun 2017
    Posts : 7
    Windows 10 Pro x64

    Quote Originally Posted by f14tomcat View Post
    @Alex 3

    They may be innocuous. Like I mentioned, if you could post the .txt file, we could look at it and maybe advise. Without it, we have no idea what the issue may be. That is entirely up to you, though. Post back if you want someone here to assist any further.

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

    Alex
      My ComputerSystem Spec
  2.    25 Jun 2017 #511
    Join Date : Oct 2014
    Arnold, MD
    Posts : 29,733
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)

    Quote Originally Posted by Alex 3 View Post
    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!
      My ComputersSystem Spec
  3.    25 Jun 2017 #512
    Join Date : Jun 2017
    Posts : 7
    Windows 10 Pro x64

    Quote Originally Posted by f14tomcat View Post
    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!

    I ran: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    It appeared to complete successfully but sfc/ scanned still fails with the same error. I've attached a new .txt file, which looks like I'm having trouble with the same files.
    sfcdetails (2).txt
      My ComputerSystem Spec
  4.    25 Jun 2017 #513
    Join Date : Apr 2015
    Posts : 12,998
    W10Prox64

    Quote Originally Posted by Alex 3 View Post
    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.
      My ComputerSystem Spec
  5.    25 Jun 2017 #514
    Join Date : Oct 2013
    Posts : 25,786
    64-bit Windows 10 Pro build 17046
    Thread Starter

    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
      My ComputersSystem Spec
  6.    25 Jun 2017 #515
    Join Date : Apr 2015
    Posts : 12,998
    W10Prox64

    Quote Originally Posted by Brink View Post
    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.
      My ComputerSystem Spec
  7.    25 Jun 2017 #516
    Join Date : Oct 2014
    Arnold, MD
    Posts : 29,733
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)

    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.
      My ComputersSystem Spec
  8.    25 Jun 2017 #517
    Join Date : Jun 2017
    Posts : 7
    Windows 10 Pro x64

    Quote Originally Posted by simrick View Post
    [CODE]2017-06-25 05:52:11, Info
    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.

    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.

    Quote Originally Posted by Brink View Post
    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
    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
      My ComputerSystem Spec
  9.    26 Jun 2017 #518
    Join Date : Oct 2014
    Arnold, MD
    Posts : 29,733
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)

    Quote Originally Posted by Alex 3 View Post
    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
      My ComputersSystem Spec
  10.    26 Jun 2017 #519
    Join Date : Jun 2017
    Posts : 7
    Windows 10 Pro x64

    Change of plans - for reasons unknown to me, the "reset" option no longer resolves the system file corruption.

    Performing an in-place upgrade through the Media Creation tool does resolve the system file corruption issue.

    I had been trying to work with the default recovery because it's going to be my dad's computer and I was trying to keep things stock, but it seems like a silly idea at this point, especially given that I was going to end up removing half of the HP programs before I gave it to him anyway.

    The computer has a three year warranty with accident protection and I confirmed with HP (who did offer to take it back) that removing the recovery partition and setting it up from scratch with a W10 iso will not void the warranty (plus I have the default recovery on a usb to flash from if there is ever a hardware problem, which would be the only reason to put a warranty claim in anyway).

    All that said, is there an appreciable difference between starting the set up from the in-place upgrade through Media Creation versus booting from a dvd iso of W10, deleting all ssd partitions and starting from scratch that way?

    I apologize for taking this off topic with this last question, but you've all been very helpful and are already looking at this thread so I figured that this would be the best way to get your advice.

    Alex
      My ComputerSystem Spec

 
Page 52 of 55 FirstFirst ... 2425051525354 ... LastLast


Similar Threads
Tutorial Category
SFC Scannow or DISM/RestoreHealth using Image
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Performance & Maintenance
How to repair your system files using Dism and Sfc in build 10041
Hello, everyone, I've managed to resolve most of my problems with build 10041 by making SFC work. I've opened a thread on Windows Insider's forums explaining how to do it. Check it out:...
Windows Insider
Windows 10 Crashing on CLASSPNP.SYS in safemode and startup repair.
I've just upgraded Windows 7 64-bit HP OEM to Windows 10 Technical preview 64-bit. Extracted the install while booted within 7, install went smoothly, opted to keep all my files, and once the install was finished it went to boot Windows 10. It hung...
General Support
W10 Disk Image Utility Reports Error After Image Creation.
I installed the 32 bit version of W10 on an old Acer laptop to get back up to speed with developments, and one of the first questions or issues that cropped up is when using W10's disk image utility to make a system image. I deliberately wished to...
General Support
Windows 10 TP Repair and Recovery Features
I'm currently running the 10 TP in a virtual machine. I see that the various boot and repair options can be accessed by <shift> Restart from the desktop, however F8 during boot doesn't appear to work. Can someone who is actually running this on...
Installation and Upgrade
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:49.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums