locked
Unexpected error refreshing Server Manager: Element not found (Exception from HRESULT: 0x80070490) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am experiencing the following error when using Server Roles on 2008 SP2 x64.

    Unexpected error refreshing Server Manager: Element not found (Exception from HRESULT: 0x80070490)

    I have followed various similar threads, with no clear answers. I have tried the System Update Readiness Tool on clean boot and normal boot. There are no missing repair packages in the log file.

    Below is my CheckSUR.log file.

    Any suggestions are appreciated, concrete steps to fix are preferred ;)

    =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.23186
    Package Version 25.0
    2019-07-13 17:19

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Commandlet-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000            failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Commandlet-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000            failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Commandlet-Package~31bf3856ad364e35~amd64~~6.0.6001.18000         failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Commandlet-Package~31bf3856ad364e35~amd64~~6.0.6001.18000         failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~~6.0.6001.18000            failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~~6.0.6001.18000            failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-CredentialManagementRole-Standard~31bf3856ad364e35~amd64~en-US~6.0.6001.18000         failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-CredentialManagementRole-Standard~31bf3856ad364e35~amd64~en-US~6.0.6001.18000         failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-CredentialManagementRole-Standard~31bf3856ad364e35~amd64~~6.0.6001.18000              failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-CredentialManagementRole-Standard~31bf3856ad364e35~amd64~~6.0.6001.18000              failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Deployment-Services-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Deployment-Services-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Deployment-Services-Package~31bf3856ad364e35~amd64~~6.0.6001.18000            failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Deployment-Services-Package~31bf3856ad364e35~amd64~~6.0.6001.18000            failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-AddOn-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000               failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-Server-Features-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-Server-Features-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-Server-Features-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-IIS-WebServer-Server-Features-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-RecDisc-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000           failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-RecDisc-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000           failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-RecDisc-Package~31bf3856ad364e35~amd64~~6.0.6001.18000                failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-RecDisc-Package~31bf3856ad364e35~amd64~~6.0.6001.18000                failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Rights-Management-Services~31bf3856ad364e35~amd64~en-US~6.0.6001.18000                failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Rights-Management-Services~31bf3856ad364e35~amd64~en-US~6.0.6001.18000                failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Rights-Management-Services~31bf3856ad364e35~amd64~~6.0.6001.18000             failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Rights-Management-Services~31bf3856ad364e35~amd64~~6.0.6001.18000             failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Admin-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Admin-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000             failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Admin-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Admin-Package~31bf3856ad364e35~amd64~~6.0.6001.18000          failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000           failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~en-US~6.0.6001.18000           failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~~6.0.6001.18000                failed to get CurrentState
    (f)     CBS Registry Error   0x80070002      Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~~6.0.6001.18000                failed to get Visibility
    (f)     CBS Registry Error   0x80070002      Package_for_KB2712808_server_1~31bf3856ad364e35~amd64~~6.0.1.0          failed to get Visibility

    Checking Component Store

    Summary:
    Seconds executed: 830
     Found 43 errors
      CBS Registry Error Total count: 43

    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.
    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.
    Customer Experience report successfully uploaded.  Thank you for
    participating.  For more information, see the Microsoft Customer
    Experience Improvement Program on the Microsoft web site.

    ================================

    Sunday, July 14, 2019 12:50 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I suspect some updates may have been removed and remnants left in registry causing errors. You may be left with a repair install.

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

     

     


    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.

    Sunday, July 14, 2019 2:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Dave,

    Thank you for the reply. I have tried that and the option for "Upgrade" from the installation DVD is greyed out and unavailable. When I try opening the installed updates window so I can remove/change installed updates, the list is empty. I have seen some post from years ago with similar issues and some kind techs created scripts specific for those cases to fix the issues avoiding a full reinstall. Hope I can find some answers.

    Thanks again,

    Rafael

    Sunday, July 14, 2019 9:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You cannot start a in-place upgrade by booting the installation media. You'll want to run setup.exe (from within windows) found in the root of the install media. I've seen \checksur like this before and a repair install is unlikely to work. The damage is beyond hope. Time may be better spent standing up a new one, patch fully and migrate the roles or applications over to it.

    As to scripting here's one to try, but again its unlikley.

    https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78

     

     


    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.

    Sunday, July 14, 2019 10:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Bummer......

    Thanks though. I'll get the painful process started then...

    Cheers,

    Rafael

    Sunday, July 14, 2019 10:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry to be the bearer of bad news, but you're welcome.

     

     


    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.

    Sunday, July 14, 2019 10:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Rafael,

    As I noticed some corrupted files located in component store, did you try with DISM command line to repair the component store file？ If not, please check the link below and try DISM command to repair them.

    How to Repair Windows 10 Image using DISM

    Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.

    Bests,

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


    • Edited by Joy-Qiao Monday, July 15, 2019 11:18 AM
    Monday, July 15, 2019 11:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Joy-Qiao,

    Does the DISM command line applies to Windows Server 2008 as well?

    Thanks,

    Rafael

    Tuesday, July 16, 2019 4:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Rafael,

    Sorry, it  not support on Windows Server 2008, we need to use "sfc /sannow" instead.

    Bests,

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

    Tuesday, July 16, 2019 5:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Rafeal, 

    Any update?

    Bests, 

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

    Monday, July 29, 2019 1:40 AM