TeraByte Unlimited

Hello Terabyte!
First major problem in ~30 years with your products.
Windows 11. SSD 500G. Windows partition has 150G, 65Gb of which are occupied.
Vss failure during backup with IFW.
I cannot follow these instructions:
https://www.terabyteunlimited.com/kb/kb ... ng-backup/

Reason : the "Properties" line is not present in Windows 11 !
So, could you please give me another path to access the window "My computer>properties'>etc.. that works in Windows 11.
Thanks,
Paul Brussels Belgium
Registered owner
PS:By the way: do not stop Phylock, please..

Seems more of a Windows issue than IFW...

Open an elevated Command prompt (run as Administrator), and copy and paste the following (one at a time) -

sfc /SCANNOW

Run again until you no longer get errors (if you do).

Then -

DISM /Online /Cleanup-Image /RestoreHealth

Then, re-register VSS (again, one line at a time) -

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

Then, check the health of the VSS Writers -

vssadmin list writers

Seems like your referring to the IVssWriterCallback error logged to the Event Log. That's normal and doesn't affect anything, the article explains how to prevent it if it bothers you.

If you're referring to something else with unable to start VSS then yes, that could be Windows, the prior message is a common method to try. But also see https://www.terabyteunlimited.com/kb/kb ... on-failed/

Well...If I say : "Vss failure during backup with IFW.", this means that the backup process stopped.
Which is something affecting me...
(and this this means also that VSS was able to start).
On your W11 do you have the 'line' : Properties when you right-click My Computer to go to the COM security tab ?

See https://www.terabyteunlimited.com/kb/kb ... vent-4001/

Also in general if VSS can't cache all changes for whatever reason you'll get a failure just like phylock. Those steps in the prior article linked may help.

You can use vssadmin list providers and vss admin list writers to see status of things. Also the event log, but you can ignore Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005

Once you get VSS (part of Windows) fixed up then things should start working again.

To finish this thread:
My Windows installation was fresh, so there were no errors.
The 'vssadmin list shadowstorage' command returned a storage space of 1.82 GB.
I increased it to 4 GB.
I ran four backup tests with IFW, with no VSS errors.
But obviously, I can't conclude anything...
Anyway, I'm stopping VSS and going back to using Phylock.
Thks

fresh installs can spend a lot of IO/Disk updating building indexes and such.