Is there antivirus running that could interfere?
What folders regarding PlatformIO and VSCode are in a OneDrive?
What other extensions do you have installed in VSCode?
There are no anti-virus programs installed except the Windows Security.
New files I created and saved were located in the OneDrive. I have removed OneDrive from my computer. After removing it Iām now getting a new error message when I try to view->command palette->PlatformIO:Home, and the bottom menu no longer turns blue but stays purple:
I have only installed the C/C++ and the platformIO extensions.
Just want to update the status of my struggles with installing platformio.
I recently upgraded my GPU from a GTX960 to a RTX1080ti and I installed some new drivers from Nvidia. I tried to mine some bitcoins using my old GTX960 just for fun but my hardware was āincompatibleā with the site I used (NiceHash), but it worked just fine with my new 1080ti. I figured I might go for a long shot and that maybe my GTX960 was āincompatibleā with VSC or platformio, so I tried to install platformio with my new GPU, and it worked! I am using it with onedrive and with no changes to my firewall in windows.
I have no idea why it worked, but maybe some with more experience know?
Just wanted to put it out there in case someone else has the same issue with installing platformio on an older GPU.
I have this message which appears when installing PltformIO under VSCode.
The installation stops with the message: āFailed to install PlatformIO IDEā
I see the MicrosoftWindowsApps\python3.exe is in the error message there, therefor itās pretty much guaranteed to be the issue as described and solved in Failed to Install PlatformIO v2.3.0 on VS Code v1.54.3.
Hello, in my case the problem was linked to my windows account, the account name had two names, the solution I had was to create a local admin user with administrator privileges and perform the configuration on that user. Worked perfectly!!
I had a similar issue yesterday. Today it is fixed somehow. I had tried uninstalling PlatformIO and deleting its folder in %userprofile% and reinstalling. Didnāt work. I then installed PySerial and pywin32 in the penv folder inside the platformio folder like this comment suggested: ImportError: DLL load failed: The specified module could not be found Ā· Issue #586 Ā· platformio/platformio-vscode-ide Ā· GitHub
That also did not work so I uninstalled PIO from VSCode again and shut down my PC. Today when I started it back up and tried to install PIO it just worked.
Maybe this can help someone else ĀÆ\(ć)/ĀÆ
tras una actualizacion forzada de windows, casi todo el archivo settings.json se me habĆa borrado dejando solo las lineas que dicen āyalm.schemasā
no compile
no work
1 dia entero perdido buscando solucion
pero deje esto en el archivo Settings y trabaja
{
"platformio-ide.forceUploadAndMonitor": true,
"platformio-ide.disablePIOHomeStartup": true,
"platformio-ide.autoPreloadEnvTasks": true,
"platformio-ide.autoRebuildAutocompleteIndex": true,
"platformio-ide.autoOpenPlatformIOIniFile": true,
"platformio-ide.autoCloseSerialMonitor": true,
"platformio-ide.useBuiltinPIOCore": true,
"redhat.telemetry.enabled": false,
"platformio-ide.activateProjectOnTextEditorChange": true,
"platformio-ide.buildTask": "PlatformIO: Build",
"platformio-ide.customPATH": "C:\\Users\\USERX\\AppData\\Local\\Programs\\Microsoft VS Code\\bin",
"platformio-ide.disableToolbar": false,
"platformio-ide.useBuiltinPython": false,
"platformio-ide.customPyPiIndexUrl": "https://pypi.org/simple",
"yaml.schemas": {
"file:///c%3A/Users/desarrollo01.DT2LABS/.vscode/extensions/atlassian.atlascode-2.9.1/resources/schemas/pipelines-schema.json": "bitbucket-pipelines.yml"
}
}
For my case, it was making sure the effective firewall profile was all PRIVATE.
I have 4 connections on my machine, only one used, the others were connected to like another machine directly or something, It was not a defined network- so in my Firewall info page it said PRIVATE (active) PUBLIC (active). In other words both were applied.
How I fixed this is a bit out there, but make sure that you are on a PRIVATE network, or that the firewall settings are compatible.
I created Exceptions to Platformio.exe and pio.exe to allow. I created a loopback exception (conns to and from 127.0.0.0-127.255.255.255) are allowed.
Neither of those fixed it.
my specific error in the console was
mainThreadExtensionService.ts:64 RequestError: connect ECONNREFUSED 127.0.0.1:8011
at ClientRequest.<anonymous> (c:\Users\andyt\.vscode\extensions\platformio.platformio-ide-2.4.0\node_modules\got\dist\source\core\index.js:956:111)
at Object.onceWrapper (events.js:422:26)
at ClientRequest.emit (events.js:327:22)
at ClientRequest.EventEmitter.emit (domain.js:467:12)
at ClientRequest.origin.emit (c:\Users\andyt\.vscode\extensions\platformio.platformio-ide-2.4.0\node_modules\@szmarczak\http-timer\dist\source\index.js:39:20)
at Socket.socketErrorListener (_http_client.js:469:9)
at Socket.emit (events.js:315:20)
at Socket.EventEmitter.emit (domain.js:467:12)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
Expanding the errors with the dropdown shows the traceback:
_doInvokeHandler @ rpcProtocol.ts:472
_invokeHandler @ rpcProtocol.ts:457
_receiveRequest @ rpcProtocol.ts:373
_receiveOneMessage @ rpcProtocol.ts:295
(anonymous) @ rpcProtocol.ts:160
fire @ event.ts:577
fire @ ipc.net.ts:513
_receiveMessage @ ipc.net.ts:871
(anonymous) @ ipc.net.ts:710
fire @ event.ts:577
acceptChunk @ ipc.net.ts:286
(anonymous) @ ipc.net.ts:247
k @ ipc.net.ts:50
emit @ events.js:315
addChunk @ internal/streams/readable.js:309
readableAddChunk @ internal/streams/readable.js:284
Readable.push @ internal/streams/readable.js:223
onStreamRead @ internal/stream_base_commons.js:188
Since RPC Features prominently in the call stack, I also allowed more of the RPC (Remote Procedure Call) related exceptions through the firewall, though ONLY on Private (e.g. on my home network- I could open it up everywhere, but its not really safe)
After tweaking the firewall, and then making sure the PRIVATE was the only active profile- the network I was connected to was defined as private, and the null connection was manually defined (169.254.x.x) and also declared PRIVATE.
This took off the PUBLIC firewall exceptions (block anything not specficially allowed) and allowed it to connect once again.
This issue has been plaguing me repeatedly for a few years now. And for me at least, I found the source- if one of the connections triggers a PUBLIC firewall policy- maybe wifi turns on, etc.) then nothing worked.
I tried all the other things, reinstalling (10x over the years) Python, path etc. And it was intermittent so really difficult to catch the source.
1 Like