Windows Vista Forums

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

  1. #1


    Rich Guest

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

    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




      My System SpecsSystem Spec

  2. #2


    Tae Song Guest

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

    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" <madeyoulook@xxxxxx> wrote in message
    news:erYMZhW4JHA.1808@xxxxxx

    > 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
    >
    >
    >

      My System SpecsSystem Spec

  3. #3


    Rich Guest

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


    "Tae Song" <tae_song@xxxxxx> wrote in message
    news:2ED9D378-F22D-47DE-BA2C-7E96D075B46E@xxxxxx

    > 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" <madeyoulook@xxxxxx> wrote in message
    > news:erYMZhW4JHA.1808@xxxxxx

    >> 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.18000_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.18000_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



      My System SpecsSystem Spec

  4. #4


    Tae Song Guest

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


    "Rich" <madeyoulook@xxxxxx> wrote in message
    news:OMES$Jf4JHA.5276@xxxxxx

    >
    > "Tae Song" <tae_song@xxxxxx> wrote in message
    > news:2ED9D378-F22D-47DE-BA2C-7E96D075B46E@xxxxxx

    >> 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" <madeyoulook@xxxxxx> wrote in message
    >> news:erYMZhW4JHA.1808@xxxxxx

    >>> 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.18000_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.18000_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.18000_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.



      My System SpecsSystem Spec

  5. #5


    Rich Guest

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


    "Tae Song" <tae_song@xxxxxx> wrote in message
    news:BDB7C8E5-765F-4981-846C-329AAA70B683@xxxxxx

    >
    > "Rich" <madeyoulook@xxxxxx> wrote in message
    > news:OMES$Jf4JHA.5276@xxxxxx

    >>
    >> "Tae Song" <tae_song@xxxxxx> wrote in message
    >> news:2ED9D378-F22D-47DE-BA2C-7E96D075B46E@xxxxxx

    >>> 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" <madeyoulook@xxxxxx> wrote in message
    >>> news:erYMZhW4JHA.1808@xxxxxx
    >>>> 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.18000_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.18000_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.18000_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



      My System SpecsSystem Spec

  6. #6


    Tae Song Guest

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


    "Rich" <madeyoulook@xxxxxx> wrote in message
    news:OpMzkki4JHA.5616@xxxxxx

    >
    > "Tae Song" <tae_song@xxxxxx> wrote in message
    > news:BDB7C8E5-765F-4981-846C-329AAA70B683@xxxxxx

    >>
    >> "Rich" <madeyoulook@xxxxxx> wrote in message
    >> news:OMES$Jf4JHA.5276@xxxxxx

    >>>
    >>> "Tae Song" <tae_song@xxxxxx> wrote in message
    >>> news:2ED9D378-F22D-47DE-BA2C-7E96D075B46E@xxxxxx
    >>>> 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" <madeyoulook@xxxxxx> wrote in message
    >>>> news:erYMZhW4JHA.1808@xxxxxx
    >>>>> 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.18000_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.18000_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.18000_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... :\


      My System SpecsSystem Spec


SFC /scannow found two termserv.dll files it couldn't repair
Similar Threads
Thread Forum
repair corrupt system files after scannow cmd couldn't repair Vista General
sfc scannow can't repair General Discussion
found corrupt files with sfc /scannow General Discussion
The specified module couldn't be found General Discussion
sfc /scannow found corrupt files but was unable to fix some of the Vista General