Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Vista General Discussion > SFC /scannow found two termserv.dll files it couldn't repair

Reply
Thread Tools Display Modes

SFC /scannow found two termserv.dll files it couldn't repair

 
 
Rich
Guest
Posts: n/a

 
      05-30-2009
I looked at the CBS.log and found that doing a search this has been going on
since 1/2008 and my system runs fine. I just rebooted yesterday with 1252
hours of processor idle time so I think the system is stable.

I looked at repairing the dll file from the vista disk but I think I could
learn Chinese sooner than follow all these steps to take ownership and get
the files from the disk.

Thanks for any help, Rich



 
Reply With Quote
 
 
 
 
Tae Song
Guest
Posts: n/a

 
      05-30-2009
What instructions did you look at?

Are you sure it's TERMSERV.DLL and not TERMSRV.DLL?

Can you post the relevant portion of your CBS.LOG


"Rich" <> wrote in message
news:...
> I looked at the CBS.log and found that doing a search this has been going
> on since 1/2008 and my system runs fine. I just rebooted yesterday with
> 1252 hours of processor idle time so I think the system is stable.
>
> I looked at repairing the dll file from the vista disk but I think I could
> learn Chinese sooner than follow all these steps to take ownership and get
> the files from the disk.
>
> Thanks for any help, Rich
>
>
>

 
Reply With Quote
 
Rich
Guest
Posts: n/a

 
      05-31-2009

"Tae Song" <> wrote in message
news:2ED9D378-F22D-47DE-BA2C-...
> What instructions did you look at?
>
> Are you sure it's TERMSERV.DLL and not TERMSRV.DLL?
>
> Can you post the relevant portion of your CBS.LOG
>
>
> "Rich" <> wrote in message
> news:...
>> I looked at the CBS.log and found that doing a search this has been going
>> on since 1/2008 and my system runs fine. I just rebooted yesterday with
>> 1252 hours of processor idle time so I think the system is stable.
>>
>> I looked at repairing the dll file from the vista disk but I think I
>> could learn Chinese sooner than follow all these steps to take ownership
>> and get the files from the disk.
>>
>> Thanks for any help, Rich
>>
>>
>>


I did a search on the web and I have to install a program to extract the dll
from the massive file etc.

If you can tell me how to do this easier I would appreciate it!

Rich

Here is the pertinent part of the cbs.log:


Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected: {l:32
b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
2009-05-30 14:23:47, Info CSI 00000248 [SR] Cannot
repair member file [l:22{11}]"termsrv.dll" of
Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-05-30 14:23:47, Info CSI 00000249 Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
{l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
2009-05-30 14:23:47, Info CSI 0000024a [SR] Cannot
repair member file [l:22{11}]"termsrv.dll" of
Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-05-30 14:23:47, Info CSI 0000024b Hashes for file
member \??\C:\Windows\System32\termsrv.dll do not match actual file
[l:22{11}]"termsrv.dll" :
Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
{l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
2009-05-30 14:23:47, Info CSI 0000024c Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
{l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
2009-05-30 14:23:47, Info CSI 0000024d [SR] Could not
reproject corrupted file
[ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll";
source file in store is also corrupted


 
Reply With Quote
 
Tae Song
Guest
Posts: n/a

 
      05-31-2009

"Rich" <> wrote in message
news:OMES$...
>
> "Tae Song" <> wrote in message
> news:2ED9D378-F22D-47DE-BA2C-...
>> What instructions did you look at?
>>
>> Are you sure it's TERMSERV.DLL and not TERMSRV.DLL?
>>
>> Can you post the relevant portion of your CBS.LOG
>>
>>
>> "Rich" <> wrote in message
>> news:...
>>> I looked at the CBS.log and found that doing a search this has been
>>> going on since 1/2008 and my system runs fine. I just rebooted yesterday
>>> with 1252 hours of processor idle time so I think the system is stable.
>>>
>>> I looked at repairing the dll file from the vista disk but I think I
>>> could learn Chinese sooner than follow all these steps to take ownership
>>> and get the files from the disk.
>>>
>>> Thanks for any help, Rich
>>>
>>>
>>>

>
> I did a search on the web and I have to install a program to extract the
> dll from the massive file etc.
>
> If you can tell me how to do this easier I would appreciate it!
>
> Rich
>
> Here is the pertinent part of the cbs.log:
>
>
> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
> 2009-05-30 14:23:47, Info CSI 00000248 [SR] Cannot
> repair member file [l:22{11}]"termsrv.dll" of
> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2009-05-30 14:23:47, Info CSI 00000249 Hashes for file
> member
> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
> do not match actual file [l:22{11}]"termsrv.dll" :
> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
> 2009-05-30 14:23:47, Info CSI 0000024a [SR] Cannot
> repair member file [l:22{11}]"termsrv.dll" of
> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2009-05-30 14:23:47, Info CSI 0000024b Hashes for file
> member \??\C:\Windows\System32\termsrv.dll do not match actual file
> [l:22{11}]"termsrv.dll" :
> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
> 2009-05-30 14:23:47, Info CSI 0000024c Hashes for file
> member
> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
> do not match actual file [l:22{11}]"termsrv.dll" :
> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
> 2009-05-30 14:23:47, Info CSI 0000024d [SR] Could not
> reproject corrupted file
> [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll";
> source file in store is also corrupted
>



You only listed one of the two files it couldn't fix. Go back and copy
paste from "Beginning Verify and Repair transaction" to the end of the
section.

It won't do you any good to copy termsrv.dll from the DVD, because it's
different version than the one that Windows thinks should be installed.
I'm guessing the file is termmgr.dll, but without missing section in the log
I could be wrong.

The version on the DVD is probably 6.0.6000.16386. The one Windows thinks
you should have is 6.0.6001.18000. Once this is fixed, Windows Update will
probably download and eventually install termsrv.dll 6.0.6002.18005.

So this what you can do...

Run regedit and run Find on:

x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762

Find all instances and export/save the entry, then delete it.

After this if you run SFC /SCANNOW, you should have only one file left to
fix.


 
Reply With Quote
 
Rich
Guest
Posts: n/a

 
      05-31-2009

"Tae Song" <> wrote in message
news:BDB7C8E5-765F-4981-846C-...
>
> "Rich" <> wrote in message
> news:OMES$...
>>
>> "Tae Song" <> wrote in message
>> news:2ED9D378-F22D-47DE-BA2C-...
>>> What instructions did you look at?
>>>
>>> Are you sure it's TERMSERV.DLL and not TERMSRV.DLL?
>>>
>>> Can you post the relevant portion of your CBS.LOG
>>>
>>>
>>> "Rich" <> wrote in message
>>> news:...
>>>> I looked at the CBS.log and found that doing a search this has been
>>>> going on since 1/2008 and my system runs fine. I just rebooted
>>>> yesterday with 1252 hours of processor idle time so I think the system
>>>> is stable.
>>>>
>>>> I looked at repairing the dll file from the vista disk but I think I
>>>> could learn Chinese sooner than follow all these steps to take
>>>> ownership and get the files from the disk.
>>>>
>>>> Thanks for any help, Rich
>>>>
>>>>
>>>>

>>
>> I did a search on the web and I have to install a program to extract the
>> dll from the massive file etc.
>>
>> If you can tell me how to do this easier I would appreciate it!
>>
>> Rich
>>
>> Here is the pertinent part of the cbs.log:
>>
>>
>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>> 2009-05-30 14:23:47, Info CSI 00000248 [SR] Cannot
>> repair member file [l:22{11}]"termsrv.dll" of
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
>> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
>> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
>> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
>> 2009-05-30 14:23:47, Info CSI 00000249 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
>> do not match actual file [l:22{11}]"termsrv.dll" :
>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>> 2009-05-30 14:23:47, Info CSI 0000024a [SR] Cannot
>> repair member file [l:22{11}]"termsrv.dll" of
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
>> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
>> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
>> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
>> 2009-05-30 14:23:47, Info CSI 0000024b Hashes for
>> file member \??\C:\Windows\System32\termsrv.dll do not match actual file
>> [l:22{11}]"termsrv.dll" :
>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>> 2009-05-30 14:23:47, Info CSI 0000024c Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
>> do not match actual file [l:22{11}]"termsrv.dll" :
>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>> 2009-05-30 14:23:47, Info CSI 0000024d [SR] Could not
>> reproject corrupted file
>> [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll";
>> source file in store is also corrupted
>>

>
>
> You only listed one of the two files it couldn't fix. Go back and copy
> paste from "Beginning Verify and Repair transaction" to the end of the
> section.
>
> It won't do you any good to copy termsrv.dll from the DVD, because it's
> different version than the one that Windows thinks should be installed.
> I'm guessing the file is termmgr.dll, but without missing section in the
> log I could be wrong.
>
> The version on the DVD is probably 6.0.6000.16386. The one Windows
> thinks you should have is 6.0.6001.18000. Once this is fixed, Windows
> Update will probably download and eventually install termsrv.dll
> 6.0.6002.18005.
>
> So this what you can do...
>
> Run regedit and run Find on:
>
> x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762
>
> Find all instances and export/save the entry, then delete it.
>
> After this if you run SFC /SCANNOW, you should have only one file left to
> fix.



OK I deleted that and then ran SFC and now it finds no errors!

Thanks a lot for the help, Rich


 
Reply With Quote
 
Tae Song
Guest
Posts: n/a

 
      06-01-2009

"Rich" <> wrote in message
news:...
>
> "Tae Song" <> wrote in message
> news:BDB7C8E5-765F-4981-846C-...
>>
>> "Rich" <> wrote in message
>> news:OMES$...
>>>
>>> "Tae Song" <> wrote in message
>>> news:2ED9D378-F22D-47DE-BA2C-...
>>>> What instructions did you look at?
>>>>
>>>> Are you sure it's TERMSERV.DLL and not TERMSRV.DLL?
>>>>
>>>> Can you post the relevant portion of your CBS.LOG
>>>>
>>>>
>>>> "Rich" <> wrote in message
>>>> news:...
>>>>> I looked at the CBS.log and found that doing a search this has been
>>>>> going on since 1/2008 and my system runs fine. I just rebooted
>>>>> yesterday with 1252 hours of processor idle time so I think the system
>>>>> is stable.
>>>>>
>>>>> I looked at repairing the dll file from the vista disk but I think I
>>>>> could learn Chinese sooner than follow all these steps to take
>>>>> ownership and get the files from the disk.
>>>>>
>>>>> Thanks for any help, Rich
>>>>>
>>>>>
>>>>>
>>>
>>> I did a search on the web and I have to install a program to extract the
>>> dll from the massive file etc.
>>>
>>> If you can tell me how to do this easier I would appreciate it!
>>>
>>> Rich
>>>
>>> Here is the pertinent part of the cbs.log:
>>>
>>>
>>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>>> 2009-05-30 14:23:47, Info CSI 00000248 [SR] Cannot
>>> repair member file [l:22{11}]"termsrv.dll" of
>>> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
>>> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
>>> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
>>> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
>>> 2009-05-30 14:23:47, Info CSI 00000249 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
>>> do not match actual file [l:22{11}]"termsrv.dll" :
>>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>>> 2009-05-30 14:23:47, Info CSI 0000024a [SR] Cannot
>>> repair member file [l:22{11}]"termsrv.dll" of
>>> Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version =
>>> 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
>>> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
>>> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
>>> 2009-05-30 14:23:47, Info CSI 0000024b Hashes for
>>> file member \??\C:\Windows\System32\termsrv.dll do not match actual file
>>> [l:22{11}]"termsrv.dll" :
>>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>>> 2009-05-30 14:23:47, Info CSI 0000024c Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762\termsrv.dll
>>> do not match actual file [l:22{11}]"termsrv.dll" :
>>> Found: {l:32 b:eu2l0R7OF4eD0nDgwyjzEjBSdVWPi5TNwcPivgyh0HY=} Expected:
>>> {l:32 b:J9eGRMrbwRw6teDBD4VP1DvNQ7bpHB7R9tNbxQEUdwE=}
>>> 2009-05-30 14:23:47, Info CSI 0000024d [SR] Could
>>> not reproject corrupted file
>>> [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll";
>>> source file in store is also corrupted
>>>

>>
>>
>> You only listed one of the two files it couldn't fix. Go back and copy
>> paste from "Beginning Verify and Repair transaction" to the end of the
>> section.
>>
>> It won't do you any good to copy termsrv.dll from the DVD, because it's
>> different version than the one that Windows thinks should be installed.
>> I'm guessing the file is termmgr.dll, but without missing section in the
>> log I could be wrong.
>>
>> The version on the DVD is probably 6.0.6000.16386. The one Windows
>> thinks you should have is 6.0.6001.18000. Once this is fixed, Windows
>> Update will probably download and eventually install termsrv.dll
>> 6.0.6002.18005.
>>
>> So this what you can do...
>>
>> Run regedit and run Find on:
>>
>> x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.1 8000_none_8e9f41c854441762
>>
>> Find all instances and export/save the entry, then delete it.
>>
>> After this if you run SFC /SCANNOW, you should have only one file left to
>> fix.

>
>
> OK I deleted that and then ran SFC and now it finds no errors!
>
> Thanks a lot for the help, Rich
>


Guess I was wrong about the second file then. One file was creating both
problems... :\

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Repair corrupted system files Zareba Windows Vista General Discussion 7 03-04-2009 02:18 PM
sfc /scannow found corrupt files but was unable to fix some of the Aaron Windows Vista General Discussion 6 05-29-2008 08:05 PM
3 corrupt system files that sfc /scannow cannot fix, including aut briantrease Windows Vista General Discussion 1 08-22-2007 09:52 AM
Repair, SFC /SCANNOW, Recovery Options Ian Matthews Windows Vista Performance 0 08-22-2006 12:17 AM
missing files,how do i repair this problem iain Windows Update 1 11-28-2003 11:53 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59