File System Filter 'wcifs' EVENT ID 4

Agreed, hope they sort soon.

Right, started getting this error few days ago too, and today i needed system restore and it fails due to this apparently

Well, it's a windows bug and not my pc issue
So, now it's not possible to restore the system from a system restore point?

Hi,


To verify that the file screening minifilter driver is working properly, you must verify that it is attached to the volume.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To verify that the file screening minifilter driver is attached to the volume:
1.Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
2.Type fltmc instances and press ENTER. The file screening minifilter driver is attached to the volume if there is a Datascrn instance listed for the volume.

Cheers,

@fdegrove

In your output theres no wcifs instance, and mine looks exactly the same as Conm3.

Hi all!

Same problem here on EVERY system that is running here. Including some clean virtual machines even. The troubles seem to have started after a series of obligatory MS-app updates some days ago.

It happens during making system restore points, system images and file back-ups. Basically everything that makes use of VSS. This sounds big. It means that there is no way anymore to restore a Windows 10 system to a former state suddenly. Neither by a system restore nor - probably - by restoring an image. Red somewhere else that also software like True image is affected. Also file backup tools seem to work unreliable, see the error here too appearing while running backups. Doesn't sound good at all. If something goes wrong now a clean reinstall will be needed :-( We decided to leave some systems off here until it's clear what is going on. Hopefully Microsoft is aware of this serious issue.


Greetz,

Pete.

Hey everyone, I just signed up to chime in that the two machines I am running Windows 10 Pro on have been kicking out this exact warning for the last few days to a week. I'm hoping it's something Microsoft can fix, but I'm looking into how to fix it myself, if possible.

Hi Corsa1, it does seem to be on Microsoft's end. I'd save yourself time and just hang on for them, your choice of course. I must of tried everything so in the end i did a complete clean reinstall and the issue is still there. Spent best part of a week on it but I'm now leaving it to MS.

Cheers for now