Hello again Cassie :)
It would take me less than a minute to fix (because it's a common problem, we're well used to dealing with it). But that doesn't answer the *should* we deal with it (an excellent question to ask, I might add).
My opinion is that we should fix this. Despite it causing no problems now, if Microsoft ever release an update to this component in the future, it could then cause that update to fail. Whether or not they ever will, I cannot possibly know.
So I guess you have a bit of a choice. Fix it now, or wait until you actually have a problem (chances are you never will). It honestly doesn't matter very much at all, because it's causing no problem now, and you know how to fix it if you ever need to.
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download SFCFix.exe (by niemiro) and save this to your Desktop.
- Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
- Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFix.txt.
- Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
https://www.dropbox.com/s/tgouirsjs9y8lhl/SFCFix.zip
Then re-run SFC to check that it's fixed.
Richard
