Server 2016 - can't install Servicing Stack Update or Cumulative Update for months

[Maxstar]

Hi,

You have extracted the ZIP-file, please run SFCFix again with the ZIP-file and run the System File Checker again.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-12-13 09:07:50.659
Microsoft Windows Server 10 Build 14393 - amd64
Using .txt script file at C:\Users\G****W****\Desktop\SFCFix.txt [0]

 

[mkaye]

sfc /scannow runs clean!!
moving on to DISM

 

[Maxstar]

Great, if DISM fails please attach the latest CBS logs.

 

[mkaye]

DISM completed successfully!
have 2 newer computers on my domain which were not there on the old disk
removed essentials connector, removed domain
reloaded connector, tried to connect - fails

 

[Maxstar]

So if I understand correctly, you have only a remaining issue with two new clients that can't connect to your DC-server?

 

[mkaye]

yes, server backup was failing also, haven't checked it yet

 

[Maxstar]

Ok, when you'll need further help please let me know and explain the issue in more detail with error codes etc.

 

[mkaye]

server backup still fails

Windows Backup failed to create the shared protection point on the source volumes.
Detailed error: The shadow copy provider had an error. Check the System and Application event logs for more information.

 

[Maxstar]

Upload the Event Viewer logs.

• Click the Start button and in the search box, type Command Prompt
• When you see Command Prompt on the list, right-click on it and select Run as administrator.
  Copy and paste the following commands one at a time into the command prompt and press enter after each.
  

  wevtutil epl SYSTEM "%userprofile%\Desktop\System.evt"
  wevtutil epl APPLICATION "%userprofile%\Desktop\Application.evt"
  PowerShell Compress-Archive -Path "%userprofile%\Desktop\*.evt" -DestinationPath "%UserProfile%\Desktop\EventLogs.zip"

• These commands will collect the System and Application logs and create EventsLogs.zip on your Desktop.
• Attach this file in your next reply.

 

[mkaye]

attached

 

[mkaye]

i tried backing up to another backup drive
Windows Backup failed to create the shared protection point on the source volumes.
Detailed error: The shadow copy provider had an error. Check the System and Application event logs for more information.

 

[Maxstar]

Hi,

Please take a look at this guide, especially the part about Junction Points which may cause this issue.

 

[mkaye]

yes, already found that, removed the junction point - backup still fails

 

[Maxstar]

Please run the following command in an elevated prompt and post the result in your next post.

vssadmin list writers

 

[mkaye]

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: {1776e89f-cdfc-487c-9939-099a890d0782}
State: [10] Failed
Last error: Timed out

Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {f88902d3-e55a-4a95-a9c6-8cfc8a309ca7}
State: [10] Failed
Last error: Timed out

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {4b3b7e62-440d-4b6e-8cc1-a848df4fb934}
State: [1] Stable
Last error: No error

Writer name: 'WIDWriter'
Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
Writer Instance Id: {ae6b9ab5-6fb3-4fc5-8b0f-091a52aa9960}
State: [10] Failed
Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {428c390b-26ab-481c-9a1d-b844629de77e}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {42d59dce-11bf-4fec-97b8-1a5bf5e7bd03}
State: [1] Stable
Last error: No error

Writer name: 'WDS VSS Writer'
Writer Id: {82cb5521-68db-4626-83a4-7fc6f88853e9}
Writer Instance Id: {9fec6f22-52ea-4086-acb4-4bb0234b9446}
State: [10] Failed
Last error: Non-retryable error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b3b3a7d2-031b-4634-96ea-58c5cf2737e4}
State: [10] Failed
Last error: Timed out

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {51144f5b-62b2-4d4d-877b-185407159e73}
State: [1] Stable
Last error: No error

Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {026f2b09-0a13-4951-b3d3-32405374edb9}
State: [10] Failed
Last error: Timed out

Writer name: 'Windows Server Storage VSS Writer'
Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
Writer Instance Id: {abd04dca-b6d6-468b-a9cd-ac06cb0fb7e0}
State: [1] Stable
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {1d840aaf-4ba9-499c-9cbe-a4cc187296dd}
State: [10] Failed
Last error: Timed out

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {752b21af-4c47-4a74-8e0f-517fab88d42e}
State: [10] Failed
Last error: Timed out

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {9fd644bd-0b7c-4463-a62a-f5675bdc39ed}
State: [10] Failed
Last error: Non-retryable error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3a3a9116-1df1-4ff8-9775-09858bc04447}
State: [10] Failed
Last error: Timed out

Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
Writer Instance Id: {d022fd75-c4ef-4ac7-b078-dab04bd02494}
State: [10] Failed
Last error: Timed out

Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {303d9944-133f-44f8-9699-c026f5212924}
State: [10] Failed
Last error: Timed out

Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {e43ef689-e0ac-45e1-adac-7bde6c6a40a8}
State: [10] Failed
Last error: Non-retryable error

 

[Maxstar]

Mmm, please run the following commands as well.

diskshadow
list shadows all

 

[mkaye]

attached

i am only trying to backup my OS & 1 hyper-v folder
i'll remove the hyper-v folder - it's on another disk

 

[Maxstar]

I would suggest to re-register the VSS dll's first with FRST to see if it will resolve the failures showed after running vssadmin list writers

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[mkaye]

attached - doesn't look like it fixed anything?

 

[Maxstar]

Please run the following command and attach Services.txt to your next post.

WMIC SERVICE GET caption, name, startmode, state > "%userprofile%\desktop\services.txt"