Good day, my friends. I hope you are doing well. I'm posting this today in response to a request. When I try to install " Proxmox" on my Windows 10 PC, I get an error notice that says "problem opening file for writing." Even when I put in my best effort to install it, the problem persists. Is there anyone who can assist me in resolving this issue? Any suggestions would be greatly appreciated.
Unable To Install Proxmox
- Thread starter Curtisestep
- Start date
-
- Tags
- install software windows 10
Hello,
I am not entirely sure what you are trying to do but Proxmox VE is based on the Linux distribution Debian. You cannot install Proxmox itself on top of Windows. You may be able to run a VM of Proxmox VE, but then you need to enable nested virtualization with whatever virtualization solution you are using within Windows to run PVE properly.
If you downloaded the ISO and expect it run like any other program within Windows, you won't succeed. You need to write it to a USB key using a program like balena Etcher. You can then boot from said USB key and install Proxmox from there, but that will likely mess up your Windows install. While dual booting is possible, it is not recommended.
I am not entirely sure what you are trying to do but Proxmox VE is based on the Linux distribution Debian. You cannot install Proxmox itself on top of Windows. You may be able to run a VM of Proxmox VE, but then you need to enable nested virtualization with whatever virtualization solution you are using within Windows to run PVE properly.
If you downloaded the ISO and expect it run like any other program within Windows, you won't succeed. You need to write it to a USB key using a program like balena Etcher. You can then boot from said USB key and install Proxmox from there, but that will likely mess up your Windows install. While dual booting is possible, it is not recommended.
Thank you for responding. You are correct. I'd like to install Virtual Machine on a Windows 10 PC. I can't open it since I don't have permission to do so. The problem has been resolved after adjusting the installer's security permissions.
[This is where you may find the source]
[This is where you may find the source]