Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't install amplify globally on windows

See original GitHub issue

I am trying to install amplify, but get this output in console:

npm ERR! code EPERM
npm ERR! syscall rename
npm ERR! path C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\cli
npm ERR! dest C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\.cli-HbiUvD7o
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\cli' -> 'C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\.cli-HbiUvD7o'
npm ERR!  [Error: EPERM: operation not permitted, rename 'C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\cli' -> 'C:\Users\andre\AppData\Roaming\npm\node_modules\@aws-amplify\.cli-HbiUvD7o'] {
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\Users\\andre\\AppData\\Roaming\\npm\\node_modules\\@aws-amplify\\cli',
npm ERR!   dest: 'C:\\Users\\andre\\AppData\\Roaming\\npm\\node_modules\\@aws-amplify\\.cli-HbiUvD7o'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\andre\AppData\Local\npm-cache\_logs\2021-01-09T01_29_15_042Z-debug.log

I have tried to disable Windows Defender, run PowerShell as administrator, use CMD instead of PowerShell, clean npm cache, use --unsafe-perm=true. Nothing did work.