I built an Electron app on 64-bit windows machine and it runs well on other machines.
But today, I ran it on my 32-bit atom processor windows machine and I got the following error message.
I tried npm update but it doesn't work too.
the error message is,
How can I fix it? : (
Thank you for reading my question.
You don't have access rights. Try running as an administrator or change permissions.
Also you may try checking, if antivirus has blocked this process.
Related
I just installed the version 1.21 of pestphp/pest for a small php library.
Installations works until I try running ./vendor/bin/pest
I keep getting this error: Exclusive locks are not supported for this stream
Research on this error has proven unsuccessful as I could not find a similar case.
Please let me know if you've experienced this before and how you fixed it.
Thanks!
I have figured out the issue.
I was running the application from the htdocs of the vm version of xampp running on my laptop.
Taking the project out of here into another directory solved this issue.
Hope this saves someone else some time.
I am having problems installing new npm packages with Yarn. Every time I go on to add a new package it's throwing me this error. But when I delete my node_modules folder and run Yarn, everything works fine. Again when I try to add another package, it throws me the same error. Any solutions, I am having a headache right now.
In Windows first stop the development server and then try to install package.
I had same problem, I went into the Task Manager (CTRL+SHIFT+ESC) and killed all the NodeJs processes.
Press "Ctrl+C" to stop the server and repeat the installation.
if you're using visual studio code, cmd, or Windows Terminal, close it and run it in administrator mode. Usually, the reason for that error message is a result of limited privilege giving to the editor or npm or Yarn if you're using that.
This is likely due to you creating your project within the windows /mnt directory structure
Rerun inside the ~/home folder
(accessible within windows # //wsl$/
did you try to open CDM as run as administrator or if with wsl terminal try to use sudo like sudo yarn
The package I was trying to install before haveing this issue was yup. So resulted to
yarn add yup --legacy-peer-deps
which worked.
Sometimes when this occurs, you may first try to uncheck node_modules folder to read only.
If it is not working try to stop the running server and install your packages and then restart the server.
Terminate or stop the server ( close and reopen Vscode) and try agin. this will work for me !!
Restarting the system which causes stopping all the processes by Node, VScode, ... solved the problem.
Problem:
When I launched Ubuntu 20.04, it pops up: "Press any key to continue...", and then if I press any key, it exits immediately. This prevents me from using (typing any command) in Ubuntu WSL. (It occurred suddenly today. For the last couple of days it has been working properly.)
Screenshot: Press any key to continue pops up after startup
Attempts Tried:
LxssManager service is running. But LxssManagerUser and LxssManagerUser_60d78 are stopped. Manually starting the two services doesn't help as they automatically stop themselves right afterwards.
Hyper-V service is set to auto. Virtualization mode is enabled (task manager -> performance -> CPU)
Trying to re-run the update from here https://learn.microsoft.com/en-us/windows/wsl/wsl2-kernel, but it shows WSL not installed (which is weird since I have been using it for a long time before)
Environment:
OS: Microsoft Windows 10 Family, Insider Preview
Version: 10.0.20152 Version 20152
System Type: x64 based
I'd accidentally mounted the WSL virtual disk image by double-clicking it in explorer, and it remained mounted to my machine even though it reported an error that made having it mounted useless. Unmounting the vdisk from Disk Management resolved the issue for me.
From https://github.com/microsoft/WSL/issues/4177#issuecomment-597736482
There is a conflict between wsl.exe and Proxifier.
Developers of Proxifier gave a solution.
Thanks for the info.
We have reproduced this issue. Apparently, wsl.exe displays this error
if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call
for wsl.exe to prevent this. Under the hood the call creates an entry
for wsl.exe at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the
parameter: NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.
And it works well for me!
This worked magic! Go to the Windows Command Prompt and run the following command:
netsh winsock reset
Then Restart your computer. NB: Don't Shutdown since it did not work for me. Instead, Restart!
More answers can be found here.
I solved by downloading the https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msimsi and excuting it.
see https://learn.microsoft.com/en-us/windows/wsl/wsl2-kernel
I went into the bios and had to enable virtualization from there
if you got this error:
An operation was attempted on something that is not a socket.
there is something wrong with windows sockets and try this command in cmd administrator mode to reset windows sockets.
1. netsh winsock reset catalog
2. netsh int ipv4 reset reset.log
3. netsh int ipv6 reset reset.log
4. Restart the computer.
Maybe not relevant for TO but I had the same issue and just had to run in Windows Terminal:
wsl --shutdown
After that Ubuntu worked again.
powershell => type "wsl --shutdown" => error message
ctrl-alt-del => services => HvHost => right button => restart (think to stop all hyperv virtual machines before ?)
powershell => type "wsl" => OK
restart hyperv virtual machines
I have installed Ubuntu 18.04 for windows subsystem for linux on windows 10, after enabling WSL in Powershell (instructions here: https://learn.microsoft.com/en-us/windows/wsl/install-win10).
I've done this before on a desktop but now I'm doing it on a laptop. I had no issues with the previous installation but this time around ubuntu will not launch. I get the ubuntu console popping up briefly before disappearing.
Also trying to run bash.exe from the command line fails silently (doesn't hang, just exits with no message), which may be related.
I'm struggling to figure this out as I have no idea where any error messages might be logged. Does anyone know how I can investigate further why this is happening?
Setup is a windows 10 Pro, os build 17134.376, everything up to date.
I'm struggling to figure this out as I have no idea where any error messages might be logged. Does anyone know how I can investigate further why this is happening?
Check with wslconfig.exe /l all registered distros, try to deregister the one you have problem with ( e.g. wslconfig.exe /u Ubuntu [^1]) and run the ubuntu.exe in your distro once again. Just a wild guess, it might be also a problem, if you have more than one copy of the linux distribution in you home directory.
[^1]: Warning: deregistering will delete all the associated files!
I had installed the create-react-app with no build configuration in my windows10 Pc got this error. I try in administrator role also I got this same error
if any one knows please tell me how to resolve
Run with antivirus disabled (if you use Windows Defender, turn off Real-Time protection and Cloud-based protection).It worked for me!
Hope it Helps!!!
Try with yarn or lower npm version.
https://yarnpkg.com/lang/en/docs/cli/create/
Hope issue will be fixed.