[TIMOB-20151] Windows 10: If you run appc/ti info, then "Error: spawn powershell ENOENT" is returned
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | None |
|---|
| Status | Closed |
|---|
| Resolution | Not Our Bug |
|---|
| Resolution Date | 2015-12-17T14:17:57.000+0000 |
|---|
| Affected Version/s | Release 5.1.2, Release 5.1.1 |
|---|
| Fix Version/s | n/a |
|---|
| Components | Windows |
|---|
| Labels | qe-5.1.2 |
|---|
| Reporter | Wilson Luu |
|---|
| Assignee | Christopher Williams |
|---|
| Created | 2015-12-17T01:06:24.000+0000 |
|---|
| Updated | 2016-04-26T05:42:50.000+0000 |
|---|
Description
*Details:* If you run appc/ti info, then "Error: spawn powershell ENOENT" is returned.
*Notes:*
* This occurs with current GA and 5.1.2 SDK.
* When I filed this ticket, I upgraded my machine from Windows 8 Enterprise to Windows 10 Pro.
* To workaround this issue, add C:\Windows\System32\WindowsPowerShell\v1.0 to your Path environment variable.
*Steps to reproduce:*
Run appc ti info
*Actual:* "Error: spawn powershell ENOENT" stack trace is returned; see attachment.
*Expected:* No errors should appear.
Attachments
| File | Date | Size |
|---|
| stack.txt | 2015-12-17T01:06:13.000+0000 | 5522 |
I'm not sure what to do about this one. Basically this looks like a one-off configuration problem, though I honestly have no idea why or how it'd happen. By default in both the System and my user PATH the powershell bin directory is listed. That should be the case for every Windows system. I think unless we start seeing more reports of this, this may just be a fluke. If it's common, I suppose we'll need to add special code for finding Powershell at the standard location when it's not on the PATH?
For now, will close ticket as "Not Our Bug".
@ Wilson, did you resolve this problem. I am facing it and have no solution. I am using Window 8 and all other path variables are set accordingly including the power shell directory added in my path.
[~Umair], At the moment, there is no fix for this issue as per Chris's comment. Can you provide the following information: * The stack trace you are seeing. * The versions you are using for: ** Appc CLI NPM: Version property in
C:\Users\<USER>\AppData\Roaming\npm\node_modules\appcelerator\package.json** Appc CLI Core:C:\Users\<USER>\.appcelerator\install\.version** Titanium SDK: SDK selected property inC:\Users\<USER>\.titanium\config.json** Node version:node -v** Architecture of your Node: 32-bit or 64-bit ** Architecture of your Windows OS * And, after you set the path, did you try restarting your Windows machine?I was on Windows 8.1 and yes after restart, I dont know what happened but the issue is fixed :)