I am running Win7Pro 64 bit and have FTK Imager 3.1.0 installed. I have mapped a network share, which Windows does show, but when I try to image "contents of a folder" and browse to "Computer" to find the share, Imager does not see it.
So, I try running Imager Lite 2.6 from a thumbdrive and it's able to see the share!! What am I missing?? Does 3.1.0 no longer see shares???
I have tried this several times with the same result.. Any ideas??
Thanks!
Jim
Apparently, YMMV, because I just tried it, same OS, and it worked fine. Full disclosure I typed in the drive letter the first time through the dialog, so I don't know if it wasn't going to show up under "Computer," but when I tried it again, it had no trouble listing the mapped drive.
I was prepared for it not to work. There is at least one known bug in 3.1 that's not in 2.54 (probably several previous versions). When you take a previously created FAT32 image, and attempt to export a file list, it completely omits one of the MAC columns. Column header is there, but the data is all blank. This doesn't happen if the list is created at the time of image creation.
Imager will see it if I type in the share "\\10.7.20.12\profiles" as the location, but it refuses to show in the browse window… Only local drives.. Very frustrating.
Thanks for testing it Tucker!
Apologies for bringing this post back from the dead, but it is the top hit in 2025 for searching "ftk Imager network share". I am using Ftk Imager 4.7.3.81 and I couldn't access a share using the example above "\\x.x.x.x\<share name>", nor from using the "map network drive" dialogue.
However, what did work for me was assigning a share through a command prompt using "net use" e.g. "net use z: \\x.x.x.x\<share name> /User:user password".
Though the z: does not appear in windows explorer, you can type "z:" at the command prompt to confirm it works.
Now, when I use FTK Imager and browse for locations to store a hard drive image, ram dump, etc., it does see "z:" and I can acquire across a network.
Â
There is a registry entry that you need to change.
I had this problem years ago and I believe this is what I did to enable it..
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.- Point to New, and then click DWORD Value.
- TypeÂ
EnableLinkedConnections, and then press ENTER. - Right-clickÂ
EnableLinkedConnections, and then clickÂModify. - In the Value data box, type 1, and then click OK.
- Exit Registry Editor, and thenÂ
restart the computer.
Hope this works!
