Cannot repair tcpmon.ini

Software & Operating Systems

Software & Operating Systems
Microsoft, Linux, Productivity software, discussion

Cannot repair tcpmon.ini

This question has suggested answer(s)

When running SFC on my brand new Alienware which is less then a week old it claims this file is corrupt but cannot fix it. Is this an issue and something I should be worried about? I'm running Windows 7.

All Replies
  • To repair it you need to do the following:

    -> First insert your OEM Windows disc.

    -> click on Start > Run. In the box type sfc /scannow. Press enter.

    A Windows scanning service will popup. This will scan your entire hard drive for damaged and corrupted files.  The Windows disc is necessary to replace the old file.

    Run it and restart your system.

    Also to reset  your TCP/IP stack

    Start -> run -> cmd  " Type the following commands (or copy and paste one at a time), each followed by pressing enter. "

    1. ipconfig /flushdns
    2. nbtstat -R
    3. nbtstat -RR
    4. netsh int reset all
    5. netsh int ip reset
    6. netsh winsock reset
    7. reboot

    If these don't help can you post your CBS.LOG - C:\Windows\Logs\CBS\CBS.LOG

  • Thanks for your help, but none of that worked. In my logs it still says the file is corrupt. It repeats the message saying the file is corrupt 4 times. Is this file important, what does it do? Should I even worry about it if I am not experiencing problems? Perhaps Windows is wrong and the file is not corrupt?

    Heres a part of the log.

    2010-02-25 16:02:21, Info                  CSI    000002dc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-02-25 16:02:21, Info                  CSI    000002dd [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
    2010-02-25 16:02:21, Info                  CSI    000002de Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-02-25 16:02:21, Info                  CSI    000002df Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-02-25 16:02:21, Info                  CSI    000002e0 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
    2010-02-25 16:02:21, Info                  CSI    000002e1 Repair results created:
    POQ 117 starts:

  • Yodasmaster
    10-02-25 16:02:21, Info                  CSI    000002dc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral,

    This entry indicates that the file content does not match the operating system definition for the file. In this situation, the SFC.exe program cannot repair the file.

    It's do with updates and printers.

    Check your device manager for any driver problems.  If nothing there then:

    You'll need to make sure that the following files still exist in the %windir%\system32 directory:

    tcpmon.dll
    tcpmon.ini
    tcpmonui.dll
    tcpmib.dll

    If those files are then then copy the lines below to a file with the extension *.REG ( * = name doesn't matter, call it whatever). launch it and it will re-add the monitor entries to the registry. Restart the computer.

    Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port] "Driver"="tcpmon.dll" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports] "LprAckTimeout"=dword:000000b4 "StatusUpdateInterval"=dword:0000000a "StatusUpdateEnabled"=dword:00000001

    But from what I've gathered it's widespread and usually pinned down to drivers and this particular one is used for printers. 

    http://www.w7forums.com/startup-repair-t441.html Is something you could try also. 

  • Thanks for your help, it seems all the files are there. I'm not too good when it comes to this stuff. If I just leave it alone will it harm anything? I have not installed a printer on this computer.

  • No, it doesn't appear to be a major issue.  If it not causing problems then you can wait until theres a solid fix.  From what everyone else is doing you can either copy a good file from another windows7 system with exact same OS or  do a clean install with ALL external devices removed or a factory restore.  But it's not something that will cause you problems for the most part.

    There's no definative information as to what causes it to become corrupted, just that it's happening and generally related to drivers that don't appear to get along with windows 7.

  • Thanks! Is this something you think will get fixed with an auto update or perhaps service patch? Thanks again for your help.

  • From what I gather is a driver compatibility so it's probally left up to the manufacturers to fix thier drivers but microsoft will no doubt address this.

  • Hi, i think I'm having the same kind of problem and I've followed your steps so far but I dont understand this part of ur solution.  Do I have to create the REG file or is it in the %windir%\system32 directory?

    "

    If those files are then then copy the lines below to a file with the extension *.REG ( * = name doesn't matter, call it whatever). launch it and it will re-add the monitor entries to the registry. Restart the computer.

    Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port] "Driver"="tcpmon.dll" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports] "LprAckTimeout"=dword:000000b4 "StatusUpdateInterval"=dword:0000000a "StatusUpdateEnabled"=dword:00000001

    "
    Below is the latest CBS file after the scan.  Any help would be appreciated. 

     

     

    2010-06-30 22:43:56, Info                  CSI    00000120 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    2010-06-30 22:44:02, Info                  CSI    00000121 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :

      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}

    2010-06-30 22:44:02, Info                  CSI    00000122 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    2010-06-30 22:44:02, Info                  CSI    00000123 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"

    2010-06-30 22:44:02, Info                  CSI    00000124 Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini"

     

    2010-06-30 22:52:00, Info                  CSI    000002da [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    2010-06-30 22:52:00, Info                  CSI    000002db Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :

      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}

    2010-06-30 22:52:00, Info                  CSI    000002dc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    2010-06-30 22:52:00, Info                  CSI    000002dd [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"

    2010-06-30 22:52:00, Info                  CSI    000002de Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :

      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}

    2010-06-30 22:52:00, Info                  CSI    000002df Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :

      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}

    2010-06-30 22:52:00, Info                  CSI    000002e0 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted

    2010-06-30 22:52:00, Info                  CSI    000002e1 Repair results created:

  • Have there been any updates on this problem?  I'm seeing the same thing on my XPS running Windows 7 64-bit.  I tried everything in this thread except the repair.  That fails because my Windows disk is Premium and since my machine has been upgraded to Professional the 'upgrade' refuses to run.  Looking at the datestamp on the TCPMON.INI file, I'm doubtful the upgrade would help anyway because the file hasn't been updated since initial install so probably matches what is on the Windows disk.  This seems to be preventing starting the 'HomeGroup Listener' service, so my Homegroup isn't working correctly. 

  • This is what I did to fix the problem: First the problem existed on my brandnew Alienware desktop (running Windows 7 64bit) from day one, so shame on you Dell boys who preload the O/S onto these wonderful machines. This problem actually doesn't cause me any problems and I suspect that sfc /SCANNOW is somewhat flawed in reporting tcpmon.ini as actually being corrupt. However I decided to fix it regardless by simply taking a backup copy of tcpmon.ini found in the Windows\system32 folder just in case I screw up things. Then because it was tcpmon.ini in the system32 bit folder that sfc /SCANNOW was moaning about on my affected machine  I checked my Laptop running Windows 7 32bit which reported no problems under sfc /SCANNOW and simply copied that onto my Alienware  Windows 7 64bit machine into the Windows\system32 folder. I then ran sfc SCANNOW and my Alienware no longer has the tcpmon.ini problem at the moment. There is no useful information as to why this file became corrupted in the first place, but this fix worked for me. An idea would be to ask a friend who has a uncorrupted version of tcpmon.ini preferably with the same version of the operating system that you have and use my simple fix solution. I hope this helps...

  • I tried copying TCPMON.ini but keep getting "Access Denied". It says I "need permission to perform this action" but when I click "try again" I get the same problem.

     

    Btw, thanks for sharing your solution. Sometimes people don't touch back after they've found their answer....regards...

  • See http://support.microsoft.com/kb/929833 - it includes the commands that will let you continue.

    I've actually copied in a good TCPMON.ini without success.  Also having a similar problem with Settings.ini!!!

  • wjlca's link to MS support worked great for me.  I copied tcpmon.ini from the system32 folder in Win 7x64 Home Premium on my laptop, and then used the commands to patch it over the corrupt tcpmon.ini on my desktop, Win 7x64 Ultimate.  Wow...two years later and the issue is finally resolved.

  • You said "and then used the commands to patch it over the corrupt tcpmon.ini on my desktop".

    Which commands exactly?

  •  Your elevated command prompt should look like this:

    C:\windows\system32>takeown /f C:\windows\system32.tcpmon.ini
    SUCCESS: The file <or folder>: "C:\windows\system32\tcpmon.ini" now owned by user "COMPUTER/USER".

    C:\windows\system32>icacls C:\windows\system32\tcpmon.ini /grant administrators:F
    processed file: C:\windows\system32\tcpmon.ini
    Successfully processed 1 files; Failed processing 0 files

    C:\windows\system32>Copy F:\Desktop\tcpmon.ini C:\windows\system32\tcpmon.ini
    Overwrite C:\windows\system32\tcpmon.ini? <Yes/No/All>: y
             1 file<s> copied.

    C:\windows\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    Note that COMPUTER/USER should be your specific computer and username.  And F:\Desktop\tcpmon.ini shoudl refer to the location of the good file that you have copied from a good Win7 system.