CallistoJag's Posts

Not sure if this is same for win11 in German, but have you tried the following: right-click on the Start menu > select Windows PowerShell (Admin) > paste this command and press Enter: Dism /Online /Ad... See more...
Not sure if this is same for win11 in German, but have you tried the following: right-click on the Start menu > select Windows PowerShell (Admin) > paste this command and press Enter: Dism /Online /Add-Capability /CapabilityName:Microsoft.Windows.Notepad~~~~0.0.1.0
The vm has virtualized HW, it is not a match to your underlying system. The virtual network cards are either using the VMware specific virtual cards or they use the default intel based virtual interf... See more...
The vm has virtualized HW, it is not a match to your underlying system. The virtual network cards are either using the VMware specific virtual cards or they use the default intel based virtual interface. The processor will be displayed as the correct type, but the rest of the virtual HW will be generic. Hope this helps.  
They will all be stored alongside the .vmx file, usually under a folder named in the same way as your VM. Copy the whole directory/disk to new computer and all should be fine.
As posted, double check status of VMware tools. Then you could try changing the type of USB controller for your VM, if USB 2.0, change to USB 3.0 and reboot or the other way round if already USB 3.0. ... See more...
As posted, double check status of VMware tools. Then you could try changing the type of USB controller for your VM, if USB 2.0, change to USB 3.0 and reboot or the other way round if already USB 3.0. Might help
Not sure Player supports 10Gbps directly attached. If you set up a bridged network to your host and use the 10gbs this way it should work.
You will not like this you need to uninstall VMware Workstation, and then remove ALL references to it from the registry with REGEDIT. Re-install and it should behave as expected again. Hope this he... See more...
You will not like this you need to uninstall VMware Workstation, and then remove ALL references to it from the registry with REGEDIT. Re-install and it should behave as expected again. Hope this helps
I do not have a Mac setup for GNS VMs, however basically, this is how you do it: On the "host" computer, edit the settings for the GNS3 VM Change the network adapter to "Bridged", and apply Close t... See more...
I do not have a Mac setup for GNS VMs, however basically, this is how you do it: On the "host" computer, edit the settings for the GNS3 VM Change the network adapter to "Bridged", and apply Close the VM settings Start the VM Once the VM has finished booting, there should be a blue screen visible *Make note of the IP address **Make note of the port number From a terminal/command prompt on the "client" computer: Ping the IP noted in step * to ensure you have network connectivity from client to VM On the "client" computer, in GNS3 client, go to Help->Setup Wizard Select the bottom option, "Run appliances on a remote computer and can be shared with multiple users" Click "Next" Enter the IP from step * in "Host:" Enter the port from step ** in "Port:" Uncheck the "Enable Authentication" Click "Next: Click "Finish" Close the GNS3 client, and restart (Ensure that the GNS3 VM is running on the "host" computer I hope this helps.
Get supported 3d graphics card pass through or do not play 3D games in a VM Seriously, can you give some more information, what version of workstation, what client OS, example games etc.... Thanks!
We have had 0 issues migrating hundreds of Windows and linux VMs to AMD from Intel. The only preparation we have needed is with some MS SQL machines that needed to have a few settings checked first. A... See more...
We have had 0 issues migrating hundreds of Windows and linux VMs to AMD from Intel. The only preparation we have needed is with some MS SQL machines that needed to have a few settings checked first. As these machines will need to be powered off anyway to move, you meet the minimum requirement
Quoting other community user John_son915 in workstation, not MAC: This issue is probably related to the VMware Authorization services, if you're running in the windows desktop kindly go through this ... See more...
Quoting other community user John_son915 in workstation, not MAC: This issue is probably related to the VMware Authorization services, if you're running in the windows desktop kindly go through this steps. Start>Control Panel>administrative tools>Services> check if the VMware Authorization Services is running or not. if not then you have to click start services. Not the same solution, but might point you in the right direction  
Not opening the logs, what was the VM OS? Windows/Linux?
Is the drive NTFS or Fat? NTFS is usually better for these VMs. Also I would remove the floppy drive from the hardware just to make it cleaner. Also this error suggests that there is some background d... See more...
Is the drive NTFS or Fat? NTFS is usually better for these VMs. Also I would remove the floppy drive from the hardware just to make it cleaner. Also this error suggests that there is some background database reaching its limits here, what is the host spec?
Not sure if you are using an Apple Silicon device, if so try this: Step 1: Click the Windows Start menu and type PowerShell in the search box. Click Run as Administrator, and click Yes on the User ... See more...
Not sure if you are using an Apple Silicon device, if so try this: Step 1: Click the Windows Start menu and type PowerShell in the search box. Click Run as Administrator, and click Yes on the User Access Control prompt. (If you don’t see Run as Administrator, right click on PowerShell and select Run as Administrator). Step 2: Type the following inside the PowerShell prompt: Set-ExecutionPolicy RemoteSigned Press Return on your keyboard to execute the command, and then type ‘Y’ and press Return to confirm the change to the execution policy. Type Exit and press Return to close the PowerShell. Step 3: In the menu bar click Virtual Machine → Reinstall VMware Tools and click the Install button on the prompt that appears. Step 4: Open Windows Explorer, navigate to the DVD drive, and ensure that VMware Tools setup is mounted. You should see a Setup.ps1 PowerShell script in the root of the DVD drive. Step 5: Right click on the Setup PowerShell Script and click Run with PowerShell. Click Yes on the User Account Control pop-up. VMware Tools will now install, along with the necessary VMXNet3 network drivers and SVGA display driver. After a short countdown, the PowerShell window will automatically close. Network functionality should now be operational, and you will also be able to configure display settings via Start → Settings → Display. There should be no need to restart in order to enable this functionality.
Hi @TheCrystalNinja There are different versions of Workstation Player and VMware Player, do you have any older versions as there might not be an upgrade path and instead are seen as blockers?
It's impossible to run Sierra or Mojave on an M1 Mac. There are no workarounds. The M1 can't emulate or translate the Intel code in those operating systems. Only Big Sur can translate and run Intel b... See more...
It's impossible to run Sierra or Mojave on an M1 Mac. There are no workarounds. The M1 can't emulate or translate the Intel code in those operating systems. Only Big Sur can translate and run Intel based apps using its Rosetta 2 technology. That said.....  https://developer.apple.com/documentation/virtualization/running_macos_in_a_virtual_machine_on_apple_silicon
Can also reference this post might help: https://communities.vmware.com/t5/VMware-Workstation-Pro/Every-VM-Failed-to-start-the-virtual-machine/td-p/2935401
In order to turn off ULM/Hyper-V mode, run the following command at the host in windows command-line with Administrator privileges: bcdedit /set hypervisorlaunchtype off Reboot the system to activ... See more...
In order to turn off ULM/Hyper-V mode, run the following command at the host in windows command-line with Administrator privileges: bcdedit /set hypervisorlaunchtype off Reboot the system to activate your changes. If you want to go back to Hyper-V mode again, then you can enable it like this: bcdedit /set hypervisorlaunchtype auto
Not sure, but does this help: https://docs.vmware.com/en/VMware-Fusion/13/com.vmware.fusion.using.doc/GUID-E142FF07-372C-4952-9AF7-B52865CCDAD1.html
Lots of good info here that might point you in the right direction: https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-14-1-and-Windows-98-no-removable-media-detected/td-p/926788
Make sure you have configured the correct network connection type for your VM, this effects the way the "shared" physical network connection is used. https://docs.vmware.com/en/VMware-Workstation-Pro/... See more...
Make sure you have configured the correct network connection type for your VM, this effects the way the "shared" physical network connection is used. https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-6F7ECBA6-A29A-40AE-B565-3D0F2E74FEA4.html