PrivaZer Discussion Thread

WDI Diagnostics Logs
C:\Windows\System32\wdi

Cached Applications Compatibility Information
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatCache

windows_tracing_logfile
C:\BVTBin\Tests\installpackage\csilogfile.log

Startup File Renaming Log
C:\Windows\PFRO.log

 

Hello,

PrivaZer version 3.0.33 has been released.
Homepage
Download
Donors Version
Release Notes

 

@Privazer

Recently Win10 updated itself and my scheduled Privazer run has kicked off Windows disk clean up but appears to have continued with the clean. Having got to free space clean the Windows clean is still chugging away slowly. Does this not result in conflict between the processes and or a considerable slowing of activity?

 

yes, it slows down the cleanup process.
The most secure way to clean Windows updates is to use the Windows disk cleanup.
It may take a while, so that we prefer to let the user know and let PrivaZer do its job.

By the way, new update available v3.0.34 realeased 2 min ago

 

PrivaZer v3.0.34 Released (7 December 2017)
Download
Download Donors Version

 

Strange one this.
With Waterfox now using it's own profile location, you have to set it up in advanced section.

The problem is that on auto clean and manual clean it's not auto detecting/cleaning cookies properly.
It's cleaning the cache files.
Here is what Privazer is leaving behind in ccleaner.
It's seems to be zero length cookies and some files.

 

If it helps any the zero length cookies relate to a text file called SiteSecurityServiceState.txt which is located in profile directory, which apparently you can be tracked through.
CCleaner seems to clean it. Privazer as far as I can tell does not.

 

Hello,

PrivaZer version 3.0.35 has been released.
Homepage
Download
Donors Version
Release Notes

 

Thanks for another heads up.

In it's current improved state it gets usage on this end every so many weeks just to speed the ole machine back up to par and to that end it does the job just fine so far.

 

Hello @EASTER,

You are most welcome ...
And I totally agree !

 

@WarGames,
thanks for the info. We will check this out.

 

C:\Users\USERNAME\AppData\Local\Microsoft\Windows\Explorer\ExplorerStartupLog.etl

C:\Users\USERNAME\AppData\Local\Microsoft\Windows\Explorer\ExplorerStartupLog_RunOnce.etl

C:\Windows\System32\umstartup.etl

 

Hello,

PrivaZer version 3.0.36 has been released.
Homepage
Download
Donors Version
Release Notes

 

HKEY_CURRENT_USER\Software\Microsoft\DirectInput\MostRecentApplication

 

Hello,

PrivaZer version 3.0.37 has been released.
Homepage
Download
Donors Version
Release Notes

 

Thanks Kent.

Gee, they're pushing out the updates lately. Do the dev's also work for Mozilla?

 

Hello @Krusty,

You are most welcome ...
I noticed the recent amount of updates also.

 

our Christmas gifts...

.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
. * .
. /.\ .
. /..'\ .
. /'.'\ .
. /.''.'\ .
. /.'.'.\ .
. /'.''.'.\ .
. ^^^[_]^^^ .
.

@liba,
thanks for all your suggestions
We keep you posted when ready.

 

C:\Program Files\OpenVPN\log

-Cryptographic Services Traces-
C:\Windows\System32\catroot2\*.log
C:\Windows\System32\catroot2\*.jrs
C:\Windows\System32\catroot2\*.edb
C:\Windows\System32\catroot2\*.chk
C:\Windows\System32\catroot2\*dberr.txt

 

Not sure if this may be some kind of bug, but following a previously not seen BSOD during the cleanup process I tried again, after a reboot, and the cleanup then ran successfully, but on viewing Restore points (in PrivaZer GUI), it said 0 GB, but when checked I saw the screenshot below. Also running WSA, HMPA, NVTDRP on Windows 7 with v3.0.37 Donors' version. Thought this may be of interest, and have DMP files if needed for checking.

 

I see a floppy disk icon on your screenshot. strange.
Certainly the calculation failed so that the rendering was not refreshed with appropriate values...
I will check this out.

Can you have more info on your BSOD with this tool BlueScreenView :
http://www.nirsoft.net/utils/blue_screen_view.html

Hitmanpro.alert may cause BSOD when monitoring PrivaZer cleanup.
BlueScreenView will give clues to its root causes...

 

Hi,

is there a list of command lines available in the donors version?

 

here :
http://privazer.com/download-donors.php#commandlines

 

Hi, and thanks for your reply and advice. Yes, I thought that icon seemed weird, and didn't know what it was! Didn't think to run BlueScreenView at the time, and here is info about this crash. In my limited knowledge I'm now inclined to think that this is probably unrelated to PrivaZer, and more likely a result of using a pretty old laptop with limited RAM etc? Time for a new one I think...

Dump File : 122617-16395-01.dmp
Crash Time : 26/12/2017 20:30:47
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x973e4fec
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8347b103
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+410bf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23915 (win7sp1_ldr.170913-0600)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+410bf
Stack Address 1 : ntkrnlpa.exe+7a103
Stack Address 2 : ntkrnlpa.exe+7df62
Stack Address 3 : ntkrnlpa.exe+7a6f5
Computer Name :
Full Path : C:\Windows\Minidump\122617-16395-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 143,200

 

If we would see "Caused By Driver : hmpalert.sys" then this would be a good indicator that HMP.A has caused this BSOD.
In #1599 it can be a device driver/hardware problem/virus scanner issue.
(Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL: "[...] indicates that Microsoft Windows or a kernel-mode driver accessed paged memory")
It's hard to narrow it down.
(If you have the time:)
Maybe deinstall your security applications one by one (which have a kernel mode driver installed) and do a scan each time with Privazer.
If you can do a scan without a BSOD you probably have found the evildoer (the security application which you have deinstalled previously)

Or maybe it is the right time to look for a new one