Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

All Content in Workstation Player

older | 1 | .... | 201 | 202 | (Page 203) | 204 | 205 | .... | 252 | newer

    0 0

    I'm running a Win10 VM via Workstation Player on a second desktop (Win10 host) and I'd like to use the context menu key/AppsKey to swap from the VM to the main desktop.

    I've made an AHK script that should remap this to the AppsKey, but the Ctrl+Alt to release cursor doesn't work, neither when run from within the VM nor from the host OS.

    Is there a way to do this?


    0 0

    Hi all,

    i would like to ask a simple question : if my laptop is running 32 bit Window 7 OS. After i install the VMware player, can i install 64 bit Window 7 OS in VMware player?


    0 0

    Context Menu  Map or Mount a Virtual Disk to a Drive on the Host System

     

    Error reading volume information

    TIM截图20170720100540.png

     

    Map button is gray, not available.

    TIM截图20170720100607.png


    0 0
  • 07/20/17--22:13: Cannot install VMTools
  • In a Workstation 12.5.7 Player running on Win 10, I cannot find a sequence of instructions for installing VMTools on a guest mint 18 64-bit.

     

    I've found several sets of instructions for Linux, Ubuntu, etc. All fail---commands they describe do not work, folders & filenames they describe do not exist.

     

    Please, where do I find of VMTools installation instructions that actually work for 12.5.7 and Mint 18 64-bit?


    0 0

    I've created a RAW image of my disk (has 2 partitions, including one bootable Windows7).

     

    How can I use this RAW image and boot it in VMware Workstation Player?


    0 0
  • 07/23/17--09:34: Second mouse usb connection
  • I have tried to use a second mouse & keyboard for the VM unfortunately I wasnt able to. once I changed the settings in my VM to show all usb connections it doesnt do that and on top of the VM there only the basic connections to the VM. Can someone please help me to figure it out? Thanks in advance!


    0 0

    Hi folks,

     

    I'm having some problems in running the VM i copied from my School machine, problems as below:

     

    1) First problem:

    "Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details."

     

    2) Second problem:

    " VMware Player unrecoverable error: (vcpu-0)

    vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:386 bugNr=1036521

    A log file is available in "C:\Users\USER\Desktop\***\REMWorkstationVM\vmware.log". 

    You can request support. 

    To collect data to submit to VMware technical support, run "vm-support".

    We will respond on the basis of your support entitlement."

     

    My machine is running in below spec:

    Processor: Intel i5-7200U @2.50Ghz

    System Type: 64 bit Operating System, x64-based processor

     

    I have attached vmware.log, feel free to let me know if other details are required. Thank guys!


    0 0

    I asked a question in the Japanese vmware community, but since there seems to be nobody with similar case,

    I will also post it to the English version.

     

    I do not have much English is good at.

    Because it is translating by google translation, it may be incomplete English, but please understand.

     

    This sentence is very long. I'm sorry.

     

    I am using a virtual machine (vmware player 12.5.7) with "MSI A88X-G43".

    Immediately after starting the virtual machine, after several hours, etc. irregularly

    "BSOD CLOCK_WATCHDOG_TIMEOUT (101)" occurs in the host OS.

     

    When "vmware player" is executed with "MSI A88X-G43", in the same way

    Is there anyone with an error "BSOD CLOCK_WATCHDOG_TIMEOUT (101)"?

    Please tell me if there is a BSOD error occurring.

    The CPU is AMD A10-7850K.

     

    AMD CPU uses "vmware player" but BSOD CLOCK_WATCHDOG_TIMEOUT (101)

    Is there anyone who doesn't happen?

    Could you tell me the CPU, BIOS version information, and motherboard name of the machine that does not occur?

     

    By the way, even with VMware 12.5.7 or earlier, the same BSOD is occurring, it is not a problem of VMware 12.5.7.

     

    With various trial and error, with the virtual machine running,

    If you do the following operation, you know that it always occurs in the environment where this failure occurs.

     

    Press [Setting (T)] on "Startup and Recovery" in the [Control Panel] - [System and Security]

    - [System] - [Advanced System Settings] - [Detail Setting] Tag.

    (I think that the English version is somewhat different, because it is the display wording of the Japanese version)

     

    At first, I thought of hardware and driver problems, and removed all connected devices such as USB and expansion cards.

    And even with minimal configuration with CPU, memory, hard disk, power supply, mouse, keyboard

    When running vmware player BSOD occurred.

     

    I diagnosed memory and hard disk with the following tools.

     

    Memory windows OS included tool, memtest86

    HDD WD Data Lifeguard Diagnostic for Windows

    By doing this, I confirmed that it is not abnormal in the hardware.

     

    So I installed Windows 10 offline and clean install.

    When running vmware player on this host OS, "BSOD CLOCK_WATCHDOG_TIMEOUT" similarly occurred.

     

    In addition, we prepared another motherboard A88X-G43 of the same model number.

     

    I have created another machine that has a separate power source, another CPU, another memory,

    another mouse, another keyboard, another hard disk, and no identical parts at all. (See the end for details)

    I cleanly installed Windows 10 offline on this machine.

    If you run "vmware player" on this machine, the host OS similarly raises "BSOD CLOCK_WATCHDOG_TIMEOUT".

    I tried using the guest OS which cleanly installed Windows 10, but similarly BSOD occurs.

     

    Therefore, it is neither an individual defect of hard nor an OS problem.

     

    Here I thought that there might be a problem with the BIOS.

    Until then, I used the latest 3.C (3.12).

    If this version is downgraded to 3.9, BSOD no longer occurs.

     

    There are two A88X-G43 as above.

    For both machines "BSOD CLOCK_WATCHDOG_TIMEOUT" will occur if "BIOS" is 3.10 or more.

    If "BIOS" is 3.9, it does not occur at all.

     

    Therefore, it is obvious that it is BUG of BIOS.

     

    AMD provides microcode such as CPU, memory controller and HT bus controller in the form of AGESA code.

    When examining the AMD AGESA version in the BIOS, it seems that it changed significantly between 3.9 and 3.10 (3.A).

     

    The results of examining the BIOS and AGESA version with HWINFO 64 are as follows.

     

    ■BIOS where BSOD occurs

     

      (1)BIOS Version:                           V3.12(3.C)

         BIOS Date:                              08/10/2016

         AMD AGESA Version:                      CarrizoFM2r2PI  V1.2.0.4X

     

      (2)BIOS Version:                           V3.11(3.B)

         BIOS Date:                              04/08/2016

         AMD AGESA Version:                      CarrizoFM2r2PI  V1.2.0.3X 

     

      (3)BIOS Version:                           V3.10(3.A)

        BIOS Date:                               01/14/2016

        AMD AGESA Version:                       CarrizoFM2r2PI  V1.2.0.2X 

     

    ■BIOS that BSOD does not occur

     

      (1)BIOS Version:                           V3.9

        AMD AGESA Version:                       GodavariPI      V1.0.0.0  

        BIOS Date:                               04/20/2015

     

    This "BSOD" seems to occur when updating "BIOS" to V3.10 (2016/01/14) or later and using "vmware player" and using virtual instruction set of AMD CPU.

     

    We analyzed complete memory dump at BSOD with windbg.

    The CPU has four processors, but the 0, 1 and 2 processors were waiting for the completion of the 3rd processor.

    Conversely, the third processor waited for the completion of 0, 1 and 2 processors, and it seemed to be deadlocked.

    In this third processor, the program being executed was vmware.

     

    It seemed like a problem of exclusive processing of memory and resources peculiar to multiprocessor.

    When running vmware in this single processor state, BSOD no longer occurs.

    However, it is slow with a single core, it can not be used at all times.

     

    I thought to downgrade the BIOS to V3.9, which does not cause BSOD problems.

     

    However, with this V3.9, connecting the Asmedia 1061 SATA Hostcortroler to the PCI-e causes another BSOD to occur frequently and the OS can not be started.

     

    Therefore, it is necessary to use problematic V3.10 or later.

    I am troubled because I can not avoid the BSOD problem by downgrading to V3.9.

     

    The problematic BIOS, V3.10 seems to be released for compatibility with the new CPU Carrizo.

    Unfortunately, it seems that the following fatal troubles are mixed from this version.

    With old CPU (Trinity / Kaveri) BSOD occurs when virtual function is used.

     

    For this motherboard, the carrizo core CPUs are "Athlon X4 845" and "Athlon X 4 835".

    This product has no GPU and the clock is lower than the previous generations.

    If there is no merit and the AGESA code is the cause, it is an annoying story.

     

    However, the Microcode of the CPU in the AGESA code is as follows and there is no change.

    AGESA code seems to be microcode other than CPU as a problem.

    #1"AMD A10-7850K", the BIOS version 3.9 - 3.12 was all the same as "6003106".

    #2"AMD A4-5300", BIOS version 3.9 - 3.10 was the same as "6001119".

     

    However, as mentioned above, although the version of the AGESA code has certainly changed,

    it is a situation where it can not be concluded that this is the cause.

     

    Because recent UEFI BIOS is considerably huge, complicated, compressed and stored in 8 MB.

    Besides the AGESA code, it is made up of more than 200 modules.

    It contains various programs (initialization code and firmware driver) as below.

    1)chipet

    2) Storage controller

    3) LAN controller

    4) Clock generator

    5) Power supply IC type etc.,

    In addition, many modules such as MSI company and BIOS maker AMI company are built in.

     

    I took the difference between the modules of BIOS 3.9 and 3.10.

    Looking at it seems that not only the AGESA code but also many modules have been changed. (See attached file)

    The yellow module shows that there is a difference.

    However, there are many things that only change a few bytes of the BIOS version.

    Therefore, I think there are fewer modules that have been modified or changed.

     

    Some of these modules have been greatly changed.

    I think this module is likely to have bugs.

     

    Like me, if I run vmware on AMD platform, is there anyone with "BSOD CLOCK_WATCHDOG_TIMEOUT (101)"

    occurring in the host OS?

     

    Likewise, if there are people with BSOD errors, please let me know.

     

    AMD CPU uses "vmware player" but BSOD CLOCK_WATCHDOG_TIMEOUT (101)

    Is there anyone who doesn't happen?

    Could you tell me the CPU, BIOS version information, and motherboard name of the machine that does not occur?

     

    The specifications of the A88X-G43 are as follows.

     

    [Current Computer]

      Computer Brand Name:                    MSI MS-7793

      UEFI Boot:                              Present

    [Motherboard]

      Motherboard Model:                      MSI A88X-G43 (MS-7793)

      Motherboard Chipset:                    AMD A88X (Bolton-D4)

      Motherboard Slots:                      1xPCI, 5xPCI Express x1, 1xPCI Express x2, 2xPCI Express x4, 1xPCI Express x16

      PCI Express Version Supported:          v3.0

      USB Version Supported:                  v3.0

    [BIOS]

      BIOS Manufacturer:                      American Megatrends

      BIOS Date:                              08/10/2016

      BIOS Version:                           V3.12

      AMD AGESA Version:                      CarrizoFM2r2PI  V1.2.0.4X 

      UEFI BIOS:                              Capable

      Super-IO/LPC Chip:                      Fintek F71879A/F71889A

     

    BIOS ----------------------------------------------------------------------

     

      BIOS Vendor:                            American Megatrends Inc.

      BIOS Version:                           V3.12

      BIOS Release Date:                      08/10/2016

      BIOS Start Segment:                     F000

      BIOS Size:                              8192 KBytes

      System BIOS Version:                    4.6

      ISA Support:                            Not Present

      MCA Support:                            Not Present

      EISA Support:                           Not Present

      PCI Support:                            Present

      PC Card (PCMCIA) Support:               Not Present

      Plug-and-Play Support:                  Not Present

      APM Support:                            Not Present

      Flash BIOS:                             Present

      BIOS Shadow:                            Present

      VL-VESA Support:                        Not Present

      ESCD Support:                           Not Present

      Boot from CD:                           Present

      Selectable Boot:                        Present

      BIOS ROM Socketed:                      Present

      Boot from PC Card:                      Not Present

      EDD Support:                            Present

      NEC PC-98 Support:                      Not Present

      ACPI Support:                           Present

      USB Legacy Support:                     Present

      AGP Support:                            Not Present

      I2O Boot Support:                       Not Present

      LS-120 Boot Support:                    Not Present

      ATAPI ZIP Drive Boot Support:           Not Present

      IEE1394 Boot Support:                   Not Present

      Smart Battery Support:                  Not Present

      BIOS Boot Specification Support:        Present

      Function key-initiated Network Service Boot Support: Not Present

      Targeted Content Distribution Support:  Present

      UEFI Specification Support:             Present

     

    The specifications of the CPU are as follows.

     

    # 1st machine

    CPU information

    [General Information]

      Processor Name:                         AMD A10-7850K

      CPU ID:                                 00630F01

      Extended CPU ID:                        00630F01

      CPU Brand Name:                         AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G

      CPU Stepping:                           KV-A1

      CPU Code Name:                          Steamroller/Kaveri

      Microcode Update Revision:              6003106

     

    # 2st machine

    CPU information

    [General Information]

      Processor Name:                         AMD A4-5300

      CPU ID:                                 00610F01

      Extended CPU ID:                        00610F01

      CPU Brand Name:                         AMD A4-5300 APU with Radeon(tm) HD Graphics  

      CPU Stepping:                           TN1-A1 (Trinity)

      CPU Code Name:                          Piledriver/Trinity

      Microcode Update Revision:              6001119

     

    Thank you for reading very long sentences.


    0 0

    Howdy,

     

    I'm trying to create a new machine but point it to an existing VMDK.  I found this link: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2010196 But it only applies up to v10.  Can anybody tell me how I do this?  My only option as I see it is create a new one with an empty vdmk and then copy the vmdk I want on top of the empty one.

     

    Thanks


    0 0
  • 08/02/17--03:53: Can't Update vmplayer Kernel
  • I recently had a kernel update. I was prompted to install the update which I did but the update does not install.  I have the following errors:

       Virtual machine monitor                                     failed

       Virtual ethernet                                                   failed

    I did some research and I was told to deactivate secure boot on my BIOS but my BIOS does not have  the secure boot option. I do not know what to do. Please can you help me?


    0 0

    Hey,

     

    I am using VMware Player 12 and just hat two VMs running like I always do. The files of the VMs are stored on an USB HDD, so that I can easily transport my VMs.

    Just now, the USB plug on my PC acted up and the HDD was disconnected from the PC for a few seconds. Both VMs reported that as an error, but when I reconnected the HDD I initially was able to use the VMs again. They reported the error that they were unable to write to NVRAM, but I was able to close some windows after confirming the error.

    Sadly, this only lasted a few seconds, and both VMs froze entirely. Sending Ctr-Alt-Del via VMware menu did nothing, and trying to shut the guests down, even using the "Power Off" option didn't do anything either.

     

    Left with no other choices, I killed the VMware Player tasks via the host's task manager. Trying to start them up again was first denied because they were in use by another user, but knowing this issue I went into the folders and renamed the lck folders.

    When I try to start the VMs now, I get the following error:

    ---------------------------

    VMware Workstation 12 Player

    ---------------------------

    Error while powering on: VMware Player cannot connect to the virtual machine. Make sure you have rights to run the program, access all directories the program uses, and access all directories for temporary files.

     

     

    The VMX process exited prematurely.

    ---------------------------

    OK  

    ---------------------------

    I haven't done anything else so far to the VMs, and I can still play other VMs that weren't running when the HDD disconnected just fine.

     

    Is there any chance to recover these two VMs?


    0 0

    Hi,

     

    Been using VMWare Player for years with no problems.

    I am using the most up to date VMWare Player version 12.5.7 build-5813279.

     

    I have a Linux Mint 18.2 KDE 64Bit host

    with a Windows 10 Pro 64Bit guest.

     

    I have bad audio on the Win 10 guest.

    I've tried everything available on the Internet to fix this issue

    but it is still there.

    (it's on 3 different desktops, so we can illuminate a hardware issue)

     

    How do I fix bad audio on Win 10 guest?

    (the Win 10 guest is Genuine and virus free)

    If this is a known issue, when will Player be updated to fix this?

     

    If you need additional information then just ask, thanks!

     

    Jesse


    0 0

    Hi all,

     

    My VMWare workstation 12 Player stopped working to access anything but itself.  

     

    My VMWare is using 192.168.203.89/28, my host ( Windows 10 ) is using 192.168.203.86/28 and my gateway is using 192.168.203.81/28.

     

    On my VMWare , I can ping myself 192.168.203.89.  But I can't ping 192.168.203.86 or 192.168.203.81. Of course, I can't Ping 4.2.2.2 .

     

    On my VMWare, I installed Ubuntu, and Fortinet FortiManager products.  All not working. 

     

    This happened all of sudden.   I tried to use "Bridge mode", "NAT mode" , even "Host Only" mode for VMWare network settings, still same. 

     

    I also tried to repair / reinstall / upgrade to latest VMWare workstation 12 Player version 12.5.7, still same issue.

     

    This issue also happened to my laptop ( Windows 10 ) and my desktop ( Windows 8.1 ).

     

    Please can anyone help me on this issue?  I can't use my VMWare at all now.

     

     

    Regards,

     

    Jerry


    0 0

    Hi, I'm new to VM.  I've allocated 500MB hard disk - and want to reduce this now to 50 instead - can someone please help me work out how to do this?  I'm happy to uninstall and reinstall everything if that is easy enough to do?

     

    I'm using VM Workstation 12 Player.


    0 0

    Fail to copy files from CD-ROM.Legacy Emulation Is enabled and tried after disabling it too tried with both enabled and disabled.tried on all three nodes.The Iso Image Is 100% Fine.I booted a DVD from it and its running in Live mode please Help.I also get Error in Mounting Where As I have Nothing to Mount Because I am using .iso image.And the bad part is that My DVD was Cracked yesterday By My CD/DVD-ROM.Please Help.Images Below will Fully Describe You Whats Happening.

     

     

     

     

    2.jpg

    1.jpg


    0 0

    Chrome does not render the tab controls in any of its windows. The Chrome window's title bar where those buttons should be is just all white. Only the 3 window buttons are visible.

    Though when I right click somewhere on the title bar it shows the proper menus as if the tab is there but I just don't see it.

     

    In an incognito tab it looks like this:

     

    It's most likely a problem with how chrome renders its GUI and how VMware player accelerates rendering on GPU because when I go to the VM settings and uncheck "Accelerate 3D graphics" chrome renders normally again.

    I didn't have this problem initially when creating this VM, it just appeared someday.

     

    Gues OS:

    Win10 x64, 4G RAM, 4 Cores

     

    Host OS:

    Win10 x64, 16G RAM, i7 6700K (4c/8t), GTX 1070 8G (driver 384.94)

     

    Ultimately, I really don't want to reinstall my guest because of this annoying bug. Can something else be done?


    0 0

    Hi!

    I just installed VMWare Player 12 (12.5.7 build-5813279) and tried to install Windows Server 2016 Essentials. However, the configuration of Windows Server is stall at 17% - and it doesn't move further (screen shot attached). I tried it on two different computers - same thing. It's impossible to work with Windows Server until initial configuration is finished. From this I conclude this is something with VMWare.


    0 0

    I am trying to extend the life of a DOS application that works fine on Windows XP. It was running on an older PC that had a built in parallel port which worked for printing. Now that old PC died and only Windows 64 bit machines are available. I created a Windows XP virtual machine that runs on this machine in VMWare Player 12.5 and the host PC has a parallel port card on LPT3. I configured the VM settings to redirect the parallel port to the file "LPT3" and the DOS application in the VM prints perfectly to the printed attached Host PC... for a while.

     

    They don't use this app often so I just had them suspending the VM and resuming it when this app is needed which worked great several times. Now sometimes it works and sometimes when trying to print VMWare pops up the error message:  Parallel:Unable to write to the file "LPT3"  over and over and printing no longer works. We somehow got this working again after several reboots of the VM and the host. I don't even know what actually fixed it and it worked for a while again. It's in this state where it doesn't print again today and I really was hoping to find either an easy way to fix this when it happens, or better a way to prevent it from getting in this state.

     

    Any suggestions?


    0 0

    Hi! I have installed OS X as a guest OS in VMware Workstation 12, and I use a High DPI monitor, which causes the screen and fonts to be really small. I was able to fix the screen size using VMware Tools vmware-resolutionSet, so now the display size is bigger, but the fonts are still minimal. Is there any way to resize the fonts? OS X does not give me the option to use larger fonts as it doesn when you are using a Retina Display.

     

    Any help is appreciated! Here's a screenshot with this webpage for scale.

    osx_fonts.png


    0 0

    Is a running Windows Update Service" wuauserv required to update VMWareTools in Win guestOS?

     

    I set the built-in Windows Update to "Never check for updates".

     

    I guess the Windows Update Service is stopped due to this settings.

     

    If I want to update now VMWareTools it refused due to not avaliable Windows Update Service.

     

    If a running wsuaserv is required:

     

    Can I simply start iot with

     

    net start wuauserv

     

    ?

     

    Matt


older | 1 | .... | 201 | 202 | (Page 203) | 204 | 205 | .... | 252 | newer