I have been following the various threads concerning DISM and SFC with interest as both commands are generating the source problem. I have to say that the PC doesn't have the the problem with the Windows Central Reset apps as they are not there at all. However, the sfclogs.txt are showing the following:-
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 suspected that the ODBC Data Source was suspect for some time now but given the source file is also corrupt what is my best course of action?