Pablo Galindo Salgado <pablogsal@gmail.com> added the comment: Isn't this saying that LongPathsEnabled is a value on the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem? ---------- nosy: +pablogsal _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue34406> _______________________________________

Ammar Askar <ammar@ammaraskar.com> added the comment: For what its worth, window's reg command also makes a distinction between the registry key and value: C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework\Enable64Bit ERROR: The system was unable to find the specified registry key or value. C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework /V Enable64Bit HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework Enable64Bit REG_DWORD 0x1 Maybe it can just be phrased as something like, "set the registry value LongPathsEnabled in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem" ---------- nosy: +ammar2 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue34406> _______________________________________

Steve Dower <steve.dower@python.org> added the comment: Yeah, it definitely shouldn't be a backslash there. The @ isn't my invention, but last time someone questioned it I couldn't find any public examples, so it may be an internal Microsoft thing? I'm not totally attached to it, but if you want to fix it it'll need to be written out in full that it's "a value named X of type Y". ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue34406> _______________________________________