Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Foobar+win10 (Read 7966 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar+win10

TY google tranclate!!!

By clicking on the cross browser window opens again, how to fix?


Player opens in fubar file location, close this window by clicking on the cross, but instead to open it opens knitted. I do not understand why ??? I'm focused on the cross shake. in win7, 8.1, had no such problems.
http://www.youtube.com/watch?v=gM0fey7THAY...eature=youtu.be


KK.SV said: August 15, 2015Prosmotret history records
 MCC: created content
Hello. The official website of the developer player is not declared compatible with Windows 10, the player is likely to not work correctly with the OS. On this issue, you should contact the developer player

Original:
http://answers.microsoft.com/ru-ru/windows...dc-6690d31f6012

Foobar+win10

Reply #1 –
I've noticed in previous versions of Windows that clicking the X on anything with Windows Explorer (File Explorer in newer versions) can cause the same window to reopen.  It also happens with Internet Explorer.  This is more of a operating system glitch as I've seen it happen a couple of times before on previous versions of Windows.  I'm not able to reproduce it consistently, just sometimes.  If you click the X too fast it has a better chance of happening.  It's annoying certainly, but it shouldn't affect foobar2000 negatively in anyway, again I've seen it with other applications on previous versions of Windows as well.

The File Explorer does flash twice each time, but seems kind of minor (more annoying) which is unusual and might be more of a glitch with foobar2000 but it can also be a Windows 10 glitch that affects other applications.

Windows 10 is still fairly new in the wild, you can expect some unwanted surprises.

Foobar+win10

Reply #2 –
I can confidently say that foobar2000 doesn't cause that kind of behavior. Are you people running perhaps some start menu replacement programs that hook themselves deep into Explorer process? These programs have caused all sorts of issues already in Windows 8/8.1 and I can't imagine them suddenly become more stable on a newer OS.

You can also use Process Monitor to create a log of this issue and upload it on the Uploads forum. Perhaps the log shines some light why Explorer window pops open again.

Foobar+win10

Reply #3 –
This is an issue with explorer itself.

Open folder options (File -> Change folder and search options), to to the 'View' tab and find "Launch folder windows in a separate process". Make sure it is unchecked.
Not sure how it would be named in russian, but you can probably find it.

This is a bug of windows 10 ever since i started using it (mid spring).

Foobar+win10

Reply #4 –
Good find, that setting seems to indeed cause this behavior.

Foobar+win10

Reply #5 –
Interesting.  I have this set as such with folders launching in separate process.  Turning it off does indeed make it go away.  I can safely say this same bug with Windows Explorer existed in Windows 7 as well.

The option exists that if one folder causes a crash it doesn't close them all on you.  It can be run on a case-by-case basis as well by holding shift and right clicking on choosing "open in a new process".

I've never bothered to use Windows 8/8.1 ever, so I've never used any start menu replacement programs.
 

Foobar+win10

Reply #6 –
Quote from: Chibisteven on
I can safely say this same bug with Windows Explorer existed in Windows 7 as well.


I've never seen this happen in win7.
I don't think i've seen it in 8/8.1 also (for the little time i've used it)

And that option is standard for me to turn on after a fresh install, for the reason you mentioned (crashing)

Foobar+win10

Reply #7 –
Quote from: fuflo on
Quote from: Chibisteven on
I can safely say this same bug with Windows Explorer existed in Windows 7 as well.


I've never seen this happen in win7.
I don't think i've seen it in 8/8.1 also (for the little time i've used it)

And that option is standard for me to turn on after a fresh install, for the reason you mentioned (crashing)


I have.  It's rare.  It happens more with Internet Explorer than anything else especially if you close the window too fast.  Of course I may just be confusing Internet Explorer with Windows Explorer.

Foobar+win10

Reply #8 –
Quote
Open folder options (File -> Change folder and search options), to to the 'View' tab and find "Launch folder windows in a separate process". Make sure it is unchecked.

It helped me. But I would like to fix it

Foobar+win10

Reply #9 –
The bug is not in foobar2000. foobar uses SHOpenFolderAndSelectItems function for the "Open containing folder" feature and the OS seems to suffer from misbehavior with it.

I made a small test program that shows the same issue:
Code: [Select]
#include <windows.h>
#include <Shlobj.h>
#include <Objbase.h>
#include <stdio.h>
#include <tchar.h>

#pragma comment(lib, "ole32")
#pragma comment(lib, "shell32")

int main(int argc, char *argv)
{
	HRESULT res;
	ITEMIDLIST *pIDL;

	res = CoInitializeEx(NULL, COINIT_MULTITHREADED);
	if (res != S_OK) printf("CoInitializeEx returned 0x%08x\n", res);

	pIDL = ILCreateFromPath(_T("C:\\Windows\\explorer.exe"));
	if (pIDL != NULL) {
		res = SHOpenFolderAndSelectItems(pIDL, 0, NULL, 0);
		if (res != S_OK) printf("SHOpenFolderAndSelectItems returned with value 0x%08x\n", res);
		ILFree(pIDL);
	} else {
		printf("ILCreateFromPath failed\n");
	}

	return 0;
}

Foobar+win10

Reply #10 –
Quote from: Case on
The bug is not in foobar2000. foobar uses SHOpenFolderAndSelectItems function for the "Open containing folder" feature and the OS seems to suffer from misbehavior with it.

I made a small test program that shows the same issue:

Why, then, the program Download Master (http://westbyte.com/dm/), correctly opens the file folder. But foobar can not open it.

http://www.youtube.com/watch?v=clI5aBY_ugM...eature=youtu.be

P.S.
I deleted foobar. And now when you install it I did not ask where to save the settings. I want to keep the install folder, but it creates a setting in the folder "...\users\...\appdata\roaming\foobar2000\". How fix it?

Foobar+win10

Reply #11 –
Installing foobar2000 in Portable mode will keep all config files within the installation directory.

Foobar+win10

Reply #12 –
Quote from: Zarggg on
Installing foobar2000 in Portable mode will keep all config files within the installation directory.

It is not. In the standard installing, then had the choice of where to set the settings.

Foobar+win10

Reply #13 –
Quote from: unk2 on
Why, then, the program Download Master (http://westbyte.com/dm/), correctly opens the file folder. But foobar can not open it.

Because it doesn't open the folder "correctly". It calls explorer.exe /e,/select,<path to file>. That only works for one file at a time and it is the wrong thing to do if user uses alternate shell instead of Explorer. A person would want the alternate shell to handle the open request instead of Windows' Explorer.

Quote from: unk2 on
P.S.
I deleted foobar. And now when you install it I did not ask where to save the settings. I want to keep the install folder, but it creates a setting in the folder "...\users\...\appdata\roaming\foobar2000\". How fix it?

Delete the file "user_profiles_enabled" from the install dir and it will use the install directory for configuration storing.

Foobar+win10

Reply #14 –
I want to point this out: the only problem with disabling user profiles on a non-portable install is you need to give foobar2000 administrator privileges every time you run it or change how Windows manages permissions by taking ownership of the install folder.  I wouldn't recommend the former from a security standpoint if you use it connected to the internet especially if you use online streams.  It's possible you could open a few vulnerables this way that would otherwise be impossible.

A really fun thing to point out: if more than one user has a profile on the same system with administrator privileges or ownership rights then you can now mess with each other in not very pleasant ways.

I tried this out of curiosity.

Foobar+win10

Reply #16 –
The log was unnecessary as the cause was already found.

But you made me further look into this issue and I noticed that the setting "Launch folder windows in a separate process" has absolutely no effect on Windows 10. Explorer windows opened by clicking a shortcut or by opening Computer view or with Win+E all open in a single process regardless of the setting. Respectively running explorer.exe always opens a new instance, again regardless of the setting. I see no reason to have the tickbox enabled there to trigger this bug.

That said I have reported the bug in their API command with the Feedback tool. Perhaps it will get fixed.