Have you tried installing an NPM package and have been presented with errors similar to “npm ERR! Error: EACCES: permission denied”? Chances are likely that you are using WSL (Windows Subsystem for Linux) and issuing commands from within VSCode terminal emulator.
Sadly, I will be unable to give you instructions on how to fix this. However, it seems to only occur whilst using the VSCode Terminal connected to a WSL.
To get around this, I have found that closing VSCode (all VSCode instances that are connected to the WSL) and issuing the command through the “app” terminal instead. You should now be able to install as normal!
Through some rigorous troubleshooting steps on a Ryzen 1700x recently, I have discovered that Ryzen Master was the cause of instability.
I am unable to rule out the suggestion that RAM compatibility might be part of the issue, however many symptoms have been fixed after removing Ryzen Master from the system.
Stuttering/Choppiness during games
Random FPS drops during games
Crashes during games
RM was installed on the system as a tool to monitor temps and voltages and was not intended to overclock. Having a search around, I read that Ryzen Master (once installed) uses a “default” profile. The default profile apparently comes with an overclock (which I was unaware of)
After removing Ryzen Master from the system, games instantly ran as expected. CS:GO no longer randomly stutters or freezes. Overwatch is as smooth as silk.
I would actually go as far as to recommend not using Ryzen Master for anything. At all. Seriously..
I read a somewhere that Ryzen Master was used to overclock the CPU. The issue arose when they tried to reverse the overclock. RM apparently overrides BIOS settings so resetting the BIOS is futile.
After removing Ryzen Master from Windows, they found that the overclock was still active. Flashing the BIOS still didn’t help. The solution was to reinstall Windows as Ryzen Master settings (somewhere) were still changing BIOS settings when Windows has been booted.
Sure, this part of my post is heresay, however after learning of this experience and solving my own issue, I will be sure not to install RM again (even of it is purely for monitoring purposes). If you plan to overclock, go old school!
Since Demember 2018, I have been experiencing long reboots and shutdown times. Alot of people have pointed out that the Reaktek drivers might be to blame for this issue. Uninstalling the latest driver and using an older version does seem to “fix” the issue out (until Windows update decides to install the latest drivers again)
I decided to try my luck again and try and fix this problem, and I found the solution.
There wasn’t a newer Realtek driver available so I decided to update my Ryzen 5 Mobile Graphics drivers. The Graphics driver didn’t seem to fix the problem, so I moved on to the Ryzen Mobile chipset drivers.
After a quick reboot, it seemed to have fixed the issue!