Skip to content
This repository has been archived by the owner. It is now read-only.

ERR! code EBUSY, ERR! errno -4082 #7370

Closed
GhostMouse opened this issue Feb 16, 2015 · 30 comments

Comments

@GhostMouse
Copy link

commented Feb 16, 2015

I'm getting this when I run npm install -g node-inspector

Help, pls :)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "node-inspector"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! path C:\Users\user\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws
npm ERR! code EBUSY
npm ERR! errno -4082

npm ERR! EBUSY, unlink 'C:\Users\user\AppData\Roaming\npm\node_modules\nodeinspector\node_modules\ws'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! error rolling back Error: EBUSY, unlink 'C:\Users\user\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws'
npm ERR! error rolling back     at Error (native)
npm ERR! error rolling back  { [Error: EBUSY, unlink 'C:\Users\user\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws']
npm ERR! error rolling back   errno: -4082,
npm ERR! error rolling back   code: 'EBUSY',
npm ERR! error rolling back   path: 'C:\\Users\\user\\AppData\\Roaming\\npm\\node_modules\\node-inspector\\node_modules\\ws' }
@smikes

This comment has been minimized.

Copy link
Contributor

commented Feb 16, 2015

It looks like one of the files npm needs to write to in order to do the installation is locked by another process. The first line approach to fixing this on Windows is to reboot. :-/

@AMEDOO

This comment has been minimized.

Copy link

commented Mar 24, 2015

I'm getting also the same problem, even when after rebooting windows.
Solution?

@smikes

This comment has been minimized.

Copy link
Contributor

commented Mar 24, 2015

AMEDOO, can you create a new issue so we can track it and follow up separately? When you do, please attach your npm-debug.log as a gist https://gist.github.com

@AMEDOO

This comment has been minimized.

Copy link

commented Mar 24, 2015

DONE :)

@ktstowell ktstowell referenced this issue Apr 27, 2015
@ehsalazar ehsalazar self-assigned this Aug 11, 2015
@ehsalazar

This comment has been minimized.

Copy link

commented Aug 11, 2015

We haven’t heard back and we’re trying to clean up some old issues.  If this is still a problem, can you please reply and let us know?  We’ll be happy to reopen if necessary.

@ehsalazar ehsalazar closed this Aug 11, 2015
@mattglynn

This comment has been minimized.

Copy link

commented Jan 18, 2016

this is still an issue
I'm trying to install abao

@vcernomschi

This comment has been minimized.

Copy link

commented Mar 3, 2016

This issue is reproducible only for Windows. Got it only one time when I had tried to install deepify npm install -g deepify (https://www.npmjs.com/package/deepify) on Windows. Rebooting helped to solve the issue.

@EugeValeiras

This comment has been minimized.

Copy link

commented May 18, 2016

C:\Users\eugen\workspace\JHipster\lecopCentral>npm install -g yo
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
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" "-g" "yo"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path C:\Users\eugen\AppData\Roaming\npm\node_modules\yo\lib\cli.js
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\eugen\AppData\Roaming\npm\node_modules\yo\lib\cli.js'
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\eugen\AppData\Roaming\npm\node_modules\yo\lib\cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\eugen\workspace\JHipster\lecopCentral\npm-debug.log

Same issue here

@IsuruCham

This comment has been minimized.

Copy link

commented Jun 22, 2016

Did any of you managed to find a solution? This is really annoying. I cannot install any of the modules through npm and literally I cannot continue my work. Please respond anyone

@EugeValeiras

This comment has been minimized.

Copy link

commented Jun 22, 2016

@IsuruCham I re-installed Node and everything start working again.

@IsuruCham

This comment has been minimized.

Copy link

commented Jun 23, 2016

@EugeValeiras I also reinstalled node two times, restarted the PC. Not solved the problem :(

@EugeValeiras

This comment has been minimized.

Copy link

commented Jun 27, 2016

@IsuruCham what version of node did you install?? Install the 4., I pretty sure you have installed the 6. version.

@echorohit

This comment has been minimized.

Copy link

commented Aug 24, 2016

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "-g" "cordova"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path C:\projects
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rename

npm ERR! EBUSY: resource busy or locked, rename 'C:\projects' -> 'C:\.projects.DELETE'
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:\projects\npm-debug.log


$ npm -v
3.8.3


$ node -v
v5.10.1

I am facing the same problem. I am not able to proceed.

@yunfeihuang

This comment has been minimized.

Copy link

commented Aug 26, 2016

same issue

@yunfeihuang

This comment has been minimized.

Copy link

commented Aug 26, 2016

Did some one had resolve this issue? Rebooting is sames no use for me.

@yunfeihuang

This comment has been minimized.

Copy link

commented Aug 26, 2016

I hate windows.

@sureshsivan

This comment has been minimized.

Copy link

commented Sep 13, 2016

@yunfeihuang - mee tooo....

@fitra90

This comment has been minimized.

Copy link

commented Sep 17, 2016

try "npm cache clean" on cli
sometimes works, but not always

@EugeValeiras

This comment has been minimized.

Copy link

commented Sep 17, 2016

Remove your current node and install version 4.*

@RakeshVenkat

This comment has been minimized.

Copy link

commented Nov 8, 2016

I faced the same issue and got a Resolution from Article: [https://github.com//issues/8564]. I am using Windows 7 Enterprise. Solution was to Uninstall 'ByteFence Anti Malware' Software.

@legodude17

This comment has been minimized.

Copy link
Contributor

commented Nov 8, 2016

@RakeshVenkat gives a good solution. Make sure to close all other programs. If that doesn't work try disabling your anti malware software.

@willstorm

This comment has been minimized.

Copy link

commented Jan 27, 2017

@RakeshVenkat save my day :)

@wallacerodrigon

This comment has been minimized.

Copy link

commented Feb 7, 2017

RakeshVenkat, thanks a lot for your contribution. I waste much time by installing and uninstalling nodejs (4.x, 5.x, 6.x, 7.x) to figure out what's happening with that "lock..." and when I almost gave up, I found your post some minutes ago with a good solution: uninstall ByteFence. Thank God and Rakesh as well.

God bless you, guy!

@Rahulkishanm

This comment has been minimized.

Copy link

commented Feb 7, 2017

@RakeshVenkat Thanks a lot

@jkomyno

This comment has been minimized.

Copy link

commented Feb 20, 2017

In my case I had to forcefully arrest adb.exe because it was holding myProject/node_modules/realm/android in a React Native project (I was removing node_modules/ to perform a new "npm install" again, due to this issue). To find which process is blocking a certain file/folder, I'd suggest y'all follow this post.

@karthiksundar

This comment has been minimized.

Copy link

commented Feb 26, 2017

@RakeshVenkat Thanks for the suggestion. Works for me now.

@girishbalanagu

This comment has been minimized.

Copy link

commented May 12, 2017

npm cache clean is resolve this issue.

@frutality

This comment has been minimized.

Copy link

commented Jun 27, 2017

I don't have ByteFence Anti-Malware or any anti-malware software except default Windows Defender. It always was like this, but few weeks ago I saw this error message when tried to npm run watch with webpack.

Workaround for me is vagrant reload command. After that I can run npm run watch without problems, but only for once. If I stop watching and run, for example, npm run build, then I see error again. And again, after vagrant reload no problems with building or watching.

I never had this problem before, for months. I am using default file syncing method between host and guest, didn't changed configs, didn't upgrade npm/node or guest OS. I believe the problem is Windows, but I cannot understand, why it was never be a problem for a long time before. And what is solution really, not workaround.

@oceanmachine89

This comment has been minimized.

Copy link

commented Jan 26, 2018

Hi guys,
I too am having this issue.I'm running Windows 7 professional with node 9.4.0 and npm 5.2.6.Any help would be greatly appreciated as I have tried restarting the computer,disabling the anti virus and the windows defender and other solutions so far that I have seen and no result.

2018-01-26T09_58_06_335Z-debug.log

@krishnpalchouhan

This comment has been minimized.

Copy link

commented Feb 18, 2018

npm install --force

clear all file from
C:\Users\chouhank\AppData\Local\Temp
C:\Users\chouhank\AppData\Roaming\npm-cache
ignore if it's not able to delete all
restart your system
then try to install using -- force option

My issue is resolved with this

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
You can’t perform that action at this time.