Createprocessw failed error 193

same problem please help me

`CreateProcessW failed 193

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: 90c51fd53df122d1)
CreateProcessW failed 193
CreateProcessW failed 193
Unhandled exception:
ProcessException: %1 is not a valid Win32 application.

Command: C:Usersto the moonAppDataLocalAndroidsdkplatform-toolsadb.EXE devices -l `

i have same issue

Can anyone help me with this Error?

CreateProcessW failed 193
Unhandled exception:
ProcessException: %1 is not a valid Win32 application.

For More info please visit the link and Help me Please
Flutter.txt

Same debug error in Flutter Web here.
«CreatedProcessW failed 2
Exited(1)»

hey subham468 i was see your problem you

Can anyone help me with this Error?

CreateProcessW failed 193
Unhandled exception:
ProcessException: %1 is not a valid Win32 application.

For More info please visit the link and Help me Please
Flutter.txt

i was see your problem C:Users Subham Paul AppDataLocalAndroidsdkplatform-toolsadb.exe
C:Users Subham AppDataLocalAndroidsdkplatform-toolsadb.exe

Change pc name in c drive Subham Paul to Subham

The solution shouldn’t be for the user to change their profile name.

It should be changed so the the path to the adb.exe inside double quotes with the argument following outside of it.

«C:UsersSubham Paul AppDataLocalAndroidsdkplatform-toolsadb.exe» devices -l

same problem
i changed the username to one word. re installed android studio. it still gives the same error

I have the same issue, the problem is also that Im not able to launch my application on emulators or even on my connected device, everything worked, suddenly I was not able anymore to run my application so I ran flutter doctor and got the error message . so annoying because you basically cant use flutter anymore because you cant run your applications live, without its kind of no fun

btw I also dont know why changing the username should fix it because before everything was working like it should.

and I also tried uninstalling flutter and reinstalling but it doesnt worked :C

I HAVE SOLVED IT the error seems to appear because their are spaces in your username but its really easy to fix you just have to, move the Android SDK which is located by default in C:UsersusernameAppDataLocalAndroidSdk
You have to move the «Sdk» Folder into a directory where are no spaces included in the path name
for example:
C:randomFolderWithoutSpacesSdk

Then you have to create a new environment variable called ANDROID_HOME and set its value to the new path of the Sdk ( in this example: C:randomFolderWithoutSpacesSdk )
Therefore you have to add these values to the Environment Variable Path (for this example):
C:randomFolderWithoutSpacesSdktools
C:randomFolderWithoutSpacesSdkplatform-tools

run flutter doctor in a new command prompt and the error should be fixed!!

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

[solved] github desktop does not work — Authentication failed. permission denied #11883

github desktop did not work with ssh. (git bash and poweshell works well.)

so I changed ssh to https back but same error again.

and I tried change internal ssh to openssh but. another error occured.

I was able to reproduce this issue, and it comes down to Desktop choosing to use it’s internal ssh program (which doesn’t know about the ssh-agent service associated with OpenSSH on Windows which runs as a Windows Service) over anything that might be defined on PATH .

The workaround for this is to change your global configuration to use the OpenSSH for Windows build of SSH:

• git bash or powershell (or command propt)

And, when I try to push or pull from github desktop or vs code, the loading spinner spins indefinitely, and the push/pull never finish.
Please let me solve this 🙁

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

• Install posh-git

1. Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned -Force
2. Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
3. Update-Module PowerShellGet -Force
   If ‘Module ‘PowerShellGet’ was not installed by using Install-Module’ error occured,
   3-A. Install-Module PowerShellGet -Force -SkipPublisherCheck and back to 3.
4. Install-Module Posh-Git -Scope CurrentUser
5. ‘Import-Module Posh-Git’ | Out-File -Append -Encoding default -FilePath $profile

• Add scripts to powershell $profile (runs when powershell is opened.)

1. open powershell directory C:UserDocumentsWindowsPowerShell
2. open Microsoft.PowerShell_profile.ps1
3. now, You can see Import-Module Posh-Git in that file.
4. Add followed lines.

Источник

SSH project on github giving issues

Issue

I ran through the whole process of adding a key to Github and doing everything on this guide that Github provided, but afterwards, it asked every 5 min for the ssh passkey, which is quite annoying while working on a project, so a found a command that eases that but this morning I got an error saying the following

C:WindowsSystem32OpenSSHssh.exe: C:WindowsSystem32OpenSSHssh.exe: command not found

reran this to check if everything was fine

it authenticated, but the error did not disappear, so I ran the same command that I got on Friday git config —global —add core.sshCommand C:/Windows/System32/OpenSSH/ssh.exe

Now when I do a ‘refresh’ (push and pull) to get the latest changes to my repo, it just keeps on synchronizing changes as if it is infinite looping and then timing out.

If I run git pull in git bash I get the following output

but before that, I ran ssh -T [email protected]

and I got the following output after entering the password

Does anyone know what I can do to fix this ?

Solution

The idea is to not use anything from Windows itself, but only from your Git for Windows (make sure to get the latest 2.33.0.2)

So remove any ssh setting from your global Git configuration, and make sure your %PATH% includes:

A where ssh in a CMD should give you: C:pathtogitusrbinssh.exe .

From there, from that same CMD, you can type «bash» to switch to a bash shelll session.
Make sure your

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Источник

Desktop does not use OpenSSH on Windows if running, favours embedded SSH #5641

There seems to be no support for the Native Windows 10 Authorisation using the built-in ssh-agent.

Windows 10 now provides it’s own built-in implementation of openssh. And it provides its own ssh-agent as a Windows Service for storing PassPhrases.

BUT I cannot get GitHub Desktop to work using the Keys setup with the Windows ssh-agent, so Pushing always fails to any private repositories on servers when using SSH.

When will the NATIVE Windows ssh-agent service be supported in GitHub Desktop application?

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

@richardbushell thanks for the report! It’s not clear to me how you’ve configured your ssh-agent setup, and I’m pretty sure a vanilla ssh-agent setup with passphrases works fine with Desktop, so could you clarify a couple of things:

• is the Git operation failing because it needs a passphrase and is failing to look it up? Could you share an example of the error from the log files (open Help | Show Logs in Explorer)?
• I’ve not had a chance to look at the latest OpenSSH work that’s gone into Windows 10 — can you point me to some details about how this Windows Service works to remember your passphrase?

Windows 10 (Spring 2018) added a direct implementation of openssh into Windows.
It therefore supports all of the openssh commands directly on the Windows command-line, and makes PuTTY and Pageant obsolete.

You run ssh-agent and ssh-add as normal but these run the built-in Windows executables.
Windows runs ssh-agent as a SERVICE, which can be enabled to run Manually, or Automatically on Windows startup (it is set to Disabled by default).

But it then uses the Windows ssh-agent service to provide PassPhrase responses automatically. There is no need for PuTTY+Pageant or a separate Bash ssh-agent any more. Just need to let Windows handle this NATIVELY.

@richardbushell thanks — I know the basics, but I had some specific questions:

• is the Git operation failing because it needs a passphrase and is failing to look it up? Could you share an example of the error from the log files (open Help | Show Logs in Explorer)?
• I’ve not had a chance to look at the latest OpenSSH work that’s gone into Windows 10 — can you point me to some details about how this Windows Service works to remember your passphrase?

I was able to reproduce this issue, and it comes down to Desktop choosing to use it’s internal ssh program (which doesn’t know about the ssh-agent service associated with OpenSSH on Windows which runs as a Windows Service) over anything that might be defined on PATH .

The workaround for this is to change your global configuration to use the OpenSSH for Windows build of SSH:

@shiftkey Thanks, that workaround works perfectly to bypass the embedded SSH. It should be a relatively simple fix to get into a subsequent release too asap. Obviously most users will switch to the native Windows SSH service as word spreads and they realise it’s now built in without bash or third-party plugins.

I’m still struggling. I can get git in WSL to work, and git in windows. But Github desktop still fails. Is there anything else it’s doing different than git.exe on the command line?

I was able to reproduce this issue, and it comes down to Desktop choosing to use it’s internal ssh program (which doesn’t know about the ssh-agent service associated with OpenSSH on Windows which runs as a Windows Service) over anything that might be defined on PATH .

The workaround for this is to change your global configuration to use the OpenSSH for Windows build of SSH:

@shiftkey I just tried this, and now any time I try to push or pull from github desktop or vs code, the loading spinner spins indefinitely, and the push/pull never finish. any ideas?

I undid the change, and removed my passphrase from the key. I’m finally free.

@yehudamakarov would you be willing to upload the log file from GitHub Desktop so I could take a look at what might have happened there? I’ve tested this a bit to confirm it works, so I want to be sure there is not something I am missing.

To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs in Explorer (Windows) . The log files are created daily — please upload a log file as an attachment from a day where you experienced the issue.

I don’t know if this will help everyone, but what I did is just signed out and signed back into GitHub Desktop, and it fixed the problem. Such a simple fix.

How do you undo git config —global core.sshCommand «‘C:WindowsSystem32OpenSSHssh.exe’» ?
I decided to just go back to using the git bash terminal for windows and now I’m seeing:

I was unable to find the default value to replace C:WindowsSystem32OpenSSHssh.exe with so I just opened the config file in a text editor and deleted that line. Everything went back to normal.

I was able to reproduce this issue, and it comes down to Desktop choosing to use it’s internal ssh program (which doesn’t know about the ssh-agent service associated with OpenSSH on Windows which runs as a Windows Service) over anything that might be defined on PATH .

The workaround for this is to change your global configuration to use the OpenSSH for Windows build of SSH:

How and where i can run the code?
p.s. I never work with github code

@lsalex133 you can find the .gitconfig file in your User directory (C:Users Repository > Open in command prompt and run the git config command from the command line. Let me know if you run into any problems.

I managed to get GitHub Desktop to use Windows’ native OpenSSL following advice above, setting sshCommand = ‘C:\Windows\System32\OpenSSH\ssh.exe’ in

/.gitconfig , after enabling the built-in OpenSSL service.

I have been able to load and work with a repo, however when it finally came to push it back to origin, I got the error:

Some snooping online suggests this may be the result of the built in Windows OpenSSL being out of date, but upgrading it manually will be a very dodgy process (and I’m not even sure this is really the issue).

Can anyone shed any light?

Ignore me. The real error appeared to be what followed:

In short I’ve got this 100% working!

@shiftkey
I was able to reproduce this issue, and it comes down to Desktop choosing to use it’s internal ssh program (which doesn’t know about the ssh-agent service associated with OpenSSH on Windows which runs as a Windows Service) over anything that might be defined on PATH .

The workaround for this is to change your global configuration to use the OpenSSH for Windows build of SSH:

I tried this but I failed.

2021-03-27T21:13:40.436Z — info: [ui] [AppStore] loading 6 repositories from store
2021-03-27T21:13:40.648Z — info: [ui] [BranchPruner] Last prune took place in a day — skipping
2021-03-27T21:13:40.706Z — info: [ui] launching: 2.6.6 (Windows 10.0.18363)
2021-03-27T21:13:40.706Z — info: [ui] execPath: ‘C:UsersDJAppDataLocalGitHubDesktopapp-2.6.6GitHubDesktop.exe’

• git bash or powershell (or command propt)

$ git push
fatal: The current branch main has no upstream branch.
To push the current branch and set the remote as upstream, use

$ git pull
CreateProcessW failed error:193
ssh_askpass: posix_spawn: Unknown error
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

And, when I try to push or pull from github desktop or vs code, the loading spinner spins indefinitely, and the push/pull never finish.
Please let me solve this 🙁

Источник

I am using a setup on Windows 10 x64 where I install and manage git via scoop, rather downloading and executing the installer myself. Via the PowerShell, I ran

scoop install git
scoop install openssh
[environment]::setenvironmentvariable('GIT_SSH', (resolve-path (scoop which ssh)), 'USER')

However, now when I try to run commands in the Git Bash like

git clone git@example.org:vendor/repository.git

or a simple

git push/pull

I only get

CreateProcessW failed error:193
ssh_askpass: posix_spawn: Unknown error

instead of the Git Bash asking me for my SSH key’s passphrase.

I am using the same setup (git installed via scoop) on many other Windows 10 x64 and no problems occur there. So I am not sure what is going wrong on this one. I previously had git installed without scoop on the same machine and the Git Bash was working fine. I uninstalled git completely (and also restarted the machine, just to be sure) before re-installing it via scoop instead.

The SSH_ASKPASS environment variable contains the following, in case this is relevant:

$ echo ${SSH_ASKPASS}
/mingw64/libexec/git-core/git-gui--askpass

Not sure what that folder refers to (something internal to the Git Bash presumably?), since it obviously does not exist like that on my machine.

Update

When using git-with-openssh instead of just git and openssh separately it works. However, I don’t use that on my other machines, so I’d still like to know why it’s not working here.