ok. now upload your sketch what didn’t worked before, and try serial monitor again.
BUT do not connect anything (wires, sensors, etc) to the esp, except usb!
You mentioned this happened after a Windows 10 update… did you mean updating to Windows 10, or you already had 10, and there was just a patch?
Is you Local Server installed ON the PC that is running Windows 10? or on something else like an RPi, etc?
When this issue is happening, is your NodeMCU plugged in with USB and using the IDE monitor, or are you using some other method of seeing the Serial Prints.
And again… can we see this sketch you are testing with?
@Gunner
1- Local Server? 0.23.0, 0.23.1 ,0.23.2 almost all
2-already had windows 10, and this was a windows update.
3-my Local Server is installed ON the PC that is running Windows 10.
4-NodeMCU was plugged in with USB Com 3 and using the IDE monitor.
something strange happened now
i am using same auth token for both local and cloud server.
now when i changed the token with another one, serial print works .
I really don’t understand what is the relation of serial print and auth token.
when i change it back, it stops again.
I am still testing.
I need to add
even i test with a very simple sketch with the same auth token it will not work.
Since you have managed to install Local Server, then I guess you realise that it and Cloud are completely separate… even if using the same login and password.
The auth comes from the server, passed through the app (and is also linked to that specific project - and must match with auth in sketch). Thus even a cloned project running exactly same process and MCU will require one auth for Cloud and another for Local.
And what you have shown from your Serial monitor is what usually prints before Blynk.begin()… usually followed by repeating connecting msgs until it actually does connect.
But that alone assumes the same auth code… that will NOT work as both servers generate and track their own… no synchronization between them.
You must also change auth codes to match what each server has generated for that project… otherwise, no connection (and no further prints… or anything really).