Run this: sudo vmware-modconfig --console --install-all You'll see that there are issues with monitor and net, thas ok. Generate a key: openssl req -new -x509 -newkey rsa:2048 -keyout VMWARE16.priv -outform DER -out VMWARE16.der -nodes -days 36500 -subj "/CN=VMWARE/" Use this key we just generated to sign the two kernel modules: sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./VMWARE16.priv ./VMWARE16.der $(modinfo -n vmmon) sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./VMWARE16.priv ./VMWARE16.der $(modinfo -n vmnet) This does not give any feedback Check that signatures are applied correctly: tail $(modinfo -n vmmon) | grep "Module signature appended" You should get Binary file (standard input) matches Now we make this key trusted by importing it to the machine owner key (MOK) management system with the command below. sudo mokutil --import VMWARE16.der This will ask you for a password, enter a new password. Reenter the same password. Reboot, When your computer start press ESC or F12 key When rebooting you should be presented with a menu with a blue screen background, you have to make your way to enroll the key and enter the password you just created, this happens only once, then continue to boot. To test the driver/module installed correctly enter the command: mokutil --test-key VMWARE16.der After updating your Linux Operating system you need to do this process each time!!
You will get this error if you booted using legacy, not the UEFI method. It would be best if you made sure to either select the UEFI boot item in the BIOS menu or select UEFI as the default boot method.
@@wznzgq1354 It is perfectly working, there might be configuration compatibility with your computer. While your laptop is restarting press the 'ESC or F12' (This might be different on different laptops) to get the blue screen.
@@stormshadow8245 As soon as the first logo screen appears, immediately press F2. (If this does not work then search on the internet for the bios button key for your laptop)
![Путин и ПЕСКОВ ждут звонка от ТРАМПА 😁 [Пародия]](http://i.ytimg.com/vi/sm8iV0SxRHk/mqdefault.jpg)
Run this:
sudo vmware-modconfig --console --install-all
You'll see that there are issues with monitor and net, thas ok.
Generate a key:
openssl req -new -x509 -newkey rsa:2048 -keyout VMWARE16.priv -outform DER -out VMWARE16.der -nodes -days 36500 -subj "/CN=VMWARE/"
Use this key we just generated to sign the two kernel modules:
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./VMWARE16.priv ./VMWARE16.der $(modinfo -n vmmon)
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./VMWARE16.priv ./VMWARE16.der $(modinfo -n vmnet)
This does not give any feedback
Check that signatures are applied correctly:
tail $(modinfo -n vmmon) | grep "Module signature appended"
You should get Binary file (standard input) matches
Now we make this key trusted by importing it to the machine owner key (MOK) management system with the command below.
sudo mokutil --import VMWARE16.der
This will ask you for a password, enter a new password. Reenter the same password.
Reboot, When your computer start press ESC or F12 key
When rebooting you should be presented with a menu with a blue screen background, you have to make your way to enroll the key and enter the password you just created, this happens only once, then continue to boot.
To test the driver/module installed correctly enter the command:
mokutil --test-key VMWARE16.der
After updating your Linux Operating system you need to do this process each time!!
[AppLoader] GLib does not have GSettings support.
(process:60059): GLib-CRITICAL **: 09:05:02.622: g_file_test: assertion 'filename != NULL' failed
Failed to setup build environment.
Thanks for your help from France 😁
Welcome from Nepal.
Thank you SO much, I've been trying for like 3 hours to solve this problem!!
Subscribe !!
Is it working how?
@@AshwinSKumarlet me know if you are facing problem.
@@threadgeek sure
Thank you very much man , I was trying since 2 hours
Glad I could help
Followed the same procedure for Vmware 17 and it works. Thanks!
Welcome mate!
Thank you so much! it worked!
Funciono OK. con la descripcion del video, GRACIAS.
@@ManuelRodriguez-if7yc De nada, es un placer.
Thank you so much maaan u are the best, this helped me so much.
Let's connect and subscribe to the channel!
Just used this fix, also works on VMware 17.
👍
SSl error nos such file or directory .how Can i fixe that PLS?
docs.vmware.com/en/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-F93E6851-951C-4FF6-BFE0-2A05E89B3E7A.html
@@threadgeek thanks
Thanks you so much!
EFI variables are not supported on this system
You will get this error if you booted using legacy, not the UEFI method. It would be best if you made sure to either select the UEFI boot item in the BIOS menu or select UEFI as the default boot method.
love u mate
Thank you
say: sudo vmware-modconfig --console --install-all
doesn't work anymore
It is still working properly. let me know your error.
@@threadgeek i am not presented with any key choosing windows upon a reboot
@@wznzgq1354 It is perfectly working, there might be configuration compatibility with your computer.
While your laptop is restarting press the 'ESC or F12' (This might be different on different laptops) to get the blue screen.
@@threadgeek i am also not getting that screen my laptop is acer predator neo 16 dual booted to kali
@@stormshadow8245 As soon as the first logo screen appears, immediately press F2. (If this does not work then search on the internet for the bios button key for your laptop)
it's not working,
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./VMWARE17.priv ./VMWARE17.der $(modinfo -n vmmon)
modinfo: ERROR: Module vmmon not found.
i got this.
Thank you very much!