[Windows 10] Installation Error on Surface Pro X / ARM64
closed
K
Kevin Tham
I get this SquirrelLog exception:
2020-04-11 13:59:27> Program: Starting Squirrel Updater: --install .
2020-04-11 13:59:28> Program: Starting install, writing to C:\Users\kevin\AppData\Local\SquirrelTemp
2020-04-11 13:59:28> Program: About to install to: C:\Users\kevin\AppData\Local\Screen
2020-04-11 13:59:28> CheckForUpdateImpl: Couldn't write out staging user ID, this user probably shouldn't get beta anything: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\kevin\AppData\Local\Screen\packages\.betaId'.
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, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
at System.IO.File.WriteAllText(String path, String contents, Encoding encoding)
at Squirrel.UpdateManager.CheckForUpdateImpl.getOrCreateStagedUserId()
2020-04-11 13:59:28> CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\kevin\AppData\Local\Screen\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.<CheckForUpdate>d__2.MoveNext()
2020-04-11 13:59:28> CheckForUpdateImpl: Reading RELEASES file from C:\Users\kevin\AppData\Local\SquirrelTemp
2020-04-11 13:59:28> CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch
2020-04-11 13:59:29> ApplyReleasesImpl: Writing files to app directory: C:\Users\kevin\AppData\Local\Screen\app-1.0.18
2020-04-11 13:59:34> LogHost: Rigging execution stub for Screen_ExecutionStub.exe to C:\Users\kevin\AppData\Local\Screen\Screen.exe
2020-04-11 13:59:35> ApplyReleasesImpl: Squirrel Enabled Apps: [C:\Users\kevin\AppData\Local\Screen\app-1.0.18\Screen.exe]
2020-04-11 13:59:36> ApplyReleasesImpl: Couldn't run Squirrel hook, continuing: C:\Users\kevin\AppData\Local\Screen\app-1.0.18\Screen.exe: System.ComponentModel.Win32Exception (0x80004005): The specified executable is not a valid application for this OS platform.
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Squirrel.Utility.<InvokeProcessAsync>d__11.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.ApplyReleasesImpl.<>c__DisplayClass10_0.<<invokePostInstall>b__0>d.MoveNext()
Log In
J Sherwani (Pop Team)
closed
Pop has had significant improvements made since this bug was filed, so we closing out this bug as stale. If you’re still experiencing this issue, please post a reply and we'll reopen the bug.
J Sherwani (Pop Team)
under review
Ana Betts (Screen Team)
Kevin Tham: This error is super opaque, but this is because right now we don't support ARM64 at the moment, our app is 64-bit Intel only for this super early release.
In the future we definitely hope to support other platforms like ARM64 or x86 (and as a fellow Surface Pro X owner, I'm definitely looking forward to native ARM64 support too!)