PrivaZer Discussion Thread

Hello,

Prior to this latest version 3.0.13, I have always been able to use PrivaZer via the right click context menu to securely delete files, folders, or the recycle bin. Once the secure deletions finished, PrivaZer would shut down (exit automatically). I prefer this in contrast to keeping PrivaZer always running in the system tray as I only use it a few times a day. With PrivaZer 3.0.13, it no longer shuts itself down (exits automatically) after using the right click context menu to securely delete a file. folder, or the recycle bin. Once the secure deletion is finished, PrivaZer remains running in the system tray and I must manually exit PrivaZer by right clicking the tray icon and then clicking "Quit" followed by clicking "Yes" to the prompt "Are you sure you want to exit PrivaZer?". These are extra steps that I find unnecessary and annoying. I do not want to keep PrivaZer running in the system tray since I only use it a few times a day and it would be really nice it it would again shut down and exit automatically when using the right click context menu to securely delete files, folders, or the recycle bin. I really hope that this functionality can be returned to the way it was prior to version 3.0.13...

 

I've installed that new update v.3.0.13 but it has some bugs, glitches.
Rolling back the new update...

 

Interesting point - I always read the processed entries as record read but it does actually say 294 thousand free of which 130 odd cleaned. Are there really that many (and more) free entries in your MFT?

 

Also seeing the application crashed popup. Restart is the only option that works. I'm running latest privazer on windows 10 home 64bit. Im running a cleanup on 1 ssd and 2 hds at the time of crash.

 

Regret I have seen this problem before
A scan of RAM and Pagefile reveals 87%RAM and 43% pagefile to clean
I have pagefile set to clean at every shutdown
After scan I ran clean and 29081Mb RAM was cleaned - I have 8Gb, so why was was there not a clean of 87% or roughly 7Gb
When the clean was finished the PC shutdown and presumably the Pagefile was cleaned

I restarted the PC and ran Privazer memory scan immediately which gave a result of 81% RAM to clean and amazingly 84% Pagefile.

I would very much appreciate an explantion of any logic to this?? Screenshots attached

 

PrivaZer is not cleaning Reliability History any more, plus I think it is actually slower too.

I'm going back to v3.0.12.

 

Hello,

@Krusty

Be sure that the option "Eventlog" listed below is checked :



@takiabtom,

1. We've investigated : it could show up more RAM than expected in PrivaZer v3.0.13 during the cleanup because some memory could be backed in the swap file instead of staying resident in RAM. This issue is fixed in the new PrivaZer v3.0.14, released few minutes ago.
   
   
2. Once memory scan is completed, PrivaZer shows up
   - the total free space of the RAM (unable to be more accurate by only showing free sections of the RAM that contains traces)
   - the sectors needing to be reset to zero in the entire pagefile.sys and hiberfil.sys files (every occupied sectors + free sectors needing to be reset to zero).
   
   so when ou use your PC, there will be always traces detected in the "memory" section of PrivaZer's scans.
   
   Hope it helps.

 

@The_PrivaZer_Team ,

I had that setting enabled with the previous version (v3.0.12) and I never disabled it. Anyway, it is enabled now with the latest version (v3.0.14) and I'm running PrivaZer now so I will see shortly if Reliability History is cleaned or not.

Edit: No, still not cleaned.

 

what is your OS Krusty?

 

Win10 x64.

Thanks.

 

ok. We will investigate. Thanks

 

Thanks. Hopefully it won't be hard to reproduce because I see the same on three Win10 x64 machines.

 

Do you run an Insider build?

 

No, 1607.

 

Nah. I don't think so. Probably entries read as you say. Most likely a glitch that no one's noticed before.

 

Thankyou for your response - a little clearer now, I think. However, the pagefile clean is an enigma.

I have just run a scan which showed 100% to clean in Pagefile. I ran the clean with shutdown, restarted the PC and immediately performed another scan and there is still 100% to clean
Thoughts......
1 The shutdown appears to be too quick for there to be any cleaning going on
2 Never had this problem before I migrated to win10
3 Never had this problem on earlier versions of Privazer which, upon rerun after shutdown, always showed near virgin pagefile
4 Is it possible to get a screen message into the shutdown process to show that a clean of pagefile is being performed ?
5 Is there anywhere a simple user can look to see that pagefile clean has been stuffed in the shutdown process ?

Hope you have some thoughts also so that I can recover waning confidence in this aspect of Privazer

 

is your pagefile encrypted?

 

could not find how to check but did find that windows is set to clear the pagefile at shutdown

Thanks to Rules - encryption is off

 

Open cmd command prompt and run following commands :

Check for encryption : fsutil behavior query EncryptPagingFile
Encrypt : fsutil behavior set EncryptPagingFile 1
Remove encryption : fsutil behavior set EncryptPagingFile 0

Rules.

 

Thankyou Rules.

Encryption is set to 0 - not encrypted

 

Were you able to reproduce?

 

not yet...

 

I have the following question.
Since updating Privazer to v.3.0.14, I've noticed a strange thing.
If I right-click on the Recycle Bin icon to erase its contents with Privazer, after the cleaning Privazer does not closes itself as requested ("Close when completed" checked), but minimizes itself.
What is the reason for that?

 

Hello zmechys.

I posed the same question in post # 1376. I am sure that @The_PrivaZer_Team Is aware and will inform us of the status (although they usually respond in a day or two). It has been the holiday season which slows down most companies responses, so I imagine we will hear something no later than after the first of the year.
HTH...

 

Staying at 3.0.12 until all the problems are fixed.
Why throw out betas, at least say "for testing proposes only"