none
Windows Server 2016 Essentials Backup Error RRS feed

  • Question

  • I have been trying to do a full backup of our server and I get an error that "the writer's timeout expired between freeze and thaw events".  Reading online a lot of people said that this was caused by 3rd party backup software being installed.  I have confirmed that no additional backup software is installed.

    Does anyone know how I can fix this?

    I've attached some pictures of the errors as well.

    Any help is greatly appreciated!

    Monday, August 5, 2019 3:16 PM

All replies

  • HI
    1 can you try to check update and install the latest update then check if update can solve your issue ?
    2 run below command as admin on wse2016 and check the result ?
    vssadmin list writers
    DISM/Online /Cleanup-image /Scanhealth
    DISM/Online /Cleanup-image /Restorehealth
    3.enter sfc /scannow and wait it finish to fix manifest and system file then go to step 2.
    4.Now type the following commands to stop Windows Update Services and then hit Enter after each one:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
    5.Next, type the following command to rename SoftwareDistribution Folder and then hit Enter:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\catroot2 catroot2.old
    6.Finally, type the following command to start Windows Update Services and hit Enter after each one:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
    7.Reboot your server to save changes.

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


    Tuesday, August 6, 2019 10:10 AM
    Moderator
  • Thank you very much for your response.  I got to step 3 and got an error.

    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    C:\Windows\system32>

    I do have the log file, but wanted to check first before posting that here.  Is there anything in the log that would be a security issue for me or for the server / windows install?

    Here is the result from running step 1

    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.
    
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {f3a79085-947f-4142-bcb3-9ad2fff4bdb5}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {d48ddf16-b1e2-43d7-bdee-4be32c186d92}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {4e7d5c16-de9e-4173-ba1e-b478bb0d667d}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'WIDWriter'
       Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
       Writer Instance Id: {4ebe7cb0-2540-4e0f-a513-39b3088ddb69}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {f7e137a9-e5bd-4541-a680-8648dcc020c9}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {1414eed5-2204-4c58-981b-ae4445ed289e}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {43fc1b58-f90b-467d-b2fe-7fb56bd965ee}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {0a760a7f-bfbf-4c87-8af7-dbb55b277265}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {59a73af1-83d9-447c-aece-d39e2fcfebad}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'NPS VSS Writer'
       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
       Writer Instance Id: {203fbfbe-8613-424d-937d-0755a9e68e66}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Windows Server Storage VSS Writer'
       Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
       Writer Instance Id: {0198dd33-35eb-4788-b960-3f86081d298a}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {e540e411-046c-460e-a40e-78ea29f1c371}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {bc9ec440-2ae8-4530-aca9-3e0f626ef7ec}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {a90cb19c-a0cf-4cfb-9608-e2ce413063d0}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {39fb1a67-9b08-4e1e-9920-c9ff0c866584}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {b7430339-0113-44f7-b4bf-126b8114844d}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {0eb4ce37-5422-4c72-a4c7-299079a06825}
       State: [9] Failed
       Last error: Timed out
    
    
    C:\Windows\system32>DISM/Online /Cleanup-image /Scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    Image Version: 10.0.14393.3085
    
    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    
    C:\Windows\system32>DISM/Online /Cleanup-image /Restorehealthenter sfc /scannow
    
    Error: 87
    
    DISM doesn't recognize the command-line option "sfc".
    For more information, refer to the help by running DISM.exe /?.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\system32>

    Should I go ahead with step 4 or do I need to do something to fix the issues found in the prior steps first?  I just wanted to check first.

    Thank you for your help!

    Tuesday, August 6, 2019 5:00 PM
  • Hi,

    Came across your post here, as been experiencing the exact same issues also as listed above. 

    Is it safe to run a "dism /online /cleanup-image /restorehealth" on a Windows Server?

    Tuesday, August 6, 2019 7:31 PM
  • HI
    Is there anything in the log that would be a security issue for me or for the server / windows install?
    I am not very sure if there is private information in your CBS.log ,so you can try to check it and check if there abvious fail information in this log .

    9 we need to run below command first in command prompt(open as admin)to try to fix the some problem .then go to step 4 to step 7. finnally then check if the problem persist .
    DISM/Online /Cleanup-image /Restorehealth

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

    Thursday, August 8, 2019 2:16 PM
    Moderator
  • HI
    Is there anything in the log that would be a security issue for me or for the server / windows install?
    I am not very sure if there is private information in your CBS.log ,so you can try to check it and check if there abvious fail information in this log .

    9 we need to run below command first in command prompt(open as admin)to try to fix the some problem .then go to step 4 to step 7. finnally then check if the problem persist .
    DISM/Online /Cleanup-image /Restorehealth

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

    Thank you very much for your help.  I ran that and got the blow error:

    C:\Windows\system32>DISM/Online /Cleanup-image /Restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    Image Version: 10.0.14393.3085
    
    [==========================100.0%==========================]
    Error: 0x800f081f
    
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\system32>

    This server is brand new and nothing has been done but setting up SQL on it...

    Friday, August 9, 2019 5:33 PM
  • Is this a DELL server with pre-installed media? Or any other pre-installed or package media?

    Mariëtte Knap [alumna Microsoft SBS MVP]
    www.server-essentials.com | Linkedin | Migrations done the easy way
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, August 9, 2019 6:17 PM
  • Is this a DELL server with pre-installed media? Or any other pre-installed or package media?

    Mariëtte Knap [alumna Microsoft SBS MVP]
    www.server-essentials.com | Linkedin | Migrations done the easy way
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Yes, this is a Dell machine.  Windows Server was preinstalled on it as well.

    Thanks again,

    Friday, August 9, 2019 6:53 PM
  • HI
    8 there is a document for your reference to troubleshoot your issue . 

    https://social.technet.microsoft.com/Forums/security/en-US/d1a5ed7b-2537-4cad-b586-8680cbb6c512/cbs-store-corruption-on-server-2016-repair-with-dism-gets-error-0x800f081f-quotthe-source-files?forum=ws2016


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

    Tuesday, August 13, 2019 5:14 AM
    Moderator
  • HI
    8 there is a document for your reference to troubleshoot your issue . 

    https://social.technet.microsoft.com/Forums/security/en-US/d1a5ed7b-2537-4cad-b586-8680cbb6c512/cbs-store-corruption-on-server-2016-repair-with-dism-gets-error-0x800f081f-quotthe-source-files?forum=ws2016


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

    I ran a scan and it looks like things went well...

    C:\Windows\system32>DISM /Online /Cleanup-Image /Scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085

    Image Version: 10.0.14393.3085

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    Should I proceed with more steps or where do I go from here?

    Thank you for your help!
    Thursday, August 15, 2019 7:07 PM
  • HI
    11 when we run below command in command prompt(open as admin) on wse2016 ,is there also happen this Error: 0x800f081f ?
    DISM/Online /Cleanup-image /Restorehealth


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

    Friday, August 16, 2019 7:57 AM
    Moderator
  • HI
    Is there any progress on your question?

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

    Sunday, August 18, 2019 11:07 PM
    Moderator
  • HI
    11 when we run below command in command prompt(open as admin) on wse2016 ,is there also happen this Error: 0x800f081f ?
    DISM/Online /Cleanup-image /Restorehealth


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

    I apologize, I guess the test wasn't complete...  I did get an error:

    C:\Windows\system32>DISM/Online /Cleanup-image /Restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085

    Image Version: 10.0.14393.3085

    [==========================100.0%==========================]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    C:\Windows\system32>

    Thank you again for your help!

    *Edit:  I just tried to open Group Policy and got this error...

    Tuesday, August 20, 2019 2:17 PM
  • I was able to get the Group Policy Manager opened...  I can't believe a Windows Update created all of these problems...

    This is insane...

    What do I do from here?  

    Thank you again for your help.

    Tuesday, August 20, 2019 7:47 PM
  • HI
    can you upload dism.log and cbs.log on wse2016 to cloud drive and share them here?(please don't include private information about your share link)
    C:\Windows\Logs\DISM\dism.log
    C:\Windows\Logs\CBS



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



    Wednesday, August 21, 2019 3:10 AM
    Moderator
  • HI
    can you upload dism.log and cbs.log on wse2016 to cloud drive and share them here?(please don't include private information about your share link)
    C:\Windows\Logs\DISM\dism.log
    C:\Windows\Logs\CBS



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



    Thank you for your help, I really do appreciate it!

    Here is a link to the ziped up log files: https://1drv.ms/u/s!Av5D8N7IhQH4lpkMNB6zwHvRQA7GCA?e=MMZded

    Please let me know if there's anything else you need.

    Thanks again!

    Wednesday, August 21, 2019 5:17 PM
  • HI
    can you upload dism.log and cbs.log on wse2016 to cloud drive and share them here?(please don't include private information about your share link)
    C:\Windows\Logs\DISM\dism.log
    C:\Windows\Logs\CBS



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



    Thank you for your help, I really do appreciate it!

    Here is a link to the ziped up log files: https://1drv.ms/u/s!Av5D8N7IhQH4lpkMNB6zwHvRQA7GCA?e=MMZded

    Please let me know if there's anything else you need.

    Thanks again!

    Good morning,

    I just wanted to follow up to see if you had a chance to download the logs yet.  I want to restrict access just out of security once you have...

    Please let me know.  Thank you again for all of your help!

    Monday, August 26, 2019 3:11 PM
  • I apologize, the last comment was from me.  A friend of mine used my computer and I didn't realize they were logged in here...

    I was just wondering though if you had had an opportunity to download or review the logs and if I could take them down yet.

    Thank you again for your help!

    Monday, August 26, 2019 7:51 PM
  • HI
    I found below 2 problem are related to your issue in CbsPersist_20190820152311.log 
    2019-08-20 10:13:21, Info                  CBS    DWLD:Search is done, set download progress to 20 percent.
    2019-08-20 10:13:21, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:13:21, Info                  CBS    Repr:Not able to find matching update for package, Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    2019-08-20 10:13:30, Info                  CBS    Failed to get bundled updates [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Info                  CBS    Failed to check whether the update is required [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Info                  CBS    Failed to download updates [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:33, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:33, Info                  CBS    WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
    2019-08-20 10:14:44, Info                  CBS    WU creates the package, AppID:TrustedInstaller MCR, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
    2019-08-20 10:14:44, Info                  CBS    Session: 30758753_2640835705 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2019-08-20 10:14:44, Info                  CBS    DWLD:Search is done, set download progress to 20 percent.
    2019-08-20 10:14:44, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:44, Info                  CBS    Repr:Not able to find matching update for package, Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    2019-08-20 10:14:44, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:44, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2019-08-20 10:14:44, Info                  CBS    Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2019-08-20 10:14:44, Info                  CBS    Ensure CBS corruption flag is clear
    2019-08-20 10:14:44, Info                  CBS   

    problem 1:
    2019-08-20 10:13:30, Info                  CBS    Failed to check whether the update is required [HRESULT = 0x800706be - RPC_S_CALL_FAILED]

    solution for problem 1
    You are unable to view Roles and Features and receive error code 0x800706BE in Server Manager
    https://support.microsoft.com/en-sg/help/2461206/you-are-unable-to-view-roles-and-features-and-receive-error-code-0x800
    ---------------------------------------------------------------------

    problem 2:
    2019-08-20 10:14:44, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    Checking System Update Readiness.
    (p) CSI Payload Corrupt   amd64_admin-dashboard_31bf3856ad364e35_10.0.14393.2636_none_064c7a6ae9cd51c3\Windows Server Essentials Dashboard.lnk
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
    Repair failed: Missing replacement payload.

    Summary:
    Operation: Detect and Repair
    Operation result: 0x800f081f
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 10
     CBS Manifest Corruption: 0
     CBS Metadata Corruption: 0
     CSI Manifest Corruption: 0
     CSI Metadata Corruption: 0
     CSI Payload Corruption: 10
    Total Repaired Corruption: 0
     CBS Manifest Repaired: 0
     CSI Manifest Repaired: 0
     CSI Payload Repaired: 0
     CSI Store Metadata refreshed: True

    solution for problem 2:
    Use the System File Checker tool to repair missing or corrupted system files
    https://support.microsoft.com/en-sg/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

    How to fix errors found in the CheckSUR.log
    https://support.microsoft.com/en-sg/help/2700601/how-to-fix-errors-found-in-the-checksur-log


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





    Thursday, August 29, 2019 7:53 AM
    Moderator
  • Thank you very much for your response.  I looked at all of the links supplied with the trouble shooting steps, and none of the tools it wants me to download support my version of Windows?  Are these tools still safe to run?  Which ones should I use?

    If this issue was created by Windows Update, shouldn't Windows Update be able to fix it?

    Thank you again for your help!  

    Friday, August 30, 2019 4:02 PM
  • Hi Andy,

    I just wanted to follow up on this matter.  I checked out the links you provided with the repair instructions, but both directed me to download a software tool from Microsoft that isn't listed to support this version of Windows Server.

    Are these tools still safe to run?  There are multiple versions listed as well, so I wouldn't be sure which one to use...

    Thank you again for your help!

    Friday, September 6, 2019 2:16 PM
  • HI
    I found below 2 problem are related to your issue in CbsPersist_20190820152311.log 
    2019-08-20 10:13:21, Info                  CBS    DWLD:Search is done, set download progress to 20 percent.
    2019-08-20 10:13:21, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:13:21, Info                  CBS    Repr:Not able to find matching update for package, Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    2019-08-20 10:13:30, Info                  CBS    Failed to get bundled updates [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Info                  CBS    Failed to check whether the update is required [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Info                  CBS    Failed to download updates [HRESULT = 0x800706be - RPC_S_CALL_FAILED]
    2019-08-20 10:13:30, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:33, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:33, Info                  CBS    WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
    2019-08-20 10:14:44, Info                  CBS    WU creates the package, AppID:TrustedInstaller MCR, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
    2019-08-20 10:14:44, Info                  CBS    Session: 30758753_2640835705 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2019-08-20 10:14:44, Info                  CBS    DWLD:Search is done, set download progress to 20 percent.
    2019-08-20 10:14:44, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:44, Info                  CBS    Repr:Not able to find matching update for package, Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    2019-08-20 10:14:44, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2019-08-20 10:14:44, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2019-08-20 10:14:44, Info                  CBS    Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2019-08-20 10:14:44, Info                  CBS    Ensure CBS corruption flag is clear
    2019-08-20 10:14:44, Info                  CBS   

    problem 1:
    2019-08-20 10:13:30, Info                  CBS    Failed to check whether the update is required [HRESULT = 0x800706be - RPC_S_CALL_FAILED]

    solution for problem 1
    You are unable to view Roles and Features and receive error code 0x800706BE in Server Manager
    https://support.microsoft.com/en-sg/help/2461206/you-are-unable-to-view-roles-and-features-and-receive-error-code-0x800
    ---------------------------------------------------------------------

    problem 2:
    2019-08-20 10:14:44, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    Checking System Update Readiness.
    (p) CSI Payload Corrupt   amd64_admin-dashboard_31bf3856ad364e35_10.0.14393.2636_none_064c7a6ae9cd51c3\Windows Server Essentials Dashboard.lnk
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
    Repair failed: Missing replacement payload.
    (p) CSI Payload Corrupt   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
    Repair failed: Missing replacement payload.

    Summary:
    Operation: Detect and Repair
    Operation result: 0x800f081f
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 10
     CBS Manifest Corruption: 0
     CBS Metadata Corruption: 0
     CSI Manifest Corruption: 0
     CSI Metadata Corruption: 0
     CSI Payload Corruption: 10
    Total Repaired Corruption: 0
     CBS Manifest Repaired: 0
     CSI Manifest Repaired: 0
     CSI Payload Repaired: 0
     CSI Store Metadata refreshed: True

    solution for problem 2:
    Use the System File Checker tool to repair missing or corrupted system files
    https://support.microsoft.com/en-sg/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

    How to fix errors found in the CheckSUR.log
    https://support.microsoft.com/en-sg/help/2700601/how-to-fix-errors-found-in-the-checksur-log


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





    Good morning Andy,

    First, I want to thank you for all of your help with this issue.

    I do want to confirm before I proceed however that these software tools are safe.  The tools that these instructions tell me to run on my server do not appear to support Windows Server 2016 however.

    Are these tools safe to run?  Given I cannot run a backup, I just want to make sure before I proceed.

    Thank you for your help!

    Tuesday, September 17, 2019 1:53 PM
  • Can someone help me with this?  The steps to correct the issue tell me to use a program that isn't listed as supporting the OS version?

    Is this safe?  Since the issue doesn't allow me to create a backup, I'm concerned about this and I can't seem to get a response...

    Thank you for your help!

    Tuesday, October 1, 2019 4:11 PM