Page 3 of 3

Re: Folder folder bug

Posted: Thu Sep 17, 2015 4:12 pm
by Curt@invincea
Dun wrote:
nanana1 wrote:
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.
Yes!....Finally, our reported bug is replicated and now being researched. :lol: Can't wait to hear what they will find out. 8)
Hmm, so did the research provide any infos?
No. This is low priority right now.

Re: Folder folder bug

Posted: Mon Oct 23, 2017 5:53 pm
by Venga
Curt@invincea wrote:
Thu Sep 17, 2015 4:12 pm
Dun wrote:
nanana1 wrote:
Yes!....Finally, our reported bug is replicated and now being researched. :lol: Can't wait to hear what they will find out. 8)
Hmm, so did the research provide any infos?
No. This is low priority right now.
Still low priority?
Issue actual.

Re: Forced folder bug

Posted: Tue Oct 24, 2017 1:35 pm
by Barb@Invincea
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.-

Re: Forced folder bug

Posted: Thu Oct 26, 2017 2:54 am
by Venga
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.

Re: Forced folder bug

Posted: Sat Jan 27, 2018 5:49 pm
by RadarNyan
Hello everyone, it seems I've found some sort of workaround for this issue.
  1. Open the "Properties" window of the program executable (.exe) file.
  2. Try run the program again.
I know this sounds pretty stupid... just give it a try - Right click - Properties.