AppGuard 4.x 32/64 Bit - Releases

#4604
I see no real need for existing 4.x-users to upgrade to 5.x

 

I have also been running in lockdown mode per your insight.

I have another one though.


06/17/16 08:44:16 Prevented process <pid: 7784> from writing to <c:\windows\performance\winsat\winsat.log>.


I did some research as to what this does. Strange thing is I took a look at that directory a bit ago and besides the log, I have 5like 5 meg video clips that I never saved to that folder. Two are mp4, two are wmv and one is just mv. do any of you have videos in that folder and it doen't seem normal to me.
three are short clips of bicycle racing and two are short waterfall clips.

 

If yes, it's realy better stay with 4.xxx. Thanks for knowladge

if yes, it's realy better stay 4.xxx thanks for knowladge.

 

Version 4.X will always have the most recent features. All beta testing will be done on the 4.X version.

Version 5.X is a consumer version - and there will be no beta testing of it and it will not be exactly the same as version 4.X.

 

But maybe 5.2 will have more features?

 

I see the same stuff. But the dates of file creation date back to when I installed Win 7.

 

Windows is doing some "benchmarks" (WinSat.exe)
The task responsible for that is: \Microsoft\Windows\Sysmain\WsSwapAssessmentTask
You can make an exception (Read/Write) for this specific file in AG.

 

No.

Version 5.X will be built on v. 4.X. 5.X = consumer, v. 4.X = professional.

 

So everything clear

Thanks

 

'Windows is doing some "benchmarks" (WinSat.exe)
The task responsible for that is: \Microsoft\Windows\Sysmain\WsSwapAssessmentTask
You can make an exception (Read/Write) for this specific file in AG."

You mean make it a power app?

 

AG is only blocking the write to the Winsat log. It isn't blocking Winsat itself.

All the blocks to logs, dat files, XML files, reg can be ignored.

Only create an exception if something is obviously broken by a block event.

 

So beta testers here can continue to use the professional version, but what about users who don't beta test and have an old-style license?

 

and so you are saying this is normal for the winsat folder?

 

From BRN support reply to @Grumlo :


If you are a current user of AppGuard consumer 4.3, your license will auto update to 4.4. There will be no further sales for AppGuard consumer version 4.

The soon to be released AppGuard Personal is version 5.2. This version will replace AppGuard consumer.

AppGuard Professional is 4.4 which is not available to the general public.

* * * * *

I suppose after 4.4, version 4.X consumer licenses will carry over to version 5.

However, that is a question for BRN support - as to how they are going to handle the situation with old licenses and the phase-out of 4.X consumer.

 

c:\Windows\Performance\WinSAT\
Administrator rights are not enough to fiddle around in this folder

 

That *.mp4 is just a movie clip that visually explains a WinSat concept...

* * * * *

If you are trying to modify the *.mp4, then it is Windows that is blocking modification - and not AppGuard.

 

I was trying to delete it. mine are not visually explaining winsat, they are of bicycle races and a water fall. unless they are leftovers from winsat testing my video card. I know it tests cpu video ect and yes windows is stopping the delete not AG.

run:winsat query

 

Those *.mp4s are installed by Windows. They're on my system too - and everyone other person's W8/10...

Some infos: http://answers.microsoft.com/en-us/...e/a16349eb-6638-4ca4-946c-7fc8bcf872e9?auth=1

In order to delete the *.mp4s you have to take ownership of the folder - and that is something I do not recommend.

Messing will folder permissions is one thing that I have found that causes all manner of problems. In the end, you might have to reinstall Windows to fix any problems created...

 

If you are going to add vulnerable processes to User Space, then use the * wildcard in the file path:

c:\windows\*\vulnerable_process.exe

It is a lot more convenient than adding each file path - System32 and SysWOW64 - and especially for Microsoft.NET (framework and framework64) objects with multiple versions.

Will save you a lot of time...

 

hjlbx

thank you very much. I will start using wild cards.

 

Using wildcards for User-Space ... I should have done that earlier - it was a pain to add these .NET-processes

 

mood

I don't seem to get any warning for net processes here thank god.

 

i just don't want some specific .NET-processes to be executed, so i added them to User-Space.
And there are at least 3-4 User-Space Entries needed for one single .NET-executable.

#4788

 

It's good you didn't until 4.4.4.1 - there was a bug that would allow processes to be executed when the file path contained a wildcard.

Barb and I discovered it independently...

 

It's not likely during day-to-day computing...