You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Node.js uninstall Windows Installer .msi leaves stranded Corepack files #646
Uninstalling Node.js that was previously installed using a Windows Installer .msi package leaves files in "C:\Program Files\nodejs" if corepack enable was executed.
This is probably expected behavior for Windows Installer, since the files left behind were not put there by the Windows Installer package. In contrast, Node.js version managers would typically uninstall everything as part of their uninstall process. So in comparison leaving files behind when using Windows Installer could be unexpected and it is not explicitly documented for Node.js or Corepack.
The issue I logged here is related to your problem, but if you are using Node.js 23.7.0 which already has the fix then you shouldn't need to delete any files. A default installation should work for you.
As I suggested previously, if you want to discuss your individual situation further I would recommend that you open a new issue.
Phase out later: stop distributing Corepack (i.e. the distribution will no longer contain a corepack executable) on future (i.e. 25+) release lines of Node.js – existing release lines as well as the very next (i.e. 24.x) will keep it as experimental.
So I no longer expect any effort on issues affecting Corepack only as it is bundled into Node.js. Windows Installer msi is a sub-set of distribution / installation methods. This issue only affects Microsoft Windows and only if a Node.js version manager is not used for installation.
There is already some related workaround advice in the README document, Manual installs section, added through #637.
Activity
inoyakaigor commentedon Feb 11, 2025
@MikeMcC399 Am I getting it right in case of problem I've met in #305 I can just delete these files manually?
MikeMcC399 commentedon Feb 11, 2025
@inoyakaigor
I left the advice for you in #305 (comment).
The issue I logged here is related to your problem, but if you are using Node.js
23.7.0which already has the fix then you shouldn't need to delete any files. A default installation should work for you.As I suggested previously, if you want to discuss your individual situation further I would recommend that you open a new issue.
MikeMcC399 commentedon Mar 24, 2025
The Node.js TSC vote stated as strategy decision:
So I no longer expect any effort on issues affecting Corepack only as it is bundled into Node.js. Windows Installer msi is a sub-set of distribution / installation methods. This issue only affects Microsoft Windows and only if a Node.js version manager is not used for installation.
There is already some related workaround advice in the README document, Manual installs section, added through #637.
Closing as not expected to be fixed.