locked
Client for NFS is not licensed for use on this version of Windows error windows 10 14393.10 RRS feed

  • Question

  • I am seeing a curious error in my event log. 

    " Client for NFS is not licensed for use on this version of Windows. "

    I am running a licensed copy of Windows 10 Pro, and the NFS client option appears in the windows add/remove component list, so why is windows telling me my version of windows can't use it?

    this question was originally posted here on the MS answers forum, but I was told to post the question to TechNet.

    since the original question was posed, Windows has been updated to build 14393.82

    Friday, August 19, 2016 3:36 AM

All replies

  • Can you advise please what the Event ID of this event you are seeing is please? And also which event log? It would be interesting to see if this occurs on other Windows 10 Anniversary builds.

    Is there any issue \ on going problem you are investigating that prompting you to look in the Event Viewer?

    Sunday, August 21, 2016 8:46 PM
  • I also have this issue.

    EventId: 16385

    Source: NfsRdr

    Message:  Client for NFS is not licensed for use on this version of Windows.

    There are tons of these messages all day long. The side effect is that RDP the saved password does not always work.


    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Saturday, September 10, 2016 9:31 PM
  • Yes ,I'm getting the same errors in my event log 

    It seems when I try and access my wd mycloud nas

    as I navigate through the folders it will hang and then It will generate this error

    Client for NFS is not licensed for use on this version of Windows.

    eventID:16385  Source: NFSRDR

    windows 10Pro 14393.187

    Thank you


    • Edited by bigcid100 Saturday, September 17, 2016 9:15 PM more info
    Saturday, September 17, 2016 7:52 PM
  • interesting related post NFS client missing in W8 RP so it appear the nfs client is deprecated. Can you update the share to use SMB ? or look for a third party NFS client.
    Saturday, September 17, 2016 9:59 PM
  • Windows 10 do have the "Services for NFS" in "Turn Windows Features on or off".

    Futhermore it now also includes the Linux Subsystem (which I installed).

    So the post related to win8 is not relevant.

    This is clearly a problem that MS should not ignore...


    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Saturday, September 17, 2016 10:07 PM
  • Yep, just checked. So if someone from MSFT can comment be interesting to see if that is a bug in Turn Windows features on or off or a bug with NSF client.
    • Edited by -Mr Happy- Saturday, September 17, 2016 11:10 PM
    Saturday, September 17, 2016 10:34 PM
  • It makes sense the NFS client is back.

    Anyway there is some interaction with something security related that should be investigated and smells like a bug.


    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Saturday, September 17, 2016 11:08 PM
  • I just checked my features list and nfs client is definetly on

    it didn't start happening till the CU before the newest one

    maybe something got changed

    Saturday, September 17, 2016 11:25 PM
  • I have the same problem ("Client for NFS is not licensed for use on this version of Windows."), I believe it is happening only since one of recent updates. Similarly, a licensed copy of Windows 10 Pro, all updates installed. Error appears when accessing certain network shares.
    • Edited by -kashmiri- Sunday, September 25, 2016 6:56 PM
    Sunday, September 25, 2016 6:55 PM
  • This PC was a Windows 7 Ultimate machine with several NFS shares mapped. When I upgraded I got Windows 10 Pro, as there is no Ultimate edition. Now I cannot map any NFS shares. Why was functionality taken away from me with the upgrade? During the whole upgrade It kept telling all my files would still be there. Well, they are, but I am not allowed to get to them.

    How do I get this access back?

    buzz

     
    Thursday, September 29, 2016 4:25 PM
  • All of you guys are on 1607 yes?

    <note to all this is not an answer, nor a proposed answer, just a data gathering point>

    • Proposed as answer by ZigZag3143x Friday, September 30, 2016 3:51 PM
    • Edited by Susan BradleyMVP Monday, October 3, 2016 3:59 PM Clarification
    • Unproposed as answer by ZigZag3143x Monday, October 3, 2016 4:48 PM
    Friday, September 30, 2016 1:30 AM
  • I am, of course. The auth issue on RDP is extremely annoying BTW.

    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Friday, September 30, 2016 6:25 AM
  • A question proposed as an answer? I am confused ...

    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Friday, September 30, 2016 3:53 PM
  • Zig Zag can you unmark this as an answer?  I'm trying to figure out what got changed in 1607 to now trigger this.

    If Enterprise is now needed, I can't find a document stating that this is now enforced in 1607.

    Friday, September 30, 2016 4:10 PM
  • It was not marked as an answer merely proposed.

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Friday, September 30, 2016 5:23 PM
  • I don't want to bother, but it was a question, not an answer ...

    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Friday, September 30, 2016 5:44 PM
  • It shouldn't be a proposed answer either.  I merely was double checking that all of these folks reporting this recently upgraded to 1607.  However that doesn't answer the root question -- why suddenly in 1607 when both 1511 and RTM didn't complain, does this error message now show up?

    I was merely gathering data points, that's all, not answering anything.

    Friday, September 30, 2016 6:48 PM
  • ZigZag, please I am requesting that you unmark my post as a proposed answer.  It is not.  I have an email into Microsoft to understand if 1607 has a change in behavior in regards to NFS.
    Monday, October 3, 2016 4:01 PM
  • Done

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Monday, October 3, 2016 4:53 PM
  • Thank you!
    Monday, October 3, 2016 5:05 PM
  • Client for NFS was added to the Professional SKU in Windows 10 Anniversary Update (1607). 

    Previously it was included only in Enterprise / Ultimate SKUs.

    We've identified a bug in that change causing it not to function on Pro SKU,  which we'll be fixing and releasing in a future Windows Update package.

    Sorry for the inconvenience.

    Regards,

    Tom Jolly

    ---

    Group Software Engineering Manager

    Windows Server High Availability & Storage team


    Monday, October 3, 2016 10:00 PM
  • Could you please confirm the authentication issues I see, will be resolved as well?

    Briefly the problem is the following:

    • two Win10 machines (one is joined to a domain, the other is not)
    • the one not joined tries to connect via rdp  to the other and most of the times it works (credentials are cached)
    • Sometimes the connection is refused and I have to re-type the credentials.
    • If I open the event viewer I can see the message "Client for NFS is not licensed for use on this version of Windows" at the same date/time.
    • If I do not type the credentials and retry later (maybe after a reboot) it mostly work, therefore it is not a cache-expiring problem.

    Thank you


    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Tuesday, October 4, 2016 6:27 AM
  • Can you advise please what the Event ID of this event you are seeing is please? And also which event log? It would be interesting to see if this occurs on other Windows 10 Anniversary builds.

    Is there any issue \ on going problem you are investigating that prompting you to look in the Event Viewer?

    sorry for the delayed response. I am seeing the error in the system logs

    Log Name:      System
    Source:        NfsRdr
    Date:          10/4/2016 3:52:05 PM
    Event ID:      16385
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ChrisSolomon-PC
    Description:
     Client for NFS is not licensed for use on this version of Windows.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="NfsRdr" />
        <EventID Qualifiers="49152">16385</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-10-04T22:52:05.364468900Z" />
        <EventRecordID>588699</EventRecordID>
        <Channel>System</Channel>
        <Computer>ChrisSolomon-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>???</Data>
        <Binary>000008000200300000000000014000C0000000006A0200C0000000000000000000000000000000006B0100006A0200C0</Binary>
      </EventData>
    </Event>

    I was checking for another issue (RDP related) when I noticed this issue. (same RDP issue as rafaelle I suspect)

    Issue is still present on 14393.222

    • Edited by Cybot Tuesday, October 4, 2016 11:43 PM
    Tuesday, October 4, 2016 11:36 PM
  • Samba as all knows in IT departments is very bad to use because of using netbios, so let's try to not advice to use that please ^^
    Thursday, October 20, 2016 9:36 AM
  • Guys can you please on various forums of yours relink this answers because I've been searching for this post for 48 hours.... and I guess that a lot of people are waiting for yo ufor an answer since we are 20/10 and still no fix.
    Thursday, October 20, 2016 9:41 AM
  • same here and for everyone on reddit, answer.microsoft etc .... 

    RDP shouldn't be affected by this issue. if you have a problem with rdp I don't think it comes from NFS but still nfs stay a problem

    Thursday, October 20, 2016 9:43 AM
  • My thoughts:

    1. The problem happens even if you don't use linux in your network or the windows bash

    2. Now that companies live in etherogeneous environments, it is necessary to remove complexity and let the users access resources easily. Everything that stay complex will die. As a developer I know how hard this could be.

    3. I literally hate to see the event log with misterious entries that can be read only from the developers who created it. Writing software is complex but it is always possible to make things usable, otherwise it is a huge fail.



    Raffaele Rialdi [MVP] My articles and videos: http://www.iamraf.net Italian blog: http://blogs.ugidotnet.org/raffaele

    Thursday, October 20, 2016 9:50 AM
  • Client for NFS was added to the Professional SKU in Windows 10 Anniversary Update (1607). 

    Previously it was included only in Enterprise / Ultimate SKUs.

    We've identified a bug in that change causing it not to function on Pro SKU,  which we'll be fixing and releasing in a future Windows Update package.

    Sorry for the inconvenience.

    Regards,

    Tom Jolly

    ---

    Group Software Engineering Manager

    Windows Server High Availability & Storage team


    Any news on this? I've 13101 error  reported in last hour. It is using machine resources to write these errors.

    Thanks,

    Paul


    ~Paul

    Thursday, October 27, 2016 7:30 PM
  • I have just updated to Windows 10 Pro 64bit, Version 1607 (OS Build 14393.447) and this Windows 10 feature bug have not been fixed yet.

    In the meantime, I made Windows feedback and got confirmation on it having same issue on another 5 Windows 10 Pro computers.

    So this Windows 10 Post Anniversary Edition feature actually does not work (Client for NTFS) as Windows 10 Pro feature, even it is installed.

    Command I sued to try it out was: (in cmd shell)
    mount -o anon \\10.42.0.1\export\home\share2 N:
    and get answer:
    ERROR - Unsupported Windows version

    I suppose this is about NFS client for Windows 10 Pro have not been actually recompiled to actually work with Windows 10 Pro as feature so it doesn't work even it is advertised as working.

    Tried to go through Voice contact technical support and got till the multiple phone transfers and then my call was cutoff.

    Thursday, November 10, 2016 12:39 PM
  • Can we have a timeframe, please? This was one of the most exciting features for us in the Anniversary Update.
    • Edited by Guy Paddock Friday, December 2, 2016 2:48 AM My response was a little harsh...
    • Proposed as answer by vigilian Saturday, December 17, 2016 2:21 PM
    • Unproposed as answer by vigilian Saturday, December 17, 2016 2:22 PM
    Friday, December 2, 2016 2:45 AM
  • Samba as all knows in IT departments is very bad to use because of using netbios, so let's try to not advice to use that please ^^

    Yours is the only message I see that mentions it.

    File Systems can be mounted as NFS without samba, of course.  :)

    Any idea when this might be fixed?  I just bought my laptop at the end of October and typically use it less than 2 hours per day, yet have event 16385 in the System log over 62,000 times.

    Thursday, December 8, 2016 1:57 PM
  • I also have the same error message, " Client for NFS is not licensed for use on this version of Windows." using Windows 10 Pro anniversary edition. I have 2 mapped drives pointing to a QNAP NAS which runs on Linux. Access to the shares works fine despite the error message in the System event log. Is the error message even valid? Are others on this thread unable to access the NFS share(s)?
    • Proposed as answer by vigilian Saturday, December 17, 2016 2:22 PM
    • Unproposed as answer by vigilian Saturday, December 17, 2016 2:22 PM
    Friday, December 9, 2016 6:47 AM
  • I noticed that on my laptop Windows 10 Pro 64 bit version 1607 that there is an NFS feature listed to turn on and off but in another Desktop PC with Windows 10 Pro 64 bit version 1511 build 10586.679 there is no NFS feature listed in the "Turn Windows features on or off" menu. What the heck is going on at Microsoft removing features and support for things like Windows Media Center and NFS, etc.  Going down hill with those decisions IMO.

    I also noticed that the 1607 version has an extra SMB on/off feature that the 1511 version does not have.

    • Edited by surfnbuy Wednesday, December 14, 2016 1:53 PM
    • Proposed as answer by vigilian Saturday, December 17, 2016 2:22 PM
    • Unproposed as answer by vigilian Saturday, December 17, 2016 2:22 PM
    Wednesday, December 14, 2016 1:51 PM
  • GOOD NEWS PEOPLE! NFS CLIENT FOR WINDOWS 10 PRO IS FINALLY AL IVE!!!!

    This thread is not to ask questions but to acquire knowledge about a specific subject.

     

    So with your latest windows 10 PRO 14393.576, your nfs client is finally operational in comparaison with before like shown in this thread.

     

    Don't forget to install the nfs client from Windows features (will show some images later). To mount the share you can do it from Explorer like you would do with samba share so \\x.x.x.x\share or you can do it with from command line with mount  x.x.x.x:/share or \\x.x.x.x\share drive:

     

    Some things you should know.

    User permission won't really work out of the box like to would be in Linux. So it is very probable that Explorer accept to map the share but won't accept to enter the share. So begin to set up a share where everybody will be able to write and read. So with chmod -R 777.

    I guess that the nfs client is not totally finished.

    Software like acronistrue won't be able to enter the share either because it seems that a whole extended interfaces features have been added to Explorer so guess is that software have to be coded to implement those  yet.

    Don't be afraid of the big latency that Explorer seems to have in comparison of Linux, again the implementation is not yet perfect.

     

     

    If anyone else have some new knowledge based on experience, please share.

    • Proposed as answer by vigilian Saturday, December 17, 2016 2:24 PM
    Saturday, December 17, 2016 2:24 PM
  • I can confirm it works now mounting NFS share in Windows 10 Pro now , after update to version 14393.576,
    both with mount command (mount -o anon \\10.42.0.1\export\home\share2 N: )
    and with entering "\10.42.0.1\export\home\share2" in explorer address.

    Yet to try out with some security and still haven't measure speed,
    but for work in progress it is ok and at least it is working now. :)

    I am updating Feedback Hub case, to reflect new NFS client  functionality started working in Windows 10 Pro.

    Only thing I don't get is why I can't see Mounted NFS folder as drive letter as a user, if I mount NFS drive with the administrator account.
    It is probably per-user mount and would need setting for every user that wants to use NFS share? ...
    • Edited by Tower224 Thursday, January 5, 2017 11:02 AM
    Thursday, January 5, 2017 10:52 AM
  • If you mount NFS shares from an admin command prompt, the mount will not show up in explorer for standard users because of user rights. Unmount the share and remount it, either from explorer or from an ordinary command prompt. Admin rights are not required for NFS mounts.

    Sunday, March 19, 2017 10:56 PM