Hello again Noel :)
Things are less confusing today. I have some new ideas as of last night, I just didn't have time to post until this morning. Your problem is isn't that I've found corruptions that I can't fix, it's that I haven't found the corruption at all.
Somewhere there's a corrupt character which shouldn't be present (something like
a -->
á). Unfortunately, neither CBS.log nor CheckSUR.log has managed to say *where* this corruption is actually located (which is very rare). Looking at what CBS.log was processing at the time it found the corruption led me to believe that it was located in the SCHEMA hive. Long story short, it isn't.
So, I've got my haystack (every file, folder, and registry key on your computer), I've got my needle (a corruption somewhere), but I don't know where the corruption is, what it looks like, or even what type it is. This, as you can probably guess, is a tiny bit problematic
However, we have some stuff to go on now. CheckSUR hasn't found it, nor has SFCFix, and it's not in your SCHEMA hive. That rules out a whole raft of possibilities. So I've been questioning: what's actually left to search -
where is it?
Anyway, I have another idea based off CBS.log.
Open an Elevated Command Prompt:
https://www.sysnative.com/forums/wi...-prompt-window-windows-windows-vista-7-a.html
Carefully copy-and-paste in the following, then press enter:
dir %SystemRoot% /S > %UserProfile%\Desktop\fileListing.txt
This may take ~two minutes to complete. When it has, zip up and upload (to Dropbox again)
fileListing.txt from your Desktop.
Thank you.
Richard
