Update atom on windows

Installing Atom on Windows just got a whole lot easier with the new Atom Windows installer that is now available from atom.io.

Using the new Atom Windows installer also sets up Atom to automatically update whenever a new release is published just like the Mac version of Atom.

If this is your first time using Atom on Windows, you can head on over to atom.io and click the Download Windows Installer button to get started.

If you’ve previously installed Atom on Windows using Chocolatey, you should follow the instructions below to migrate to the new Windows installer.

Uninstalling the Chocolatey Version of Atom

When Atom on Windows first shipped the recommended installation flow was to install Atom via Chocolatey. So if you’ve previously installed Atom using Chocolatey you should follow these next two steps to completely uninstall the Chocolatey version of Atom.

• Run cup Atom to upgrade to the latest Atom release. This is required since previous versions of the Atom Chocolatey package did not uninstall correctly
• Run cuninst Atom to uninstall the Chocolatey version of Atom. This will not delete any of your installed packages or Atom config files

Using the New Atom Windows Installer

• Go to atom.io
• Click the Download Windows Installer button
• Run the downloaded AtomSetup.exe file
• Atom will launch once the installation completes
• Atom will automatically update when a new version is available

The new Atom Windows installer sets up Atom just like the Chocolatey package did.

• An Atom desktop shortcut is added
• An Open With Atom context menu is added to the Explorer for selected files and folders
• atom and apm are added to the Path environment variable so they can be run from the Command Prompt or PowerShell.

Squirrel For Windows

Since Atom’s first release last February it has used the open source Squirrel for Mac library for handling automatic app updates.

Until recently there wasn’t a Windows version available which is why Chocolatey was originally chosen to do the heavy-lifting. Now, thanks to @paulcbetts and many other awesome contributors, there is a version of Squirrel for Windows that not only does automatic updates but also makes creating installers for any app incredibly easy.

If you are developing an Atom Shell app you can use the recently released Atom Shell installer Grunt plugin to create a Windows installer for your app. You can take a look at how how Atom configures its Windows installer build here.

Thanks

A big thanks to everyone who helped test out early versions of both the Atom Windows installer and Squirrel for Windows.

If you have any issues with the new Windows installer or automatic updates please open an issue on the atom/atom repository.

Have feedback on this post? Let @AtomEditor know on Twitter.

Update atom on windows

Last year I joined the Atom team with the goal of making Atom a better experience on Windows and thought it would be worth highlighting some of our work so far as well as a few of the things new in Atom 1.14 (currently in beta).

If you haven’t tried Atom on Windows in a while or were just plain heads-down on your projects here’s some Windows-specific improvements you may have missed.

64-bit

In 1.14 two architectures of Atom are now available for Windows. The existing 32-bit (ia32/x86) version and the shiny new 64-bit (amd64/x64) version.

The new version leaves the 32-bit resource limits behind and can take advantage of faster 64-bit instructions in lower layers such as node, v8 and native modules.

In order to ensure compatibility current installations will not switch to a new architecture without intervention — you’ll need to grab the 64-bit version yourself. Visitors to Atom.io will be offered x64 versions from 1.14 onwards if they are on an x64 system.

Your settings and extensions will be preserved when switching although there may be a delay while apm rebuilds native modules for any packages you have installed. Let us know if you run into any issues!

File association

Atom’s auto-update mechanism happens transparently behind the scenes without services running full-time to make that happen. This does however mean that the Atom executable path changes between revisions so files you manually associated with atom.exe would break.

Now however Atom registers itself as a file handler automatically meaning it shows up right away in Open With… and you can just chose it from there. When Atom upgrades itself it will rewrite these associations for you so no more broken links. If you want to change this behavior you can turn it off with a single check in the Atom > Settings > System pane. Once associated you’ll see a sparkly new Atom document icon for the file.

Also in Atom 1.14 you will find an atom.exe stub one level up in the file system that never moves! You can point apps that don’t support Windows file associations like Cyberduck here as an alternative.

Installation

Installation is often overlooked but can be a real pain if you don’t get it right thanks to the proliferation of malware and the responsive measures from the anti-virus community.

We have improvements to help ensure Atom gets installed correctly on your system including:

• Stronger code signing with sha256, timestamping and a new certificate
• Extract-in-place to prevent on-access scanners interfering with files being moved
• An MSI installer that installs a personal copy of Atom for each user as they sign in
• Better update reliability for pins and shortcuts via Squirrel (the install/update system we use)

Contributing

Using Windows to contribute to Atom was a little harder than it should have been.

The Windows build instructions have been updated with accurate steps on getting started as well as a more comprehensive troubleshooting for scenarios you may run into. You can now even use the much smaller “C++ Build Tools” instead of a full Visual Studio installation.

Atom’s test suite now runs and passes on Windows 64-bit builds so just type script\test to ensure no regressions (or atom —test if contributing to an Atom package). Debugging inside Developer Tools you’ll see the sources navigator is no longer jumbled (Windows backslashes in sourcemaps were confusing it).

We also added a new section to the Atom Flight Manual called Cross-Platform Compatibility that gives some guidance on how to make sure your code works well across platforms.

Portable mode

The portable mode was finally documented and some important changes made in the forthcoming 1.14 release;

• The ATOM_HOME environment variable no longer prevents portable mode
• The —portable argument was removed as it caused confusion (it copied your .atom folder to be portable not actually forced portable mode)

Getting up and running with a portable version is simple:

1. Download the atom-windows.zip and extract it where you want it
2. Create a .atom folder in the folder above atom.exe where your config will live (or copy your existing one from %userprofile%)
3. Launch Atom from the folder!

In 1.14 you can also create an electronUserData folder in there and have Atom store the Electron data there instead of in your roaming appdata. (where DevTools console history etc. lives)

Some have asked for Atom to use the portable drives even for temporary and cache files. While we don’t recommend it as these drives are slower than modern SSDs you can put a simple .cmd file on your drive to achieve it and launch atom via that:

Setting TEMP is necessary to ensure Atom and its various dependencies store temporary files in the right place.

Shell extension option

We heard from some passionate users that they didn’t like the Open with Atom context-menu that appeared throughout Explorer for every single file and folder.

There was no performance hit, it was simply an icon and label in the registry. But it’s clutter if you don’t use it, and redundant now that we have proper file associations working, so now off by default.

If you want to switch it on you can head to our new System settings pane shown above and check a box to get it back for either files or folders. If you’ve had Atom installed a while it is still on for you so you can also head into System settings to turn it off.

Taskbar enhancements

The taskbar on Windows is capable of supporting menu options and in 1.14 you’ll see a New Window task as well as recent files and integration with our new reopen projects feature either of which you can pin to for fast access.

Package installation

Sometimes installing an Atom package doesn’t succeed for any number of reasons. We’ve made improvements that help including;

• Detecting git.exe from GitHub Desktop when git isn’t on your path
• Bypassing auto-run scripts when we shell out to avoid parsing errors
• Supporting “C++ Build Tools” for native dependencies (instead of Visual Studio)

Little extras

Of course there are many other improvements and tweaks this year that benefit Windows users — some exclusively and some cross-platform including;

• International AltGr keyboard support
• Path length improvements with npm3
• Simultaneous use of Atom by multiple signed-in users
• Atom file icon for associations in the Windows style
• CP 850 support (DOS codepage in Europe)
• No command-line noise when launching atom.exe directly
• Improved C# syntax highlighting
• Better handling of spaces in paths
• Improved command-line launching from cygwin, Git Bash, and msys
• File and Selection menus accessible with alt — f and alt — s

Share and Enjoy!

Have feedback on this post? Let @AtomEditor know on Twitter.

A hackable text editor for the 21st Century

Teletype for Atom

Great things happen when developers work together—from teaching and sharing knowledge to building better software. Teletype for Atom makes collaborating on code just as easy as it is to code alone, right from your editor.

Share your workspace and edit code together in real time. To start collaborating, open Teletype in Atom and install the package.

GitHub for Atom

A text editor is at the core of a developer’s toolbox, but it doesn’t usually work alone. Work with Git and GitHub directly from Atom with the GitHub package.

Create new branches, stage and commit, push and pull, resolve merge conflicts, view pull requests and more—all from within your editor. The GitHub package is already bundled with Atom, so you’re ready to go!

Everything you would expect

Cross-platform editing

Atom works across operating systems. Use it on OS X, Windows, or Linux.

Built-in package manager

Search for and install new packages or create your own right from Atom.

Smart autocompletion

Atom helps you write code faster with a smart and flexible autocomplete.

File system browser

Easily browse and open a single file, a whole project, or multiple projects in one window.

Multiple panes

Split your Atom interface into multiple panes to compare and edit code across files.

Find and replace

Find, preview, and replace text as you type in a file or across all your projects.

Make it your editor

Packages

Choose from thousands of open source packages that add new features and functionality to Atom, or build a package from scratch and publish it for everyone else to use.

Themes

Atom comes pre-installed with four UI and eight syntax themes in both dark and light colors. Can’t find what you’re looking for? Install themes created by the Atom community or create your own.

Customization

It’s easy to customize and style Atom. Tweak the look and feel of your UI with CSS/Less, and add major features with HTML and JavaScript.

Under the hood

Atom is a desktop application built with HTML, JavaScript, CSS, and Node.js integration. It runs on Electron, a framework for building cross platform apps using web technologies.

Open source

Atom is open source. Be part of the Atom community or help improve your favorite text editor.

Atom installation and update error on Windows #5767

Comments

equinusocio commented Feb 26, 2015

Hi all,
when i try to install Atom on my Windows 8.1 machine i get this error.

And the log say:

After this error, i’ve found the full Atom app (0.182.0) inside the folder AppData\Local\atom\app-0.182.0. I’ve tried to run Atom.exe inside this folder and the app start regularly and i have linked the .exe file to desktop. The directory \bin does not exist in AppData\Local\atom

The text was updated successfully, but these errors were encountered:

Sigmanor commented Feb 26, 2015

same here, Windows 8.1

50Wliu commented Feb 26, 2015

batjko commented Feb 26, 2015

anaisbetts commented Feb 26, 2015

Is this happening all the time? Usually this happens when you try to uninstall then immediately reinstall, but atom.exe is still hanging around

DavidA2014 commented Feb 27, 2015

I rebooted and repeated the install of 0.184. Again I saw the ‘Install has failed’ message box shown in equinusocio’s post above.

anaisbetts commented Feb 27, 2015

Do you have an Antivirus product? Does it suck?

andischerer commented Feb 27, 2015

got the same Problem with the same logmessages. After killing the hole «%LOCALAPPDATA%\Temp» folder atom installs successfully.

basarat commented Feb 28, 2015

Getting the same error. Only since yesterday.

basarat commented Feb 28, 2015

The following worked:

Delete the whole of %LOCALAPPDATA%\Temp

vgturtle127 commented Feb 28, 2015

Actually, I got the same error when I tried to install on Windows 7. Have no AV running, no other processes open, no firewall, nothing.

Using the zipped version worked fine though, so the installer is the problem.

I also tried it on my Windows 8 PC, with Windows Defender off and it still did that.

Anybody found a fix besides turning AVs off?

equinusocio commented Feb 28, 2015

The issue was fixed by purging the %LOCALAPPDATA%\Temp folder. In my temp folder there were a lot of temporary folders of atom. By deleting this folders the atom installer run ok. Try it.

I think that the installer crash when find others atom temp folders.

andischerer commented Feb 28, 2015

PS: I cam up to the solution of purging %LOCALAPPDATA%\Temp by looking at the callstack. System.IO.Path.InternalGetTempFileName(Boolean checkHost) is failing in case of a thrown IO-Exception.

• The GetTempFileName method will raise an IOException if no unique temporary file name is available. To resolve this error, delete all unneeded temporary files.
• The GetTempFileName method will raise an IOException if it is used to create more than 65535 files without deleting previous temporary files.

batjko commented Feb 28, 2015

Well, I wouldn’t say it’s the solution, since the actual root cause is
unknown and still needs to be looked into.
But at least there’s an easy workaround now.

On Sat, Feb 28, 2015 at 1:23 PM Andreas Scherer notifications@github.com
wrote:

PS: I cam up to the solution of purging %LOCALAPPDATA%\Temp by looking at
the callstack. System.IO.Path.InternalGetTempFileName(Boolean checkHost)
is failing in case of a thrown IO-Exception.

MSDN Note for this Exception
https://msdn.microsoft.com/de-de/library/system.io.path.gettempfilename(v=vs.110).aspx:
The GetTempFileName method will raise an IOException if no unique temporary
file name is available. To resolve this error, delete all unneeded
temporary files.

—
Reply to this email directly or view it on GitHub
#5767 (comment).

anaisbetts commented Mar 1, 2015

Windows Defender should be fine, you do not need to disable it.

vgturtle127 commented Mar 2, 2015

I purged the temp directory and it still doesn’t work.

Not sure what is causing the problem.

The application still works fine as I said, and it works great. The installer just keeps giving me trouble.

basarat commented Mar 2, 2015

@vgturtle127 which version is it. I had trouble with updating before 182. That’s why I uninstalled on this machine but couldn’t install anymore till I cleared my temp directory.

anaisbetts commented Mar 2, 2015

@vgturtle127 Can you paste the actual error you receive? A lot of people on these threads are self-diagnosing «the same error» when it’s not actually the case

Trudko commented Mar 2, 2015

DavidA2014 commented Mar 2, 2015

Deleting the contents of «%LOCALAPPDATA%\Temp» fixed this issue for me.

vgturtle127 commented Mar 2, 2015

I am using the 184 installer now. I tried running CCleaner and restarting my computer. It still doesn’t work.

I thought it might have had something to do with previous Atom data getting in the way, so I used Revo Uninstaller to uninstall Atom and then ran CCleaner, BleachBit, and System Ninja (latest versions) all with Winapp2.ini. I deleted all portable versions of Atom as well. I also deleted all the installers and archives containing Atom. Then I restarted. After that, I re-downloaded the latest installer (184), and tried to re-run it. This time, the installer started and displayed the error message (pictured above) but this time the log was fresh, and it was fine until it started to write data to the AppData directory. That is when it crashed and displayed the error message.

Tried the same on my Windows 8 machine and it did the same thing.

Like I said, the zip folder works fine. Just not the installer.

anaisbetts commented Mar 2, 2015

@vgturtle127 Can you paste the actual error you receive on clean install please? You don’t have to run all those crazy programs to reset Atom, just delete C:\Users\YOURNAME\AppData\Local\atom and C:\Users\YOURNAME\AppData\Local\SquirrelTemp and run the installer again.

vgturtle127 commented Mar 3, 2015

Program: Starting Squirrel Updater: —install .
Program: Starting install, writing to C:\Users\Turtle\AppData\Local\SquirrelTemp

in System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
in System.IO.__Error.WinIOError()

Then I get some more garbage about System.IO, but it crashes after that.

vgturtle127 commented Mar 3, 2015

I also have the crash log if you would rather have that.

[7244:6540:0302/010927:VERBOSE1:crash_service_main.cc(68)] Session start. cmdline is [—reporter-url=http://54.249.141.255:1127/post —application-name=Atom —v=1]
[7244:6540:0302/010927:VERBOSE1:crash_service.cc(133)] window handle is 003F0728
[7244:6540:0302/010927:VERBOSE1:crash_service.cc(279)] pipe name is .\pipe\Atom Crash Service
dumps at C:\Users\Turtle\AppData\Local\Temp\Atom Crashes
[7244:6540:0302/010927:VERBOSE1:crash_service.cc(283)] checkpoint is C:\Users\Turtle\AppData\Local\Temp\Atom Crashes\crash_checkpoint.txt
server is http://54.249.141.255:1127/post
maximum 128 reports/day
reporter is atom-shell-crash-service
[7244:6540:0302/010927:VERBOSE1:crash_service_main.cc(83)] Ready to process crash requests
[7244:8028:0302/010927:VERBOSE1:crash_service.cc(313)] client start. pid = 5184
[7244:8028:0302/010928:VERBOSE1:crash_service.cc(313)] client start. pid = 8016
[4876:1376:0302/010929:VERBOSE1:crash_service_main.cc(68)] Session start. cmdline is [—reporter-url=http://54.249.141.255:1127/post —application-name=Atom —v=1]
[4876:1376:0302/010929:VERBOSE1:crash_service.cc(133)] window handle is 000A0718
[4876:1376:0302/010929:VERBOSE1:crash_service.cc(279)] pipe name is .\pipe\Atom Crash Service
dumps at C:\Users\Turtle\AppData\Local\Temp\Atom Crashes
[4876:1376:0302/010929:VERBOSE1:crash_service.cc(283)] checkpoint is C:\Users\Turtle\AppData\Local\Temp\Atom Crashes\crash_checkpoint.txt
server is http://54.249.141.255:1127/post
maximum 128 reports/day
reporter is atom-shell-crash-service
[4876:1376:0302/010929:ERROR:crash_service.cc(290)] could not start dumper
[7244:1056:0302/010935:VERBOSE1:crash_service.cc(321)] client end. pid = 8016
[7244:1056:0302/010935:VERBOSE1:crash_service.cc(321)] client end. pid = 5184
[7244:1056:0302/010936:VERBOSE1:crash_service.cc(342)] zero clients. exiting
[7244:6540:0302/010936:VERBOSE1:crash_service.cc(480)] session ending..
[7244:6540:0302/010936:VERBOSE1:crash_service.cc(485)] clients connected :2
clients terminated :2
dumps serviced :0
dumps reported :0
[7244:6540:0302/010936:VERBOSE1:crash_service_main.cc(88)] Session end. return code is 0

vgturtle127 commented Mar 3, 2015

Squirrel Updater log:

Notice the access denied in the first AppData.

I am using an admin account and running as admin as well.

50Wliu commented Mar 3, 2015

Are you saying you right-clicked—>»Run as Administrator»? If so, please don’t do that (in fact, in the next release of Squirrel, Squirrel will intentionally relaunch itself to run as a normal user if it detects that it has administrator permissions).

LibertyBeta commented Apr 3, 2015

I’m reporting a similar issues with the most recent installer, however it doesn’t create a atom direction in the appdata or fail with a log body.

Note: I did try to uninstall after the borked update and it that didn’t go well. I had to manually remove the registry for atom in several places.

vgturtle127 commented Apr 4, 2015

After Revo Uninstalling leftover Atom installations, using CCleaner, BleachBit, and System Ninja with Winapp2.ini, going through my registry, AppData, and ProgramData and deleting everything Atom related, restarting, re-downloading the latest Atom installer, and running it NOT as Admin, it finally worked! I don’t know what I did this time, but I guess maybe the issue has been fixed? I still had issues with this installer last time I tried, but whatever it works now.

I’m guessing a temporary file that was created was causing some issue when it started the installer because I ran it as admin the first time. UAC sucks. Anyway, it works now so try what I did and see if it works for you.

izuzak commented Apr 13, 2015

Reported again for 0.190.0 over in #6343 by @sryze.

gvpinto commented Jun 3, 2015

Atom installer would just try to start-up and then disappear. I went ahead deleted C:\Users\YOURNAME\AppData\Local\atom and C:\Users\YOURNAME\AppData\Local\SquirrelTemp directories and ran the installer again. The directories were present because I had cancelled a previous installation. This resolved the issue.

vgturtle127 commented Jun 4, 2015

Maybe the Atom installer should put all of the files in sub-directory instead of in ProgramData/AppData?

iUwej commented Jul 26, 2015

My installation worked after launching Atom set up as an admin.

joshburgess commented Dec 2, 2015

This is still a problem now in December 2015. Just ran into it while trying to install Atom on a fresh install Windows 8 machine at work.

ghost commented Jan 13, 2016

I deleted the folder %USERPROFILE%.atom and it worked for me, but I know that is not the best solution. =/

vgturtle127 commented Jan 14, 2016

I run into more problems on Windows 8-10 than on Windows 7, if that even helps a little.

xiaoxinw commented Feb 16, 2016

I just closed the Atom editor and then install again

vgturtle127 commented Feb 17, 2016

Can this be closed? I think this issue has been solved by now, right?

CreativeWebGuy commented Feb 18, 2016

Appears to still be an issue. I’m on Win7 64bit. Upon install I’m getting the same issues. I’ve tried all the temp deletions and permission notes above but nothing. If I pull the zip for windows it runs fine but the installer appears to be stalling. See below:
2016-02-18 17:55:47> Program: Starting Squirrel Updater: —install . 2016-02-18 17:55:47> Program: Starting install, writing to C:\Users\MYUSERID\AppData\Local\SquirrelTemp 2016-02-18 17:55:47> Program: About to install to: C:\Users\MYUSERID\AppData\Local\atom 2016-02-18 17:55:47> CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:\Users\MYUSERID\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__3d.MoveNext() 2016-02-18 17:55:47> CheckForUpdateImpl: Reading RELEASES file from C:\Users\MYUSERID\AppData\Local\SquirrelTemp 2016-02-18 17:55:47> CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch 2016-02-18 17:55:47> ApplyReleasesImpl: Writing files to app directory: C:\Users\MYUSERID\AppData\Local\atom\app-1.5.3 2016-02-18 17:55:54> 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, Boolean expandShortPaths) at System.IO.Path.GetFullPathInternal(String path) at System.IO.Path.GetFullPath(String path) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner) at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf. b__a8>d__b8.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__54 1.MoveNext()
2016-02-18 17:55:54> Unhandled exception: System.AggregateException: One or more errors occurred. —> 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, Boolean expandShortPaths)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.Path.GetFullPath(String path)
at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry)
at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner)
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf. d__b8.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__54 1.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Squirrel.UpdateManager.ApplyReleasesImpl.d__78.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.UpdateManager. d__f.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Squirrel.Update.Program. d__37.MoveNext() — End of inner exception stack trace — at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at System.Threading.Tasks.Task.Wait() at Squirrel.Update.Program.executeCommandLine(String[] args) at Squirrel.Update.Program.main(String[] args) —> (Inner Exception #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, Boolean expandShortPaths) at System.IO.Path.GetFullPathInternal(String path) at System.IO.Path.GetFullPath(String path) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner) at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf. b__a8>d__b8.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__54 1.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.d__78.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.UpdateManager.d__f.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.Update.Program.d__37.MoveNext()

vgturtle127 commented Feb 19, 2016

@CreativeWebGuy Huh, I wish I could help debug this in some way.

I just started running into the errors and issues again, so I have uninstalled Atom, cleaned my PC again, and now have a portable version in C:\atom that I use.

Does anybody have any idea what is causing this?

From what I can gather, it is the installer either not being allowed access to something, or the installer just becomes self-aware and hates anybody with a face. 😥

Zireael07 commented Feb 19, 2016

That’s your problem right here and there is a separate issue for ‘path too long’ problems.

CreativeWebGuy commented Feb 19, 2016

@Zireael07 — Completely missed that. I was hung up on the RELEASES folder in the «from scratch load» it’s looking for not being there. Didn’t go much further beyond that in the log. Where I’m now hung up on is how to correct this. If I’m using a standard Win7 install and the files are attempting to load into their default location the only variable in length is the userid in the path. I’m on a domain so the folder becomes userid.domain (currently 16 char in length). I guess at this point I just go on running in a folder in a portable format.

Zireael07 commented Feb 19, 2016

@CreativeWebGuy: Download the zip version from atom.io. It doesn’t care about long paths.

CreativeWebGuy commented Feb 19, 2016

@Zireael07: That’s what I’m doing. I just wanted to add this in here to help put a finger on it for others.

damieng commented Feb 23, 2016

As this has been identified as PATH too long I am closing it and providing a link to the issue tracking that #5109

meghanakshathra commented May 15, 2016 •

I downloaded and installed the atom on windows 7.After installation it opened automatically and the next time i’m not able to open it. i»m basically not able to find the shortcut. Only .exe file is there on my downloads, and when I run it, it shows some error. can anyone please get the solution for this. 🙂

damieng commented May 15, 2016

@meghanakshathra Please open a new issue and include the exact error message/screen shot of the error.

JohnTocher commented May 16, 2016

I had the same issue running the installer on Windows 10, 64 bit. Manually deleting most of the contents (Firefox had some files locked which couldn’t be deleted) worked for me.

gideondsouza commented May 23, 2016

I had the same issues, tried all suggested solutions. I had a virus scanner that sucks, McAfee. I disabled it’s on on access scan and now the installer worked.