I recently attempted to apply the cumulative patch to upgrade my Windows 10 Pro V1511 to V1607. The patch appeared to run, but the 1st time I tried to sign in it went to that dark screen with the windows icon and the spinner for awhile, then it took me to a generic looking login screen. When I logged in the computer acted like it was a new install, asking for a product key etc. I bypassed all that and made it to the desktop only to discover that it had in fact done a new install. All of my installed software was gone. Luckily I learned long ago not to allow Microsoft updates to run whenever they want to and when I see one of these version updates I make a system image backup before I allow it to run. I was able to restore that and get back to V1511. I've been through 2 Microsoft support sessions and they were unable to help. The last time they ran chkdsk, dism and sfc. Many corrupted lnk files were found that could not be fixed. They also tried to use the normal 1607 install media to do the upgrade. When they tried that it told them there was no upgrade path available so they gave up and informed me my only choice was a fresh Windows 10 V1607 install.
I did some digging and found the sfcfix tool. I ran that and it apparently fixed all but 3 of the link file issues:
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-iSCSI_Initiator_UI and file iSCSI Initiator.lnk. File is reported as corrupt by SFC.
CORRUPT: iSCSI Initiator.lnk of component Microsoft-Windows-iSCSI_Initiator_UI.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator and file ODBC Data Sources (64-bit).lnk. File is reported as corrupt by SFC.
CORRUPT: ODBC Data Sources (64-bit).lnk of component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator and file ODBC Data Sources (32-bit).lnk. File is reported as corrupt by SFC.
CORRUPT: ODBC Data Sources (32-bit).lnk of component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator.
I have not attempted another upgrade yet. I'm hoping that somebody that monitors this forum has run into a similar issue and has a solution.
I did some digging and found the sfcfix tool. I ran that and it apparently fixed all but 3 of the link file issues:
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-iSCSI_Initiator_UI and file iSCSI Initiator.lnk. File is reported as corrupt by SFC.
CORRUPT: iSCSI Initiator.lnk of component Microsoft-Windows-iSCSI_Initiator_UI.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator and file ODBC Data Sources (64-bit).lnk. File is reported as corrupt by SFC.
CORRUPT: ODBC Data Sources (64-bit).lnk of component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator and file ODBC Data Sources (32-bit).lnk. File is reported as corrupt by SFC.
CORRUPT: ODBC Data Sources (32-bit).lnk of component Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Administrator.
I have not attempted another upgrade yet. I'm hoping that somebody that monitors this forum has run into a similar issue and has a solution.