Problems Importing packages in window 11.

[Orlandoiii]

Is there an existing issue for this?

• I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

First, thank you for creating such an amazing tool! Postman has always been my go-to API client for its ease of use and powerful features.

I’ve encountered an issue with the Package Manager (the new feature for importing external packages) in the Windows desktop app. When attempting to import the npms packages (I try very differents ones the uuid), the app throws this error:

[1952][1745768825013][requester][error]["external-packagePackageControlleraddPackage: Error loading npm:[email protected]",{"name":"Error","message":"Error invoking remote method 'runtime-ipc-cb': Error: ENOENT: no such file or directory, mkdir 'C:\Users\ORLAND1\AppData\Local\Temp\scriptPackageFiles\npm:[email protected]'","stack":"Error: Error invoking remote method 'runtime-ipc-cb': Error: ENOENT: no such file or directory, mkdir 'C:\Users\ORLAND1\AppData\Local\Temp\scriptPackageFiles\npm:[email protected]'\n at IpcRenderer.invoke (node:electron/js2c/renderer_init:2:6995)"}]

I try for several hours thinking it was my local enviroment because in the web the package work perfectly. But after delete all data, reinstall and update (even clean cache). The issue persist, finally I try to create the package manually I find the folder created until this point AppData\Local\Temp\scriptPackageFiles\ , so I try to create the package folder and thats when Window dont let me create a folder using :
This issue does not occur in the Postman web version or Linux desktop app, confirming it is specific to Windows.

Steps To Reproduce

1. Just create a collection and try to import a package in window desktop app

Screenshots or Videos

No response

Operating System

Windows

Postman Version

11.42.5

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[appurva21]

Hi @Orlandoiii! Thank you for reporting this. I can confirm that this seems to be an issue on our end. We'll update this thread once the fix it out.