No. This is low priority right now.Dun wrote:Hmm, so did the research provide any infos?nanana1 wrote:Yes!....Finally, our reported bug is replicated and now being researched.Curt@invincea wrote:I am able to recreate the problem with the steps provided by btm. For some reason, when Windows sends us the notification of a process starting, it is giving us the old file path. I will research this to find out why.Can't wait to hear what they will find out.
Forced folder bug
Moderator: Barb@Invincea
-
Curt@invincea
- Sandboxie Lead Developer
- Posts: 1638
- Joined: Fri Jan 17, 2014 5:21 pm
- Contact:
Re: Folder folder bug
Re: Folder folder bug
Still low priority?Curt@invincea wrote: ↑Thu Sep 17, 2015 4:12 pmNo. This is low priority right now.Dun wrote:Hmm, so did the research provide any infos?nanana1 wrote:
Yes!....Finally, our reported bug is replicated and now being researched.
Issue actual.
Sorry for grammar. English is not my native language.
-
Barb@Invincea
- Sandboxie Support
- Posts: 2337
- Joined: Mon Nov 07, 2016 3:10 pm
Re: Forced folder bug
Hello Venga ,
The issue is low priority. A reboot takes care of it.
If any updates or fixes are found, we will update this thread.
Regards,
Barb.-
The issue is low priority. A reboot takes care of it.
If any updates or fixes are found, we will update this thread.
Regards,
Barb.-
Re: Forced folder bug
I would like to report a way without restart.
I often have to install programs and prefer to pass it through the sandbox first - probably the program can work portably. This approach is palpable reduce OS thrashing. For this - sandbox is incredibly useful! But constant restart annoying.
Way - is a simple everytime renaming of sandbox.
illustration:
Getting setup (for example CPU-Z). Right click, "start in sandbox" (for example DefaultBox). After install move content outside (for example in folder C:\test01\). Then rename "DefaultBox" in "NCsKqlr39x" (set a random text. I using any password generator). Content starts properly, not in sandbox. (finally we can delete renamed sandbox. Wasted.)
It makes sense to set a random name of sandbox before start working with setup. And then anyway necessarily to set another random name after content removing. "Double random rename" - excludes issue emergence.
Thank you.
I often have to install programs and prefer to pass it through the sandbox first - probably the program can work portably. This approach is palpable reduce OS thrashing. For this - sandbox is incredibly useful! But constant restart annoying.
Way - is a simple everytime renaming of sandbox.
illustration:
Getting setup (for example CPU-Z). Right click, "start in sandbox" (for example DefaultBox). After install move content outside (for example in folder C:\test01\). Then rename "DefaultBox" in "NCsKqlr39x" (set a random text. I using any password generator). Content starts properly, not in sandbox. (finally we can delete renamed sandbox. Wasted.)
It makes sense to set a random name of sandbox before start working with setup. And then anyway necessarily to set another random name after content removing. "Double random rename" - excludes issue emergence.
Thank you.
Sorry for grammar. English is not my native language.
Re: Forced folder bug
Hello everyone, it seems I've found some sort of workaround for this issue.
- Open the "Properties" window of the program executable (.exe) file.
- Try run the program again.
Sandboxie 5.23.5 | Windows 7 SP1 x64 w/ security updates only
Who is online
Users browsing this forum: No registered users and 1 guest
