Issues getting PIO up and running again on VSC

[airnocker]

Quick workstation summary:
Windows 10 Pro 64-bit, 22H2, OS Build 19045.5371, w/latest updates
MSI MAG Z490 TOMAHAWK motherboard, Intel Core i5-10400F CPU @2.90GHz, 32GB RAM

Version: 1.96.3 (user setup)
Commit: 91fbdddc47bc9c09064bf7acf133d22631cbf083
Date: 2025-01-09T18:14:09.060Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

Prior discussion that led to this thread on Arduino IDE thread, with this link:

PlatformIO was removed, just how I did this I don't recall. I moved the NightDriver-main folder from my C: drive to my G: USB external drive at that time. Last night I unzipped a fresh copy of NightDriverStrip-main overwriting the G: NightDriver-main folder.
PlatformIO Extension was re-added to VSC and the NightDriverStrip-main folder was loaded. The PlatformIO.ini file was edited for device, default environment (laserline) and COM3 as upload_port. The upload_speed used previously (last year) was 1500000 but is now 200000 for some reason.

Doing an F1-compile brought on npm errors and a compile failure that pointed me to needing to load Node.js, which I did, following default prompts. This improved the npm errors but resulted in this on referring to Powershell ExecutionPolicy setting.

I ran Windows Powershell as admin and did a Set-ExecutionPolicy to RemoteSigned.

Compile process was greatly improved but now fails with this screenshot and declaring that COM3, which had been working fine during compiles, as not existing after using Dave's NightDriver ESP32 Installation Wizard https://plummerssoftwarellc.github.io/NightDriverStrip/ to load laserline on my M5 StickC Plus. Laserline works fine then with my WS2812B strip(s).

Help appreciated. Thanks

[airnocker]

Problem solved...at least for now. Successful upload of laserline!

I rediscovered an old thread of mine that @rbergen helped me last year or so and (https://github.com/PlummersSoftwareLLC/NightDriverStrip/discussions/433) that refreshed my memory about using the Auto button in PlatformIO's toolbar at the bottom for auto selecting the com port. Removing my typed "COM3" in the platformio.ini's upload_port and monitor_port lines, leaving them blank, then unplugging the M5 StickC Plus from the USB port and plugging it back it, fixed the port communication problem.

So, here's to a new effort with using PIO.

[airnocker]

Problem resolved: Exit out of Malwarebytes, then everything works great