Share via

Seagate FreeAgent GoFlex Home Drive Not Detected with Recent Windows 10 Update

Anonymous
2018-05-27T21:22:39+00:00

HELP!

I have a FreeAgent GoFlex Home Drive that is connected to my router via ethernet.  It is available to share files to anyone on our network.  My Mac can see it no problem (so it's not a device problem).  It was fine from my Windows 10 PC until the update that went in the last few weeks.  It is a Windows 10 issue.

I  have contacted Seagate and this is what they said:

Thank you for contacting Seagate Support. I understand Windows 10 is not seeing your GoFlex Home NAS on your network. I'm sorry for the inconvenience this is causing for you. I'd be glad to assist you.

As far as the Seagate Dashboard/Memeo Instant Backup software is concerned, the software is really not going to be of any benefit to you. The Seagate Dashboard/Memeo Instant Backup software is not compatible with Windows 10 anyway. The Seagate Dashboard/Memeo Instant Backup software was only supported in Windows XP through Windows 8, and there are no plans to update the software to include Windows 10 compatibility. software was only supported in Windows XP through Windows 7, and there are no plans to update the software to include Windows 10 compatibility.

The Paragon Driver software you downloaded only works with GoFlex USB connected external hard drives, not network drives.

I believe the reason Windows 10 is not seeing the GoFlex Home is probably because of an update that Microsoft pushed out recently that changed the way Windows 10 detects network devices. The GoFlex Home is dependent on a Microsoft protocol called SMBv1. Microsoft created this protocol and it was used for providing shared access to files, folders, printers, serial ports, and basically anything you wanted to share. This used to be the standard protocol on all previous versions of the Windows operating system. With the recent updates that Microsoft sent out for Windows 10, however, Windows 10 now has SMBv1 disabled by default in the Windows operating system. From my understanding, Microsoft did this to address some security flaws in the SMBv1 protocol. The only thing we can point you toward is this 3rd party knowledge base support article on how to enable SMBv1. 


Thanks!

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2018-05-27T22:31:18+00:00

    See if this works...

    Press Windows key + R

    Type: optionalfeatures.exe

    Hit Enter

    Scroll down to SMB 1.0/CIFS File Sharing Support

    Tick the SMB 1.0/CIFS Client

    Untick SMB 1.0/CIFS Automatic Removal and

    Untick SMB 1.0/CIFS Server

    Click OK

    Restart if prompted.

    Microsoft apparently has a workaround which does not require enabling SMBv1, for those who rely on the ability to 'browse' the network.

    https://support.microsoft.com/en-us/help/403431...

    Explorer Network Browsing

    The Computer Browser service relies on the SMBv1 protocol to populate the Windows Explorer Network node (also known as "Network Neighborhood"). This legacy protocol is long deprecated, doesn't route, and has limited security. Because the service cannot function without SMBv1, it is removed at the same time.

    However, if you still have to use the Explorer Network in home and small business workgroup environments to locate Windows-based computers, you can follow these steps on your Windows-based computers that no longer use SMBv1:

    Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start). When you open Explorer Network, enable network discovery when you are prompted.

    All Windows devices within that subnet that have these settings will now appear in Network for browsing. This uses the WS-DISCOVERY protocol. Contact your other vendors and manufacturers if their devices still don't appear in this browse list after the Windows devices appear. It is possible they have this protocol disabled or that they support only SMBv1.

    Also...

    Press Windows key + R

    Type: services.msc

    Hit Enter

    1. Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them toAutomatic (Delayed Start).
    2. When you open Explorer Network, enable network discovery when you are prompted.
    30+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-05-31T05:32:59+00:00

    Ok so the only thing that worked was to uninstall the Windows 10 update.  As soon as I did so, my pc now looks like this:

    10 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-05-29T01:58:09+00:00

    Hi  Andre Da Costa,

    Thank you for your reply.  I tried to do what you recommended.  However, when I

    Press Windows key + R 

    Type: optionalfeatures.exe 

    Hit Enter

    I only have the option:   SMB 1.0/CIFS File Sharing Support

    Here's a print screen of what I see:

    When I look in device manager, my device appears under network, but if I attempt to click on it, it disappears:

    If I look in device manager, this is what I see:

    I also tried the windows workaround that you provided.  As you can see below.  However, if I start up Microsoft Edge (Windows 10 doesn't have Internet Explorer), I don't get the prompt to  2. When you open Explorer Network, enable network discovery when you are prompted.

    So far none of these solutions have worked, but not sure if I'm implementing them correctly.  Please advise.

    Thanks for your help,

    Pam Duren

    1 person found this answer helpful.
    0 comments No comments