locked
Server Manager encountered an unexpected error while collecting data about the status of this computer. RRS feed

  • Question

  • I have a 2008 Enterprise server.  I need to access roles and features to uninstall Exchange 2007 and demote it from a DC.

    I am unable to access the roles and features.  I get the error in the title.

    Thanks!


    • Edited by Susan_773 Tuesday, November 13, 2018 2:55 PM
    Tuesday, November 13, 2018 1:11 AM

Answers

All replies

  • I'd verify system and servicing health by running;

    sfc /scannow

    also system update readiness tool

    https://support.microsoft.com/en-us/kb/947821

    Then check for errors in;
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log

     

     




    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, November 13, 2018 1:51 AM
  • Thanks for the reply.

    Ran both.  Found some corruption.  Only fixed some of it.  

    Issue persists.

    Features gives this error: unexpected error refreshing server manager: element not found (exception from HRESULT: 0x80070490)

    Win updates gives an error with the same code.

    • Edited by Susan_773 Tuesday, November 13, 2018 5:41 AM
    Tuesday, November 13, 2018 5:27 AM
  •   Only fixed some of it.  

    Too funny, what were results? check for errors in;
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log

     

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, November 13, 2018 5:36 AM
  • I fixed my post some but you replied first.

    hecking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum Line 1: INDX(

    Checking Package Watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~0.0.0.0 WUClient-SelfUpdate-Au8-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS Registry Error 0x80070002 Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11 failed to get Visibility

    Checking Component Store
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344.manifest amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344
    (f) CSI Missing Identity 0x00000000 identity amd64_b54e65fa34a6e489b86eaeb07044e57f_b77a5c561934e089_6.0.6002.18601_none_ef0613512b8ac1b8
    (fix) CSI Missing Identity CSI Registry Item Repaired amd64_b54e65fa34a6e489b86eaeb07044e57f_b77a5c561934e089_6.0.6002.18601_none_ef0613512b8ac1b8

    Summary:
    Seconds executed: 1458
     Found 5 errors
     Fixed 1 errors
      CSI Manifest Failed Catalog Check Total count: 1
      CSI Missing Identity Total count: 1
      Fixed: CSI Missing Identity.  Total count: 1
      CBS MUM Corrupt Total count: 1
      CBS Registry Error Total count: 1
      CBS Watchlist Package Missing Total count: 1

    Unavailable repair files:
    winsxs\manifests\amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344.manifest
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.cat
    Checking CoreOS key for repairing corruptions.
    Winner version: 6.0.6002.18971.
    Processor architecture: amd64.
    Check key to be repaired: wcm://Microsoft-Windows-CoreOS?

    Tuesday, November 13, 2018 5:44 AM
  • Unavailable repair files: winsxs\manifests\amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344.manifest servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.cat

    2008 (vista kernel) was always prone to servicing corruption. I put repair files up here.

    https://drive.google.com/open?id=1S1QsQSzuPer2RgUa0nxz0dQJmIT8rdtu

    put the manifest file in;

    windows\Temp\CheckSUR\winsxs\manifests\

    and the MUM/CAT pair in;

    windows\Temp\CheckSUR\servicing\packages\

    and rerun the SUR tool to complete repairs.

    Also you mentioned you're demoting a domain controller? If so it may not be worth the trouble to repair. You can simply transfer roles, remove from network and perform clean up.

    https://support.microsoft.com/en-us/help/255504/using-ntdsutil-exe-to-transfer-or-seize-fsmo-roles-to-a-domain-control

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816907(v=ws.10)#bkmk_graphical

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Tuesday, November 13, 2018 2:48 PM
  • 2008 (vista kernel) was always prone to servicing corruption. I put repair files up here.

    https://drive.google.com/open?id=1S1QsQSzuPer2RgUa0nxz0dQJmIT8rdtu

    put the manifest file in;

    windows\Temp\CheckSUR\winsxs\manifests\

    and the MUM/CAT pair in;

    windows\Temp\CheckSUR\servicing\packages\

    and rerun the SUR tool to complete repairs.

    Also you mentioned you're demoting a domain controller? If so it may not be worth the trouble to repair. You can simply transfer roles, remove from network and perform clean up.

    https://support.microsoft.com/en-us/help/255504/using-ntdsutil-exe-to-transfer-or-seize-fsmo-roles-to-a-domain-control

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816907(v=ws.10)#bkmk_graphical

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thanks for the reply.

    Just in case, can you please provide what files would be replaced by the steps you provided so I can back them up first? 

    I need to get the server operational again since I need to properly remove Exchange 2007 from my environment and this error is preventing that.

    If I am unable to get it working properly again, could you provide information on how to remove Exchange 2007 from a 2013-2007 coexistence if the 2007 server isn't operational?

    Thanks!

    Tuesday, November 13, 2018 4:17 PM
  • Just in case, can you please provide what files would be replaced by the steps you provided so I can back them up first?

    The three mentioned unavailable repair files

    http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx

    If I am unable to get it working properly again, could you provide information on how to remove Exchange 2007 from a 2013-2007 coexistence if the 2007 server isn't operational?

    I'd reach out to experts over here on this subject. https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrgenerallegacy

     

     (please don't forget to mark helpful replies as answer)

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.



    Tuesday, November 13, 2018 4:26 PM
  • Tried using those files and the tool again.  No change.

    Just mentioning Exchange 2007.  I need to get this server operational again and just can't simply remove it from AD.

    Tuesday, November 13, 2018 6:02 PM
  • Tried using those files and the tool again. No change.

    What was new result? %SYSTEMROOT%\Logs\CBS\CheckSUR.log

    Just mentioning Exchange 2007. I need to get this server operational again and just can't simply remove it from AD.

    All questions related to exchange should be ask here.

    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrgenerallegacy

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, November 13, 2018 6:56 PM
  • =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.23186
    Package Version 25.0
    2018-11-13 15:12

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum Line 1: INDX(

    Checking Package Watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~0.0.0.0 WUClient-SelfUpdate-Au8-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS Registry Error 0x80070002 Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11 failed to get Visibility

    Checking Component Store
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344.manifest amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344
    (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_514bd4236b32fc87f7f15f083733478c_31bf3856ad364e35_6.0.6002.24170_none_63737f416bd65344.manifest From: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab

    Summary:
    Seconds executed: 1444
     Found 4 errors
     Fixed 1 errors
      CSI Manifest Failed Catalog Check Total count: 1
      Fixed: CSI Manifest Failed Catalog Check.  Total count: 1
      CBS MUM Corrupt Total count: 1
      CBS Registry Error Total count: 1
      CBS Watchlist Package Missing Total count: 1

    Unavailable repair files:
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.cat


    Checking CoreOS key for repairing corruptions.
    Winner version: 6.0.6002.18971.
    Processor architecture: amd64.
    Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
    Recreated value: @_type.
    Recreated value: @dataOnly.
    Recreated value: @default.
    Recreated value: @description.
    Recreated value: @displayName.
    Recreated value: @handler.
    Recreated value: @legacyName.
    Recreated value: @legacyType.
    Recreated value: @migrate.
    Recreated value: @scope.
    Recreated value: @xsd:type.
    Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
    Recreated value: @_type.
    • Edited by Susan_773 Tuesday, November 13, 2018 9:09 PM
    Tuesday, November 13, 2018 8:20 PM
  • You can also try a repair install by running setup.exe from the root of the install media, but note that not all conditions are repairable.

    I'd ask for help with exchange recovery over here.

    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrgenerallegacy

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, November 13, 2018 9:09 PM
  • Thanks for the reply.

    Does it matter if the install image has SP2 or not? I'm not 100% sure if I have an image with SP2 as a part of it.

    Tuesday, November 13, 2018 11:13 PM
  • Yes, it would need to have service pack two. My experience says I'd give this method no more than about a 25% chance of succeeding. Time would likely be better spent on the exchange recovery.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, November 13, 2018 11:18 PM
  • In order to remove exchange, I need to get this corruption fixed so I can access Remove Features in the Server Manager in order to do so. 

    I have a separate TechNet post for exchange specifically relating to this issue.

    https://social.technet.microsoft.com/Forums/en-US/1ab985ef-0d62-46e4-b511-431d9e9a7b4f/removing-exchange-2007-from-2013-coexistence-environment-problem?forum=exchangesvrgeneral

    Wednesday, November 14, 2018 12:30 AM
  • Sounds good, you're welcome. You can follow along here.

    http://forums.msexchange.org/Move_Exchange2007_From_Old_to_New_Server/m_1800514921/tm.htm

    or also start a support case here.

    https://support.microsoft.com/en-us/gp/contactus81?forceorigin=esmc&Audience=Commercial 

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, November 14, 2018 12:43 AM
  • Hi,

    Please confirm that if DISM with parameter Source to specify an external reparation source would be helpful:
    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:< the location of your repair source> /LimitAccess

    Once corruption has been found, we can reference section “How to manually replace a corrupted system file with a known good copy of the file” and try to manually replace the file:
    https://support.microsoft.com/en-ie/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 14, 2018 2:24 AM
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 19, 2018 8:14 AM
  • Hi,

    Is there any update?

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 21, 2018 9:06 AM
  • I'm currently working on a recovery source to try the dism.exe
    Wednesday, November 28, 2018 2:15 AM
  • Hi,

    Is there any update?

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    I keep getting the DISM is not a recognized command.  How do I get to where I can use DISM?
    Wednesday, November 28, 2018 5:26 PM
  • I keep getting the DISM is not a recognized command.  How do I get to where I can use DISM?

    DISM can only be used in Windows 7 and Windows Server 2008 R2 (Not in Windows Vista or in Windows Server 2008)

     

     




    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, November 28, 2018 6:08 PM
  • I keep getting the DISM is not a recognized command.  How do I get to where I can use DISM?

    DISM can only be used in Windows 7 and Windows Server 2008 R2 (Not in Windows Vista or in Windows Server 2008)

     

     




    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    My server is a 2008 Enterprise installation (not R2).

    So, how can I repair Roles and features so I can uninstall the SMTP feature in Server management?

    Is it possible to find these files in a healthy unit or possible for you to provide me with these if it will help the problem?

    Unavailable repair files:
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.mum
    servicing\packages\Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11.cat

    Thanks

    Wednesday, November 28, 2018 7:19 PM
  • Advanced guidelines for diagnosing and fixing servicing corruption
      
     https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee619779(v=ws.10
     
      
    Then the following steps:
      
     1. Download the KB from update catalog. Go to https://www.catalog.update.microsoft.com/search.aspx?q=4034775 This link is for Security Update for Windows Server 2008 for x64-based Systems (KB4034775)
      
     2. Expand the package.
     
      Assuming you downloaded the msu package to the \windows\temp directory and you want to expand the package to c:\targetDir, for example, run the following command:
      
    expand %Windir%\Temp\windows6.0-kb4034775-x64_0d621242403219c85616cb546a72010935eacc15.msu /f:* c:\targetDir
     
      3. Expand the cab files to the same location.
      
    expand C:\targetDir\Windows6.0-KB4034775-x64.cab /f:* c:\targetDir
      
     All the files will be located in the above directory as only payload files are located in specific subdirectories.
      
     Occasionally, the required file may be a root package. Check the above link for detailed instructions.
      
     Then the following steps to fix the error:
      
     4. Copy the files to \windows\Temp\CheckSUR directory of the corrupted computer following the subdirectory format as follows:
      
     All files of type *.mum and *.cat should be placed in the %windir%\Temp\CheckSUR\servicing\packages directory

     All files of type *.manifest should be placed in the %windir%\Temp\CheckSUR\manifests\ directory
       
       
    copy C:\targetDir\package_for_kb4034775_server_bf~31bf3856ad364e35~amd64~~6.0.1.11.cat to %Windir%\Temp\CheckSUR\servicing\packages\
    copy C:\targetDir\package_for_kb4034775_server_bf~31bf3856ad364e35~amd64~~6.0.1.11.mum to %Windir%\Temp\CheckSUR\servicing\packages\

    5. Rerun the System Update Readiness tool.
    https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, November 28, 2018 7:56 PM
  • I also put the two files up here.

    https://drive.google.com/open?id=1S1QsQSzuPer2RgUa0nxz0dQJmIT8rdtu

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, November 28, 2018 8:05 PM
  • Still no luck.  Tried the steps you proposed.  Even tried replacing the windows\servicing folder from a healthy unit.

    Each time I run sfc /scannow, it says it finds and fixes corruption.

    Here's the last run on the update tool. I replaced some of the token with **** in case it contained information that shouldn't be publicly displayed.

    Checking System Update Readiness.
    Binary Version 6.0.6002.23186
    Package Version 25.0
    2018-12-03 21:28

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\package_for_kb4034775_server_bf_31bf3856ad364e35_amd64__6.0.1.11.mum Expected file name Package_for_KB4034775_server_BF~31bf3856ad364e35~amd64~~6.0.1.11.mum does not match the actual file name
    (fix) CBS MUM Corrupt CBS File Replaced package_for_kb4034775_server_bf_31bf3856ad364e35_amd64__6.0.1.11.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
    (fix) CBS Paired File CBS File also Replaced package_for_kb4034775_server_bf_31bf3856ad364e35_amd64__6.0.1.11.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\update-bf.mum Expected file name Package_for_KB4034775_BF~31bf3856ad364e35~amd64~~6.0.1.11.mum does not match the actual file name
    (fix) CBS MUM Corrupt CBS File Replaced update-bf.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
    (fix) CBS Paired File CBS File also Replaced update-bf.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\update.mum Expected file name Package_for_KB4034775~31bf3856ad364e35~amd64~~6.0.1.11.mum does not match the actual file name
    (fix) CBS MUM Corrupt CBS File Replaced update.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
    (fix) CBS Paired File CBS File also Replaced update.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.

    Checking Package Watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~0.0.0.0 WUClient-SelfUpdate-Au8-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS Registry Error 0x80070002 Package_for_KB4034775_server~31bf3856ad364e35~amd64~~6.0.1.11 failed to get Visibility

    Checking Component Store

    Summary:
    Seconds executed: 1437
     Found 5 errors
     Fixed 3 errors
      CBS MUM Corrupt Total count: 3
      Fixed: CBS MUM Corrupt.  Total count: 3
      CBS Registry Error Total count: 1
      CBS Watchlist Package Missing Total count: 1
      Fixed: CBS Paired File.  Total count: 3

    Checking CoreOS key for repairing corruptions.
    Winner version: 6.0.6002.18971.
    Processor architecture: amd64.
    Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=amd64&publicKeyToken=*********&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
    Recreated value: @_type.
    Recreated value: @dataOnly.
    Recreated value: @default.
    Recreated value: @description.
    Recreated value: @displayName.
    Recreated value: @handler.
    Recreated value: @legacyName.
    Recreated value: @legacyType.
    Recreated value: @migrate.
    Recreated value: @scope.
    Recreated value: @xsd:type.
    Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=wow64&publicKeyToken=*********&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
    Recreated value: @_type.
    Recreated value: @dataOnly.
    Recreated value: @default.
    Recreated value: @description.
    Recreated value: @displayName.
    Recreated value: @handler.


    Tuesday, December 4, 2018 4:38 AM
  • The item marked (fix) were repaired by SUR tool you can get other files using similar method I described above or copy them from another healthy server, place files in correct locations and rerun SUR tool.

     vista kernel 2008 was very susceptible to servicing corruption. Unfortunately not all conditions can be repaired.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.



    Tuesday, December 4, 2018 4:40 AM
  • I copied all of the expanded files from KB4034775 into the proper locations so I have nothing left to copy into folders that isn't already there.

    I am also getting update error 0x80070490 if that helps.  

    Tuesday, December 4, 2018 5:56 AM
  • Unfortunately not all conditions can be repaired.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, December 4, 2018 1:29 PM
  • Is there any way to add SP2 to my SP1 image so I can try a repair install?
    Tuesday, December 4, 2018 5:32 PM
  • Slipsteaming is not supported.

    https://blogs.technet.microsoft.com/kevinremde/2008/02/09/i-cant-do-what-why-cant-i-create-my-own-slipstreamed-installation-of-windows-vista-sp1/

    there are still quite a few for sale on ebay. buyer beware

    My experience says a repair install is likely to fail as well.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Tuesday, December 4, 2018 5:42 PM
  • Since DISM is unavailable to me due to not having 2008 R2, is it possible to copy registry entries or other system files from a health unit manually to repair this?

    Doesn't need to be "pretty".  Just needs to be stable enough to uninstall the SMTP feature from server manager and then Exchange 2007/

    Thursday, March 21, 2019 12:52 AM
  •  is it possible to copy registry entries or other system files from a health unit manually to repair this?

    Unlikley, but you can start a support case here with product support.

    https://support.microsoft.com/en-us/hub/4343728/support-for-business

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, March 21, 2019 1:46 AM