Nothing about the faster, snappier response?, nothing about Video card enhancing capability? Nothing about it taking advantage of the new RTX video card? ability to use 32 core on 5950X? better memory management of those who have 64-128 DDR5/DDR4 memory? More compatibility with DirectX12? ... the upgrade is basically on ...... encryption... wow.
My biggest let down is that I am unable to use with my Xeon X5670. I had to revert back to 16. Make sure you have a "compatible 64-bit x86/AMD64 CPU launched in 2011 or later".
I used both VMware workstation and virtual box under windows and managed to get them both to auto start (and stop before shutdown) their VMs, but disliked the rigged solution and ultimately put them under ESXi and simply forget about them. I probably will use VMware workstation again under windows to go, as a portable lab.
I don't suppose this Workstation version has a feature to simulate a TPM 2.0 module? That sure would be a helpful feature as my hardware lacks a TPM. It's not that old, but I'm not ready to upgrade everything as I don't know what the requirements of Windows 12 will be.
I have workstation pro 16 on an older pc. I need to replace my pc now and I see a lot of online comments about how workstation pro does a bad job of managing performance vs efficient cores on the host. Is this still a problem?
Hello Sir, i'am working now in my new job. and try to seek some of your videos about VMware workstation 17pro. im here in a remote area, i wish i could have this app. hope tou can help me in the future. thanks
I have VMWare Pro installed on client computers on a domain. The clients cannot add VMNets because they don’t have admin rights. Is there a way around this?
There is two major bugs on WS17, 1.If you autostart vms through the new ui process then you cannot manage your vms through the console, seems as they are not started but they are running and the only way to manage them is via other console methods (RDP,VNC,Ssh) dependent on the Os flavour, this is kind of annoying for not being tested by VMware. 2. If your VMs have enabled the "3D support" options under VGA Device and they have assigned more VRam they cannot even start, the Vmware workstation kernel halts with error and the vms cannot be started, although if you uncheck the 3D option you can start the VMs and workaround the issue. These 2 are my findings on 2days before upgraded from 16.x, i hope it will stop there and fixed on 17.x patch update from VMw. What the hell VMware.. in any new version always supplies new features and breaks others that worked fine for ages.. (eg the CBT Bug on ESXi 7.x that returned.. same shit on 4.1, 5.5 and first 6.x versions) all on them fixed in later versions but if using vsphere on production after every upgrade there is a "Black" Friday
worse yet is if your VM has a desktop GUI - you can't connect to it if it is autostarted. In my case I have WS17 pro and autostart a fedora desktop. I rarely need / want the desktop for Fedora, but I'm still trying to figure out how to use it when it is needed other than stopping the autostart and starting via the Workstation GUI oh and my use case... Selenium testing / debugging.. It would kinda be nice to see that browser to help create the selenium script.
In the latest update 17.0.1 Vmware fixed the issue with vram setting on virtual vga but did not fixed the autostart option, still if you set a vm to automatically start on system boot 🥾 with autostart service you are unable to get virtual machine's console while the vm is running
@@rontidd6551 Fuck Auto-start option an take a look what i did an managed to get over this situation, create a batch file eg Startvms.cmd edit it and place the following line "c:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws start "c:\VM\VM.VMX" nogui -cutomize the path of your .vmx- save the startvms.cmd and place it on your system startup by copying it to the following path C:\Users\xx-yourusername-xxx\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup then reboot the system and logon (if you have a password you can set system to auto logon and then lock) by doing the following your vm will start without seeing nothing on the desktop but the magic comes that if you open vmware workstation app you ll see normally the play button on your vm and of course the vm console will be accessible. Try it and tell me
Another bug: If a VM is under a tree folder, it will not show up in the Auto Start VM list. You have to move the VM to the root to be able to select the VM for auto start.
i switched from Windows to Linux, been using VMWARE for years. Had VMware 16 on Windows running a Windows vm for torrents/etc, everything worked fine. Got linux going, installed VMware 16,... updated to 17 and the shit broke. lagged like hell so i had to go back to version 16. Maybe its something with Linux running Windows that caused a glitch cause i'm using an Nvidia card. AMD card is on the way, so i'll test this theory and get back to ya if i can remember...
Jason thank you for the comment please do let us know on that front. It being a .0 release I'm sure a patch is forthcoming soon to squash the initial bugs.
@@VirtualizationHowto I switched back to Windows for work-related reasons and so i could play PC games, but i use Linux Mint at work with VMware running Windows 11 and no issues. That PC is using an Nvidia GT 710. Not a problem at all with Linux running Windows in a VM. Hope this helps :)
@DikiciBurak thank you for the comment! The 64 GB limit is per virtual machine, not total. See the official link here: docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-023888CC-5252-4EC3-AB3C-D7CEAD306CCC.html
I see. But the problem for me is that i am going run eve-ng in one vm. Thats why i wonder the limit of ram per vm. Maybe i should think of using hyperv in this case. My notebook doesnt support esxi by the way.
I switched to hyper-v after many many issues with past versions of VMware workstation. How stable is it? Does it crash on AMD filter driver or exhibit strange behavior on certain Intel chipset software on the host?
Thank you for the short intro. Autostart is the big new feature, really great for me as a consultant, but upgrade 17 major only one feature is an expensive upgrade feature though.
yes been using vmware workstation since ver 10 love the new auto-start feature 🙂
It's not a new feature, it was there in version 16 but en few build later gone.
Great review!
Nothing about the faster, snappier response?, nothing about Video card enhancing capability? Nothing about it taking advantage of the new RTX video card? ability to use 32 core on 5950X? better memory management of those who have 64-128 DDR5/DDR4 memory? More compatibility with DirectX12? ... the upgrade is basically on ...... encryption... wow.
I'm confused. Does it have these improvements or does it only have improvements in its OS encryption?
I'm getting a 5700x CPU, does that benefit in any way?
My biggest let down is that I am unable to use with my Xeon X5670. I had to revert back to 16. Make sure you have a "compatible 64-bit x86/AMD64 CPU launched in 2011 or later".
A pity they have not given IPv6 as an option for networking. I feel thy are silly in not offering that as more and more move to it.
I used both VMware workstation and virtual box under windows and managed to get them both to auto start (and stop before shutdown) their VMs, but disliked the rigged solution and ultimately put them under ESXi and simply forget about them.
I probably will use VMware workstation again under windows to go, as a portable lab.
Hyatt Center
Conner Fall
I don't suppose this Workstation version has a feature to simulate a TPM 2.0 module? That sure would be a helpful feature as my hardware lacks a TPM. It's not that old, but I'm not ready to upgrade everything as I don't know what the requirements of Windows 12 will be.
I encountered a problem that after I installed Docker for Windows my VMware Workstation VM wouldn't start any more (Win 10 Home host)
Yes but new vmware workstation version does not anymore allow to remotely connect to shared VMs on another host. Or does it?
Katrina Parks
I have workstation pro 16 on an older pc. I need to replace my pc now and I see a lot of online comments about how workstation pro does a bad job of managing performance vs efficient cores on the host. Is this still a problem?
Which is the best for small hosting business. Vmware workstation pro 17 ya vmware exsi 7?
Is it worth it to upgrade from Hyper-V?
Thank you for the comment! Sign up on the forums and I can give more personalized help here: www.virtualizationhowto.com/community
Schulist Camp
Hello Sir,
i'am working now in my new job.
and try to seek some of your videos about VMware workstation 17pro.
im here in a remote area, i wish i could have this app.
hope tou can help me in the future. thanks
I have VMWare Pro installed on client computers on a domain. The clients cannot add VMNets because they don’t have admin rights. Is there a way around this?
Thanks, can you please tell me how to get captured document from VMware workstation? I lost my capture which mean I saved it on word document.
Can you clone your host system to a VM with Pro? Thank you in advance for your answer.
There is two major bugs on WS17, 1.If you autostart vms through the new ui process then you cannot manage your vms through the console, seems as they are not started but they are running and the only way to manage them is via other console methods (RDP,VNC,Ssh) dependent on the Os flavour, this is kind of annoying for not being tested by VMware. 2. If your VMs have enabled the "3D support" options under VGA Device and they have assigned more VRam they cannot even start, the Vmware workstation kernel halts with error and the vms cannot be started, although if you uncheck the 3D option you can start the VMs and workaround the issue. These 2 are my findings on 2days before upgraded from 16.x, i hope it will stop there and fixed on 17.x patch update from VMw. What the hell VMware.. in any new version always supplies new features and breaks others that worked fine for ages.. (eg the CBT Bug on ESXi 7.x that returned.. same shit on 4.1, 5.5 and first 6.x versions) all on them fixed in later versions but if using vsphere on production after every upgrade there is a "Black" Friday
VK, good shout out about these current bugs with auto start, etc.
worse yet is if your VM has a desktop GUI - you can't connect to it if it is autostarted.
In my case I have WS17 pro and autostart a fedora desktop.
I rarely need / want the desktop for Fedora, but I'm still trying to figure out how to use it when it is needed other than stopping the autostart and starting via the Workstation GUI
oh and my use case... Selenium testing / debugging.. It would kinda be nice to see that browser to help create the selenium script.
In the latest update 17.0.1 Vmware fixed the issue with vram setting on virtual vga but did not fixed the autostart option, still if you set a vm to automatically start on system boot 🥾 with autostart service you are unable to get virtual machine's console while the vm is running
@@rontidd6551 Fuck Auto-start option an take a look what i did an managed to get over this situation, create a batch file eg Startvms.cmd edit it and place the following line "c:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws start "c:\VM\VM.VMX" nogui -cutomize the path of your .vmx- save the startvms.cmd and place it on your system startup by copying it to the following path C:\Users\xx-yourusername-xxx\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup then reboot the system and logon (if you have a password you can set system to auto logon and then lock) by doing the following your vm will start without seeing nothing on the desktop but the magic comes that if you open vmware workstation app you ll see normally the play button on your vm and of course the vm console will be accessible. Try it and tell me
Another bug: If a VM is under a tree folder, it will not show up in the Auto Start VM list. You have to move the VM to the root to be able to select the VM for auto start.
i switched from Windows to Linux, been using VMWARE for years. Had VMware 16 on Windows running a Windows vm for torrents/etc, everything worked fine. Got linux going, installed VMware 16,... updated to 17 and the shit broke. lagged like hell so i had to go back to version 16. Maybe its something with Linux running Windows that caused a glitch cause i'm using an Nvidia card. AMD card is on the way, so i'll test this theory and get back to ya if i can remember...
Jason thank you for the comment please do let us know on that front. It being a .0 release I'm sure a patch is forthcoming soon to squash the initial bugs.
It was freezing up with Wayland. Try switching back to Xorg.
@@VirtualizationHowto I switched back to Windows for work-related reasons and so i could play PC games, but i use Linux Mint at work with VMware running Windows 11 and no issues. That PC is using an Nvidia GT 710. Not a problem at all with Linux running Windows in a VM. Hope this helps :)
Thank you sir !! Might just have to give this a shot after i do more stuff with ESXI 8.
What about very slow shared folders, has this been fixed?
Hello Brandon,
Is the maximum memory limit 64Gbyte for the vmware workstation version 17 also ? Thank you.
@DikiciBurak thank you for the comment! The 64 GB limit is per virtual machine, not total. See the official link here: docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-023888CC-5252-4EC3-AB3C-D7CEAD306CCC.html
I see. But the problem for me is that i am going run eve-ng in one vm. Thats why i wonder the limit of ram per vm. Maybe i should think of using hyperv in this case. My notebook doesnt support esxi by the way.
Brandon I see you have a drone in the background, any vids on that coming soon, great video, happy thanksgiving
Justin, it is a DJI Air 2S....maybe something on that coming in the future...would be a little out of my niche, but would be a fun video.
I am using my vmware to tun my medically necessary software
I switched to hyper-v after many many issues with past versions of VMware workstation. How stable is it? Does it crash on AMD filter driver or exhibit strange behavior on certain Intel chipset software on the host?
Timothy, I have been running Workstation 17 now for several days and it has been rock solid.
Glenda Throughway
Thank you for the short intro. Autostart is the big new feature, really great for me as a consultant, but upgrade 17 major only one feature is an expensive upgrade feature though.
Thank you! 💯❤
Bailey Meadows
No gpu passthough support
L
Janiya Hill
Josue Place
Set Speed to 1.5x -- You're welcome~