Postman Taking a Very Long Time to Start

Hello. I’m running x64 Windows 11 25H2 with Postman 12.9.7.

Lately, I’ve had a problem starting the app. No splash screen, no crash or error message, just.. nothing. After starting the app, I have 2x instances of Postman.exe running, one of which uses 8% CPU, the other 0%, and negligible memory usage by either.

For a while I thought it was broken, and a temporary workaround is to reinstall and delete the contents of the appdata folders, but the issue just occurs again the next day.

But I discovered recently that if I just wait for like, half an hour or an hour, the GUI starts up and runs as normal.

Where can I start to go about troubleshooting this? Is there a log file?

If you find a solution, please share here, because I’m facing the same issue. Although I haven’t waited for over an hour, so I have to wait whether or not the Postman app eventually will start.

Indeed, after quit some time the app started. So, that’s the work around for now: just sit and wait.

I have found this also. But it frequently crashes and the i have to start all over again

I’m experiencing the same issue. I haven’t tried waiting until it fully starts, but what worked for me was deleting the folder C:\Users\<my-user>\AppData\Roaming\Postman. After that, the application launched correctly.
Just make sure you have everything backed up beforehand so you don’t lose any data.

I have the same problem

+1 , i have the same issue

Me too. I was also using the manual delete-every-day approach. Then one day I forgot I had opened it, and about 15 minutes later it suddenly popped up again.

Ever since the last update, it’s been really difficult to use. Even the update process itself took ages to complete properly. It’s quite disheartening that no one from the Postman team has responded, especially when so many users seem to be affected.

same issue here win 10 Version 10.0.19045 Build 19045 started this week

Hey folks,

Really sorry you’re hitting issues, totally get how annoying that is, and thanks for flagging it.

Best spot to get this in front of the team is our GitHub issue tracker.

Worth a quick look there first too, there might already be an open ticket you can jump on and add your details to. Keeping things in one place is way easier for us to dig into than chasing threads across Discourse.

Couple of discussions already going on similar stuff, so have a peek in case yours overlaps: