Windows 10: Windows Server Long Path Name Support 2016 vs 2019

Discus and support Windows Server Long Path Name Support 2016 vs 2019 in Windows 10 Network and Sharing to solve the problem; I have an issue with extracting a tar file with relatively long paths ~120+ chars into a folder structure that is also relatively long 130 chars, as... Discussion in 'Windows 10 Network and Sharing' started by jfbradfo, Apr 19, 2021.

  1. jfbradfo Win User

    Windows Server Long Path Name Support 2016 vs 2019


    [COLOR=rgba85, 85, 85, 1]I have an issue with extracting a tar file with relatively long paths ~120+ chars into a folder structure that is also relatively long 130 chars, as some of the file names are long enough they exceed the 260 character limit for path names. We have enabled the Enable Win32 long paths policy, as well as ensured that the LongPathsEnabled registry value is set to 1, and the servers were rebooted after the change. I'm using 7-Zip v19.00 to do the extracts and have used both TAR and ZIP files to ensure that the format doesn't play a part.[/COLOR]


    [COLOR=rgba85, 85, 85, 1]On a Windows Server 2016 instance, the extract works correctly with no errors. However, on a Windows Server 2019 instance, using the same TAR and ZIP files and the same target path to extract 130 chars, several files fail to extract, apparently because the paths are longer than 260 characters. We validated this by shortening the extract target path slightly, which allowed all files to extract without error.[/COLOR]


    [COLOR=rgba85, 85, 85, 1]We are able to make this work with the 7-Zip GUI and with WinZip, but the command line fails consistently on Server 2019. [/COLOR]


    The one server configuration difference we noticed was that the Server 2016 box has .NET 4.7 and the Server 2019 box has .NET 4.7.2.


    [COLOR=rgba85, 85, 85, 1]What differences in long path handling have we missed in Server 2019 vs 2016?[/COLOR]

    [COLOR=rgba85, 85, 85, 1]
    Thanks in advance![/COLOR]

    :)
     
    jfbradfo, Apr 19, 2021
    #1
  2. Fatmasari Win User

    Activate RDS CAL 2019 on Windows Server 2016

    Dear Microsoft Support,



    We recently purchased Windows Server RDS CAL 2019.

    When we tried to install Windows Server RDS CAL 2019 into Windows Server 2016, it shows the license is not recognized and couldn’t install.



    My questions are :

    1. Can’t Windows RDS CAL 2019 be installed in Windows Server 2016? If can, how?
    2. Is there any way to downgrade RDS CAL from 2019 to 2016 version?

    Thanks,
     
    Fatmasari, Apr 19, 2021
    #2
  3. Ahhzz Win User
    Office 2019

    Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

    Microsoft Office 2019 will only work on Windows 10

    https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

    Spoiler Office 2019
    Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

    • Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
    • Office 2019 apps will be supported on:
      • Any supported Windows 10 SAC release
      • Windows 10 Enterprise LTSC 2018
      • The next LTSC release of Windows Server
    • The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.
     
    Ahhzz, Apr 19, 2021
    #3
  4. Windows Server Long Path Name Support 2016 vs 2019

    Exchange Support For Windows Server 2016


    Exchange Support For Windows Server 2016

    Source: https://blogs.technet.microsoft.com/...s-server-2016/
     
    Cluster Head, Apr 19, 2021
    #4
Thema:

Windows Server Long Path Name Support 2016 vs 2019

Loading...
  1. Windows Server Long Path Name Support 2016 vs 2019 - Similar Threads - Server Long Path

  2. Can't delete folders with long path names

    in Windows 10 Network and Sharing
    Can't delete folders with long path names: I copied some folders onto a work computer into the "My Documents" directory.I didn't realize it but the directory is actually connected to OneDrive, as in it synchronizes to it. The actual folder path is something like:"C:\Users\FirstName.LastName\OneDrive - Company with a...
  3. Enabling Long Path to Allow Files with Long Names in Windows 10 File Explorer

    in Windows 10 Customization
    Enabling Long Path to Allow Files with Long Names in Windows 10 File Explorer: I’ve done the fixes suggested by the Microsoft Community: Setting the registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled Type: REG_DWORD to 1 Adding Enable Win32 long paths in the Local Computer Policy: Computer...
  4. Upgrade Windows server 2016 OEM license to server 2019 Retail license

    in Windows 10 Updates and Activation
    Upgrade Windows server 2016 OEM license to server 2019 Retail license: If I have an Windows server 2016 OEM license embedded in BIOS, but want to upgrade to a Windows server 2019 license, can I buy a retail license for Windows server 2019 and activate that? Will there be any problems due to the OEM license embedded in BIOS?...
  5. Long path names on Windows 10 Home.

    in Windows 10 Network and Sharing
    Long path names on Windows 10 Home.: Does Windows 10 Home support long path names? Simply changing the LongPathsEnabled to 1 and rebooting doesn't work. I need to work with long paths in Windows Word and I have Word 365....
  6. Long Path Enabled

    in Windows 10 Network and Sharing
    Long Path Enabled: Hi Team, We have been trying to increase the long path value as per the documents from Microsoft. We can create maximum of 20 sub folders beyond that we cannot go. So could you please help me in getting this sorted out. thanks. Sriram Krishnamoorthy...
  7. PSEXEC on windows 7 Vs windows 10, 2016, 2019

    in Windows 10 Customization
    PSEXEC on windows 7 Vs windows 10, 2016, 2019: Hi, when we execute PSEXEC on windows 7 it able to return output of size 21 mb. When execute PSEXEC on Windows 2016, 2019 or Windows 10 it able to return output only till 70KB. Is there any limitation on latest operating System....
  8. File History and Long Path Names

    in Windows 10 Backup and Restore
    File History and Long Path Names: Shawn - or anybody that knows... Can you tell me if FH manifest is Long Path aware? (Sorry - All the FH .manifest files I can find are binary, not text) I am trying to help a dyslexic user with memory problems (memory as in "brain", not "bytes") Her system is Win 10 Home,...
  9. File History and Long Path Names

    in Windows 10 Customization
    File History and Long Path Names: Shawn - or anybody that knows... Can you tell me if FH manifest is Long Path aware? (Sorry - All the FH .manifest files I can find are binary, not text) I am trying to help a dyslexic user with memory problems (memory as in "brain", not "bytes") Her system is Win 10 Home,...
  10. Exchange Support For Windows Server 2016

    in Windows 10 News
    Exchange Support For Windows Server 2016: Exchange Support For Windows Server 2016 Windows Server 2016 Technical Preview 5 is available from the TechNet Evaluation Centre. While that’s great to download the bits and get the OS running in your test lab, please do not update the OS on your Exchange servers right...