I know why it's there. I know what it's doing.
But it's not acceptable that it will grow to a size of 10:s of GB:s without alerting the user anyway.
Using weekly builds of a web browser (in my case, Vivaldi), is not what "normal" users will do, but still it shouldn't cause a total disk space meltdown. What's more annoying is that in the past you could turn off over-zealous logging by setting the process status at "Control Active Processes" from "Monitor" to "Allow". But now with the latest version of WSA (v9.0.2.21), even if vivaldi.exe has been set to "Allow", the log still says:
Sat 2015-08-22 11:40:44.0934 Monitoring process C:Program Files (x86)VivaldiApplicationvivaldi.exe [020C1E9893B002D9EEB838F7861C9F37]. Type: 2 (11873)
Please fix it.
Reporting every file with this kind of behaviour through tech support (to be white-listed) is waste of time and resources.
Page 1 / 1
Hi affe
Welcome to the Community Forums.
Unfortunately there is no 'fix' as you put it as that is how the product works and unfortunately in case where you are using an app like Vivaldi, which is new and relatively 'unknown' then WSA will err on the side of caution in terms of 'monitoring' it and therefore journalling its actions, with the results that you have described.
Your best course of action is to complain directly to the Support Team as and when you have to notify them of the files that you need to get whitelisted. There current is just no other way to go at present.
There are a couple of feature requests; here & here in the Ideas Exchange that has been raised about getting a solution to this and you may like to add your comments to that/support it, and there is also a linked request that you may also wish to consider supporting.
The Development Team do review the Ideas Exchange contents regulalrly and the status of each request is updated, so this is the best way to try to influence the functionality in the product.
I hope that the above is of some assistance?
Regards, Baldrick
Welcome to the Community Forums.
Unfortunately there is no 'fix' as you put it as that is how the product works and unfortunately in case where you are using an app like Vivaldi, which is new and relatively 'unknown' then WSA will err on the side of caution in terms of 'monitoring' it and therefore journalling its actions, with the results that you have described.
Your best course of action is to complain directly to the Support Team as and when you have to notify them of the files that you need to get whitelisted. There current is just no other way to go at present.
There are a couple of feature requests; here & here in the Ideas Exchange that has been raised about getting a solution to this and you may like to add your comments to that/support it, and there is also a linked request that you may also wish to consider supporting.
The Development Team do review the Ideas Exchange contents regulalrly and the status of each request is updated, so this is the best way to try to influence the functionality in the product.
I hope that the above is of some assistance?
Regards, Baldrick
My guess is that every new build of the browser is being set to monitored, which means all changes it makes are being journaled which is what is causing the file size to grow. At each update would you be able to check the monitoring and whitelist the file?
The other possible option is for you to switch to the business version, as that now has a feature where you can exempt folders and files from being scanned. You could put the Vivaldi folder in that exempt section and then it wouldn't care about the new builds every week.
The other possible option is for you to switch to the business version, as that now has a feature where you can exempt folders and files from being scanned. You could put the Vivaldi folder in that exempt section and then it wouldn't care about the new builds every week.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.