Weird SFC/SCANNOW Errors

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_2e9 76e2e5fa70844\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_2ce6c 04cdc275758\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_2e9 76e2e5fa70844\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 wrote:
> They keep referencing AMD64 and I'm running an Intel processor. See below:

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:

http://support.microsoft.com/kb/947821

Hope it helps,
Andrew

--
amclar at optusnet dot com dot au

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" <> wrote in message
news:...
> 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_2e9 76e2e5fa70844\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_2ce6c 04cdc275758\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_2e9 76e2e5fa70844\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.
>
>
>

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" <> wrote in message
news:...
> Mike wrote:
>> They keep referencing AMD64 and I'm running an Intel processor. See
>> below:
>
> 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:
>
> http://support.microsoft.com/kb/947821
>
> Hope it helps,
> Andrew
>
> --
> amclar at optusnet dot com dot au

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" <> wrote in message
news:eA$...
>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" <> wrote in message
> news:...
>> 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_2e9 76e2e5fa70844\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_2ce6c 04cdc275758\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_2e9 76e2e5fa70844\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.
>>
>>
>>
>