Long file path issues in Windows 11 Pro with Microsoft VS Code and File Explorer

Anonymous
2022-05-04T22:27:47+00:00

I spent way too long debugging a compile error in MS VS Code (64bit version 1.66.2). It would fail with 'file not found' or 'unable to access file' errors. The workspace is located in "C:\Users\UserName\Documents\My Workspaces\firmware", with several levels of nested source folders below.

Initially, I got several linking errors due to Controlled Folder Access protection using the Ransomware protection built-in to Windows Security. I whitelisted ar.exe and as. exe, but the errors persisted. I even turned off Ransomware protection. Seeing a thread online about long file paths reminded me I hadn't enabled that on Windows 11 yet (fresh install), so I changed the following settings and rebooted the PC:
Registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled set to 1.

Group Policy: System "Configuration>Administrative Templates>System>Filesystem>Enable Win32 long paths" enabled.

About that time I noticed an issue with not being able to delete or rename files on an SMB share that were in a deep path. If I went to the other system and moved them up a few folders I was again able to rename the files.

Both of these scenarios work fine from my Windows 10 Pro PC. My Windows 11 Pro PC is a fresh install (Version 21H2 Build 22000.613).

So I believe Windows 11 isn't respecting my Long Paths settings. As a final test, I moved my VS Code Workspace folder to system drive root (C:\firmware) and it compiled without error.

I've seen other questions on here about Windows 11 path length issues that were brushed away because they were encountered using non-Microsoft 3rd Party software, but this is all built-in File Explorer and Microsoft's own VS Code product.

My question is, how do I actually allow long file paths in Windows 11 Pro?

Windows for home | Windows 11 | Files, folders, and storage

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

77 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-22T10:33:52+00:00

    The above script worked for me on my Windows 11 Pro 22H2.

    But I am still not able to close this repository due to Long path errors https://github.com/kiegroup/drools-wb

    Used the same two steps enabled group policy and then LongPathsEnabled to 1.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-20T05:03:22+00:00

    This thread has just broken me...... I have recently deployed 130 W11 laptops and migrated to Sharepoint Online. We are hitting this issue all over the place (after the business decided to change their file structure).

    If you get any updates to this I am super keen to hear about them as I am currently scratching my head on how to resolve this problem.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-01-16T17:22:42+00:00

    Ok. Final update from my trouble ticket with Microsoft:

    "Hope you are doing well,

    We have checked the same on our Windows 11 environment and unfortunately due to product limitations the long path enabled does work on the scenario

    that you have been facing.

    You can post the same on feedback hub, so that next time when a patch will be released, this feature may get an update.

    You can find the feedback hub, by clicking on the start menu and type feedback hub and select the category accordingly."

    So, the first couple of times I read that, I thought it said that they reproduced the issue. But, reading it again I think it says the opposite.

    Good luck finding a feedback hub issue on long paths that has a lot of up votes. LOL, they're probably using bing as their search engine🤦‍♀️

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-01-16T00:32:20+00:00

    You had me worried for a moment there. I just checked on my Window 10 box. It's running latest: 22H2 build 19045.2486.

    I can still create deep folders and read/write files in those deep folders. All via ISE powershell.

    Granted: Windows explorer is not long path enabled. So, you're right: you cannot use windows explorer for doing useful stuff in those deep folders.

    My own applications are long path enabled via the manifest I build them with. Was going to paste a sample manifest here, but it won't let me. It's pretty easy to google for a sample manifest to enable long path aware applications. The file APIs are somewhat limited for the long path stuff, but I managed to port all my file i/o accesses to the long path APIs.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-14T08:39:59+00:00

    I'm amazed this is broken, even on Windows 11 pro 22H2

    It worked fine on my last Windows 10 pro machine

    Setting with regedit: BROKEN

    Setting with group policy: BROKEN

    Setting with M365 configuration: BROKEN

    It should be on by default!

    And it should work...

    Recently it's been broken on W10 as well though.

    Not quite the same as W11, since apps can apparently still write the files (unlike W11, where my C# app just died when it tried to write that file).

    But WinExplorer on my W10 (Home) laptop ... naaaah ... not happening anymore. Only have RegEdit for that one, no GPEdit.

    There it's broken in an annoying way too. The file is there, I can literally see it ... but if you try to rename, it won't work ... it won't let you type any characters anymore to 'add' and the 'save' just doesn't go through even if you've removed characters.
    Work around there is to then move the file to the root of some HDD path, rename it there & move it back.

    Anyway, max 260 characters is truly 80's level shizzle dudes, so it's a pain that such a basic feature doesn't work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments