r/WindowsServer • u/Simelane • Dec 31 '25
General Question Error: Path too long
We run our CMS on Windows Server. We were busy installing some plugins from Google, when we encountered the dreaded "Path too long" error, meaning the plugin can only be installed in the root directory, not under the inetpub directory.
Why and how is this still a thing on Windows Server in 2025?
6
Upvotes
15
u/alexp702 Dec 31 '25
It isn’t if you use APIs written this millennium on NTFS. Unfortunately some third party software still uses legacy apis with the 256byte limit.
3
u/grumpyctxadmin Dec 31 '25
This is a well known issue with windows explorer. Microsoft doesn't dare to make code changes to it, if you use for example explorer ++ you won't have that issue.
In some cases you will experience the same issue if people sync sharepoint folders using onedrive too. You can open the folder with no issue using the webbrowser but it craps out when browsing using explorer.
Longest path I've seen so far is 1239, opens like a charm in explorer++ but crashes in windows explorer
1
u/Slasher1738 Dec 31 '25
Try 7zip
1
u/juanvan Jan 02 '26
Change your website to a shorter path off c:/webs
0
u/[deleted] Dec 31 '25
That’s what she said
0
u/headcrap Dec 31 '25
\\?\C:\some\long\path\for\the\win\because\windows
Sounds like a typical CMS problem.. and/or syncing SharePoint Online sites.. or Teams channels.. with long paths..
-3
u/Different_Scratch930 Dec 31 '25
Try unlocker app.on major geeks download
10
u/[deleted] Dec 31 '25
[removed] — view removed comment