PlatformIO Community

PlatformIO Terminal dead and Build process unresponsive

On one of my machines AMD Ryzen/Win10 PlatformIO does not work for some time. Don’t no for how long. Recocknized when playing around with serveral IDEs as ATMEL Studio, Eclipse/Sloeber/STM32CUBE and Arduino and judging PlatformIO as the the one to go with, it wasn’t working any more.
However, VSC/PlatformIO does not give any error message, but the terminal accepts no input and when I start a build process I get the Message “Executing task in folder 191219-225226-arduino-blink: C:\Users\thomas.platformio\penv\Scripts\platformio.exe run <” and thats it, building indication will circle forever.
Toggleing developer tools gives me the following error messages:

bootstrap-window.js:213 [uncaught exception]: Error: connect ENOENT \\.\pipe\winpty-conin-908-1-1d5b8fc98f86194-807a7b94bc2c9c1c427485d15ce21821
onUnexpectedError @ bootstrap-window.js:213
bootstrap-window.js:216 Error: connect ENOENT \\.\pipe\winpty-conin-908-1-1d5b8fc98f86194-807a7b94bc2c9c1c427485d15ce21821
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1054)
onUnexpectedError @ bootstrap-window.js:216
events.js:177 Uncaught Error: connect ENOENT \\.\pipe\winpty-conin-908-1-1d5b8fc98f86194-807a7b94bc2c9c1c427485d15ce21821
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1054)
bootstrap-window.js:213 [uncaught exception]: Error: connect ENOENT \\.\pipe\winpty-conout-908-2-1d5b8fc98f86194-9c9f9d0b2c609e442eb4b2da6829d84c
onUnexpectedError @ bootstrap-window.js:213
bootstrap-window.js:216 Error: connect ENOENT \\.\pipe\winpty-conout-908-2-1d5b8fc98f86194-9c9f9d0b2c609e442eb4b2da6829d84c
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1054)
onUnexpectedError @ bootstrap-window.js:216
events.js:177 Uncaught Error: connect ENOENT \\.\pipe\winpty-conout-908-2-1d5b8fc98f86194-9c9f9d0b2c609e442eb4b2da6829d84c
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:

The most weird:
I uninstalled extensions (PlatformIO, GitLens, C/C++Ext), uninstalled VSC, run CCleaner, rebooted and installed VSC again in System mode. All easy.
After first start of VNC, console was empy - no errors. When installing extensions a Buffer DeprecationWarning showed up but installation for all three extensions was confirmed.
Since terminal was working I started a build of arduino blink example - all went fine everything seemed perfect. But …
Closing VSC and starting it again brings back the problem. On VSC startup PlatformIO was running an update and I got the message PlatformIO Core was updated sucessfully. Now the terminal is dead again and ENOENT connect errors are back.
Any suggestions?

Solved - for whoever it may concern:
This is caused by using PStart utility (Pegtop) for starting VSC.I asume it has to do with context the SW is running in and rights. This works with Win7 and Win 10 before so some update seems to have changed system bahaviour.
Fully reproducable: Starting VSC using PStart, PlatformIO will update and doing changes messing up the system.
Starting by desktop icon PStart, PlatformIO will update again and doing changes and the problem is gone.
So after a fresh install is did start VSC automatclly and all was working. After closing VSC I started it again using Pstart and it got spoilt.
Used Psart for years. but it is outdated now, chaged to SyMenu.