SDSSnapshotProcess triggers errors with VSS Volume Shadow Copy Service

I just bought two new Optiplex 7000 Towers and one new Precision 3660 Tower from Dell, all three with Win 10 Pro 64-bit and a number of Dell's add-on programs.

In Event Viewer on all three machines, about twice per day (and NOT at startup), there are pairs of Errors about VSS Volume Shadow Copy Service. These seem to be triggered instantly by SDSSnapshotProcess, which might be one of those Dell add-on features (not sure).

Now, these VSS Errors occur only some of the time when SDSSnapshotProcess starts, not all of the time. But the VSS Errors do occur about twice per day and seem always to be triggered by SDSSnapshotProcess. (FYI - On the other occasions when SDSSnapshotProcess starts (no VSS Error), there is a following Information line that "The VSS service is shutting down due to idle timeout.” )

The full Event Viewer Error entry for the VSS Errors is the following:

Log Name: Application
Source: VSS
Date: 8/7/2022 2:48:48 PM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-[Deleted]
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {37cb45f3-0117-4abf-a32e-1ee6a1574338}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-08-07T18:48:48.9427639Z" />
<EventRecordID>3978</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-Deleted]</Computer>
<Security />
</System>

The full Event Viewer Information item for the SDSSnapshotProcess process is the following:

Log Name: Application
Source: SDSSnapshotProcess
Date: 8/7/2022 5:24:07 PM
Event ID: 278
Task Category: (6)
Level: Information
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-[Deleted]
Description:
The description for Event ID 278 from source SDSSnapshotProcess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

The message resource is present but the message was not found in the message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> [schemas.microsoft.com]
<System>
<Provider Name="SDSSnapshotProcess" />
<EventID Qualifiers="16384">278</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>6</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-08-07T21:24:07.3333104Z" />
<EventRecordID>4318</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-[Deleted]</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
</EventData>
</Event>

What do you think about the VSS Errors? How can I fix?

Thanks.

How To Fix "Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface" - Your Digital Mind

FreeBooter - thanks. Update:

Two things have NOT fixed this problem: Macrium Reflect's Fix VSS Problems, and Solution 1 in the article you link to above. I continue to get the VSS Errors,

The Digital Mind article also has Solution 2, but I have not yet tried it because it changes settings at a high level in dcomcnfg, NOT in a specific DCOM component two levels down. What do you think?

You can create a system backup image and try other solutions on that article if anything goes wrong, you will have a backup image to fall back on.

FreeBooter - thanks for suggestion, and good to do.

But my concern is that Solution 2 might create a weakness that I won't know about until much later, when a backup is obsolete.

Does anyone have comments about Solution 2 in the Digital Mind article above?

glnz said:

FreeBooter - thanks for suggestion, and good to do.

But my concern is that Solution 2 might create a weakness that I won't know about until much later, when a backup is obsolete.

Does anyone have comments about Solution 2 in the Digital Mind article above?

No, the suggestion at solution 2 is safe.

Component Services - Administration Practice Windows Server 2003

Freebooter - thanks for your interest!

Your article link is interesting and -- to me -- educational. But I don't see how it discusses whether Solution 2's increased accesses are safe or risky. And by making the access change at the high level suggested by Solution 2, those increased accesses would be for everything in the DCOM hierarchy below - correct?

I'm not zealous about this - just want to understand better what this is.

Thanks.

glnz said:

Freebooter - thanks for your interest!

Your article link is interesting and -- to me -- educational. But I don't see how it discusses whether Solution 2's increased accesses are safe or risky. And by making the access change at the high level suggested by Solution 2, those increased accesses would be for everything in the DCOM hierarchy below - correct?

I'm not zealous about this - just want to understand better what this is.

Thanks.

You are just modifying service permission, how is that going to risk your computer security?