We’ve just released a minor update 8.3.2 to Folder Guard. This update corrects an error introduced in version 8.3.1 that prevented some license keys from being accepted as valid. If you’ve installed version 8.3.1 and the software asked you to enter a valid license key (even though you’ve already entered it), please download and install version 8.3.2 to correct this error.
Previously we’ve shown how easy it was to set up Folder Guard to prevent downloads of programs from the Internet. As a side effect, the filter that accomplished that task prevented running programs from the removable drives, as well. However, what if you want to stop users of your computer from using the external drives at all? For example, what if you don’t want them to copy documents and files from the computer to the removable drives they could bring with them? With Folder Guard, it’s easy to achieve that.
As before, let’s start by creating a file access filter that would restrict the use of the removable drives. Run Folder Guard, and choose View – Filters from the menu to switch to the window that shows the existing filters. If you use one of the latest version of Folder Guard, you should see a filter that we need already in the list, it’s called Lock external drives:
If you don’t see this filter in the list, it’s easy to create it: choose Filter – New from the menu, and then enter the properties of the filters as follows:
The most important part of this filter is the content of the Except folders box: it contains the mask C:*;\\*;*:\RECYCLE.BIN . Why it is there? Because we don’t want the restrictions that this filter would create to apply to the files located on the main drive of your computer (which is most probably the drive C:). We only want the restrictions to apply to other drives, which would have drive letters other than C:. The star character (*) in the mask means any set of characters, so the mask C:* would match any folder located on the C: drive. As a result, the filter would not apply to any file or folder on the C: drive, just what we want.
We also don’t want the filter to apply to the network files. Since the paths of such files usually start with the double-backslash, we use the mask \\* to specify such paths.
Finally, we’ve added the mask *:\RECYCLE.BIN to the Except forders box. It is necessary to prevent the filter from applying to the files located in the Recycle Bin folders. Without such a mask, Windows would be denied access to Recycle Bin, and it would cause it to display messages about it being corrupted.
Now, if your computer has other drives permanently attached and you want the users to be able to use such drives without restrictions, you should add the appropriate masks to the Except for folders box, too. (You can separate masks with comas, semicolons, or line breaks). For example, if your computer has a DVD drive that has the drive letter D: and you want the users to use the DVD drive without restrictions, modify the content of the Except folders box to read as follows: (Press the […] button to modify the content of the box.)
The rest of the filter properties can be left empty. An empty Apply to box means Apply to all and an empty Except for box means Except for none. We have entered a star character in the Apply to files box, to emphasize that it should apply to all files, but we could have left the box empty, it would produce the same result as the star character.
Now that we have created the filter that we need, it’s time to apply a restricting attribute to it. We basically have two choices: the No access attribute and the Read-only one. Which one to assign to the filter depends on how exactly you want the external devices to be restricted. If you want to completely lock access to the removable drives, assign the No access attribute to the filter:
The result of the No access attribute would be that the users would be prevented from both opening the files from the external devices, and saving the files to them. If you only want to stop users from saving files to the removable drives, but allow them to open or copy files from them, than the Read-only attribute would do the job:
Attention System Administrators: Folder Guard is enterprise-ready! The Folder Guard Administrator’s Kit is available now.
What if at some point you do need to access a removable drive? Just pause the protection of Folder Guard, perform the task, then resume the protection back (no Windows restart required).
- What people are saying about Folder Guard…
- A FREE 30-day license is included
- What’s new in the new version
- Folder Guard press release
- Folder Guard licenses explained
- End User License Agreement (ELUA)
- Emergency Recovery Utility
- How to lock folders and drives with passwords
- How to hide folders and files
- How to unhide a folder hidden with Folder Guard
- How to restrict access to Control Panel
- How to set up Folder Guard to stop downloading from the Internet
- Locking access to the external drives with Folder Guard
- How to make Folder Guard recognize network drives
- Preventing installations of specific programs with Folder Guard
- How to password-protect a USB flash drive (video)
- Always have a backup of your important files
This is a minor update to Folder Guard that corrects an issue that could cause the mapped network drives not to be protected as expected on the Windows 7/Vista computers in some situations.
If you have not experienced a problem protecting the mapped network drives with Folder Guard, you may want to skip this update. Otherwise, download it from our web site and install over the previous version.
What’s new in Folder Guard version 8.3:
- An option to enable protection in the safe mode of Windows. (Previously, this could only be enabled manually).
- User-specific restrictions for the domain users.
- Several new filters to allow you to lock all applications, or lock your MP3 collection, or restrict access to any removable drive someone might attach to your computer.
- Several other minor improvements and corrections.
If this sounds like something you were waiting for, give the new version a try. (It’s free for the first 30 days!)More information about Folder Guard…
One of the useful tools that Windows offers is the ability to assign drive letters to the network locations. You can use the Map Network Drive command of Windows Explorer or AB Commander to create the network drives. After a network drive has been created, you can use it just like any other drive: browse its contents, copy file to or from it, and so on.
A problem may occur, however, if you use Windows Vista or Windows 7 and need to access the network drive from an application that runs elevated (a.k.a. as administrator). For example, when you run AB Commander as usual, it runs as the standard user, and displays any network drive that you might have created, for example:
However, unlike Windows Explorer that always runs as a standard user, AB Commander offers you an option to run it as administrator. (You can do it by using the Restart as Administrator command on the Tools menu.) If you restart AB Commander as administrator, you might be surprised to see no network drive in its window:
(You can recognize that AB Commander is running as administrator by the presence of the Administrator label in its title bar).
To understand why the network drive is not visible to the programs running as administrator, we have to consider how Windows handles the standard and administrator user access internally. In simple terms, when UAC (User Account Control) is enabled, Windows creates a split personality for your user account: one with the standard user’s access rights to do the the regular tasks, and another one with the full administrative access to the system. When you log in to the computer, Windows tries hard to create the impression that these two personalities are the same: they share the login name and password, the desktop and documents, settings and preferences, and so on. However, when it comes to mapping the network drives, Windows prefers to treat them as separate accounts (for security reasons). That’s why the network drives created when you wear the hat of the standard user do not automatically become available when you put the administrator’s hat on. This Microsoft article explains it all in detail.
Such behavior is rather counter-productive: after all, the administrator account is supposed have more access to the system, it’s supposed to be able to see and do all things that are available to the standard user, plus some more. Why can’t it see the network drive created by the standard user?
In any case, there is a way to force Windows to make the network drives available to both the standard and administrator accounts automatically. All you need to do is run Registry Editor (regedit.exe), locate the following key:
and create a new DWORD entry with the name EnableLinkedConnections and value 1:
Caution: If you are not very experienced with Registry Editor, please be extra careful: it’s a powerful tool that can do a lot of damage to your system if used carelessly.
After you’ve added the EnableLinkedConnections value to the Registry, restart the computer, and after that the network drives you create should become available to the elevated applications, as well.
Update for Windows 8
It appears that the EnableLinkedConnections setting is not always working correctly on Windows 8: if a standard user has created a mapped network drive pointing to a subfolder of a shared folder (for example, drive Z: connected to //server/share/subfolder), then the elevated user will see the drive Z:, but it will be pointing to the root share, //server/share/, not to the subfolder.
If this error creates a problem for you, then it’s better not to use the EnableLinkedConnections registry fix at all. Instead, just create the mapped network drive twice: first time using a standard user’s account, and the second time using an administrator account. Sure, it’s twice the work, but it should work correctly in all situations.
If you want to link to this article, you can use this HTML code: <a href=”http://www.winability.com/how-to-make-elevated-programs-recognize-network-drives/”>How to make elevated programs recognize network drives</a>
- What people are saying about AB Commander…
- A FREE 30-day license is included
- What’s new in the new version
- AB Commander press release
- End User License Agreement (EULA)
- Space Investigator
- Using DiffMerge as the external tool of AB Commander
- Is "Wipe the content" the same as "Secure Delete"?
- How to start programs elevated from a batch file
- How to make elevated programs recognize network drives
- How to disable hibernation with AB Commander
- How to set up Notepad++ as the external text editor for AB Commander
- Integrating AB Commander with Universal Viewer
- How to repair Windows desktop icons with AB Commander
- How to show drive letters first in AB Commander and Windows Explorer
- Organize your photo library with the Rename tool of AB Commander
- How to move images from an Android device to PC
- How to synchronize images between a PC and an Android device
- Using junction points to change the iTunes backup folder location
- Always have a backup of your important files