File System Filter 'wcifs' EVENT ID 4

Hi,

There's a free version :





Macrium Reflect Free

Cheers,

Yeah, I know. But if I go for it I prefer to have all options etc.

fdegrove said:

Hi,

There's a free version :





Macrium Reflect Free

Cheers,

I just restored an image from 2017-01-14 to my Dell Inspiron laptop and tried creating a restore point and then restored form it. It was successful so whatever app update killed the restore point process happened after that date.

True. It happened between 16 and 20 of February.

SoFine409 said:

I just restored an image from 2017-01-14 to my Dell Inspiron laptop and tried creating a restore point and then restored form it. It was successful so whatever app update killed the restore point process happened after that date.

Win10usr said:

True. It happened between 16 and 20 of February.

Right, I forgot that had already been said.
FYI, this is not the first wonky app that MS has released. See: .Net Native Framework Package 1.2.23205.0 keeps updating from July, 2016.
Eventually MS will fix it.

I think unfortunately it has nothing to do with one of the apps itself. I suspect the update system has a serious flaw. It might also be the reason why they halted February's patch Tuesday. But then they shouldn't have rolled out app updates in the same week also. First repair, then do I'd say.

SoFine409 said:

Right, I forgot that had already been said.
FYI, this is not the first wonky app that MS has released. See: .Net Native Framework Package 1.2.23205.0 keeps updating from July, 2016.
Eventually MS will fix it.

Hi!

I wouldn't risk a system restore in this situation, you might end up with an instable system after a partly or completely failed one! Just be very carefull...

EdTittel said:

Just for grins I ran a restore point create on my apparently healthy (no SFC nor DISM /checkhealth errors) 14393 production desktop. Here's what shows up in my Event Viewer right when I do that:

I haven't yet tried to restore the restore point (which reports a successful completion, BTW) but I won't be surprised if it fails with the error that others have reported in this thread. I have to take my son to school now, but when I get back I'll run it and report back.
HTH,
--Ed--

Ok, tnx for yet another confirmation!

in case I switch to Macrium - which seems to be unavoidable - which partitions should be exactly backed up for making a system image? Win 10 always takes - as far as I remember - the C-partion with Windows (duh), EFI and Recovery. And can I restore an image WITHOUT destroying a seperate data partions on my HD?

EdTittel said:

I make nightly backups with Macrium Reflect, so I wasn't worried about a failed restore. In my experience MS is pretty good about making sure of roll-forward/roll-back recovery with restore -- that is, nothing left halfway between the previous state and the restored restore point state. And if the worst were to happen, this machine has the Macrium recovery partition in the boot menu so I could boot directly into that and restore last night's backup. That's why I proceeded to test the restore anyway. It reported a successful completion during the restore process, but here's what popped up on my screen following the restart:



More or less as I'd expected, based on the error when creating the restore point reported in my previous post here, the restore itself also fails. I'm posting a long message to the Feedback Hub about this, and will also blog about it this morning. Bottom line: don't count on restore points to bail you out of a jam at present. Something is wrong, and needs repair.
Thanks,
--Ed--

PS: I just checked the Event Viewer and it shows a restore error all right, but not the same one that others have been reporting here. Here's a screen cap of the error detail:

Next stop: Feedback Hub!