Run SFC Command in Windows 10  

I have been following the posts concerning SFC and DISM commands as both are saying that I have a problems. SFC is saying it is not able to fix the issues and DISM is saying it is unable to locate the source files. The logs have identified that there is something wrong with the 64 bit ODBC and the backup is corrupt as well. The entry is below.

2017-06-23 21:35:28, Info CSI 00002850 [SR] Beginning Verify and Repair transaction
2017-06-23 21:35:30, Info CSI 00002852 [SR] Cannot repair member file [l:30]'ODBC Data Sources (64-bit).lnk' of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-23 21:35:35, Info CSI 000028a0 [SR] Cannot repair member file [l:30]'ODBC Data Sources (64-bit).lnk' of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-06-23 21:35:35, Info CSI 000028a1 [SR] This component was referenced by [l:169]'Microsoft-Windows-Client-Features-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-Package-AutoMerged-enduser-Deployment'
2017-06-23 21:35:35, Info CSI 000028a4 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\ODBC Data Sources (64-bit).lnk; source file in store is also corrupted
2017-06-23 21:35:37, Info CSI 000028e8 [SR] Verify complete

I have used Shawn's tutorial to download the ISO and have mounted it and is under the G drive. However the install file under Sources is an esd and there is no wim. I have used the esd command for the DISM and it gets to 80% and generates the source error message. I have gone through the 4 commands SFC/DISM/SFC/DISM in a row many times and I still have the problem.

I am aware that the download via the Media Creation Tool must be the same version etc as the existing, but where does one look to check this?

If the only option is a repair install as per Shawn's tutorial, I am wondering if this will work given the problems with DISM

parsonm said:

I am aware that the download via the Media Creation Tool must be the same version etc as the existing, but where does one look to check this?

Here's how...

See Language, Edition, Build, and Architecture of Windows 10 ISO file

The current MCT will only download the Creators Update (15063) but it looks like you want the Anniversary Update (14393). If so, use F12 developers tools in Edge or IE to emulate a non-windows browser - you'll be redirected to a page where you can get both the CU and AU .ISOs directly. See here for more details....

How to Download Creators Update ISO via MS w/o Media Creation Tool

Bree, many thanks for that. Yes MCT has downloaded the creators update 15063 Professional edition. No wonder it doesn't want to know. So, do I just use delete to remove the mounted iso on the G drive?
Lack of knowledge means I don't know what you mean in your last part talking about CU and AU.

parsonm said:

So, do I just use delete to remove the mounted iso on the G drive?

Right-click on the G: drive in Explorer's 'This PC' and select Eject to dismount it.

... I don't know what you mean in your last part talking about CU and AU.

Just shorthand for Creators Update and Anniversary Update.

Bree, I am a little confused by the three options on the second link above ( Download Creators Update ISO ). I obviously need to go for the browser plugin to download the correct version of windows 10 from the MCT- does one leave the plugin loaded or is it best to remove it once it has been finished with?

Method 2 using the HeiDoc.net the download page only shows windows 10 not the version - do other pages permit you to specify or is it automatic? Also this method refers to the MS Tech Bench Site that appears to be no longer available - do you think this method will still work?

What I want to do, is download the correct version of the ISO, mount it on the main drive and use that to be the "source" for error corrections. I would also like to create a DVD of the ISO as well for future use.

Parsonm wants an Anniversary Update ISO. The MCT makes a Creators Update one.

To use Method One here open Download Windows 10 in Edge, press F12 and on the Emulation tab set the User Agent String to 'Apple Safari (iPad)'. The page then changes to one where you have a choice of ISO versions to download.

Thank you for your help.
Using Firefox instead of Edge or Explorer, I thought I would take a look at Method 2 to see how it would progress. HeiDoc.net seem to stall early on and then I noticed that Comodo was running it in a virtual mode, so once I had set it as a trusted file things progressed much better. It was a bit hit and miss finding the correct version of the ISO with all the options but got there in the end and downloaded it OK.
Ran DISM and it corrected all the problems which SFC did as well. I still have one or two issues showing up in the logs so I will be running the SFC/DISM sequence a couple of time more to see if I can clear them.

I was wondering if a note could be added to the various tutorials that advise the need to download ISO's for a repair or DISM use, raising the issue of the MCT not downloading like for like ISO's, referring to the tutorial above without the use of the MCT. It is just a thought as I obviously wasn't aware that this was an issue.

Thanks again

Just to let you know that I now have a clean sfcdetails log but the CBS log is showing a number of DIRSD OWNER WARNING which are shown below:-

2017-06-28 19:58:38, Info CSI 00005d60 [DIRSD OWNER WARNING] Directory [l:30 ml:31]'\??\C:\WINDOWS\IME\IMEKR\DICTS' is not owned but specifies SDDL in component Microsoft-Windows-IME-Korean-Core, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-28 19:58:38, Info CSI 00005d61 [DIRSD OWNER WARNING] Directory [l:24 ml:25]'\??\C:\WINDOWS\IME\IMEKR' is not owned but specifies SDDL in component Microsoft-Windows-IME-Korean-Core, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-28 19:58:38, Info CSI 00005d62 [DIRSD OWNER WARNING] Directory [l:29 ml:30]'\??\C:\WINDOWS\IME\IMEKR\HELP' is not owned but specifies SDDL in component Microsoft-Windows-IME-Korean-Core, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-28 19:58:38, Info CSI 00005d63 [DIRSD OWNER WARNING] Directory [l:39 ml:40]'\??\C:\WINDOWS\SysWOW64\IME\IMEKR\DICTS' is not owned but specifies SDDL in component Microsoft-Windows-IME-Korean-Core, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-28 19:58:38, Info CSI 00005d64 [DIRSD OWNER WARNING] Directory [l:41 ml:42]'\??\C:\WINDOWS\SysWOW64\IME\IMEKR\APPLETS' is not owned but specifies SDDL in component Microsoft-Windows-IME-Korean-Core, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2017-06-28 19:58:39, Info CSI 00005d86 [DIRSD OWNER WARNING] Directory [l:28 ml:29]'\??\C:\WINDOWS\SysWOW64\Ipmi' is not owned but specifies SDDL in component Microsoft-Windows-IPMIProvider, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Any course of action to address these issues please?