Romex Software Forum

Had an issue with my Windows 7 64-bit (that had NOTHING to do with FancyCache (wife got a drive-by virus)) that caused me to have to restore the backup image that I have made daily (Windows backup) from my spinner to my SSD.

The backup restored fine to the SSD BUT... When I went to reboot the restored drive, It needed to run a disk check, which would not run with FancyCache installed. I went to safe node, uninstalled Fancy Cache, then let it reboot and perform the scan. All is fine and I re-installed FancyCache.

After reboot, I found the issue with the corrupted file system pieces in the found.000 directory:
I was running a logoff script that cleans out temp files automatically. The found.000 directory contained multiple directories of temp files...
It looks like the cleaning program was still doing its thing when FancyCache turned off its driver (or unloaded it) resulting in the file system not being updated... Or that is my theory...

I have disabled the logoff task and re-enabled my FancyCache with write deferred back on. We will see if this fixes it....

Thanks for the feedback.

I am waiting for your result. If the problem is related to the logoff script, could you send us the script? So then we can try to do the test.

Confirmed... Data loss occurs during the logoff script. Disabled it and all works fine.

Here is the contents of the logoff script (batch file):
"C:\Program Files (x86)\CCleaner\CCleaner.exe" /AUTO

It runs a free program called crap cleaner that clears out the temp files, cookies, etc. Site: http://www.piriform.com/

On looking at the batch file, I guess I SHOULD be using the start /wait command to fire up ccleaner and then wait for it to finish...
It may be the issue (ccleaner is still running when FancyCaceh is unloading and the shutdown cycle happens).

CC should go down with your session.
FC should go down with system.
So this shouldn't be the rootcause :-O

horizon wrote:CC should go down with your session.
FC should go down with system.
So this shouldn't be the rootcause :-O

I found that the issue is in how I am running the logoff script.....
It is all in how you start ccleaner (or any other program) from the command line... If you don't tell the batch file to wait till ccleaner is done (with the /w switch) then the batch file exits immediately while ccleaner is still doing its thing. The OS detects the batch file exit and allows whatever is next to run (shutdown the cache).

magic-man wrote:If you don't tell the batch file to wait till ccleaner is done (with the /w switch) then the batch file exits immediately while ccleaner is still doing its thing. The OS detects the batch file exit and allows whatever is next to run (shutdown the cache).

quite possibly