You did it correctly this time however it looks like you used the 32-bit command-prompt window and not the 64-bit.
When you opened cmd.exe you opened it from C:\Windows\SysWOW64
I was using a keyboard shortcut program (HotkeyP) that opened the command prompt at c:\windows\system32. However, as HotkeyP is a 32-bit program, Windows in its infinite wisdom redirected it over to C:\Windows\SysWOW64, where it got the 32-bit version of the command prompt.
I need you to open it up from c:\windows\system32 and then do the steps again.
Thanks.
Having run into similar versions of this problem before, I had actually created a junction point named C:\Windows\system64 that always pointed to c:\windows\system32. So I changed my command prompt entries in HotkeyP to run C:\Windows\system64\cmd.exe. This worked, and I now get the 64-bit version of the command prompt when I invoke it via hotkey.
The results of running sfc /scannnow are completely different when I use the 64-bit version of the command prompt. In fact, sfc now runs perfectly, with no errors, and no corrupted files detected. So my sfc problem can be considered fixed. Thanks!
This still leaves the problem that when I create a shortcut for my Windows 10 app (Fitbit) in the taskbar, the shortcut's icon is invisible, and none of the standard fixes for repairing this work. Interestingly, this started right after I restored my system from backup; the icon had been displaying fine for months before this. Everything else on my system works fine after the restore from backup. Is this something you could look into, or is there somewhere else on this forum that I should be asking about this?
Thanks again for all your help!