Talk:File Explorer

"Explorer" trademark in Germany - Symicron vs. Microsoft et. al.
In Germany, the small, now defunct company of Symicron once held the trade mark for the word/term "Explorer". Microsoft and others have been received written warnings because of that. This German trade mark was deleted one day. More on the case here (for example) unter the title "Explorer - Cases" : http://www.linksandlaw.com/linkingcases-trademark.htm Alrik Fassbauer (talk) 10:42, 4 September 2011 (UTC)

File Type associations
This particular statement is wrong and misleading.
 * the Explorer process also houses the operating system's search functionality and File Type associations (based on filename extensions)

Actually Explorer houses none of that. Shell32 does some of this work. Such as keeping its own copy of HKEY_CLASSES_ROOT around in memory. And such as creating and maintaining the 'shell namespace' in memory. But the 'File Type' stuff is external. That's in the Registry and even if the Registry is managed through dedicated APIs it's still a hive of files on disk. This is totally external to Explorer and any other process. Otherwise Registry manipulation would have to go through Explorer by means of some kind of IPC which of course is ridiculous. As the 'shell' is configurable; as you don't really need Explorer running (and it can and does crash) this would break down communications in the system and render Registry operations impossible. Moreover the kernel uses the Registry extensively building up 'control sets'. And it would simply be bad design to let half the Registry exist on its own and the other half within a mysterious 'Explorer process'. But thankfully that's not the case.

What the author meant was that Explorer offers an interface on HKCR for working with file extensions and file types and sundry data. But that's not at all the same thing: for any program can do that (and many do). —Preceding unsigned comment added by 86.201.152.214 (talk) 12:27, 25 March 2008 (UTC)

Explorer vs. Shell
I believe this article is propogating a common misconception. Windows Explorer is not just the file-browsing application, it was the name of the entire user interface shell. (Recent MSDN documentation refers to it simply as the "Windows Shell" and seems to have dropped the Explorer portion, probably to avoid confusion with Internet Explorer.) --mordemur 05:34, 18 Jan 2005 (UTC)
 * The shell is configurable. It doesn't have to be Explorer. This is a long standing trait of Windows.
 * I was about to say that after reading this article, and a year later after the above comment was posted it still hasnt been addressed. Ho hum. Windows Explorer as described in here and the Windows shell use the same EXE, so they're essentially the same thing. Is there a seperate article about the shell anywhere? -- jeffthejiff  ( talk ) 22:47, 28 January 2006 (UTC)
 * Uh...are we reading the same article? Read the first two paragraphs again (current form dates to March 2005; the same info was presented but much less clearly from July 2004).  It's pretty clearly stated that the article is about the Windows Explorer shell and how it accesses the Windows file structure.  The "file manager" interface, whether used in navigational or spatial mode, is part of the shell, as is the desktop, taskbar, start button, etc.  They are all the same executable because they are all aspects of the shell.  Are you saying that there isn't enough attention paid to other individual aspects of the shell gui?  Each one has its own article, because they are not specific to Windows but appear in many OSes that use a desktop gui. Canonblack 13:57, 7 February 2006 (UTC)
 * Ah, it is mentioned in a sentence or two, but that doesnt reflect on the rest of the article. The rest of the article is about Explorer as a file manager; shouldnt there be more information on the general Windows GUI shell or another article about it or something? -- jeffth  e  jiff  16:04, 9 February 2006 (UTC)
 * I think you're off track here. Explorer doesn't have the code that manages the system anyway. That's in a DLL. The article is called 'Windows Explorer'; it's probably best to stick to that topic. Programmatically Explorer is very much the 'interface' of which this article speaks. The 'shell' of which you speak is different. It's a DLL. SHELL32.DLL. HTH

I remember that when Windows 95 was introduced, the "Windows Explorer" was the two-paned version of what you got when you right-clicked My Computer and clicked Explore. It also had a start menu entry. "screen shot" (Note: I'm editing hte page to clarify that Explorer did NOT replace Win3.1(1)'s Program Manager -- Start Menu did.) I believe as late as XP, the "Explore" menu command is still there on My Computer, and really any folder. If you execute Start -> Run -> Explorer, you will get ... the Windows Explorer. Discussion welcome. Check "Nathan's GUI Gallery" for some historical screen shots. So ... my two cents is that this article is largely accurate. -- David Spalding 18:30, 28 October 2006 (UTC)
 * Those are the two 'modes' it operates in. One is more or less 'spatial' and the other is the traditional file management interface. In Windows 95 and later your folders are actually 'Explorer' (or more correctly 'ShellDefView') windows.
 * The start menu is a part of Windows Explorer, so is the taskbar and all icons on the desktop. Try closing explorer.exe in the task manager, this will close the start menu, the taskbar and remove all icons from the desktop. The reason you can right-click and choose "Explore.." is merely because this will give you the folder list on the left.

--


 * . --David Spalding | Talk 19:04, 13 November 2006 (UTC)

Windows Explorer Is the User Inteface of the Shell
Windows Shell includes not only explorer.exe, but also Shell32.dll. So I think Windows Explorer is a user interface of the shell, including the system tray, the start menu and the folder browsing/exploring windows.
 * Close but not quite. What your shell is can be defined as given in the path below. Explorer is the interface between the user and shell32. That's it.
 * No he's right. Programmatically that is. explorer.exe is simply the UI for shell32.dll. That there's a Registry key as below has nothing to do with it.


 * Just look in the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell

Hehe...never end the process EXPLORER.EXE...you get nothing but your wallpaper. So I think it's the interface.
 * These are meaningless terms. Unless of course you are referring to actual software components in the system. Which seems unlikely. In such case this is mere semantics and thus pointless.
 * They're referring to software components. Seeing 'nothing but your wallpaper' simply means that the screen no longer displays your desktop folder.


 * Hmm, I don't seem to see that... oh, right, I made the joyful switch to BBLean. Xiong Chiamiov    :: contact ::   22:52, 23 August 2006 (UTC)

explorer "activities"
Just two points not included in the article.

-When u run windows, explorer.exe appears in the programs list running "in the back".

-Even with a popular firewall like ZoneAlarm, it warns you that explorer.exe is trying to access the internet. At least windows 98.

Can anybody clarify that, please? I will wait posible feedback before deciding a retouch of the text.

thanks :)
 * Explorer is your desktop. It's running even when you don't think you see it running. By default it's your 'shell' meaning it's what starts first. The desktop itself in such case is a special case of the Windows 'list view' control. That's Explorer. When you open Explorer as you would an ordinary application you are actually starting new threads within the one and the same Explorer process. HTH —Preceding unsigned comment added by 86.201.152.214 (talk) 12:19, 25 March 2008 (UTC)

"This can be done" section
The This can be done information is vague and what is meant is not understandable. It should be replaced with a paragraph explaining the things. Soumyasch 08:04, 9 February 2006 (UTC)Soumyasch

Complete rewrite

 * There's 'a rat' in 'separate'.

Okay, I've rewritten the article, and added some screenshots. The Windows XP portion got the most attention here, and there is definitely a lot of missing information, still. I haven't addressed the whole "Windows Explorer" vs. "Windows shell" issue yet; there is probably grounds for creating a separate article which talks about the Windows shell as a whole, though... Warrens 09:40, 13 February 2006 (UTC)

== Internet explorer V.S. Windows explorer

The talk about IE seperating from Windows Explorer beginning with IE7 is nonsense.

The file management part of Windows Explorer does look a lot like Intenet Explorer, but they are really to seperate applications. If you use IE to vist a web page it will append "- Microsoft Internet Explorer". If you use Windows Explorer (at least the version on the computer i'm typing this on) to visit a web page This is not appended. Likewise IE appends "- Microsoft Internet Explorer" when using it as a file manager.

Now IE will pretend to be Windows explorer when used to browse local files, by doing things such as changing the menus to very nearly match those of Windows Explorer's File Manager and even changing the "About" dialog that is shown. Windows Explorer's File manager will likewise pretend to be Internet explorer when being used as a web browser.

Never the less they are distinct. Now if one is to remove Internet explorer from Windows XP, Windows Explorer's File manager will attempt to take on the job of Internet Explorer. AIUI Windows explorer will still work for web browsing, and still pretend to be Internet explorer even when IE has been removed. Nevertheless removing IE will cause things to break, including things that embed IE. (Windows Explorer's File manager does not embed IE, but more or less reimplements some of it. This is not to say that it does not use parts of IE, because in some cases it does, and those features would break if IE was not available.

The whole thing is very strange.... It is most likely a good thing if IE 7 stops trying to appear coupled with Windows explorer. I assume this would mean that IE would stop pretending to be Windows Explorer's File manager when used to browse local files, and Windows Explorer's File manager would stop prenting to be IE, or even lose the ability act as a web browser. I'm uncertain about that as I have never used Vista or IE7. 199.218.240.5 20:02, 14 March 2006 (UTC)


 * I highly recommend that you use the software before calling it "nonsense". Warrens 21:01, 14 March 2006 (UTC)


 * The fact is that Windows Explorer and Internet Explorer have always been two seperate applications. Windows Explorer (the file manager component [pre-Vista]) happens to have a mode in which it can pretend to be IE. If IE is available it can reuse some IE components to enable features that would not work in the absense of IE. IE 6 happens to have a mode in which it can pretend to be Windows Explorer's File manager component. AFAIK this does require Windows Explorer ro be installed, as it resuses some Windows Explorer dlls.
 * [Note that both IE AND Explorer use the same underlying display engine: Trident.]
 * Now IE 7 replaces IE 6 and lacks the ability to act like windows Explorer's File Manager. When IE 7 is installed, the Windows Explorer File Management does not enter the IE emulation mode, but will lauch the default browser whatever it happens to be) instead.
 * Note that even on Vista, it is theoretically possible to have a Windows Explorer window that has a frame that contains a webpage. That is due to using Trident as the rendering engine. Tacvek 20:58, 22 March 2006 (UTC)


 * I'm sorry, that simply isn't correct. The Trident engine, which resides in MSHTML.DLL, is not loaded or used by Windows Explorer in XP or 2003 unless you specifically ask for a web page to be displayed; when that happens, the ActiveX control which provides web browsing capabilities is loaded into the main frame, which of course will load MSHTML.DLL.  You can check this for yourself by using the Sysinternals Process Explorer utility.  Windows Explorer uses its own internal layout engine, as well as the Windows Shell common controls, to present the user interface.  Warrens 22:14, 22 March 2006 (UTC)
 * Whoops. You are correct. I had assumed the layout engine used by Windows Explorer was Trident. I assumed that because I had forgotten that Web View which is Trident based is no longer enabled by default in Windows. When Web View is enabled, *some* parts of the file manager are displayed using an html rendering engine of some sort, which i would presume would be Trident. I also suspect that if Active Desktop is enabled, the primary Explorer process will have Trident loaded for the purpose of displaying any web content on the desktop. But you do agree with me that Windows Explorer is quite distinct from Internet Explorer, so talk of seperating the two is (at least somewhat) misleading? AFAICT in Vista Windows Explorer simply will no longer offer an Internet Explorer emulation mode that works by embedding Trident, and IE will not offer an a Windows Explorer file manager emulation mode. 199.218.240.5 18:12, 27 March 2006 (UTC)
 * To reply to myself: I guess it could be argued that IE7 is becomping less integrated by not using SHDOCVW.DLL and BROWSEUI.DLL (or at least using them less). Those are the main two components that both IE4-6 and Windows Explorer share, besides MSHTML.dll which as you mentioned is not always used by Windows Explorer and which should not be considered a component of IE or windows explorer anyway (It could still potentially be usefull if neither IE nor windows explorer was availble, albeit less usefull). 199.218.240.5
 * Also how sure are you that Windows Explorer uses the "WebBrowser Control" (the ActiveX control exported by Shdocvw.dll) to embed IE? It seems that Windows Explorer uses Shdocvw.dll for other purposes as well, as it is loaded even when mshtml.dll is not. Since Windows Explorer is already using Shdocvw.dll, it would seem logical to call the code directly rather than through the ActiveX interface. 199.218.240.5 18:34, 27 March 2006 (UTC)
 * Actually, all applications shipped with Windows that need to display HTML use (as far as I can tell) the WebBrowser Control. This is also the standard way to do this in your own applications. The reason behind this is a bit subtle. The WebBrowser Control does not actually display any HTML. So in fact, the statement that "applications that need to show HTML use the WebBrowser Control" needs to be refined a bit more. The WebBrowser Control is used when an application needs to be able to navigate from content to content, regardless of that contents location / file type. So if you instruct the WebBrowser control to load a file from the internet (using the Navigate2 method) and it sees a MIME type "text/html", it will look up this value in the registry to figure out what this means. It sees that the classid is {25336920-03F9-11CF-8FD0-00AA00686F13}. It then looks up this identifier in the registry and sees that this class should be browsed in place (i.e. in the WebBrowser Control, not in a new window). So then it uses a standard COM API to instanciate this class. COM looks in the registry and sees that the in-process server is located in %SystemRoot%\System32\mshtml.dll, so it loads that DLL and performs some initialization as it would for every class instanciated. It gives the newly created object back to the WebBrowser Control which asks for an appropriate interface that contains the methods to feed data to this object, and then calls those methods. It also in a similar fashion asks for an interface that enables the WebBrowser control to display the object (at the location of the WebBrowser Control). Then events will be sinked to it just like this would happen with any embedded object, and the object paints itself, reacts to mouse clicks, etc. Note that all the specifics of showing HTML are handled by this object, whose classid is {25336920-03F9-11CF-8FD0-00AA00686F13}. Similarly, other object classes may be available, for example to show PDF documents. Also note that the HTML showing object contains no specifics about where the data is coming from. This is not, in fact, handled by the WebBrowser Control itself either. Depending on the location (internet, local file system, a file inside a compound file, like a .chm help file) various classes can be instantiated. These support an interface that the WebBrowser Control gives to the display object, so that these objects can communicate directly, without the WebBrowser Control getting between them. Everything clear? Shinobu 01:42, 26 June 2007 (UTC)

Windows NT Explorer
Wasn't there a Windows NT Explorer in Windows NT 4? --Evice 19:07, 27 June 2006 (UTC)


 * Yep, it was renamed Windows Explorer in Win2000. "In Windows 2000, Windows NT Explorer has been renamed Windows Explorer [sic] and is located on the Accessories menu. Windows Explorer shows you the hierarchical struture of files, folders and drives on your computer. It also shows any network drives which have been mapped to drive letter on your computer. For information about using Windows Explorer, see Related Topics." (quote from Win2000 Help, emphasis exists in the original.) --David Spalding | Talk 18:30, 13 November 2006 (UTC)

windows explorer
if there is a 3 in front of windows explorer what does that mean?


 * Huh? I don't grok the question. Please clarify. --David Spalding | Talk 18:30, 13 November 2006 (UTC)
 * If you are referring to the taskbar button, it means that you have three open Windows Explorer windows. Usually these are folders that you have opened that Windows grouped together in one button to create room in your taskbar. Windows does this with windows belonging to other applications as well. Shinobu 19:17, 26 June 2007 (UTC)

Ending EXPLORER.EXE
People mentioned ending the explorer process with Task Manager earlier... you can also use a keyboard shortcut:

Use Start > Shutdown, and hold Ctrl+Shift+Alt whilst clicking No/Cancel in the Shut Down box. You will end explorer.exe (and it won't automatically reload). This is documented by Microsoft (see Debugging with the Shell on MSDN).

129.67.18.125 23:38, 30 May 2007 (UTC)

My Computer
My Computer redirects here, but nowhere in the article does it give any explanation. Shinobu 00:58, 26 June 2007 (UTC)

The disambiguation page states:
 * My Computer may refer to a component of Windows Explorer, a Microsoft file system browser. That component is the desktop icon labeled "My Computer" unless the name has been modified by the user. — Senator2029 (talk) 10:43, 31 July 2011 (UTC)

Fair use rationale for Image:Windows Explorer Icon.png
Image:Windows Explorer Icon.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot 12:14, 6 July 2007 (UTC)
 * Added a short fair use rationale; please check if it is okay. Shinobu 13:09, 1 August 2007 (UTC)

Windows - disambiguation
My search for 'Windows' came here - what I wanted was a good explanation (with diagrams) on how to use a Window widget (for example, resizing it). - The information isn't available under 'Computer Literacy' either. Not sure if such an explanation is in the scope of Wikipedia really. —Preceding unsigned comment added by Wikivek (talk • contribs) 20:12, 21 January 2008 (UTC)
 * I'm not entirely sure how applicable this is to Windows Explorer? [Jam][talk] 20:39, 21 January 2008 (UTC)

rewording?
The sentence "Windows Explorer includes significant changes from previous versions of Windows such as improved filtering, sorting, grouping and stacking, as well as diminished searchability of folders." is confusing. What is diminished searchability? Kushal 02:56, 2 March 2008 (UTC)
 * It means the 'searchability' (is that a word) is diminished. It means you can't search for things as well anymore. —Preceding unsigned comment added by 86.201.152.214 (talk) 12:17, 25 March 2008 (UTC)

Shell extensions
The current info on shell extensions is so limited. Explorer supports a very rich extensibility model (preview handlers, context menu extensions, column handlers, Explorer bars). Can anyone describe it? —Preceding unsigned comment added by 221.128.180.168 (talk) 06:48, 23 March 2008 (UTC)
 * Extensibility is barely covered. It needs to be written. I will get to it soon. --soum talk 11:04, 23 March 2008 (UTC)

Basic functionality?
As far as I know most programs that ship with Windows like Paint and Wordpad provide only basic functionality, so that a user may buy a program from another company if he/she needs to do something professional. Does this apply to Windows Explorer? Can operating system vendors include their best file managers in the OSes without being sued by concurrent companies? Lefter 09:45, 10 February 2009 (UTC) —Preceding unsigned comment added by Lefter (talk • contribs)

Manually start explorer.exe
Hi, I know "This is not a forum", but since this is information that belongs on this page (it goes hand-in-hand with ending explorer.exe), I felt it safe to ask here. I have encountered a serious error on my computer, where, on boot up, Explorer.exe does not start (I've tried re-booting many times, to no avail). The only three programs I can run are Utility manager (CTRL+U still works), and the internet browser (there is a link to the Microsoft website on Utility manager, which opens up my browser for me). The third is Task Manager (CTRL+Shift+ESC). Hitting the "Windows key" does nothing. I cannot lose focus of any program, unless one of the other two programs are open, as then it is the only visible one. I checked Task Manager, and all my other start-up programs were there, but Explorer.exe was not. Does anyone how to start this program manually? Timeroot (talk) 00:03, 3 March 2009 (UTC)

"It is now often updated together with Internet Explorer as a bundle package."
I'd like to put that in the initial statement since it's quite obvious latest versions of it at least, just update the file explorer too. They do seem to just have many parts common. --AaThinker (talk) 11:26, 5 May 2009 (UTC)

Reasons why explorer.exe tries to connect to the internet
A common problem that's been around for years, and is mentioned very often all over the internet, is the fact that when you open a folder, Windows explorer tries to access the internet. explorer.exe is detected by firewalls such as Zonealarm. Shouldn't that be in the article? That it tries to connect to the internet, and a reason why? I don't know the answer, or I'd add it in myself. Most people don't look up a file, unless they notice it doing something it shouldn't have a reason to be doing, and then they come to the Wikipedia to find out what it is, and what's going on.  D r e a m Focus  02:24, 3 November 2009 (UTC)
 * I'm pretty sure there is a trojan that hides under the name of explorer.exe, so that might be the cause of this. I think we should add a section about malware masquerading as explorer.exe, as I believe this a widespread problem. ClothNapkin (talk) 04:26, 25 February 2012 (UTC)
 * I have never seen explorer.exe getting connected to Internet unless I install a shell extension that does so. It does connect to local network and that's when I tell it to do so. I have seen rumors like this over the Internet. If you add it to the article, you had better have VERY reliable source and I do not mean musings of a PC Magazine expert (who only works on and writes about Mac) about Windows in his personal blog. Fleet Command (talk) 06:39, 25 February 2012 (UTC)

Windows 7 image
Please add Windows explorer in Windows 7 picture. —Preceding unsigned comment added by 180.222.0.158 (talk) 01:08, 27 March 2010 (UTC)

Requested move

 * The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section. 

The result of the move request was: move. The suggested title already redirects here; the parenthetical isn't needed. Cúchullain t/ c 18:56, 8 January 2013 (UTC)

File Explorer (Windows) → File Explorer – Right now, the article link for File Explorer redirects to this article at its current titling of File Explorer (Windows). This introduction also clarifies the scope of the article and references readers over the the general term of file manager. My understanding is that Wikipedia suggests using non-parenthetical titles if possible, so I suggest that we move this page to just File Explorer. 68DANNY2 (talk) 00:21, 30 December 2012 (UTC)
 * Support, this should be uncontroversial. Thryduulf (talk) 10:16, 30 December 2012 (UTC)
 * Oppose. "File explorer" could be easily thought of as a generic term. Indeed, it is generic enough that some other OS might well have a "file explorer" some day, just as 16-bit Windows and early versions of the NT family had a "File Manager". Then we'll just have to name this one back... Exactly what does it hurt to have the qualification in the article title? Jeh (talk) 10:56, 30 December 2012 (UTC)
 * Per WP:CRYSTAL we don't disambiguate articles because they might at some future point become ambiguous. It doesn't harm to have qualification in the article title, but it is completely unnecessary and therefore contrary to our naming scheme. Thryduulf (talk) 11:16, 30 December 2012 (UTC)
 * I think it's quite a stretch to cite WP:CRYSTAL here; I can't find a single point there that's really on-point. "File Explorer (Windows)" is not predictive of anything, it is merely descriptive and restrictive. And I think that when someone types "File Ex..." into the search tool here and sees immediately "File Explorer (Windows)" there is value in that immediate confirmation that that article is what they are looking for... or that it isn't. The reader will not get that with "File Explorer" until they open the article and read the first few lines. Jeh (talk) 01:18, 31 December 2012 (UTC)
 * By including the presently unnecessary disambiguation you are predicting that another notable non-Windows File explorer will get an an article. As for the the search tool issue, the present disambiguated title will remain as a redirect as it is a likely search term (the article is presently at this title, bookmarks, memories, links, etc. take a long time to get updated, if ever; people may assume there are other notable file explorers and so search with disambiguation; etc) in addition to the attribution record. This may seem confusing, but redirects are not articles and different considerations apply, therefore it is no contradiction for the default action for articles (move) and redirects (keep) with unnecessary disambiguation to be different. Thryduulf (talk) 05:30, 2 January 2013 (UTC)
 * Support. Unnecessary disambiguation seeing as File Explorer redirects here anyway. Zarcadia (talk) 20:07, 30 December 2012 (UTC)
 * Maybe it shouldn't. Maybe "File explorer" should go to a disambiguate page that has links here and to "File manager" and to "File manager (Windows)" too. Jeh (talk) 01:18, 31 December 2012 (UTC)
 * Oppose per Jeh. You frequently find the term "file explorer" in the generic about such programs on Android devices. -- 70.24.248.246 (talk) 06:00, 31 December 2012 (UTC)
 * Support. It doesn't matter if there are other programs named "File Explorer". Since there is only one that has a Wikipedia article, it gets the article name. If other articles are created in the future, then we can move this back to File Explorer (Windows) and have File Explorer as a disambiguation page. Not disambiguating when there's only one article is standard in Wikipedia. Actually, even if there is another File Explorer article created, it may still be a good idea not to disambiguate this one, in accordance with WP:PRIMARYTOPIC, if the second program is far less known. Trinitresque (talk) 08:06, 31 December 2012 (UTC)
 * Support. The generic term is "File manager", not "File explorer". Nobody refers to this kind of utility as "file explorers". - 190.138.6.234 (talk) 10:41, 31 December 2012 (UTC)
 * Oppose—confusing and annoying for Mac users if it's not explicitly tagged. Tony   (talk)  07:50, 3 January 2013 (UTC)
 * Eh? There is no other article about anything called "file explorer" so this is the primary topic, the article doesn't have anything to do with Macs and already has a hatnote to the article about the generic software type. The only relevance to macs I can find is windows users asking is "$foo the equivalent of file explorer?". By this logic every piece of software should be explicitly named for the operating system(s) it runs on, which is contrary to everything we say about file naming. Are you perhaps being facetious or implying Mac users aren't intelligent enough to work out that an article about windows software is not relevant to macs unless it's got "(Windows)" in the title? (These are genuine questions not personal attacks, they're the only two scenarios in which I can make sense of your rationale). Thryduulf (talk) 08:00, 3 January 2013 (UTC)
 * Literally one of the most well known facts about the Mac OS X operating system is that our file explorer is called Finder. It's the one that has that logo that everyone's seem only about a million times in their lives. Don't worry, us Mac users will be alright. Trinitresque (talk) 10:54, 3 January 2013 (UTC)
 * Support We don't disambiguate for nonexistent articles. If another article named File explorer, File Explorer, or something similar is made, we can discuss whether or not there's a primary topic. For now, the hatnote will help any confused readers. --BDD (talk) 18:53, 7 January 2013 (UTC)
 * The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

This article is inaccurate
This article seems to be under the impression that File Explorer is Windows' shell and provides with many of the OS' features such as the taskbar, which is inaccurate. Windows' shell is Explorer, and File Explorer is just one of the many features provided by it. In other words, File Explorer is just the file manager included in the shell, not the shell itself. Saying that File Explorer is the shell and the desktop and taskbar are part of it is as inaccurate as stating that the Start Menu, another feature provided by Explorer (prior to Windows 8, anyway), is the shell and everything else is part of it. - 190.138.6.234 (talk) 10:54, 31 December 2012 (UTC)
 * If the article is inaccurate, that's nothing compared to the above.
 * Care to elaborate? What's inaccurate about the above paragraph? 181.95.86.168 (talk) 00:38, 14 August 2019 (UTC)

CMD in Explorer's cwd
Despite WP:TALK and WP:NOTHOWTO, this method of running cmd.exe in the current directory of Explorer is just too spectacular not to be mentioned here (or even in the article): -- Michael Bednarek (talk) 05:25, 23 October 2013 (UTC)
 * after navigation to the desired folder, simply type cmd in the address bar. In short: Alt cmd, or language-independent: F4 Esc cmd
 * Hi. It is so spectacular that I am going to share it over my social network.


 * But if you are going to insert it into the article, you are going to need a source. Otherwise, sorry.


 * Best regards,
 * Codename Lisa (talk) 19:10, 23 October 2013 (UTC)

Windows 10 image
Please add the icon that appears in Windows 10. This icon is no longer in use in Windows 10. — Preceding unsigned comment added by Giorgos456 (talk • contribs) 21:49, 30 July 2015 (UTC)

Also, there should be a whole section on Windows 10 in the History part. — Preceding unsigned comment added by 169.226.246.243 (talk) 12:42, 14 October 2015 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on File Explorer. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive http://web.archive.org/web/20060414084606/http://msdn.microsoft.com:80/archive/en-us/dnarolegen/html/msdn_propset.asp?frame=true to http://msdn.microsoft.com/archive/en-us/dnarolegen/html/msdn_propset.asp?frame=true

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at Sourcecheck).

Cheers.—cyberbot II  Talk to my owner :Online 10:28, 28 February 2016 (UTC)

Shows images in sort order
One essential feature that Windows Explorer does as standard but which no Linux file manager does, to my knowledge, is show images in the sort order. So if you have a directory of photos, put them in list view, sort them by date order, then click on one of them, then click "next", then in Windows Explorer the next image you see will be the photo with the next date. Frustratingly, I have tried several Linux file managers and all of them will only show the next photo which is the next in alphabetical order, regardless of how you have them sorted in the Linux file manager. 92.28.242.67 (talk) 11:06, 20 April 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on File Explorer. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20071028171026/http://www.viruslist.com/viruses/encyclopedia?virusid=25409 to http://www.viruslist.com/viruses/encyclopedia?virusid=25409
 * Added archive https://web.archive.org/web/20040831153932/http://msdn.microsoft.com/msdnmag/issues/0300/w2kui/w2kuifigs.asp to http://msdn.microsoft.com/msdnmag/issues/0300/w2kui/w2kuifigs.asp
 * Added archive https://web.archive.org/web/20081022103457/http://www.sigchi.org/chi96/proceedings/desbrief/Sullivan/kds_txt.htm to http://www.sigchi.org/chi96/proceedings/desbrief/Sullivan/kds_txt.htm
 * Added archive https://web.archive.org/web/20070125201721/http://www.codeproject.com/shell/shellextguideindex.asp to http://www.codeproject.com/shell/shellextguideindex.asp

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 13:16, 4 September 2017 (UTC)

New feature: Windows 7 or 10?
The article fails to mention one speciific innovation and when it was introduced (in Windows 7 or 10?): When you're dragging a folder into another place which already has a folder of the same name, and Explorer will offer adding the files within the new folder to the existing folder. Before that feature was introduced, you could only either overwrite the old folder, or cancel the process. --46.93.155.166 (talk) 20:50, 29 June 2019 (UTC)
 * I could be wrong, but wasn't that feature introduced in Vista? 181.95.86.168 (talk) 00:35, 14 August 2019 (UTC)

File Explorer =/= Windows Explorer
I'm pretty sure that the shell that handles GUI features such as windows is called Windows Explorer. File Explorer is merely the name of the file manager, which is part of Windows Explorer.

Yes, it's still called Windows Explorer as of Windows 10. You can verify this by opening the Task Manager. The processes associated with the shell are listed as "Windows Explorer" there. Bluest Bird (talk) 22:14, 26 July 2020 (UTC)

File Explorer icon
The File Explorer icon is outdated; the logo has changed in Windows 11. Please could you change the icon? Thepurplepiano (talk) 12:37, 26 July 2021 (UTC)

A Commons file used on this page or its Wikidata item has been nominated for speedy deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for speedy deletion: You can see the reason for deletion at the file description page linked above. —Community Tech bot (talk) 05:52, 15 April 2022 (UTC)
 * Win11 file exp.png

A Commons file used on this page or its Wikidata item has been nominated for deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion: Participate in the deletion discussion at the. —Community Tech bot (talk) 22:22, 9 May 2022 (UTC)
 * Windows Explorer Win11.png

Can't find a source for the rename to "File Explorer"
I couldn't find a source for the assertion in that "Windows Explorer" was renamed to "File Explorer" in Windows 8. This old trade magazine article still refers to it as "Windows Explorer," and this Microsoft support document refers to it being called "File Explorer" Windows 10, but this forum thread says it was renamed in Windows 8. I'm going to use the latter as a source to support the footnote in the lead. If you've got a more definitive source, please update. --Ernstkm (talk) 17:29, 3 January 2024 (UTC)


 * Disregard. It was already cited elsewhere in the article. --Ernstkm (talk) 17:45, 3 January 2024 (UTC)

Source(s) for the userinit.exe → explorer.exe startup process, or remove?
I'd like to remove this paragraph entirely (referencing ): "After a user logs in, the explorer process is created by the userinit process. Userinit performs some initialization of the user environment (such as running the login script and applying group policies) and then looks in the registry at the Shell value and creates a process to run the system-defined shell – by default, Explorer.exe. Then Userinit exits. This is why Explorer.exe is shown by various process explorers with no parent – its parent has exited." I'm not sure it adds anything consequential to the article, and seems like it's probably more in the domain of a Windows Internals book rather than a Wikipedia article. But if there's a sensible way it might be worked into the article, perhaps in a new section, that's okay. I found and  with a quick web search, but I'll need better sources than that. Suggestions welcome. --Ernstkm (talk) 17:59, 3 January 2024 (UTC)