Missing System Writer

Missing System Writer

Below are the identified causes for missing system writer issue, In most of the case it was identified system writer went missing after patching.

First thing to check if patches took place recently.

1.       Check if recently patching was done, Identified patches causing an issue (KB4087398, KB4089175, KB4089229, KB4089344, KB3170455, KB4090450, KB4056564

For recent issue patching was done on 22/06/18 and patches were found on server having issue.

Further checks to perform.

2.       Check & Delete any .BAK Entries in Registry – This has worked for me on Server 2008R2 - 

    "HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList” 

  Please open the registry editor with regedit. Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer."

3.       Give full rights to NETWORK SERVICES Account on below Reg Key – “HKLM\CurrentControlSet\Services\VSS\Diag” - When this occurs, the Network Service account is removed.     

4.       Delete Temp Files from .NET Folder

C:\Windows\Microsoft.NET\Framework\v2.0.50727 – Delete any Temp Files found inside

5.       Capi2 – 513 Event ID

Execute below:

sc sdset MSLLDP D:(D;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BG)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCDCLCSWRPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SO)(A;;LCRPWP;;;S-1-5-80-3141615172-2057878085-1754447212-2405740020-3916490453)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

You should receive a successful result of

[SC] SetServiceObjectSecurity SUCCESS