The drive is pre-formatted in exFAT (cross-compatible with macOS and Windows) and should automatically be recognized without the need to initialize and format before use. If the drive has been reformatted after purchase with a file system not natively supported by your operating system, it may need to be mounted manually. Click here for instructions on reformatting drives if desired in Windows. Click here for instructions in macOS.

Installing the latest Thunderbolt 3 and BIOS firmwares from your system manufacturer is strongly recommended. Some systems with outdated firmware may not be compatible with this (and other) Thunderbolt 3 devices. (Note: This only applies to Windows systems. Apple Thunderbolt 3 systems automatically receive firmware updates during macOS upgrades.)

The only host platforms with Thunderbolt 3 to be confirmed as incompatible at this point are the Dell Latitude 7275 and ASUS ProArt Station PA90.

Boot Camp with Windows 10 (version 1809 and up) is supported.

Transfer speed is affected by many factors. While this Thunderbolt™ 3 NVMe drive is capable of sequential transfer speeds of 2400+ MB/s read and 1800+ MB/s write, results will vary depending on the program being used, OS, and workload.

Some Thunderbolt 3 ports support a 2-lane PCI Express configuration (PCIe x2), and some support a 4-lane PCI Express implementation (PCIe x4). Performance will depend on the specific workload. The maximum throughput of the drive be reduced in some scenarios on systems with a PCIe x2 implementation. In our testing, the maximum R/W results on an x2 system were ~1400MB/s R and 1200MB/s W.

Most system manufacturers list these details in their online system specifications. For example, Dell has this information available for most of their popular hosts in a handy single document: here.

Yes! The screenshot below is from a 2019 MacBook Pro 15″ with a PCIe x4 implementation.

Our NVMe SSD drives must be connected to a Thunderbolt™ 3 equipped USB-C port. On systems which have a mix of Thunderbolt™ 3 and non-Thunderbolt™ 3 USB-C ports, please ensure the device is connected to a Thunderbolt™ 3 port. Most systems with a mix of ports will have a Thunderbolt symbol next to the Thunderbolt 3 ports.

With Windows 10 version 1809 the default removable storage settings are set to have write caching disabled in favor of quickly removing the drive vs needing to “safely remove”. This setting can be changed in the Device Manager. See here for instructions: https://support.microsoft.com/en-us/help/4495263/windows-10-1809-change-in-default-removal-policy-for-external-media

A solution for this issue was found here: https://discussions.apple.com/thread/8262732

• In Disk Utility, switch the View option to “Show All Devices”.
• Select the entry named “PCIe SSD Media”, with “TBT3_SSD” indented below it.
• Click on Erase.
• Change the Scheme to “GUID Partition Map”. The Format choices will then expand to include several APFS choices.
• Set the Format to “APFS”.
• Press Erase.

Originally authored by: Jeff Everett, March 21, 2013

This post is intended to offer detailed technical information for troubleshooting issues affecting new “Advanced Format” 512e SATA disk drives. 

Plugable’s full-size 3.5″ hard drive docks, the USB3-SATA-UASP1, USB3-SATA-U3 and USBC-SATA-V; these feature support for these new 512e Advanced Format drives. Our Plugable Storage System “PSS” products also support 512e large volumes (as soon as 2.5″ drive capacities increase and these drives become available in smaller sizes than 3.5″).

Some docks have a non-standard sector emulation feature that enables using capacities above 2TB on Windows XP 32 bit. But this requires that drives initialized and formatted in a special way, and NOT be used with other SATA controllers in desktop PC’s or other drive docking stations, unless those units also have a matching firmware version and support for this feature.

Plugable USB SATA docks do not support sector emulation for XP.   Rather, we’ve chosen to support 3TB+ Advanced Format drives in the standard way without any emulation.

Background

The storage model used by disk makers for the last 10+ years is changing, and this post is an effort to explain how these changes work in detail. In case of issues moving drives between different systems, or when encountering issues using USB attached drives to host enterprise application data, the details here can help understand what factors are at play.  

Data is stored fundamentally in bits (bits with a little b). Busses like USB often measure throughput in bits, like USB 2.0’s 480 Megabits per second (480 Mbps) or SATA III’s Gigabits per second (6 Gbp/s). Eight of these individual bits of data make up one of the capital-B “Bytes” that we usually measure data in, be it kilobytes (KB) in a document, MegaBytes (MB) in an MP3, or GigaBytes (GB) of data on a storage volume like a hard drive or SSD.  Generally speaking, transfer rates industry-wide are measured in bits so transfer rates appear higher than if they were measured the same way the data is actually stored, in Bytes.

On modern solid state drives and traditional hard or even floppy disks, these bytes are grouped into sectors for actual read/write operations. Over the last decades, almost all storage drives used 512 Bytes per sector to store data since addressing individual bits and Bytes would be impractical.

Having all drives at 512 bytes per sector was nice, as there were few compatibility issues to think about when moving drives between systems or SATA docks, or when cloning them.

Evolution

512 byte sectors present problems with larger capacity drives (3TB+)- to make way for larger drives, sector sizes had to grow.  This presents challenges throughout the “software stack” from the SATA hardware controllers and their firmware, their drivers, the operating system, and even to how applications may sometimes assume certain sector sizes or where sectors will start.  Resulting issues are numerous and will take time for the industry to fully work out. 

Over the past few years, Advanced Format Drives (512e, AF) drives reporting 512 Bytes/”logical” sector while actually using physical sectors of 4096 Bytes/”physical” sector have gained in popularity due to their higher data density potential, and resulting larger capacities. For more on how these drives work and why the industry switched, read this great ZD net post.  Soon, we’ll be seeing drives that use 4096B logical and physical sectors.  

*from Microsoft support policy for 4K sector hard drives in Windows

As you can see from the table above, determining whether you have a 512n (drive with reported and physical sectors of 512 bytes), 512e (the 512 emulation 4096 “Advanced Format” drives with physical 4096B clusters), or 4Kn (drive with both reported and physical sectors of 4096B) is crucial to determine which Windows operating systems will be able to recognize the drive.

On OS X, large volume support is somewhat better, with effectively no limits on volume size in modern OS X versions:

*From Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits

How to check your drive’s sector size

To determine if you have an 512e Advanced Format Drive, open an administrative command prompt and run the following command on the NTFS formatted volume:

fsutil fsinfo ntfsinfo [your drive]

[your drive] will be the letter of the disk you’re testing, so c: or d: etc.

The output will look like this, with the bold portion below being the relevant information. Bytes per Sector of 512 and bytes per Physical Sector of 4096 indicate a 512e drive:

C:\Windows\system32>fsutil fsinfo ntfsinfo h:
NTFS Volume Serial Number : 0x8a0c5e820c5e68e9
NTFS Version : 3.1
LFS Version : 1.1
Number Sectors : 0x00000001d1bcafff
Total Clusters : 0x000000003a3795ff
Free Clusters : 0x000000003a3671d7
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
 Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000040000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0000
Mft Zone End : 0x00000000000cc820
Resource Manager Identifier : DB59D441-7AD6-11E2-BEE8-00027232D73D’

If your drive reports:
Bytes Per Sector : 512
 Bytes Per Physical Sector : 512
This one of the 512n volumes commonly used over the last decade. Support for these drives is universal.

If your drive reports:
Bytes Per Sector : 512
 Bytes Per Physical Sector : 4096
The volume is operating in 512e mode, and should be recognized by most Windows Vista (SP1 and later) systems, as well as by newer Windows 7 and 8 PC’s. Windows 7 and Server 2008 users who do not have Service Pack 1 installed need a system update for 512e compatibility.

Macs should also be able to see the volume with no issue, however do not have native NTFS write capabilities, so they may only be able to read the drive.

If your drive reports:
Bytes Per Sector : 4096
 Bytes Per Physical Sector : 4096
Then the drive has been formatted with non-standard sector emulation, in order to support 3TB+ drives on Windows XP.

A special release of firmware for the Plugable USB3-SATA-U3 (firmware v12092681f600) is available by special request that uses this non-standard emulation strategy. However, it is not the default and is generally not recommended as it limits moving the drive to other docks with the same emulation strategy.

How to clean and re-initialize a volume

Moving volumes initialized with 4096B sector re-emulation to other SATA controllers (other drive docks or PC SATA connections) may result in drives that are visible in disk manager but with no partitions, and no option to re-format the drive since the “new” (non U3) SATA controller doesn’t support the 4096B sector re-emulation.  In this case, wiping the drive is necessary to use it on the new controller. 

Wiping a misaligned drive’s partition table will allow the volume to be re-initialized as though it were new, and a new partition table may be written when the disk is re-formatted.

Performing the following steps will destroy all data on the disk selected, so these steps must be performed with extreme caution. 

To check for all attached volumes, open an administrative command prompt and enter diskpart, then enter the list disk command as shown below, and select the disk of your choice to clean. After selecting whichever disk number you want to wipe, the clean command will destroy the partition table and allow you to re-initialize the volume.

C:\Windows\system32>diskpart

Microsoft DiskPart version 6.2.9200

Copyright (C) 1999-2012 Microsoft Corporation.
On computer: GRANDCENTRAL

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
——– ————- ——- ——- — —
Disk 0 Online 111 GB 1024 KB
Disk 1 Online 1863 GB 0 B
Disk 2 No Media 0 B 0 B
Disk 3 No Media 0 B 0 B
Disk 4 No Media 0 B 0 B
Disk 5 No Media 0 B 0 B
Disk 6 Online 1862 GB 0 B
Disk 7 No Media 0 B 0 B
Disk 8 Online 465 GB 0 B

DISKPART> select disk 8

Disk 8 is now the selected disk.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART>

From here the disk is blank and can be re-initialized and formatted with whatever partitions are desired.  Most consumers will not need to be aware of the other issues that can arise with Advanced Format volumes in enterprise applications.

Partition Alignment

If the performance of your 512e large volume has degraded when being moved from system to system, partition alignment issues may be the cause.  Issues with non-bootable cloned volumes may also be due to improperly aligned partitions. Western Digital and Hitachi offer drive alignment utilities for affected operating systems. Seagate drives should not require alignment. Customers with other brands of drives will need to check with the manufacturer of their drive to determine if an alignment tool is available and/or necessary.  Partition alignment issues often affect older Windows Vista and Windows XP systems where drives are frequently accessed on other operating systems.

Before initializing a new drive, using a large volume with Windows XP, or especially before cloning an Advanced Format Western Digital drive, please check the chart below to determine if aligning your drive is necessary for maximum performance and compatibility with your software environment.

Using your WD Advanced Format Hard Drive with a Windows Operating System may require you to run the WD Align Windows software utility after you install your operating system or partition and format the drive as a secondary drive. The WD Align software aligns existing partitions on the Advanced Format drive to ensure it provides full performance for certain configurations. (Please see table for configuration details)

Running Hitachi’s “HGST Align” tool may be necessary for Windows XP or Windows Vista users. Windows 7 and Windows 8 users should not need to use this utility.

Windows support in the enterprise

Most end-users won’t need to worry about drive sector sizes, partition alignment, or any of the details above. Due to the specific issues documented by Microsoft with some of their enterprise applications, thorough planning for drive purchasing and migration is crucial in enterprise environments leveraging the following technologies:

• Hyper-V: http://support.microsoft.com/kb/2515143
• Microsoft SQL Server: http://blogs.msdn.com/b/psssql/archive/2011/01/13/sql-server-new-drives-use-4k-sector-size.aspx
• Windows Home Server v1: http://support.microsoft.com/kb/2385637
• Microsoft Exchange Server: http://technet.microsoft.com/en-us/library/ee832792.aspx#Phys
• Third-party applications and hardware: Applications and hardware devices may have reliability and performance issues when they are connected to these new drives. Contact your application and hardware vendors about their support policy for these drives.

*from “Microsoft support policy for 4K sector hard drives in Windows.”

For more details on 512e and 4Kn Advanced Format support across Windows versions, application specific issues, other known issues, and unsupported scenarios, read Microsoft support policy for 4K sector hard drives in Windows.

Further details on the evolution from 512n to 512e and 4Kn drives are available in this presentation from IDEMA (International Disk Drive Equipment and Materials Association).

Deeper technical details for driver developers are available in Microsoft’s “Advanced format (4K) disk compatibility update (Windows)” article.

Synopsis – If your Thunderbolt 3 driver or utility version types are mismatched within a Windows host system, you may receive an error message stating, “Application Cannot run – This Thunderbolt application is not in use anymore and can be safely uninstalled” when attempting to run the Intel Thunderbolt Software management utility or the Intel Thunderbolt Control Center utility. This prevents proper management of Thunderbolt devices on the host system. (This problem does not occur on Apple Mac systems.)

Before proceeding with this or any other procedure that makes changes to your system, please ensure you have a full system backup of any and all important data and create a fresh System Restore Point as a precaution. Plugable will not be able to help restore any data or return a system to a working state should things not work as expected. If you do not wish to take this risk, please do not follow this procedure

You will have to be logged on to the system as a User with ‘Administrator’ permissions in order to perform these steps

1. Disconnect any Thunderbolt 3 devices from the host system (this is done to prevent Windows Update from automatically loading any Thunderbolt drivers).
2. Right-click on the Windows Start button and select ‘Device Manager’.
3. Click on ‘View’ from the application menu bar, and click the option ‘Show hidden devices’ (this is necessary because the Thunderbolt controller will not be active if no Thunderbolt devices are connected).
4. Expand the ‘System Devices’ category. Scroll down until you find the entry for the ‘Thunderbolt Controller’.
5. Right-click on the ‘Thunderbolt Controller’ entry and select ‘Uninstall device’ from the context menu that appears.
6. From the ‘Uninstall Device’ window that appears, click to place a check mark within the ‘Delete the driver software for this device’ option.
7. Click the ‘Uninstall’ button.
8. Close Device Manager.
9. Click the search button on the taskbar (looks like a ‘O’) and search for the letters ‘cmd’.
10. Right-click on the ‘Command Prompt’ search result and select ‘Run as Administrator’ from the context menu. If prompted, enter your Administrator password.
11. From the Administrative Command Prompt window, enter ‘sc delete nhi’ (without the quotes) and press enter. You should receive a ‘SUCCESS’ indicator. ** Be very careful to type this command correctly ** 

This command deletes the ‘nhi’ Windows service presently installed on the system.

Overview and Drivers

In general, Plugable Thunderbolt 3 Docking Stations and Thunderbolt 3 Dual Display Adapters do not require the installation of any drivers when used with macOS or Windows. When connecting a Thunderbolt 3 device, the host operating system should install all the necessary drivers automatically.

However, there are certain instances with Windows systems where additional driver installation may be necessary when using our Thunderbolt 3 docking stations (these are NOT required on macOS systems):

TBT3-UDV Docking Station:

• Windows 10 – In general, no driver installations are required when using Windows 10. After initial connection if all functions of the dock are working as expected, then no additional action is required. However, when the TBT3-UDV is used with certain eighth generation Intel processor-based Windows 10 systems an updated USB 3.0 driver may need to be installed to ensure the best performance of USB peripherals attached to the TBT3-UDV. We recommend installing the updated Asmedia USB 3.0 drivers here. For additional details, please see our TBT3-UDV product page.
• Windows 7 – When using Windows 7 64-bit (32-bit systems are not supported), you will need to install a separate Intel Network Adapter driver and a driver for the Asmedia USB 3.0 Host Controller.

TBT3-UD1-83 / TBT3-UD1-85 Docking Stations:

• Windows 7 – When using Windows 7 64-bit (32-bit systems are not supported), you will need to install a separate Fresco USB 3.0 Host Controller driver and an Intel Network Adapter driver.

General Thunderbolt 3 Information

Before purchasing or using a new Thunderbolt™ 3 docking station or video adapter for use with your personal computer running Windows, you will want to make sure that your computer can support it and be aware of differences from basic USB devices:

Note: The following does not apply to Apple Thunderbolt 3 systems.

• Many early Thunderbolt 3 PCs require firmware and software updates before all adapters and docks will work.
• Dual display support is optional for Thunderbolt 3 PCs. How many displays are supported over Thunderbolt 3 depends on how the USB-C port has been wired on the system motherboard (up to a max of two), and is not changeable in software or by the Thunderbolt 3 graphics device.
• Support for PC charging (USB Power Delivery) on Thunderbolt 3 systems is optional. Many Thunderbolt 3-enabled PCs do not accept a charge over USB-C, and some PCs only will charge with their own branded power adapters.
• Unlike USB devices, Thunderbolt 3 devices must be manually authenticated (approved) for use by the user before the system will recognize them.

Additional detail

• Host computers equipped with Thunderbolt 3 have the ability to install various updates including NVM (Thunderbolt 3 related Non-volatile memory) and PD (Power Delivery) firmware, UEFI BIOS, supplemental Thunderbolt 3 software utilities (for authentication) and various drivers to resolve potential issues and increase compatibility with new Thunderbolt 3 products as they are released.
• System manufacturers have substantial discretion in how they implement various technical elements and features. As a result, compatibility information is complex. As a result many currently available Thunderbolt 3 systems are not fully compatible with our Thunderbolt 3 dual graphics adapters (we do our best to maintain compatibility tables of the individual product pages). Some systems may only be equipped with a single DisplayPort (DP) Alternate Mode (Alt Mode) line to the Thunderbolt 3 port which limits the port to a single display output. Due to this limitation some systems won’t be able to take advantage of our dual port Thunderbolt 3 graphics adapters regardless of firmware/software updates. This is a physical hardware limitation.
• Many system manufacturers ship systems with older firmware and may or may not have updated versions available for download at this time. The latest Thunderbolt 3 firmware for a specific system cannot be downloaded from Intel directly, as it first it has to be customized by the original system manufacturer. Intel has a Thunderbolt updates page with some update information, but as of this writing the list if fairly small. Currently our TBT3-HDMI2X-83 and TBT3-DP2X-83 adapters require the host system to have a Thunderbolt 3 firmware update with NVM version 14 or higher in order to work properly. The latest UEFI BIOS update from your system manufacturer must be installed before updating the NVM firmware.

Operating System Compatibility

Thunderbolt 3 technology is supported by any operating system which has driver support for Thunderbolt 3. Currently, Plugable supports Windows 10, 8.1, and 7 (64-bit only) and macOS 10.13 or later. Although support for Thunderbolt 3 devices under Linux is steadily evolving, Plugable does not support Thunderbolt 3 devices within a Linux environment at this time.

Authenticating a Newly Attached Device

Click here for this process.

General Thunderbolt 3 FAQ

Q: Can a Thunderbolt 3 dock or adapter work in any system with any USB-C (USB Type C) port?
A: It depends.

• Early Thunderbolt 3 docks and adapters will only work with Thunderbolt 3 USB-C computers and ports and connecting to a USB-C port without Thunderbolt 3 capability will not work. Note that computers and docks may have a mix of Thunderbolt 3 and other USB-C ports that look very similar. Look for the Thunderbolt icon on both sides of the connection to ensure compatibility:

• Current Titan Ridge based docking stations like our TBT3-UDC1 and TBT3-UDZ are backwards compatible with USB-C systems in most cases (with limitations).

Q: How can I identify the NVM version on my system?
A: See “Identifying the NVM” section below.

Q: What if a newer compatible NVM is not available from my system manufacturer?
A: Unfortunately the only option is to contact your system manufacturer and ask when a newer version will be available, and to let them know that until it is, certain accessories you are looking to use will not work.

Q: How can I identify if my system has the necessary two DisplayPort lines to provide dual display output through the Thunderbolt 3 port?
A: Unfortunately in many cases this information is very hard to discern based on the manufacturers published specifications. If your system is not among those listed in our compatibility table above, please contact your system manufacturer for confirmation of how many DisplayPort lines are routed to your Thunderbolt 3 port.

Q: I connected my Thunderbolt 3 dual display adapter and my monitor configuration changed by itself.
A: This may occur and is considered normal. You can change the main display back to your desired screen through the “Display settings” control panel.

Q: I connected my Thunderbolt 3 dual display adapter and am only getting a single output.
A:  Depending on what Thunderbolt 3 equipped system you have, it may only support a single output because of the DP Alt Mode line configuration. See above “Known Host NVM Versions & DP Lines” to find out if your system has one or two lines.

Q: I connected my Thunderbolt 3 dual display adapter for the first time and my system crashed (hard lock).
A: Check to see if your system is running the latest Thunderbolt 3 software, NVM, UEFI BIOS, and all other updates from your system manufacturer. If everything is updated, unplug the adapter, reboot the system, and then reconnect.

Q: I connected my Thunderbolt 3 dual display adapter and am not getting any output to either display.
A: If your system has hybrid graphics (combination of built-in Intel GPU and AMD or NVIDIA discreet graphics) make sure the Intel GPU is set to be the primary GPU in the UEFI BIOS.

Support

If you have any questions feel free to contact our support team, we’re more than happy to help!

Thunderbolt and the Thunderbolt logo are trademarks of Intel Corporation in the U.S. and/or other countries.

It's not uncommon for users to notice a certain level of heat generation from electronics and by extension, Plugable products during operation. In this knowledge base article, we'll explore the reasons behind this heat generation and why it is considered a normal experience within reasonable limits.

Electronics, by their nature, generate heat during operation. This is primarily a result of the electrical current flowing through various components, such as integrated circuits, transistors, and other electronic elements. As Plugable products are designed to efficiently process and transfer data (among other functionality), some level of heat generation is inherent.

Factors Influencing Heat Generation:

1. Power Consumption: The power consumption of a device directly influences the amount of heat it generates. Higher power usage, especially during data transfer or charging processes, can lead to increased heat.
2. Enclosure Design: The design of the product's enclosure and its ability to dissipate heat play a crucial role. Adequate ventilation and heat sinks are often incorporated to manage and disperse generated heat effectively. This is evident in our TBT3-UDZ and TBT4-UDZ designs. The metal case in these docks are designed to function as a heatsink with thermal pads placed throughout the enclosure. This allows heat dissipation from inside to the outside, but will also make it feel as if the device is “too hot”. 
3. Ambient Temperature: The external environment may also play a role. Higher ambient temperatures can contribute to increased perceived heat from the product. This means that summer temperatures may increase the heat generation of not just Plugable products, but many other electronic devices.

Normal Heat Levels: While it is normal for electronic devices to generate heat, Plugable products are engineered to operate within safe temperature ranges. We conduct rigorous testing to ensure that the heat generated during normal operation falls within industry-standard safety parameters. While not all products are or need to be UL certified, we try to go by UL guidelines for thermal readings. The UL threshold is 77C/170.6F, and we aim for around 71C/160F.

Tips for Users:

1. Ventilation: Ensure that Plugable products have sufficient ventilation around them. Avoid placing them in enclosed spaces where heat dissipation may be impeded.
2. Usage Patterns: Intensive tasks such as high-speed data transfer or charging multiple devices simultaneously may result in increased heat generation. This is generally normal but may be more noticeable in such scenarios.
3. Accessories: A number of our devices will allow for the connection of USB accessories and as such, these will require power. If too many “power-hungry” devices are connected, this will cause the device to run much hotter than expected. Be sure to keep in mind the power limits of your dock/device.

In conclusion, experiencing heat from Plugable products is a normal aspect of their operation. Users can rest assured that we prioritize the safety and efficiency of our devices. By understanding the factors influencing heat generation and following simple usage guidelines, users can make the most of their Plugable products while ensuring a reliable and efficient user experience.

Often it can be helpful to have access to a folder or external hard drive from two computers.  Instead of unplugging an external hard drive and physically moving it to the second computer it may be more efficient to share the driver over the network.

Windows file sharing includes password based authentication and can be easily configured to share specific folders or entire drives over the network, providing access to the same data from multiple computers, while slower than a directly connected USB 3 hard drive it can be more convenient.

This article will demonstrate how to share the file system from an externally connected SATA SSD over the network for access from other Windows workstations.  We will use the computer's local user account and password for authentication.

Definitions:

• Server - The server will be the computer with the USB attached SSD, this can have Windows 10 or 11 with an administratively privileged user account
• Client - The computer connecting to the shared driver over the network, this can have Windows 10 or 11

Hardware to replicate this setup:

• 2x Windows computers, the process is very similar for Windows 10 and Windows 11 to act as Server and Client
• 1x SATA Vertical Hard Drive Dock with USB-C connection USBC-SATA-V ( https://plugable.com/products/usbc-sata-v )
• 1x SATA SSD or Hard Drive
• Network with both Server and Client - recommended a wired network for best performance, however wireless also works

Setting up the file server

1 - Connect the hard drive to the Server, if not already formatted the partition and format the drive with an NTFS file system, ensure the file system is detected and accessible under your user account.

2 - Open Windows File Explorer, holding down the Shift key, right-click on the drive or folder to be shared, hover over “Give access to” and select “Advanced sharing…” to open the “Advanced Sharing” window

3 - Under the “Advanced Sharing” subsection, select the “Advanced Sharing” button, this requires local administrative permissions

4 - Under the “Settings” subsection, select the “Share this folder” checkbox", then select the “Permissions” button to open the “Permissions for <sharename>” window.

5 - Under “Group or user names:” subsection, select the “Add…” button to open the “Select Users or Groups” window

6 - In the text box in the “Enter the object names to select (examples):” heading, type in your user account name, in this example “plugable”, then click the “Check Names” button to automatically complete the field, the first part of this name is the computer's host name ending before the back slash “\”, noted this down for connecting to this computer, when done select “OK” button

7 - On the “Permissions for <sharename>” window, under the “Group or user names:” subsection, select your username, then under the “Permissions for <username>” subsection, check the “Allow” boxes to provide both read and write permissions to the shared drive, click on “OK” when complete

8 - The drive or folder should now be shared and available for any Windows host connected to the same network - one note, this does require the computers to be on the same subnet ( for example connected to the same WiFi or same Ethernet switch/router ) and for the Windows Firewall to be set to a Private network - additional details here ( https://kb.plugable.com/2600495 )

Connecting to the share for quick access

1 - Connect the Client to the same network as the server if not already connected

2 - Use the keyboard shortcut Windows + r to open the Windows Run dialog ( Press and hold the Windows Flag key, then tap the ‘r’ key, and release the Windows Flag key )

3 - In the Run dialog, type in two back slash characters “\\” then type in the name of the Server, in this example “HP-22-ELITEG9” ( from Step #6 in the file server setup above )

4 - Enter your user account credentials when prompted, these are the credentials for the Server not the Client computer

5 - Windows File Explorer should be open with the shared folder or shared drive accessible now.  You can drag and drop items into and out of this folder, however if you would like to save files to this folder from within applications you will need to mount the share as a drive letter

Assigning a drive letter to a network share

1 - Complete the “Connecting to the share for quick access” section above, then right-click on the share name in Windows File Explorer and select “Map Network Drive”

2 - Make any changes you see fit and Select the “Finish” button to use the default settings, by default network drive assignment starts with “Z:” and works backwards through the alphabet.

From here you can save files directly to the “Z:” drive and they will be saved onto the shared folder or drive for access from either the Client or Server computers.

Additional notes

This method of network file sharing requires the Server to be active and on the network for the Client to access the shared files.  If the Server is set to enter sleep mode or hibernation when idle the network share may become inaccessible.

Network file systems also have reduced performance compared to a directly connected USB external hard drive, depending on the network, drive type, and connection to the Server this can be anywhere from 1/10th the speed to nearly the same speed.