I’ve replaced my c:\user[name]\Downloads folder to a mklink /j link to another HDD since I want to avoid unnecessary write/erase on my new SSD.
{outside sandbox}
When using FF outside the sandbox, I can download to that folder by choosing the Download link on the left side of the pane.
{INSIDE sandbox}
When using FF INSIDE the sandbox, I can download to that folder as well, BUT it won’t save it outside the sandbox (won’t transfer the file from the sandbox to the HDD)
As a matter of fact, if I look at the download window of FF, and select “open container folder”, it does nothing at all.
I’ve selected the proper options so that the sandbox can detect the proper directories etc. It just won’t work on that one though.
Needed to exclude some folders which aren’t at their default locations anymore. (I moved Win Temp, user Temp + some others to a physical mechanical HDD).
Once I excluded said folders, everything went back to normal. Downloads Folder now works.
I can also read pdf files – wasn’t able before since it was trying to save a temporary copy to my m:\winTemp folder which isn’t part of the non virtualized defaults. Once I added m:\winTemp in the exclusion setting, the reads now work properly.
Hint. I’d use the TEMP and TMP environment variables to determine what you can exclude or not from within the Avast application… this way they’d be automatically setup properly without having users exclude their new location if they’re not the defaults.
Starting to wonder as well. When I think about it, if an adware unpacks in the %TEMP%, it does so outside the sandbox right now (with my exclusions).
The issue though is that if I don’t exclude the %TEMP%, foxit reader cannot read any pdf from Firefox. Everytime it does try, it gives me a message saying… “cannot find m:\userTemp\xyz.pdf for reading.” The only way I found to fix it was to exclude my new %TEMP%.
If you have a more secure option, I’d love to hear any suggestions on it
Thanks for letting me know… I’ll probably revert back to defaults (except perhaps the “Downloads” since it won’t work at all without it).
You should exclude a dedicated folder intended for downloads. (Such as, say, D:\Downloads or whatever). Not system %TEMP% - this one should remain virtualized. And save your downloads there. If it still doesn’t work, the sandbox has a bug. Not familiar w/ the sandbox in Avast, but sandboxie has a feature called quick recovery. It initially virtualizes the above D:\Downloads or whatever you configure, when the download is completed, it will prompt you whether you want the file recovered from sandbox to the live filesystem location.
Wrt PDFs - yeah these need to be treated within sandbox code if you use a browser plugin to display them. If you set up the PDF reader so that it opens its own window and does not display the PDF in browser, the problem should be gone. Again, the above valid and tested with sandboxie, not with avast.
Wrt PDFs - yeah these need to be treated within sandbox code if you use a browser plugin to display them. If you set up the PDF reader so that it opens its own window and does not display the PDF in browser, the problem should be gone. Again, the above valid and tested with sandboxie, not with avast. ;)
For the Downloads, I fixed it & I’ve removed all exclusions from my settings now. (You can move the Default Download Location in the registry).
For the PDF, I’ll give that a shot! (opening a separate window for reading). I’ll report back soon.
Wrt PDFs - yeah these need to be treated within sandbox code if you use a browser plugin to display them. If you set up the PDF reader so that it opens its own window and does not display the PDF in browser, the problem should be gone. Again, the above valid and tested with sandboxie, not with avast. Wink
You were right! It works when I have it display the pdf outside the browser. ;D
Thanks tons for the suggestions. I can say I don’t have an issue anymore. /cheers