Path too long exception on Windows install #5109
Comments
|
Refs #4583 (comment). |
50Wliu
added
bug
windows
kevinsawicki
changed the title
kevinsawicki
changed the title
|
Same issue on my machine Windows 8.1 x64 |
|
I also get this issue. |
|
I am too facing the same issue when installing Atom: Program: Starting Squirrel Updater: --install . |
|
Same issue on Windows 7 Enterprise x64 |
|
I'm hitting this as well - only work around is to install an older version. |
|
This should be fixed once #5175 is released-there is no need to add additional logs. |
|
Once it gets merged, you'll be able to get the fix if you build Atom youself. Otherwise, it'll be in the next release after it gets merged (probably by 0.177.0). |
|
It works great now in version 0.175.0. Thanks guys! |
|
I'm seeing this issue again with 0.176.0. Can anyone confirm? |
|
@zephraph what is the path it is complaining about? |
|
Worked for me: |
|
I've included the relevant part of the log below. I suspect it's not Atom's installer but rather my company's antivirus that's messing things up. I wouldn't open this up again unless more people report the same issue. |
|
@zephraph I have run into the same issue just today |
|
Just downloaded the Windows Installer and I get the same error: |
|
One way around this is to use atom-windows.zip distribution from https://github.com/atom/atom/releases. |
|
Atom needs to move to npm 3.0 and this will go away. |
|
For now, I'm using atom-windows.zip, thanks @gliviu |
|
Still an issue, solved using steps given by @Indomitable above. |
Done! (edit: reopening until Atom is running the updated apm version) |
|
at last! |
|
Out of the box, the executable fails for me with the same error about long paths. I was using the portable version (zip) until now, but found the "extract the exe and run |
|
Install is also failing for me. Win 10 / Atom 1.11.2 / exe installer. Any chance to reopen this issue so I don't have to hack the install? Thanks. If it helps diagnose this, my user name is 30 chars long - a local account on a domain-joined machine, so the account name includes the machine name.
|
|
Hi, although this is closed in case it helps anyone: we're experimenting with issue duplication detection algorithms and found that the following are (along with #10117 which is already logged duplicate) duplicates of this issue as well: |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
and others
I download AtomSetup.exe
I run it as an administrator
I agree there are probably curious permission setups and my user directory is mapped to a central server.
I get no choices where to install from the installer.
Other applications have worked
I get the error dialog. Here's the log.
I can't alter where it tries to install, nor am I clear why the install path is too long.
Chocolatey didn't install 174.1 either - there's clearly something pathological in my setup.
Any chance of being able to configure where it installs to and from?
============SquirrelSetup.log============
Program: Starting Squirrel Updater: --install .
Program: Starting install, writing to C:\Users\john.drummond\AppData\Local\SquirrelTemp
CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\john.drummond\AppData\Local\atom\packages\RELEASES'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Squirrel.Utility.LoadLocalReleases(String localReleaseFile)
at Squirrel.UpdateManager.CheckForUpdateImpl.d__28.MoveNext()
CheckForUpdateImpl: Reading RELEASES file from C:\Users\john.drummond\AppData\Local\SquirrelTemp
CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch
ApplyReleasesImpl: Writing files to app directory: C:\Users\john.drummond\AppData\Local\atom\app-0.174.0
IEnableLogger: Failed to write file: C:\Users\john.drummond\AppData\Local\atom\app-0.174.0: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.PathHelper.GetFullPathName()
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at NuGet.PhysicalPackageFile.GetStream()
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass8b.b__8a()
at Squirrel.Utility.LogIfThrows(IFullLogger This, LogLevel level, String message, Action block)
IEnableLogger: Failed to install package to app dir: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.PathHelper.GetFullPathName()
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at NuGet.PhysicalPackageFile.GetStream()
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass8b.b__8a()
at Squirrel.Utility.LogIfThrows(IFullLogger This, LogLevel level, String message, Action block)
at Squirrel.UpdateManager.ApplyReleasesImpl.copyFileToLocation(FileSystemInfo target, IPackageFile x)
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass84.b__80(IPackageFile x)
at System.Collections.Generic.List
1.ForEach(Action1 action)at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass84.b__7f()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.d__86.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.Utility.d__4b`1.MoveNext()
The text was updated successfully, but these errors were encountered: