You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
kougyoku 16c9c8f9b4 Update Program.cs
Update so program can handle path with spaces in it.
Update location of debugging output data to a spot where a user most likely has access to write.
1 year ago
Properties Update AssemblyInfo.cs 1 year ago
.gitignore Update .gitignore 1 year ago
App.config initial commit 1 year ago
LICENSE Initial commit 1 year ago
LocalExplorer.csproj initial commit 1 year ago
LocalExplorer.ico initial commit 1 year ago
LocalExplorer.sln initial commit 1 year ago
Program.cs Update Program.cs 1 year ago Change directory of program to C:\Windows\ISD\ 1 year ago
RegistryEntries.reg Change directory of program to C:\Windows\ISD\ 1 year ago
test.html initial commit 1 year ago


IE 11 has a feature that allows users to click a URL to access file folders in local computer or network drive using Windows Explorer. Modern web browsers such as Edge and Chrome don't allow this to security measures.

This application was inspired by the "LocalExplorer" Chrome Plug-In and corresponding "integration module". (Source: )

The problem with this solution is that the Chrome plug-in can "read and change all your data on all websites", includes Google Analytics, collects debug info by default, and presents no EULA or terms of utilizing the software. The software was also home-brewed "in house" which the developer released free of charge but did not provide source code. This is a red flag for me in terms of security and gives me cause for concern with exactly how the program works and what it's doing.

So in response, I have created a clone of this software and am also releasing it free of charge, and open source since there is no alternative in the FOSS space. I hope this program provides useful to you. If it does, buy me a beer.


Run the below steps as administrator.

  1. Drop the LocalExplorer.exe file into the C:\Windows\ISD\ directory so that the full path is C:\Windows\ISD\LocalExplorer.exe
  2. Run the LocalExplorer.reg file to register the protocol handler.

As always you can verify exactly what the program is doing and what entries are being created in your registry by viewing the source code.