It is currently Thu Jun 07, 2018 9:04 pm

All times are UTC - 8 hours [ DST ]


Forum rules


Please, keep discussions on topic and in the right forum. The start menu topics go into the Classic Start Menu forum, etc. This makes it easier for people to locate topics they are looking for.
If you get a satisfactory response to your question, please mark the topic as "solved". Click the green √ button in the bottom-right of the post.



Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Wed Feb 27, 2013 2:14 pm 
Offline

Joined: Wed Feb 27, 2013 12:16 pm
Posts: 3
I'm using Win7 Home Premium (64 bit) with Classic Shell installed.

Whenever I open Windows Explorer and then select any folder within it, a second Windows Explorer will always open.

If I select any folder within that second opened Windows Explorer, I can navigate around and continue to make other folder selections fine within the second Windows Explorer without any other Windows Explorer windows from opening.

However, regardless if that second Windows Explorer is open or not, anytime I go back to that VERY first opened Windows Explorer and make another folder selection, it will open up another Windows Explorer window.

I looked around within Classic Shell to see if there was a setting to prevent this from happening, and I couldn't see one, unless I either keep over looking it, or it is labeled in a fashion to where I haven't recognize it.

Is this a quirk of Classic Shell, or is there a setting that will prevent this from happening?

Thanks. :D


Top
 Profile  
Reply with quote  
PostPosted: Wed Feb 27, 2013 7:10 pm 
Offline
User avatar

Joined: Thu Feb 21, 2013 11:04 pm
Posts: 463
i have never experienced this, but i also use qttab..

it sounds more like a problem with your install.. i'd try uninstalling, rebooting, then installing again..

otherwise, i dont think this is classicshell related, unless its a conflict with some other explorer tweak on your system


Top
 Profile  
Reply with quote  
PostPosted: Wed Feb 27, 2013 8:21 pm 
Offline

Joined: Wed Feb 27, 2013 12:16 pm
Posts: 3
Oops. My bad, and my apologies. I had gone into the folder settings countless times to examine it, but it wasn't set to open the folders in a separate windows explorer. I even had set it open, saved it, and then set it back to normal with no positive results. Then it hit me that I had made a custom version of windows explorer and that it might causing the issue.

This was it.

%windir%\explorer.exe /e,/root, C:\

I made a small change to:

%windir%\explorer.exe /e C:

No more second windows explorer!


Top
 Profile  
Reply with quote  
PostPosted: Thu Feb 28, 2013 1:25 am 
Offline
User avatar

Joined: Thu Jan 03, 2013 12:38 am
Posts: 5341
An unfortunate bug in Explorer.exe since Vista. With certain switches used, a second Explorer.exe process does start as expected but doesn't exit at all. We have to terminate it using Task Manager or taskkill.

_________________
Links to some general topics:

Compare Start Menus

Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.


Top
 Profile  
Reply with quote  
PostPosted: Thu Feb 28, 2013 5:56 am 
Offline

Joined: Wed Feb 27, 2013 12:16 pm
Posts: 3
I have used Win7 and Classic Shell for quite a while, but I had installed Classic Shell at roughly the same time that I first started using Win7, and I had also made the custom Desktop icon launch for Windows Explorer. I had made similar custom Windows Explorer launches for my previous versions of Windows, so when I just started using Win7 and also just started using Classic Shell, I had created this custom launch for Win7, I just took it for granted that it was a "bug" of Classic shell. I liked many of the other benefits Classic Shell so much that I felt that small inconvenience was well worth it.

I had roughly roughly looked in here at the forums from time to time to see if anyone else had made mention of it. I felt that the second launching might get mentioned at some point, but I never saw it, so that's the reason that I brought it up. In the previous versions of Windows, I had never had this happen before, so I naturally took it for granted it was Classic shell, and hoped for a future fix. When the more recent update happened and the second launching still continued to occur, I felt that I should mention it.

I am very surprised this was related to Microsoft, since I had never had this happen to me before, so I am big enough to step forward to admit my embarrassment and mistake. I hope this entire posting of my assumption will be of some benefit to some other person that might be suffering from the same issue, just lurking for an answer, and that they will read it and perform a similar fix.

Again, my apologies to the developer(s) of Classic Shell. :oops: :D


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 8 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group, Almsamim WYSIWYG Classic Shell © 2010-2016, Ivo Beltchev.
All right reserved.