Running win10 with the latest patches
15.0.3 upgraded failed with an error of "cant write temp files"
Remove workstation all the way, still no go
Tried to install 15.0.2 and even 15.0 but get the same exact error
So pretty much I cant use a product I bought right now
Author : John Domenichini
Topic Name : Selecting the Disk Mode
Publication Name : Using VMware Workstation Pro
Product/Version : VMware Workstation Pro/14.0
Question :
what is file name extensions typically associated with VMWare workstation pro virtual machine's primary configuaration and VMware workstation pro virtual file?
VMWare Workstation 15
Win10 host, Win7x64 guests, all on many different SSDs
I have a master template VM with snapshot and many linked clones (over 500).
Some of the linked clones have begun exhibiting 2 MB/s write and multi-second disk latency on suspend. Resource manager shows that it's the vmem file being written to disk that is causing this issue.
This doesn't happen to all VMs but certain ones, i think it's the ones that are old and have been used a lot.
Moving the entire linked clone from one disk to another does not solve the issue. I have also tried defragmenting the volume in VMWare settings, as well as compacting the volume in VMWare settings.
The only thing that seems to make this go away is if I make a full clone of that linked clone. This is not fully tested and it wouldn't be a good fix because that would make each VM about 50 GB, instead of the approx 5 to 15GB that each linked clone currently occupies.
Please comment on possible fixes for for this persistent problem on some of my VMs.
Hi,
is is there any way I can emulate a hardrive gong off line / loowing connection etc in a virtual machine.
i would like able to do this for the second hard drive but keep the primary system one running
thanks,
ward
I have seen so many different methods to install Vmware tools and I'm stuck. I'm running Ubuntu 16.04 as host & guest. I had exprience up until version 12 but stopped using it for a while, but used it all the time up until then.
I see that there is an "Install Vmware tools" under the VM menu on workstation. When I click this it seems to stall saying it is installing. It also says to extract a folder from the tar or iso and then run the vmware_install.pl file. I've done this in the past with no problems.
This time I navigated to the folder (vmware-tools-distrib) with the and ran (as root) ./vmware_install.pl -f (because there were previous failed attempts to install. The install seemed to go fine and I was finally able to make my screen resolution larger. I kept getting notices to install VMtools though on boot (sometimes saying the CD drive was locked and to run the .pl file, even after it completed with the -f (forced) function.
So after the successful install I still had the pop-up open and it asked me if I wanted to install. The window told me to run the vmware-install.pl in the first paragraph, then it gave me the option to keep the CD (iso file) locked or install vmware tools. So I thought I had to click the install button AGAIN.
Now I'm looking at the menu with the VM -> "Cancel Vmware tools installation" so I guess it is installing it again, but maybe it is hung up b/c it was installed earlier. I also had a notice that there was a newer version. I'm using 10.2.5 xxxx version, so I thought clicking the install might upgrade it.
How long do I have to wait for VMware tools to install - or can I click the cancel button in the drop down menu under "VM (between View and Tabs).
This used to be a breeze to install, took maybe 2-3 minutes now it seems the system is confusing the user for some reason.
Also, should I stick with open-vmtools, or use the official Vmware tools?
Ahh, the headache, between this and about 20+ other things.
Any help is greatly appreciated.
When connecting to something like an airport or hotel wifi on my windows 10 host my guest OS operating systems can no longer get an IP. After logging into the public wifi portal and going to my guest windows 10 OS, I can't get an IP. I have tried bridged and NAT, restarted the guest, restarted DHCP and NAT VMWare services on the host, rebooted the host, nothing works. As soon as I connect to WiFi that doesn't require a login, the networking on the guest starts working (both NAT and Bridged). I also tried restoring the defaults in the Virtual Network Editor, nothing works when I am connected to a WiFi hotspot that requires login. Is there something I am missing?
Hi,
After upgrading fedora 29 to 5.0.3-200.fc29.x86_64 i can not start vmware workstation pro, tried uninstalling and reinstalling no success using (VMware-Workstation-Full-15.0.3-12422535.x86_64.bundle). Any one has a suggestion?
2019-03-27T10:51:11.984+03:00| host-9907| I125: Log for VMware Workstation pid=9907 version=15.0.3 build=build-12422535 option=Release
2019-03-27T10:51:11.984+03:00| host-9907| I125: The process is 64-bit.
2019-03-27T10:51:11.984+03:00| host-9907| I125: Host codepage=UTF-8 encoding=UTF-8
2019-03-27T10:51:11.984+03:00| host-9907| I125: Host is Linux 5.0.3-200.fc29.x86_64 Fedora release 29 (Twenty Nine)
2019-03-27T10:51:11.984+03:00| host-9907| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2019-03-27T10:51:11.984+03:00| host-9907| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2019-03-27T10:51:11.984+03:00| host-9907| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2019-03-27T10:51:11.984+03:00| host-9907| I125: DictionaryLoad: Cannot open file "/home/ismet/.vmware/config": No such file or directory.
2019-03-27T10:51:11.984+03:00| host-9907| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/ismet/.vmware/config": No such file or directory.
2019-03-27T10:51:11.984+03:00| host-9907| I125: PREF Optional preferences file not found at /home/ismet/.vmware/config. Using default values.
2019-03-27T10:51:11.991+03:00| host-9907| W115: Logging to /tmp/vmware-root/vmware-9907.log
2019-03-27T10:51:11.996+03:00| host-9907| I125: Obtaining info using the running kernel.
2019-03-27T10:51:11.996+03:00| host-9907| I125: Created new pathsHash.
2019-03-27T10:51:11.996+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".
2019-03-27T10:51:11.996+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:11.996+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:11.996+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:11.996+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.000+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.000+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.112+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers
2019-03-27T10:51:12.112+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Read 20627 symbol versions
2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmmon module.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmnet module.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmci module.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vsock module.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Setting vsock to depend on vmci.
2019-03-27T10:51:12.122+03:00| host-9907| I125: Invoking modinfo on "vmmon".
2019-03-27T10:51:12.124+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.
2019-03-27T10:51:12.124+03:00| host-9907| I125: Invoking modinfo on "vmnet".
2019-03-27T10:51:12.125+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.
2019-03-27T10:51:12.125+03:00| host-9907| I125: Invoking modinfo on "vmci".
2019-03-27T10:51:12.125+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.
2019-03-27T10:51:12.125+03:00| host-9907| I125: Invoking modinfo on "vsock".
2019-03-27T10:51:12.127+03:00| host-9907| I125: "/sbin/modinfo" exited with status 0.
2019-03-27T10:51:12.133+03:00| host-9907| I125: to be installed: vmmon status: 0
2019-03-27T10:51:12.133+03:00| host-9907| I125: to be installed: vmnet status: 0
2019-03-27T10:51:12.140+03:00| host-9907| I125: Obtaining info using the running kernel.
2019-03-27T10:51:12.140+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".
2019-03-27T10:51:12.140+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.140+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:12.140+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:12.140+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.143+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.143+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.253+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers
2019-03-27T10:51:12.253+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.
2019-03-27T10:51:12.263+03:00| host-9907| I125: Read 20627 symbol versions
2019-03-27T10:51:12.263+03:00| host-9907| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.3-200.fc29.x86_64/build/include
2019-03-27T10:51:12.263+03:00| host-9907| I125: Update kernel header path to /lib/modules/5.0.3-200.fc29.x86_64/build/include
2019-03-27T10:51:12.263+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.263+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:12.263+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:12.263+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.267+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.267+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.268+03:00| host-9907| I125: Found compiler at "/usr/bin/gcc"
2019-03-27T10:51:12.269+03:00| host-9907| I125: Got gcc version "8".
2019-03-27T10:51:12.269+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-03-27T10:51:12.271+03:00| host-9907| I125: Got gcc version "8".
2019-03-27T10:51:12.271+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-03-27T10:51:12.272+03:00| host-9907| I125: Trying to find a suitable PBM set for kernel "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.272+03:00| host-9907| I125: No matching PBM set was found for kernel "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.276+03:00| host-9907| I125: Got gcc version "8".
2019-03-27T10:51:12.276+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-03-27T10:51:12.276+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-03-27T10:51:12.276+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.276+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:12.276+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:12.276+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.279+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.279+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.280+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-03-27T10:51:12.280+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.280+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:12.280+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:12.280+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.283+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.283+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.283+03:00| host-9907| I125: Using temp dir "/tmp".
2019-03-27T10:51:12.284+03:00| host-9907| I125: Obtaining info using the running kernel.
2019-03-27T10:51:12.284+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".
2019-03-27T10:51:12.284+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.284+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h
2019-03-27T10:51:12.284+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-03-27T10:51:12.284+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check
2019-03-27T10:51:12.288+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".
2019-03-27T10:51:12.288+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid. Whoohoo!
2019-03-27T10:51:12.400+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers
2019-03-27T10:51:12.400+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.
2019-03-27T10:51:12.410+03:00| host-9907| I125: Read 20627 symbol versions
2019-03-27T10:51:12.410+03:00| host-9907| I125: Invoking modinfo on "vmmon".
2019-03-27T10:51:12.412+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.
2019-03-27T10:51:12.412+03:00| host-9907| I125: Invoking modinfo on "vmnet".
2019-03-27T10:51:12.413+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.
2019-03-27T10:51:12.461+03:00| host-9907| I125: Setting destination path for vmmon to "/lib/modules/5.0.3-200.fc29.x86_64/misc/vmmon.ko".
2019-03-27T10:51:12.462+03:00| host-9907| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2019-03-27T10:51:12.466+03:00| host-9907| I125: Successfully extracted the vmmon source.
2019-03-27T10:51:12.466+03:00| host-9907| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-1d9cBn/vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.3-200.fc29.x86_64/build/include CC=/usr/lib64/ccache/gcc IS_GCC_3=no"
2019-03-27T10:51:13.512+03:00| host-9907| W115: Failed to build vmmon. Failed to execute the build command.
2019-03-27T10:51:13.513+03:00| host-9907| I125: Setting destination path for vmnet to "/lib/modules/5.0.3-200.fc29.x86_64/misc/vmnet.ko".
2019-03-27T10:51:13.513+03:00| host-9907| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2019-03-27T10:51:13.516+03:00| host-9907| I125: Successfully extracted the vmnet source.
2019-03-27T10:51:13.516+03:00| host-9907| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-1d9cBn/vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.3-200.fc29.x86_64/build/include CC=/usr/lib64/ccache/gcc IS_GCC_3=no"
2019-03-27T10:51:15.047+03:00| host-9907| W115: Failed to build vmnet. Failed to execute the build command.
Hi everybody
Since a while, i have issues with Workstation 14 and 15 Pro on computers with more than one monitor. Depending on the message, sometimes the window is quite long and needs two monitors or more, even if the message is quite short. It does not matter on the size of the Workstation pro software, neither on if or how many VMs currently running. It’s hard to describe, so I attached a screenshot.
Any help or suggestions?
Thanks!
Since v15 I have the shown problem with Google Chrome in W10 Machines...
VMware Workstation Pro14, 15 could not connect to VMware vSphere Client. MKS: Internal error.
VMware Workstation Pro12 does not have this problem, what is the reason?
VMware vSphere Client is version 6.5.
I'm trying to install VMWare workstation and install fails with error: VMWare workstation setup wizard ended prematurely - unable to install .
* From CMD/Powershell as admin ran vmic/product get name it shows an existing "VMware Workstation" line, when I tried to remove it I get: ReturnValue = 1603 and it's still there.
* From programs/features there is nothing.
* There is no file in C:\Program Files or C:\Program Files (x86) that references VMware Workstation.
* I removed files from regedit and I have already tried restarting my computer as well.
We have a scenario where we automatically create CentOS7 VMware images.
This process is done using Vmware Workstation Pro 15 (licensed version) and packer. In this process the VM is created and later it is converted to OVF and VMDK files using ovftool.
In the installed CentOS7, we also install open-vm-tools using 'yum'. The installed version of open-vm-tools is 10.2.5.
Now the problem we are facing is that, once the VM is imported in Vmware Workstation Player in windows environment, the guest time is not synced with the host time.
If we manually check/uncheck the 'Synchronize guide time with host' checkbox in the VM settings, the time is synced correctly, but upon restart it gets de-synced.
In de-synced state, following are our observation
Guest Local time : X (this is timezone time based on the current Universal time; is timezone is UTC+2 and current Universal time is 00:00 Hrs, then the Local time is 02:00 Hrs)
Guest Universal time : Y ( this is same as the host time)
Ideally we expected the guest local time to be same as the host time. Please assist us with this problem.
Regards
Lakhya
Author : John Domenichini
Topic Name : Configuring Display Settings
Publication Name : Using VMware Workstation Pro
Product/Version : VMware Workstation Pro/12.0
Question :
I have VM Pro 12 and running a windows 7 VM. I would like to use the host's printers, and have modified the hardware to connect printer at power up. I am unable to print to host printers. Can anyone help with what I should checkout?
I am trying to work out if Workstation Pro shared folders support Windows 10 long paths? This is file paths longer than 260 characters.
I have enabled long path support on my Windows 10 host and tested that it works without problem in the host. If I share this path using shared folders into an Ubuntu VM I get an error when accessing the folder (from inside the VM) saying "File name too long".
Is this because Workstation does not support long paths or a vmware tools or Fuse FS problem?
Hi,
I run some windows virtual machines in a Workstation and I am pretty confused about 'free' output:
| total | used | free | shared | buffers | cached | |
| Mem: | 59G | 58G | 576M | 46G | 146M | 51G |
| -/+ buffers/cache: | 6,8G | 52G | ||||
| Swap: | 71G | 344M | 71G |
Since 'used' without 'cached' is 6.8G, I assumed, until some days ago, that TPS was enabled and a lot of memory was deduplicated between my many windows VM's.
But after some problems running more VM's, and the OOM killer appearing when I disable swap, I think that TPS is not working, is it available for Workstation? If yes, how can I enable it?
I would like to know exactly why the used/cache values are so confusing when running vmware virtual machines.
Thanks.
Solaris 11.4 is not listed as a supported operating system for Workstation 15 Pro.
Upgrading functional 11.3 VMs to 11.4 breaks the mouse.
Suggested entries to vmx file regarding usb mouse do not fix the problem, and cause 11.3 mouse to act "wonky" - never move from upper left corner, and clicks just cause the menu bar to expand/contract.
Has anyone "successfully" gotten 11.4 to run in Workstation 15 Pro? If so, would you be willing to share how?
If not, can VMWare look into the problem?
Thanks!
I'm trying to migrate a Windows XP machine that currently has the drive configuration set to RAID.
I can successfully install the VM and when I try to boot, the splash screen appears for a few seconds then blue screens with a 0X0000007B.
I've tried both using the physical disk and converting the physical drive to a VM file, always the same result.
Any advice would be greatly appreciated!
Kurt
Hey all, I've been playing around for the last few days trying to get vmware shared folders recognized by a USB boot drive, but it doesn't seem to work for me.
I'm using the Paragon Backup and Recovery software to create backups of my system, and my goal was to utilize vmware to test the backups.
I will break down some details. Feel free to ask for anything that may be missing. Any help is appreciated.
Version: VMware Workstation 15 Pro and Paragon Backup and Recovery 17 Free
Info:
Host machine is Windows 10 Pro
VM machine with Paragon installed is Windows 7 X64 Pro
Facts:
-I can access vmware shared folders from the vm machine ok. The path shows up as \\vmware-host\Shared Folders
-I created a system backup and stored it in the E drive which is located on my host machine. This is accessed through the vm as \\vmware-host\Shared Folders
-I created bootable recovery media via Paragon and saved it to my USB drive
-I'm able to boot into the recovery media from vmware, but the vmware shared folders directory will not show
What I have tried within Recovery Media:
-"Use this Windows Image (No ADK required)"
-Under the network settings(optional), I chose to "Mount a network share automatically" and entered the path \\vmware-host\Shared Folders with the credentials for my host machine
-I have also tried adding the vmware storage device driver "pvscsi" and the network driver "vmxnet3". Neither of these options worked, as I still couldn't access the vmware shared folders directory where my backup is stored
-Utilities/Configure Network - IP address is assigned, and I'm able to ping the Host machine successfully
-Network Drives/Map a Network Drive, \\vmware-host\Shared Folders - "Error: The network Path was not found"
-While slightly changing the syntax, I can eventually get the "Select Network Share" window to come up, and it shows my host PC, so I expand it and then receive error "Cannot get shares for server JASON-PC:The server service is not started"
I've scoured the internet and have come across various different threads discussing similar issues, but have not yet found a solution that worked for me. Here are a couple of the threads, seemingly illustrating the same type of issues with Paragon and VMware.
https://www.wilderssecurity.com/thre...achine.283834/
https://www.wilderssecurity.com/thre...ery-cd.304177/
Do you guys have any ideas as to what may be causing the problem?
Thanks,
Tech
Ok, so i just downloaded and installed vmware workstation free for personal use. I have installed two linux distros for testing. Back in the day, there was an arrow on the top menu where i could toggle between VMs without minimizing and then maximizing the other. I can not find that option now
I have used the following commands to install vmtools
apt update
apt install open-vm-tools-desktop
each has completed successfully.
I am not sure what to do next to toggle between them:)
thank you
Hi, I have Windows 10 Insider Preview Skip Ahead 18860 on VMware Workstation and Windows 10 Pro Host. I'm trying to update to the next Build 18865.1000. After downloading and installing from windows update I reboot and it fails and removes any changes. I can't get the next Build to install. I had this problem on Azure and I just tried over and over again till it worked. I don't have that anymore and would like to know how to Update Insider Builds on VMware. The problem is when it tells me to reboot and then it fails and everything goes back to 18860. Has anyone herd of this problem? Probably an easy question. Please reply. Thanks