I am unclear on what you mean by "remove the whole network". Where I am right now, the network folder is empty. I can't see any other computer on it, and I'm told that "Network Discovery and File Sharing are turned off. Network computers and devices are not visible. Click to change ...", which doesn't. Indeed, that's the issue.
This seems as disconnected and removed as it can get. Is there some other step I'm not seeing?
I have to think that you haven't actually analyzed the log file at all. Let's do that.Until you can fix the file integrity problems I don't think your situation will improve.
When SFC writes a new entry to this file, it is tagged with [SR]. (Other programs may also write to this file. If you want a completely clean file with just SFC entries, delete or rename the existing log file. When SFC can't repair a file, the entry begins with "Cannot repair member file". Any text editor can be used to search for "Cannot repair" in order to find the files causing the problems.
In this log, there is exactly one file that is doing so. It is a log file named MSDTC.LOG and SFC's complaint of it is that it cannot be found.
Running the MSDTC -install command will create or re-create this logfile in %windir%\System32\msdtc and install the distributed transaction coordinator service, which can be started, all without complaint, issue or error. But SFC continues to complain that it cannot find this one file, and not about anything else.
This makes me think that "file integrity problems" is an even more general statement that has even less to do with the actual problem.
Last edited by Bagby; 21 Aug 2012 at 14:26.
What I saw in the CBS. log was that sfc has to move bunches of files around as it tried to fix them and it also complained about dual ownership.
There appeared to be more problems than just one file there.
The only other fixes for this problem I can find are....
Please make sure the following services are enabled and running.
- DNS Client
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
Which is why I recommended the repair install.
Of course having a system image from a point before the problems occurred would come in handy.
Last edited by chev65; 22 Aug 2012 at 11:05.
UPnP Device Host was set to manual and was not running, though the others were. Starting it made no difference to the Computer Browser issue, though.
As I said, Windows refuses to do the repair install.
Restoring a previous system image is my final resort, if this can't be fixed. There are too many situations where windows seems to tie itself in irreparable knots, just like this one, and where ultimately, no one has any idea what could have gone wrong, or how to fix it.
SFC says it's ignoring dual ownership issues. Fine, it's ignoring them, so that's not a problem. EOS. What it IS saying is that a file that's right where it's supposed to be, is missing. I even restored MSDTC.LOG from the install disk to its correct location, yet SFC continues to complain that it's missing.
Bottom line, we have a diagnostic that's lying. Something else is wrong. The tool can't be trusted, so since we don't know what's wrong (and we can't see how what it says is wrong is even germaine to the actual issue -- why should the presence or absence of that log file matter to the Computer Browser service, and why doesn't CBS throw an error when it crashes, if it is crashing?-- we just scrap the whole mess and go back to either the beginning, or some point before it collapsed of its own weight. I'm not convinced that running down SFC's problems is not just a red herring and a distraction anyway, that if they were all solved, this would even affect the issue at hand.
Quote