Event ID 4 in Event Log.

Using the latest version of SPD on WIndows 10 x64 Creators Update.

I started getting the warning message below recently.  It might have been after installing the Windows 10 Creators Update or one of the subsequent Cumlative Updates.  This warning is generated when taking a backup.  A similar error is generated when I mount a backup volume. Other than the warning message everything seems to be OK.

--------------------------------------------

File System Filter 'wcifs' (Version 10.0, ‎2001‎-‎02‎-‎13T23:10:20.000000000Z) failed to attach to volume '\Device\00000072'.  The filter returned a non-standard final status of 0xC0000010.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

--------------------------------------------

I opend up a support request (00286778) but haven't heard back from STC.  BTW... is there a way to view my support request?  I can't seem to find a way.

Comments

streetw0lf

Is their anyone alive at STC?

Doesn't anyone from STC respond?  I also haven't gotten any response in regards to my support request.  Great product, lousy support.

STC-JoshS

Currently there isn't a way

Currently there isn't a way to view your support requests and the currently released version of SPX was not tested against the creators update, so there might be some weird errors that come out from it. Is it functioning correctly and still taking backups and just posting this into the log?

Edit: doing a little more digging, this doesn't look like its being caused by us directly. It looks like its an issue with VSS (which we leverage to do backups) in the Creators Update. So while we are initating the action that puts the event into the log, there isn't anything we can do to fix it.

Here is one of the forum threads I saw detailing this issue.

https://www.tenforums.com/general-support/77514-file-system-filter-wcifs...

RabbitWolf

I get the same error - started before 1703 update

Hi,

I get the same error. I also have updated to Windows 10 x64 Creators Update. However, this error started appearing in February after a Windows update. The strange thing I noticed is that the 'Device\xxxxxxxx' is different each time. This error is definitely generated when ShadowProtect created a backup.

STC-JoshS

This is an issue with VSS,

This is an issue with VSS, not us in particular. I would recommend clearing out your shadow storage (vssadmin delete shadows /all) and potentiall looking for any disk errors in the event logs.

streetw0lf

Let's give STC the benefit of

Let's give STC the benefit of the doubt and say it's Microsoft's fault.  I would think that since you depend on VSS so much your developers would reach out to MS to find out what exactly is going on.  Perhaps a circumvention can be found.  In my case, even though I get the error messages, it doesn't affect my backups which are full backups.  But what about your users that get failing backups and restores.  Is telling them that it's Microsoft's fault the way to go?  Of course not.  You have a responsibility to sort out MS's mess to make your users feel secure in using your product.

STC-JoshS

I still haven't gotten any

I still haven't gotten any indication of whether or not the backups are failing. I haven't been able to recreate the issue in my testing so far either. A warning in the event logs is just that, a warning. But from what I can tell so far its not affecting our backups.

coleys

A lot of people started

A lot of people started getting this same warning in February that aren't even using StorageCraft's products. I think that would indicate that this isn't StorageCraft's problem.

streetw0lf

Even if this is the case I

Even if this is the case I would think that STC would touch bases with Microsoft about the issue.  Those that use STC products and see the messages will think there is a problem with STC products.  MS might have even made a change that never got communicated to the products that use VSS.

I recall looking at the Macrium forum where they also have this problem and Macrium provided a fix for it.

RabbitWolf

Problem continues in Windows Creator Update (1703)

I did a clean install of Windows Professional 10 v1703. I also installed ShawdowProtect Desktop v6.5.2. I then did a quick mount of a backup and got this error:

File System Filter 'wcifs' (Version 10.0, 2088-07-28T20:04:59.000000000Z) failed to attach to volume '\Device\ShadowMount1'

As you can see, the new version of WIndows does not solve the problem.

 

 

STC-JoshS

Was the mount successful? Is

Was the mount successful? Is this a warning or an error?

RabbitWolf

Mount/Backup success

The error does not seem to affect mounting a backup or creatiing one.

STC-JoshS

Good. if it starts affecting

Good. if it starts affecting the system stability or backups, let us know!

Terms and Conditions of Use - Privacy Policy - Cookies