1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Weird SFC/SCANNOW Errors

Discussion in 'Windows Vista' started by Mike, Jun 26, 2009.

  1. Mike

    Mike Guest

    They keep referencing AMD64 and I'm running an Intel processor. See below:

    \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\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=}
    2009-06-26 23:13:37, Info CSI 000002ce [SR] Cannot
    repair member file [l:20{10}]"tcpmon.ini" of
    Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    6.0.6001.18000, 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
    2009-06-26 23:13:37, Info CSI 000002cf Hashes for file
    member
    \SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758\settings.ini
    do not match actual file [l:24{12}]"settings.ini" :
    Found: {l:32 b:0PDSWziLzWVBYwaR3HhXAym9NjNH+J+Minhz2QfaecY=} Expected:
    {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
    2009-06-26 23:13:37, Info CSI 000002d0 [SR] Cannot
    repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
    Version = 6.0.6002.18005, 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
    2009-06-26 23:13:37, Info CSI 000002d1 Hashes for file
    member
    \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\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=}
    2009-06-26 23:13:37, Info CSI 000002d2 [SR] Cannot
    repair member file [l:20{10}]"tcpmon.ini" of
    Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    6.0.6001.18000, 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

    --

    Don't pick a fight with an old man.
    If he is too old to fight, he'll just kill you.
     
    Mike, Jun 26, 2009
    #1
  3. Andrew McLaren

    Andrew McLaren Guest

    Mike wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > They keep referencing AMD64 and I'm running an Intel processor. See below:<!--colorc--><!--/colorc-->

    Hi Mike,

    Microsoft code and messages usually describe the x64 processor
    architecture as "AMD64", whether the actual CPU is an AMD x64 processor
    or an Intel EM64T processor. AMD invented the 64-bit extensions first,
    so they got naming rights.

    So the fact the messages mention AMD64 is completely normal.

    As to why these SCF messages appear at all ... it seems pretty common
    for SCF to report a mismatch on tcpmon.ini. even on completely normal,
    functioning systems. The INI file is a plain ASCII text file, not an
    executable, so it's pretty low-risk. And these messages are referring to
    the copies in the SxS cache, not the "real" ones out in the System32
    subdirectory; so that makes it even less of an issue.

    But if you really want to clean up all inconsistencies, you can try
    running Microsoft's System Update Readiness Tool. This tool attempts to
    repair any inconsistencies in SxS file data, including the 0x800736CC
    error you're seeing:



    Hope it helps,
    Andrew

    --
    amclar at optusnet dot com dot au
     
    Andrew McLaren, Jun 27, 2009
    #2
  4. Richard Urban

    Richard Urban Guest

    I have over 6300 folders in Winsxs that are labeled AMD64.

    I also run an Intel processor, 64 bit.

    If it isn't broke - don't fix it! (-:

    --

    Richard Urban
    Microsoft MVP
    Windows Desktop Experience


    "Mike" <rathbunger@garbagemail.com> wrote in message
    news:e1SbRbt9JHA.1376@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > They keep referencing AMD64 and I'm running an Intel processor. See
    > below:
    >
    > SystemRootWinSxSamd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844tcpmon.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=}
    > 2009-06-26 23:13:37, Info CSI 000002ce [SR] Cannot
    > repair member file [l:20{10}]"tcpmon.ini" of
    > Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    > 6.0.6001.18000, 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
    > 2009-06-26 23:13:37, Info CSI 000002cf Hashes for file
    > member
    > SystemRootWinSxSamd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758settings.ini
    > do not match actual file [l:24{12}]"settings.ini" :
    > Found: {l:32 b:0PDSWziLzWVBYwaR3HhXAym9NjNH+J+Minhz2QfaecY=} Expected:
    > {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
    > 2009-06-26 23:13:37, Info CSI 000002d0 [SR] Cannot
    > repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
    > Version = 6.0.6002.18005, 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
    > 2009-06-26 23:13:37, Info CSI 000002d1 Hashes for file
    > member
    > SystemRootWinSxSamd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844tcpmon.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=}
    > 2009-06-26 23:13:37, Info CSI 000002d2 [SR] Cannot
    > repair member file [l:20{10}]"tcpmon.ini" of
    > Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    > 6.0.6001.18000, 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
    >
    > --
    >
    > Don't pick a fight with an old man.
    > If he is too old to fight, he'll just kill you.
    >
    >
    > <!--colorc--><!--/colorc-->
     
    Richard Urban, Jun 27, 2009
    #3
  5. Mike

    Mike Guest

    Thanks Andrew.

    --

    Don't pick a fight with an old man.
    If he is too old to fight, he'll just kill you.



    "Andrew McLaren" <me@somewhere.org> wrote in message
    news:u7FWi1v9JHA.2872@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Mike wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    >> They keep referencing AMD64 and I'm running an Intel processor. See
    >> below:<!--colorc--><!--/colorc-->
    >
    > Hi Mike,
    >
    > Microsoft code and messages usually describe the x64 processor
    > architecture as "AMD64", whether the actual CPU is an AMD x64 processor or
    > an Intel EM64T processor. AMD invented the 64-bit extensions first, so
    > they got naming rights.
    >
    > So the fact the messages mention AMD64 is completely normal.
    >
    > As to why these SCF messages appear at all ... it seems pretty common for
    > SCF to report a mismatch on tcpmon.ini. even on completely normal,
    > functioning systems. The INI file is a plain ASCII text file, not an
    > executable, so it's pretty low-risk. And these messages are referring to
    > the copies in the SxS cache, not the "real" ones out in the System32
    > subdirectory; so that makes it even less of an issue.
    >
    > But if you really want to clean up all inconsistencies, you can try
    > running Microsoft's System Update Readiness Tool. This tool attempts to
    > repair any inconsistencies in SxS file data, including the 0x800736CC
    > error you're seeing:
    >
    >
    >
    > Hope it helps,
    > Andrew
    >
    > --
    > amclar at optusnet dot com dot au <!--colorc--><!--/colorc-->
     
    Mike, Jun 27, 2009
    #4
  6. Mike

    Mike Guest

    Sound advice. Thanks, Richard.

    --

    Don't pick a fight with an old man.
    If he is too old to fight, he'll just kill you.



    "Richard Urban" <richardurbanREMOVETHIS@hotmail.com> wrote in message
    news:eA$lr6v9JHA.1248@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >I have over 6300 folders in Winsxs that are labeled AMD64.
    >
    > I also run an Intel processor, 64 bit.
    >
    > If it isn't broke - don't fix it! (-:
    >
    > --
    >
    > Richard Urban
    > Microsoft MVP
    > Windows Desktop Experience
    >
    >
    > "Mike" <rathbunger@garbagemail.com> wrote in message
    > news:e1SbRbt9JHA.1376@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> They keep referencing AMD64 and I'm running an Intel processor. See
    >> below:
    >>
    >> SystemRootWinSxSamd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844tcpmon.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=}
    >> 2009-06-26 23:13:37, Info CSI 000002ce [SR] Cannot
    >> repair member file [l:20{10}]"tcpmon.ini" of
    >> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    >> 6.0.6001.18000, 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
    >> 2009-06-26 23:13:37, Info CSI 000002cf Hashes for
    >> file member
    >> SystemRootWinSxSamd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758settings.ini
    >> do not match actual file [l:24{12}]"settings.ini" :
    >> Found: {l:32 b:0PDSWziLzWVBYwaR3HhXAym9NjNH+J+Minhz2QfaecY=} Expected:
    >> {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
    >> 2009-06-26 23:13:37, Info CSI 000002d0 [SR] Cannot
    >> repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
    >> Version = 6.0.6002.18005, 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
    >> 2009-06-26 23:13:37, Info CSI 000002d1 Hashes for
    >> file member
    >> SystemRootWinSxSamd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844tcpmon.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=}
    >> 2009-06-26 23:13:37, Info CSI 000002d2 [SR] Cannot
    >> repair member file [l:20{10}]"tcpmon.ini" of
    >> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
    >> 6.0.6001.18000, 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
    >>
    >> --
    >>
    >> Don't pick a fight with an old man.
    >> If he is too old to fight, he'll just kill you.
    >>
    >>
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Mike, Jun 27, 2009
    #5

Share This Page