Messages

1

Tweaking.com Support & Help / Re: Windows Repair - Security Setting on ReParse points

« on: May 13, 2017, 05:49:02 am »

I decided in the end to revert to a previous backup and take a look more closely at what the product did. I tried doing things more slowly and I think I discovered what may have been happening there was a directory that should not have been where it was, that I think was adding to the confusion. Now without even running the windows repair tool I have SFC and DISM both working as they should be and the corruption I had, has been repaired.

That said all the re-parse points you create are just not present on the current WIN10 builds so I wonder why you create them in the first place. They may have been there on older Windows versions but are not required now. Should Windows repair be more observant of which windows version it is attempting to repair? It makes me wonder what would have happened if I had gone onto look at the registry bits and what would have perhaps been done that was not required or at worst incorrect.

2

Tweaking.com Support & Help / Re: Windows Repair - Security Setting on ReParse points

« on: May 12, 2017, 09:08:31 am »

Yes it was

3

Tweaking.com Support & Help / Windows Repair - Security Setting on ReParse points

« on: May 12, 2017, 08:42:23 am »

Hi, I had an issue with DISM not being able to repair corrunption (which seems to affect quite a few people on the Win10 x64 Creators Update). I downloaded and ran the repair program and looked at the results from option 2 Packages/reparse points/environment variables. It listed quite a few reparse points that were "Incorrect/Missing" and when it did the repair I noticed that it was also cahnging the security settings and it seems that I have shortcuts to directories I cannot access because you have set Everyone to Deny. Is this correct or has the setting been done incorrectly?

Fixing the reparse points did resolve DISM not working and a package that was shown as incorrect is now fixed. Both SFC and DISM now work OK.

4

Tweaking.com Support & Help / Re: Registry Bakup and event log items

« on: March 13, 2017, 04:28:23 am »

Uninstalled with iobit uninstaller and reinstalled (several times) but the MSVBVM60.DLL issue still remains, as does the File System Filter 'wcifs' ... message in the eventlog

5

Tweaking.com Support & Help / Re: Registry Bakup and event log items

« on: March 10, 2017, 02:20:12 am »

@Jpm

Thanks for your comments but when I run my backup program it creates snapshots but the wcifs error does not occur. If the AV was the issue I would have expected it to happen for every program that created a snapshot?

@Boggin
Following yesterdays uninstall/install test I also find I have this error in the event log which I did not have before:

Faulting application name: TweakingRegistryBackup.exe, version: 3.5.0.3, time stamp: 0x582f3b59
Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3
Exception code: 0xc0000005
Fault offset: 0x000c9ba6
Faulting process ID: 0x1dd4
Faulting application start time: 0x01d299857e9f3657
Faulting application path: C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVBVM60.DLL
Report ID: 2d25154a-ce62-405b-aa88-84f65146e312
Faulting package full name:
Faulting package-relative application ID:

6

Tweaking.com Support & Help / Re: Registry Bakup and event log items

« on: March 09, 2017, 08:14:13 am »

Yes it still happens after uninstall/reinstall. My backup program also creates shadow copies and in both instances you can see the copy using vssadmin list shadows. But the event log only occurs when registry backup is run.

7

Tweaking.com Support & Help / Re: Registry Bakup and event log items

« on: March 09, 2017, 05:57:10 am »

sfc /scannow - no errors
dism /online /cleanup-image /scanhealth - no errors

when other programs create snapshonts the error does not happen.

8

Tweaking.com Support & Help / Registry Bakup and event log items

« on: March 09, 2017, 01:02:59 am »

Whenever Registry backup runs it creates a shadow volume but it seems it does this in a way that causes this error in the event log:

File System Filter 'wcifs' (Version 10.0, ‎2016‎-‎09‎-‎15T16:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy1'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

I have also noticed that the shadow is retained until the program is closed - should it be released when the backup has completed?

Windows Build 10.14393.693 version 1607