Configuration Options Grayed Out - Windows 10 Parallels 13

NorbertG1

Bit poster
Hello everyone.

I have Parallels Version 13 and installed a Windows 10 Machine. For some reason, I cannot make changes to the hardware configuration of the virtual machine. I have shut down the virtual machine and still cannot modify for example the CPU's cores or Ram allocation. These settings are grayed out.

The only way I can modify these settings is when I change the option under General Tab..... Configure for:..instead of Productivity I change it for Gaming.

Any clues????

Thanks and regards,
Norbert
 
I cannot make changes to the hardware configuration of the virtual machine. I have shut down the virtual machine and still cannot modify for example the CPU's cores or Ram allocation. These settings are grayed out.
Hi NorbertG1. Shut down the virtual machine and open the configuration window. Release the lock from the bottom left corner in the configuration window and try to change the settings.
 
Hello. The lock is unlocked and still the settings are grayed out. I had to uninstall Paralells and install again in order to make changed to the configuration settings. What can I do if this happens again in th future? Is there a fix for this issue and i dont need to uninstall and reinstall to overcome?

Thanks
Norbert
 
Hello. The lock is unlocked and still the settings are grayed out. I had to uninstall Paralells and install again in order to make changed to the configuration settings. What can I do if this happens again in th future? Is there a fix for this issue and i dont need to uninstall and reinstall to overcome?

Thanks
Norbert
Hi, the issue might be due to some misconfiguration during the installation and it should not happen again since the configuration is enabled after the reinstallation od Parallels Desktop.
 
I have the same problem as NobertG1 described. I have Parallels 13 and a brand new Mac 27". I have uninstalled Parallels and Windows 10 and reinstalled. The problem persists.
Tom
I need to know an answer to this also. Any updates to this issue?
 
Make sure you shut down the VM properly - I wasn't doing that. When in Windows, go to "Actions" in the menu bar. Then choose "Shut Down" (I was only quitting Windows, not shutting it down). After doing it properly, all was good.
Nice to know that you were able to sort it out. Thanks for sharing the info.
 
Back
Top