When I run sfc /scannow, these are the problems that can't be fixed:
2016-04-17 17:10:09, Info CSI 000051ab [SR] Cannot repair member file [l:17]"Snipping Tool.lnk" of Microsoft-Windows-SnippingTool-App, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing
2016-04-17 17:10:09, Info CSI 000051ad [SR] Cannot repair member file [l:17]"Snipping Tool.lnk" of Microsoft-Windows-SnippingTool-App, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing
2016-04-17 17:10:09, Info CSI 000051ae [SR] This component was referenced by [l:88]"Microsoft-Windows-SnippingTool-Package~31bf3856ad364e35~amd64~~10.0.10586.0.SnippingTool"
2016-04-17 17:10:09, Info CSI 000051af [SR] Could not reproject corrupted file [l:68 ml:69]"??C:ProgramDataMicrosoftWindowsStart MenuProgramsAccessories"[l:17]"Snipping Tool.lnk"; source file in store is also corrupted
2016-04-17 17:10:09, Info CSI 000051b1 [SR] Repair complete
Trying to run the DISM command gives me an error that says the source file can't be located. At one point, I had the snipping tool pinned to my taskbar and had a keyboard shortcut/hotkey set to open it, so I'm sure this is somehow related to that. I don't suppose it's causing a major problem, but it annoys me that I can't run these utilities so I would like to fix this. I don't want to have to refresh my PC and re-download every 3rd party app over again, though, because I think that's more time and energy than it's worth. I've removed the keyboard shortcut command, removed the icon from my taskbar and start menu, and the only instance of the .exe file that I'm aware of is
C:WindowsWinSxSamd64_microsoft-windows-snippingtool-app_31bf3856ad364e35_10.0.10586.0_none_26499a8833fa2713
I used this to make a shortcut and put in the ProgramsAccessories folder since it wasn't there anymore and since I got the error above saying so, but I restarted and ran SFC again and it didn't fix the problem. I also rebuilt the icon cache and that didn't work either.
Any ideas?
Hi, I'd suggest an in-place upgrade repair install. I've done this 3 times, and it's one of the better facilities of Win 10.
Precede it with this in case sthg has happened to your file system:
Windows key + X, click command prompt (admin)
chkdsk C: /F
Make sure the result is clear or fixed.
An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.
For this you need an installation medium with the same base build as you have installed.
Repair Install Windows 10 with an In-place Upgrade - Windows 10 blog
This will refresh Windows, after the manner of a Windows installation.
- all/most associations will be unchanged
- all your programs will be left installed
- you will lose any custom fonts
- you will lose any customised system icons
- you may need to re-establish your Wi-Fi connection
- you will need to redo Windows updates subsequent to the build you have used for the repair install
- Windows.old will be created
- system restore will be turned off- you should turn it on again and I recommend you manually schedule a daily restore point.
- you will need to redo any language downloads including the display language if you changed that)
This is one of the better features of Win10: as each major build comes out, that's your updated reference build, and as updates are mostly cumulative, there will be few to do.
Recommendation:
Before you perform this major repair procedure, do create a disk image.
Please consider using disk imaging regularly. It's a brilliant way to
- preserve your system (and your sanity)
- back up your data
- restore your system to a previously working state in a relatively short time
Recommended: Macrium Reflect or Aomei Backupper (free) + their boot disk/device + large enough external storage medium.
I am chasing a similar error. What I have determined is that SFC is looking for C:ProgramDataMicrosoftWindowStart MenuProgramsAccessorieswhen in Windows 10 it has been renamed to C: ProgramDataMicrosoftWindowStart MenuProgramsWindows Accessories. I checked and this is the case in both my 10 Pro x64 systems.
What do I have to do to fix this?
