I’m encountering the following error when launching Postman on Windows:
"stack":"Error: Command failed: dir \"C:\\Users\\XXXX\\AppData\\Local\\Postman\" /Q
at genericNodeError (node:internal/errors:984:15)
at wrappedFn (node:internal/errors:538:14)
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:518:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)"
Additional logs:
[34140][1761119193647][main][info]["App Ownership Service: Windows ownership check",{"appPath":"C:\\Users\\xxxx\\AppData\\Local\\Postman","isCurrentUser":true,"isElevated":false,"isRoot":false}]
[34140][1761119194723][main][info]["App Ownership Service: Windows ownership check",{"appPath":"C:\\Users\\xxxx\\AppData\\Local\\Postman","isCurrentUser":true,"isElevated":false,"isRoot":false}]
[34140][1761119286086][main][info]["Emitting screen event on main process","unlock-screen"]
It looks like Postman is trying to access the AppData folder but fails when running the dir command.
I’m running Postman on Windows 11, standard user (not elevated), with the latest desktop version.
Has anyone encountered this issue before or found a workaround?
I’ve already tried reinstalling and clearing the AppData\Local\Postman folder, but the problem persists.
Well, I set ‘run Postman as administrator’ and issue no longer occurs.
I will observe the desktop app behaviour in next days.
But I guess issue still exists, and must be fix (not all users can use admin mode).
Hi,
It seems the issue is still not resolved. Could you please look into it?
By the way, I know two other colleagues are experiencing the same problem — Postman freezes after locking Windows.
By “freeze”, I mean that nothing happens after unlocking Windows and pressing Send— not even the sending animation appears, and the Cancel button doesn’t work either.
- Are you still seeing this issue on your side?