Windows 10: Why directxdatabaseupdater.exe try to delete a Volume Shadow Snapshot

We are using Crowdstrike and it detected that directxdatabaseupdater.exe tried to delete a Volume Shadow Snapshot. I want to know why it did this. Is it a normal operation? Thank you.

:)

 

Failed to Create Volume Snapshot Macrium Error 0x8004230f VSS Error

Hi, you might try this:
Microsoft Volume Shadow Copy (VSS) Troubleshooting - Microsoft Volume Shadow Copy (VSS) Troubleshooting

or the free cautious repair tool
Tweaking.com - Windows Repair Free/Pro
- observing the steps and using only the relevant repairs

More:
How to Fix VSS Errors Step-by-Step

Otherwise I suggest- assuming your disk and file system are sound-
an in-place upgrade repair install which keeps all progs, data and most settings

You need an iso of the same base language and build- freely downloadable.

 

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.

I am getting a bunch of errors in the application log related to the Volume Copy Service. I first noticed it when I tried to create a recovery drive and the error simply said that "A problem occurred while creating the recovery drive"

I examined the application log and noticed that this error occurs periodically, not only when I try to create the drive. I included the four errors below.

What do I need to do to fix this?

I am using a Surface pro 4, windows 10 with up to the minute patches. I also have installed carbonite but I doubt this is the cause as I did not encounter this problem on previous PCs

Thanks in advance for any assistance

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance
on class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered

].

Operation:

Obtain a callable interface for this provider

List interfaces for all providers supporting this context

Check If Volume Is Supported by Provider

Add a Volume to a Shadow Copy Set
Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Snapshot Context: 4194304

Execution Context: Coordinator

Provider ID: {00000000-0000-0000-0000-000000000000}

Volume Name: \\?\Volume{acda900a-c1f6-4b66-831d-a54d0f93e6db}\

Execution Context: Coordinator

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

List interfaces for all providers supporting this context

Check If Volume Is Supported by Provider

Add a Volume to a Shadow Copy Set

Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Snapshot Context: 4194304

Execution Context: Coordinator

Provider ID: {00000000-0000-0000-0000-000000000000}

Volume Name: \\?\Volume{acda900a-c1f6-4b66-831d-a54d0f93e6db}\

Execution Context: Coordinator

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from
CoCreateInstance on class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

Add a Volume to a Shadow Copy Set

Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Execution Context: Coordinator

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

Add a Volume to a Shadow Copy Set
Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Execution Context: Coordinator

 

Windows Defender incorrectly reports threat in Volume Shadow Copy

I think you misread my question.

I did what you suggest immediately after I first downloaded the file.

The problem is NOT that the file itself gets flagged -- it does not as it is in the exclusions list.

The problem is that the exclusions list applies to the absolute path to the file.

What Windows Defender is complaining about is the COPY of the file that is present in the Volume Shadow Copy, NOT the original file.

There appears to be no way to tell Windows Defender to ignore the COPY of the file in the Volume Shadow Copy. Then, every time my backup program (Retrospect) runs, Windows Defender detects the file IN THE VOLUME SHADOW COPY and complains.