npm install fails on Windows: "Error: EPERM: operation not permitted, rename"

[barbalex]

I work on Windows 10, up to date installation. npm i runs in powershell node v5.2.0 npm v3.3.12

This error occures every time. I have repeated 5 times, deleting the node_modules folder beforehand. I have also run it twice as administrator. It works on my OsX notebook.

Here the error message in powershell:

npm WARN EPACKAGEJSON ae@1.0.0 No repository field.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i"
npm ERR! node v5.2.0
npm ERR! npm  v3.3.12
npm ERR! path C:\Users\alex\ae\node_modules\.staging\escope-b5ac5ca528edb372dbff854e4a2941fb
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename

npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\alex\ae\node_modules\.staging\escope-b5ac5ca528edb372db
ff854e4a2941fb' -> 'C:\Users\alex\ae\node_modules\escope'
npm ERR!     at Error (native)
npm ERR!  { [Error: EPERM: operation not permitted, rename 'C:\Users\alex\ae\node_modules\.staging\escope-b5ac5ca528edb3
72dbff854e4a2941fb' -> 'C:\Users\alex\ae\node_modules\escope']
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\Users\\alex\\ae\\node_modules\\.staging\\escope-b5ac5ca528edb372dbff854e4a2941fb',
npm ERR!   dest: 'C:\\Users\\alex\\ae\\node_modules\\escope',
npm ERR!   parent: 'ae' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\alex\ae\npm-debug.log

This is the complete log from npm-debug.log: https://gist.github.com/barbalex/da6100299bf5b76f19c2

This is the project: https://github.com/barbalex/ae This is package.json: https://github.com/barbalex/ae/blob/master/package.json

[richardscarrott]

I was getting the same issue, npm cache clean fixed it for me :)

[barbalex]

@richardscarrott : thanks, will try that next time. Unfortunately this type of issues keep happening to me quite often so your tipp could turn out to be very helpful.

Don't ask me why but the next morning this issue had disappeared and npm i works nicely. So I close the issue but I'm quite sure it will return for me.

[defmans7]

I disabled Avast which allowed me to get around this issue. https://www.webfoobar.com/node/39

[hsingh23]

Why was this issue closed? What was the root cause of this problem? Do we have to clear cache for every install?

[mohanr]

npm ERR! Error: EPERM: operation not permitted, open 'D:\WebstormProjects\Frisby \node_modules\karma\node_modules\isbinaryfile\test\fixtures\pdf.pdf'

It happens. I run as admin.

[kneerunjun]

Yeah! npm cache clean worked for me too! cheers :wine_glass:

[ganeshran]

npm cache clean fixed the issue for me too

[franklin-vidal]

Check if another application is using the project folder, like Atom editor. In my case i close Atom, run node and open editor again.

[john-osullivan]

I've gotten this issue in the past (and just got it again, prompting me to Google and remember) when the project folder I'm operating on is within Dropbox. Particularly after running generate commands which suddenly produce a lot of files, it seems like Dropbox's syncing code locks up files and prevents NPM from renaming as necessary.

[linfangwu]

Open cmd prompt by right clicking and then click "open as administrator"

[priiduneemre]

Also, be sure to disable your anti-malware and antivirus software temporarily. This solved the problem for me (Windows Antimalware Service & Avast Free Antivirus in my case).

[chrahunt]

I had this same issue and none of the above solutions worked. The specific operation that failed was

npm ERR! Error: EPERM: operation not permitted, rename 'c:\[...]\node_modules\node-sass' -> 'c:\[...]\node_modules\.node-sass.DELETE'

It seems like the problem was that .node-sass.DELETE already existed, as moving it allowed the installation to proceed.

[UnderZerOx]

@richardscarrott | TY, worked for me.

[Sandiejat]

yes, seems like either anti-virus is locking the installation folder for that particular file or the user is not with elevated rights. Disabling McAfee worked for me.

[mohanr]

I did something similar. Fixed many such problems. But in my case the scanner rules were updated after the security team looked at the logs.I didn't disable the scanner. That is an extreme measure.

Mohan

On 25 June 2016 at 06:55, Sandeep Verma notifications@github.com wrote:

yes, seems like either anti-virus is locking the installation folder for that particular file or the user is not with elevated rights. Disabling McAfee worked for me.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/npm/npm/issues/10826#issuecomment-228499391, or mute the thread https://github.com/notifications/unsubscribe/AAWamtcFRjCekuJJXFV1t2AhufAB3fzOks5qPIOCgaJpZM4G1m67 .

[johnwonder]

npm cache clean fixed the issue for me too

[southnan0]

what is means in npm of -4048

[happy2share]

I don't know which steps worked for me. But these are my steps to get rid of this error:

1) Updated Node.js 2) Ran npm cache clean command in Command prompt ( With some element of doubt for cache presence) 3) Ran reactive-native init in command prompt as Administrator (on Windows OS), hoping works well with sudo reactive-native init on Mac OS

[7xrobin]

npm cache clean fixed the issue for me too

[mkdonz]

C:\xampp\htdocs\application>npm install npm -g npm ERR! Windows_NT 10.0.10586 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "npm" "-g" npm ERR! node v6.3.1 npm ERR! npm v3.10.3

npm ERR! shasum check failed for C:\Users\user\AppData\Local\Temp\npm-7496-120e7f31\registry.npmjs.org\npm-\npm-3.10.5.tgz npm ERR! Expected: 4753bfbb1526077d61c3b6a251cff61a22206cc6 npm ERR! Actual: 6e854f06f38ed2c4cde49a94189cc1a3b045b238 npm ERR! From: https://registry.npmjs.org/npm/-/npm-3.10.5.tgz npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request: npm ERR! C:\xampp\htdocs\application\npm-debug.log

Can anyone assists me wit that error

[danielrf121]

NPM Cache Clean not work for me. I download old versions but It keeps happening the same error.

npm ERR! Windows_NT 10.0.10586 npm ERR! argv "E:\nodejs\node.exe" "E:\nodejs\node_modules\npm\bin\npm-cli.js" "i" npm ERR! node v4.4.7 npm ERR! npm v2.15.8

I have even installed node in other directories outside the C: / and yet still the same problem. Any fix for this?

Using windows 10.

[fawwaz]

I still got a problem, npm cache clean does't work for me. i've run the program as administrator.

This will walk you through creating a new React Native project in E:\S2\for fun\belajar react\belajarreactnative\belajar
Installing react-native package from npm...

> spawn-sync@1.0.15 postinstall E:\S2\for fun\belajar react\belajarreactnative\belajar\node_modules\react-native\node_modules\yeoman-generator\node_modules\cross-spawn\node_modules\spawn-sync
> node postinstall

npm WARN peerDependencies The peer dependency react@~15.3.0 included from react-native will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Asus\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save" "--save-exact" "react-native"
npm ERR! node v4.4.5
npm ERR! npm  v2.12.1
npm ERR! path C:\Users\Asus\AppData\Roaming\npm-cache\babel-runtime\6.11.6\package\package.json.e85a9ea0e36f7c5d62de3633a498cbbc
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename

npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\Asus\AppData\Roaming\npm-cache\babel-runtime\6.11.6\package\package.json.e85a9ea0e36f7c5d62de3633a498cbbc' -> 'C:\Users\Asus\AppData\Ro
aming\npm-cache\babel-runtime\6.11.6\package\package.json'
npm ERR!     at Error (native)
npm ERR!  { [Error: EPERM: operation not permitted, rename 'C:\Users\Asus\AppData\Roaming\npm-cache\babel-runtime\6.11.6\package\package.json.e85a9ea0e36f7c5d62de3633a498cbbc' -> 'C:\Users\Asus\AppDat
a\Roaming\npm-cache\babel-runtime\6.11.6\package\package.json']
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\Users\\Asus\\AppData\\Roaming\\npm-cache\\babel-runtime\\6.11.6\\package\\package.json.e85a9ea0e36f7c5d62de3633a498cbbc',
npm ERR!   dest: 'C:\\Users\\Asus\\AppData\\Roaming\\npm-cache\\babel-runtime\\6.11.6\\package\\package.json',
npm ERR!   parent: 'babel-plugin-transform-es2015-block-scoping' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\S2\for fun\belajar react\belajarreactnative\belajar\npm-debug.log

`npm install --save --save-exact react-native` failed

i am using windows 8.

[danielrf121]

I think I found my problem. I installed NPM still on windows 8.1 and it worked perfectly. I upgraded to Windows 10 and it was then that stopped working. This transition from Windows 8.1 to 10 that made something come out of the place with the NPM. I formatted my computer for windows 10 factory removing all programs. Installed all again and again NPM run beautifully. Who made this update windows, try formatting, the one that had something here. Hug.

[squarewave24]

at least on windows, I had to do "npm cache clean" 5 times. each time it would get stuck on a different component until all of them got updated. maybe there is a neater way to do npm reinstall.

[xersist]

I'll give my two cents on this. I had the same issue and npm cache clean did nothing for me either. At the point of frustration I was just going to restart my machine and noticed that it had updates to install. I just let it (Windows 10) and when I tried again without clearing anything or deleting the node_modules directory everything was working again.... so far.

[hheennrryy21]

Hey guys, I was tackling this for 3 hours straight and finally found the problem. Well, I had a similar problem but instead I was trying to install phonegap and had a EPERM: operation not permitted, rename the file t_module .DELETE. What I ended up doing was 1)disabling the anti-virus 2) executing [npm cache clean], 3) deleting the t_module.DELETE file. Then on step 4) I ran[ npm install -g phonegap@latest]. This should work, of course the t_module would be the file in question. t_module is a file name I just made up. In my case it was .phonegap.DELETE

Hope it helps someone out there

[amellnik]

Similar to what @john-osullivan reported with Dropbox, Syncplicity also causes issues and should be disabled.

[eTorAken]

I tried everything listed here but nothing fixed my problem (I'm runnning on a Surface Pro 3 and it seems that security has been pushed too far).

The thing that resolved my case was to give my session full access control on the Program Files (x86)/nodejs folder by doing right click -> Properties -> Security -> Modify -> Select my user -> Authorize total control.

[luisbd]

Samething here:

1. disabled anti-virus
2. npm cache clean

Issue solved.

[LooxooTremo]

I did the same thing npm cache clean, and it didn't work because my %appdata%/Roaming/node/node_modules contained a strongloop folder already in use and unremovable. So you might need to kill a nodejs process in order to install it ;) Hope it helps

[summitmman-zz]

The issue occurs generally because npm tries to rename the file when the antivirus software is still scanning the files. The ideal solution to this is to disable the antivirus software, npm cache clean and then try installing. But I use my office machine for work in which i needed to install angular-cli using npm, and such machines have antivirus enabled, to disable which will require a long time consuming process from the IT team.

Found a simple solution to this. -Reboot your system, but in "Safe Mode With Networking" (you usually get this option by pressing F8 on reboot, for desktops) -npm cache clean -Then try installing.

It worked for me and did not have to follow the long process of getting permissions to disable the antivirus from the office.

Cheers!!!

[VishalGulati]

I executed the command npm cache clean but still getting the same error. Anyone having any idea about it, please share. Kindly see my error desciption on stackoverflow: http://stackoverflow.com/questions/40241392/postinstall-command-in-package-json-fails-with-error-windows-nt-6-2-9200-on-azur

[JulianH99]

closing every program using the folder worked for me, like sublime text or prepros

[clarkworld]

Thanks everyone for the details. I had a auto start program in the background holding onto the folder not letting the upgrade process. Once I killed that I was good to go.

[njanmelbin]

I got the previous error cleared but i am getting new error now. still windows

(node:8384) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

> bcrypt@0.8.7 install C:\Users\Thomas\my-api\node_modules\bcrypt
> node-gyp rebuild

C:\Users\Thomas\my-api\node_modules\bcrypt>if not defined npm_config_node_gyp (node "C:\Users\Thomas\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild )
(node:8104) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading 64-bit node.lib
gyp ERR! stack     at Request.<anonymous> (C:\Users\Thomas\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\install.js:403:20)
gyp ERR! stack     at emitOne (events.js:101:20)
gyp ERR! stack     at Request.emit (events.js:188:7)
gyp ERR! stack     at Request.onRequestResponse (C:\Users\Thomas\AppData\Roaming\npm\node_modules\npm\node_modules\request\request.js:985:10)
gyp ERR! stack     at emitOne (events.js:96:13)
gyp ERR! stack     at ClientRequest.emit (events.js:188:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:474:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:363:20)
gyp ERR! stack     at emitOne (events.js:96:13)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Thomas\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Thomas\my-api\node_modules\bcrypt
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Thomas\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.9.1
npm ERR! npm  v2.12.1
npm ERR! code ELIFECYCLE

npm ERR! bcrypt@0.8.7 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt@0.8.7 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the bcrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Thomas\my-api\npm-debug.log

[CSchulz]

I am using npm install --cache cache to use a local cache folder without success.

[avatar21]

I'm facing the same issue ... on Windows 10 I tried npm cache clean

However the main reason could be due to I've node task in the background killing the node process and retry helps ...

[hvpulok]

npm cache clean helped me! Thanks

[jeneser]

npm cache clean helped me! Thank you very much!

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 4.4.0-38-generic
npm ERR! argv "/home/jeneser/Tools/nvm/versions/node/v7.2.1/bin/node" "/home/jeneser/Tools/nvm/versions/node/v7.2.1/bin/npm" "install"
npm ERR! node v7.2.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! bcrypt@0.8.7 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the bcrypt@0.8.7 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the bcrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs bcrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/jeneser/workspace/hpu-api/npm-debug.log

[jay4smile]

npm cache clean is not worked for me. I have deleted all the folders in App Data/roaming related to node. and again started from scratch, and it worked for me!

[lloyddugmore]

Tried cache clean and disabling McAfee.... no luck with npm install -g yo generator-angular2

[scipper]

I got an error like:

bootstrap_node.js:158 throw err; ^ Error: EPERM: operation not permitted, open 'C:\Users\user\.node_repl_history' at Error (native)

Deleting C:\Users\user\.node_repl_history helped.

[mescalito]

@eTorAken thanks! good idea. I solved the problem by changing windows user access for the older:

Here is a screenshot: http://prntscr.com/djdn0g

[hishamkaram]

on Windows disable McAfee(real time scanning and firewall) then use npm cache clean

[pescweb]

Ok gente ja conseguir instalar. Como? 1. Desativei o Anti Virus 2. Acessei a C:\Users\Users\AppData\Roaming e deletei as pastas npm e npm-cahce 3. Re- instalei o cordova e Pronto.

[vayodya]

$ npm install npm WARN deprecated es6-module-loader@0.17.11: This project has been deprecated for "npm install es-module-loader" based on the newer loader spec. npm WARN deprecated node-uuid@1.4.7: use uuid module instead

angular2-test@1.0.0 postinstall F:\projects\angular2-test typings install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN angular2-test@1.0.0 No description npm WARN angular2-test@1.0.0 No repository field. npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" npm ERR! node v6.9.2 npm ERR! npm v3.10.9 npm ERR! file C:\WINDOWS\system32\cmd.exe;C:\Program Files\MongoDB\Server\3.0\bin npm ERR! path C:\WINDOWS\system32\cmd.exe;C:\Program Files\MongoDB\Server\3.0\bin npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn C:\WINDOWS\system32\cmd.exe;C:\Program Files\MongoDB\Server\3.0\bin npm ERR! angular2-test@1.0.0 postinstall: typings install npm ERR! spawn C:\WINDOWS\system32\cmd.exe;C:\Program Files\MongoDB\Server\3.0\bin ENOENT npm ERR! npm ERR! Failed at the angular2-test@1.0.0 postinstall script 'typings install'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the angular2-test package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! typings install npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs angular2-test npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls angular2-test npm ERR! There is likely additional logging output above. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN angular2-test@1.0.0 No description npm WARN angular2-test@1.0.0 No repository field. npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" npm ERR! node v6.9.2 npm ERR! npm v3.10.9 npm ERR! code ELIFECYCLE

npm ERR! angular2-test@1.0.0 postinstall: typings install npm ERR! Exit status -4058 npm ERR! npm ERR! Failed at the angular2-test@1.0.0 postinstall script 'typings install'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the angular2-test package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! typings install npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs angular2-test npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls angular2-test npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! F:\projects\angular2-test\npm-debug.log

I fixed it above error by install OS again as fresh copy because I had windows 8.1 and I upgrade it to 10. I think because this transition this error occurred.

[ghost]

D:\test\react>npm install react --save npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "react" "--save" npm ERR! node v6.9.2 npm ERR! npm v3.10.9 npm ERR! code ENOSELF

npm ERR! Refusing to install react as a dependency of itself npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request: npm ERR! D:\test\react\npm-debug.log

I have same issue.

[ghost]

I reinstall node 4.4.5. And it worked.

[ghost]

Hello, everybody. I think node v4.4.5 is very comfortable. Please use it. Thank you.

[CorsCode]

Running the install on a USB/Cloud folder will cause this issue EVERY TIME. If running cache clean won't fix it, recommend pulling files from source to local machine, then pushing edits to the source.

This is the easiest and perhaps best way to solve this issue.