This error. No matter what i do. For half a year of different attempts to fix it. Please, help, i am nearly ran out of hope to use pd again on that pc...

@bellyband I see that you are trying to start pd.com and that name could be resolving in DNS to the internet. Try starting pd.exe directly from the Pd/bin folder.
As @fishcrystals noted....... when you double-click a patch to open Pd it is pd.exe that is started.
But maybe you are only trying to start pd.com to get the stderr information in the cmd window?

If that doesn't work then there could be a problem with your DNS server.
The hosts file overrides DNS, so if you specify the localhost in the hosts file that might help.
The lines starting with # are simply comments......

# 127.0.0.1 localhost

# ::1 localhost

Remove the # symbols for them to be effective......
127.0.0.1 localhost
::1 localhost

The file you need to edit is ........ C:\Windows\System32\drivers\etc\hosts
Use administrator rights to change it.

If you check the traceroute in a command prompt you should have only 1 hop...... the first number in the line returned......
Both localhost and 127.0.0.1 should return the name of your computer

David.

@fishcrystals sadly, nothing. No reaction. Except it silently starts wish86 in task manager...

@whale-av well, it goes fine on that step. But pd is not starting anyway...

@bellyband Hmm.....
I was going to suggest deleting the preferences in the registry (probably still at "Computer\HKEY_CURRENT_USER\Software\Pure-Data" ) but I see you have tried the -noprefs flag.
As it is starting wish it is getting part way through its startup sequence.

You don't need to start a patch as Pd starts...... out of the box you wouldn't have one to start.
Audio problems can stop Pd starting, even though dsp will not be running as it starts.

Create a shortcut to pd.exe in the bin folder. Edit the shortcut to open pd.exe with the -noprefs and -noaudio flags.... don't open a patch with the command.

If that doesn't work then try a portable version of Pd.
puredata/info seems to be down at the moment.
When it is back up go to this page ........ http://puredata.info/downloads/pd-extended ..... I remember that the page will allow you to navigate to recent versions of Pd vanilla.
Find a portable version of Pd for Windows...... it will be a .zip file that you can download and run anywhere (it does not require installation).
Unzip it into a folder on your desktop and double-click the Pd/bin/pd.exe binary.

If that doesn't work then try starting that binary with the -noprefs and -noaudio flags in a shortcut rather than a cmd window.

If that doesn't work then create a new user in windows, and see if that user can run Pd.
You could have a corrupted user profile in Windows 10.
And then, for the moment, I am out of ideas, but you could try uninstalling windows updates that have been installed since just before the problem first occurred.
David.

@whale-av none of this worked out.... i guess the universe itself refuses to give me acess to the pd((((((

@whale-av btw portable version behaves the same

@whale-av And you know what? f*ck all this, I'm switching to plugdata. thanks for trying to help me, but I think it will be better for everyone

@bellyband Fwiw... Did you try starting Pd without loading a patch immediately?

That was suggested above but it's not clear to me whether you tried it or not.

For "differential testing" this would tell the difference between a pd startup problem and a patch-loading problem.

In any case plugdata's interface has a lot to recommend it. As tcl/tk ages, it becomes more and more likely to run into weird problems like this, so it's good that there's a modern alternative.

hjh

just fyi the original error is due to pd trying to configure a cursor for the pd console window without it being open
not sure why that would happen tho
it does seem like either a permissions or maybe network thing. Or maybe the architecture in one of the binaries isn't supported by your system.
if you feel like more troubleshooting you could try starting 'wish86.exe' from command line too to see if that gives errors..

It might sounds obvious, but be sure that pd is not reading an old .tcl plugin somewhere from a path... like document/pd/ etc...

I remember having this issue once.