Yes, but there should be a second location on his machine here C:\Windows\winsxs\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5 which is where, I believe, the system file checker attempt to get the backup from and that file is apparently corrupted also. According to the CBS.log file that he posted the everything looked good except for this one file, and if he runs it again, with out replacing the one in the other location, I'm affraid it may very well re-corrupt the good file so I would recommend that he replace the file in that location also. I don't think they actually disappeared so much as became corrupted, probably due to something we haven't heard about yet and you're probably right a repair install would probably be the best approach, but he is also booting a Linux Distro so he may very well need your help if he takes that route because all that stuff you do when you help members with multi-boot issues and moving boot files and assigning active partitions and such is a bit out of my wheelhouse.Two points, the first is I would re-run the SFC after a reboot to see if it would help.
Second, it appears the file is the same for 32 and x64 bit and is only in the Windows\System32 folder, BUT there are other related files, like tcpmon.dll and tcpmonui.dll
It is not normal for files like this to disappear...... A repair install may still be the best option.
Nice trouble-shooting, all's well that ends well :I notice that yesterday after executing sfc /scannow I forgot to reboot my laptop afterwards (silly mistake, I am very sorry). Today morning when I have turn it on (for the first time after executing sfc /scannow) I notice the miracle!
cybercore said:With 7 DVD in your drive, Start => type sfc /scannow and wait for the operation to complete
In researching your particular issue, I did find multiple reports of people suggesting that perhaps the System File Checker was reporting a false report of tcpmon.ini being corrupted. I suspect that this might be the case in your instance. I think you would see other problems cropping up if it was infact corrupted. If you look at your actual copy of the file you could certainly compare it to the one that I sent you and see if there are any marked differences.Cybercore,
Effectively, the troubleshooting procedure for this particular problem of "print spooler not running and missing on the service list", is like you said as folowing:
1) Run sfc /scannow.
Details: Do not forget to mention to open an command prompt as administrator (right clik on command console on the menu and choose run as administrator) and to have the Windows 7 DVD on the DVD tray.
2) Wait for it to complete
(I have to add something here before point 3)
2.1 Look at the CBS log (in the command prompt as administrator run notepad and open the file C:\Windows\Logs\CBS\CBS.log), then pressing F3 (or selecting in menu Edit/Search the folowing) search the keyword "corrupted" and see if some files were corrupted, and in such case if the sfc had managed to repair them.
2.2 It is principally important that sfc has repair (if it was damaged) the file spoolsv.exe, I am not very sure (because of my case at least) that, if tcpmon.ini was damaged and sfc was unabled to repair it, that would be important or not. I would bet my soul on that, but, here I am with the tcpmon.ini file not repaired and still I am able to add printers (the final test will be tomorow with the network shared printer).
3. After that reboot
At this point, after rebooting and doing Start -> Run services.msc (or equivalent: control panel -> administrative tools -> Services) you should see (at least in my case it worked that way) "Print Spool" service in the list of services and active. The final check up of that the problem is completly solved is of course trying to add a printer and print a test page.
Cheers!