Stuck ImageAssist - VMWare Workstation 12

Hello world

I'm having a problem where ImageAssist is blocked indefinitely at a point whenever I run it. I try to capture a Windows OEM 10 image created using VMWare Workstation 12. This post describes the exact steps I took:

ImageAssist crashes and then to 32 of the stages of this process, as shown in the screenshot below:

I actually left ImageAssist running overnight, and it never progressed beyond that point. The virtual hard disk is certainly big enough (60 GB) and I had no problems with the image at all. I even started from scratch and re-created the entire image to test again and ImageAssist still crashes at this exact point.

Any help with this problem would be greatly appreciated!

Hello

Windows 10 does a lot of things during a "Windows Update". Running it in a virtual machine is a good idea as not getting driver updates. There are a few more things that occur that cause problems. The reason ImageAssist fails generally after an update is because the system can no longer be Sysprep. To check that you can browse manually to sysprep. C:\windows\System32\sysprep and run the executable. If sysprep fails, the AI tool will also fail. The biggest culprit is when the OS is upgraded. Windows 10 will upgrade to the latest version which won't allow sysprep run. Microsoft tells us that "Redstone" will not have this problem. You should also know that the 'Crush Saga of Candy' and 'Twitter' can install, causing sysprep to no longer work. I hope this helps... TK

Tags: Dell Tech

Similar Questions

  • Problem installing Windows on VMWare Workstation 11 10

    Good evening

    I'm a french user on VMWare.

    I have a problem when I try to install Windows on VMWare Workstation 11 10, I'm stuck here:

    Capture.PNG

    I tried several times to reinstall.

    I use this iso standard: Windows10_TechnicalPreview_x64_FR - FR_9926.iso

    Can you help me?

    See you soon.

    Set up 2 x 2 cores CPU and memory: 3 GB

  • VMware workstation 11 and Windows 10 build 9926 auto resizing does not

    Host: Windows 8.1 Pro x 64

    VMware: Workstation 11

    Client: Windows 10 Build 9926

    Problem I have is in the guest operating system (win 10).  I can not auto resize the guest to fit the window (now Vmware worksation, opinion, comments made.  It flashes on the full screen, then goes back to the resolution that it is.  I'm stuck at the Windows gives me resolutions.

    I know that this version comes out today.  But I thought I'd give you guys a heads up.

    THX.

    Build 10074 works!

    So, I did a clean install of the new generation (10074).  Workstation makes easy installation on it.  During the easy setup process, it didn't install VMWare tools, but I see the tools have been installed.  I tried to re-size that the screen with 3D powered acceleration; and it worked!

    This issue is finally resolved. !

  • VMware Workstation 7.1.3 Installer empty in Windows 7 x 64

    Hello

    I am trying to install a new copy of VMware Workstation 7.1.3 in my PC (WIndows 7 x 64), and I have a white screen instead of the installation steps, please see the image below:

    blank_installer.jpg

    Can someone help me with this problem? Thank you.

    Hi all

    I had a lot of pain with this and spent all day trying to reset the internet settings, java update and finally found the solution has been associated with an adobe update that fills the internet zone settings in the registry and prevents the display of the Setup window is displayed according to the original screenshot stuck by hiperjp.

    Here is the solution

    Export the key below before deleting. Do a right click and export.

    You must remove 1 (parasite) of additional area

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\¬]

    Basically it has a Pseudo-graphique number, you will see before the zone number 0.

    It seems that it is a bug in update of Adobe flash player, but I'm not sure.

    This additional area prevents the desktop gadgets to figure out properly and also prevented an other Java windows look in other products Secunia 2 being one of them.

    Thank heavens, it drove me crazy!

    Putneyboy

  • VMWare Workstation 6.5.1 & Windows 95 PCI Bridge / peripheral system

    Hello everyone.

    I tried to create a virtual image of Windows 95 in VMWare workstation.  I managed to create one for Win98, WinNT and Win2000.  But I'm having trouble with Win95 (I tried both Win95B and Win95C).

    Installing Windows 95 in VMWare workstation work perfectly fine, but I'm still stuck with an unrecognized hardware...

    In the Windows 95 Device Manager I see:

    Other devices

    |

    +-- ? PCI bridge

    |

    +-- ? System PCI device

    SCSI controllers

    |

    +-- ! Bus PCI SCSI controller

    Network is fine and his card seems to be installed correctly, but I still can't audio.  I'm guessing it's because the devices PCI is not installed correctly.  Anyone can please help / guide me in getting those devices installed correctly.  I tried my luck with google and research here, but no luck so far.

    Thank you very much.  Kind regards

    Willem Moolenaar

    PS. I've attached a screenshot of the Device Manager.

    You have installed VMware tools in this prompt again?  The tools must contain the device drivers for the bridge network, SCSI, PCI devices etc.  For audio, you can download the driver for the Creative Labs site for card SoundBlaster AudioPCI (ES1371).  See the OS Installation Guide invited for specific details.

  • Re: Satellite keyboard Funtions vs. VmWare Workstation

    Hello

    I'm new to this forum...
    I recently bought a Toshiba Satellite U500-115.
    After you install all the programs I need, I noticed that the eco and the start/stop button lights buttons didn t work anymore.

    I uninstalled programs Toshiba - nothing works. So I installed win 7 pro x 64 again.
    Buttons worked!!

    I discovered that vmware workstation 6 and 7 are at the origin of this problem.
    As soon as I install the vmworkstation software the keys won´t work.
    Uninstall--> buttons work.
    I don't want to use both: buttons and vmware 6 or 7.
    It seems to work with vmware 5.x, but this version of vmware is officially not recommended to work with win7. It takes about 10 minutes push button vmware initially until the vm ware starts booting.

    Perhaps someone could confirm this problem.
    Hope of a quick solution!
    Concerning
    bachmayeah

    Maybe it sounds pessimistic now, but I don't think you'll have a quick solution to this.
    The feature tools and utilities Toshiba is tested with the own operating system preinstalled and not with some third-party additional party software.
    Can you imagine how these applications you will find there? Who should test the functionality with hundreds of other application? It is certainly not possible.

    I use VmWare, but I imagine that there is a problem where two applications met the other.

    Sorry, but I don't think that there is nothing you can do about it.

  • Qosmio F50-111: control buttons stopped working using VMWARE Workstation

    Hello

    Since I've installed VMWARE Workstation v6.0.3, my touch buttons (play, pause, stop, media library, next, previous, updated muted and light webcam and dolby) stopped working.

    So I chose Restore my Vista before installing on my VMWARE of ve. It works again my buttons work...

    BUT I need to install this software (vmware) for my use of employment.

    I've tried remove and install then new value-added Package from Toshiba Web site, but it does not work.

    Please help me

    This means that applications (in TBS folder, such as TDspBtn.exe, TBSbtnSt.exe,...) start running, but stops immediately.

    Thank you for coming to help

    Here the solution:
    http://forums.computers.Toshiba-Europe.com/forums/thread.jspa?MessageID=181231

    + After the installation of vmware workstation 6.x or 7 - the default setting is "Disable Autorun on the host". (you can find it in: Edit-> preferences-> devices). +
    + Clear hook and restart. After the reboot, the buttons should be working. +

  • Toshiba button Support do not work with VMware Workstation

    Hi all

    for all people having the same problem - * Support Button Toshiba do not work after the installation of VMware Workstation.*

    Short solution:
    After the installation of vmware workstation 6.x or 7 - the default setting is "Disable Autorun on the host". (you can find it in: Edit-> preferences-> devices). Release the hook and restart. After the reboot, the buttons should be working.

    The long version:
    Support Button Toshiba uses the Windows function "MobilePC" - > "Hotstart". HotStart only works when the autostart feature is not disabled (the value of registry key: + HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Po licies\Explorer\NoDriveTypeAutoRun + has the value 0xFF). VMware is the default to disable Autorun of CD/DVD. Turn on the autorun, restart the Qosmio and Hotstart (and also Toshiba button support) works very well. That's the problem.

    Greeting
    Thomas Wermuth

    Thanks for the solution. :)

  • K6V69AV #ABA: HP Desktop 500-520qe: cannot install VMWare Workstation

    I try to install the virtual machine using vmware workstation or vmware player.  But it gives me the message saying Intel vt - x is not enabled. I've seen a few videos youtube that says that I need to enable virtualization, but I don't seem to have seen.  Can anyone suggest if there is something else?

    Hello

    Open the command run and enter: MSINFO32

    The returned information will tell you if virtualization is enabled.  If this isn't the case, then you need to make a change in the BIOS to turn on VT is defined by default to disable.  See the image below.

  • VMWare Workstation and Windows 7 64 bit

    Someone had problems with VMWare Workstation running Windows 7 64 bit? My computer hangs when creating the virtual machine guests. I also have VirtualBox running very stable with Windows 7. I was wondering if anyone has had problems? VMWare has a new version of 7 who suppose to be stable with Windows 7. I am skeptical. Your comments are welcome.

    "There is a time and place for that. The time is... Never. You can figure out the place on your own.

    I have no problem with VMware Workstation 7.0.1 build 227600 and Windows 7 Ultimate edition. It works like desingned.

  • VMWare Workstation UI error

    I have a HP Pavilion DV7 running Windows 7 64-bit 4 GB of ram

    I'm trying to install VMWare Workstation as part of a communications car software install, whenever I get the same expired error, I downloaded from the internet the same version, the latest version and still the same, so I think that the problem is with my machine, even though everything else works perfectly.

    I don't have any antivirus installed and I tried to not disable the firewall... no joy.

    I read all kinds online but it is all over my head as I try fails.

    Y at - it someone who can display a resolution that is simple to follow and makes sense for a dummy code?

    Everyone please help.

    Thank you.

    Hi Mark,

    You can post your question to the community of VMware using the link below.

    http://communities.VMware.com/index.jspa

    I hope this helps.

  • ACS 5.4 installation on vmware workstation

    Hi all

    is it possible to install cisco acs 5.4 on vmware workstation 8?

    Thank you

    Pellen

    Yes.

    Check this box:

    https://supportforums.Cisco.com/message/3714114

    Rating of useful answers is more useful to say "thank you".

  • ACS 5.3 vmware Workstation Ubuntu

    Hello

    I managed to install ACS 5.3 on vmware 8.0.4 (Ubuntu 12.04).

    I can connect but I have some fatal errors from the server ({0} or 500) when you work wihthin access policies.

    I can not change (or same) selection of selection of unique result of selection of the rule result. That triggered the error message.

    My question:

    VMware workstation is really OK 5.x (I got the same errors with 5.1 and 5.2 even on windows 7 / vmware workstation 9)?

    Best regards.

    Vincent.

    Thank you for following it upwards. + 5.

    Tarik Admani
    * Please note the useful messages *.

  • VMWare Workstation 12 and 18 of Linux Mint (Ubuntu 16.04) and vmware tools or open-vmware-tools

    I created a new virtual machine using VMWare Workstation 12.1.1 build-3770994 with a guest OS from Linux Mint 18 (which is built on top of Ubuntu 16.04). I have two monitors on my system, the two 2560 x 1440. I am unable to get this virtual machine Linux Mint 18 to cover all of my two monitors when I disable "Accelerate 3D graphics" in my vm settings, I get an error. I have another Linux Mint 17 VM running on the same VMWare Workstation 12 on the same host machine from Windows 10 and it is able to expand on my two monitors very well with "Accelerate 3D graphics" disabled, but he does not open-vmware-tools.

    I have read instructions telling me to install open-vm-Tools-Office in this guest operating system of Linux Mint 18. I did it. Then I restart the guest operating system. When starting, I can click on 'Enter full screen mode' in my menu of VMWare Workstation, and the guest OS has a monitor as expected. When I then click on "Cycle multiple monitors", I get the following error. "The virtual machine could not be changed to the selected screen layout. If you add a monitor to the host computer, you must turn off and turn on the virtual machine to use this monitor. »

    vmware-monitors-error.jpg

    I can optimize my VM to automatic adjustment, only one of my two screens, but not both. I tried to uninstall and reinstall open-vm-tools, open-vm-tools-desktop and restart. I tried to use /vmware-tools-distrib/vmware-install.pl's original vmware tools and who does not work either.

    In my vmware.log, I get these two lines that occur when I get the above error.

    2016 07-12 T 15: 43:19.068 - 06:00 | MKS | I125: ToolsSetDisplayTopology: send rpcMsg = 1 DisplayTopology_Set, 0 0 2560 1440

    2016 07-12 T 15: 43:24.768 - 06:00 | MKS | I125: ToolsSetDisplayTopology: rpcMsg sending = DisplayTopology_Set 2, 0 0 2560 1440, 2560 0 2560 1440

    2016 07-12 T 15: 43:24.853 - 06:00 | vCPU-1 | I125: TOOLS of the call to DisplayTopology_Set failed.

    When I activate "Accelerate 3D graphics" with the configuration described above, I am able to use both of my monitors. Why is this the case?

    I think remember having to disable "Accelerate 3D graphics" in my Linux Mint 17 comments vm because it would crash randomly. I try to run this VM Linux Mint 18 with 3D acceleration and see if it crashes, but why is there a difference with spanning multiple monitors?

    Thank you.

    I didn't experience this problem for a few weeks. I don't have a definitive answer to my original problem.

    I installed Mate instead of cinnamon 3 to my MINT 18. Then, I created a new VM with Ubuntu Gnome 3 16.04 running as the OF. I did have problems with both approaches. I also tried using Firefox as my main browser instead of Chrome, as I read that Chrome can have problems of memory. It could be a combination of several of these changes that have allowed me to work without problems.

    Knowing what I know now, I think the move away from cinnamon 3 is what seems to have fixed my problems. I can certainly say that you use Firefox consumes less memory, as I can monitor the monitor system under Ubuntu. Chrome would eventually eat all my system memory, that I could see. The extent of the why? I'm not sure at this point.

  • VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

    Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

    After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

    2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

    Hi, I faced the same problem, and now I have corrected this issue.

    He was vmnet.ko, at least for me.

    Here's how to solve,

    You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

    Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

    And then run vmware, if you fail at the first, please run again.

    If so, you can run vmwre!

    I hope this will help you.

    Good day.

Maybe you are looking for

  • keyboard and multi langgages

    I work with a QWERTY keyboard. Because I often write in different languages, I would like AutoCorrect in the language I'm writing in. I know that on an iPhone and an iPad that's easy to do. I know that I can add different keyboards in iMac as well, b

  • Bluetooth process causes 100% CPU

    Hello After the installation of the battery of Toshiba BT my CPU usage is 100%.It seams like the process TosOBEX is the largest consumer of it. How can I solve this? Thank you!/ Tommy

  • HP flow: the Administration password

    request a password from the administration and got the disabled system number 53620114

  • Stripped of Remote Desktop Web 2012

    I am looking for a lighter version of the Remote Desktop Web site available in r2 Server 2012/2012. I tried to pull him out so that I have a minimum of just the login page and none of the other sees it as the Web, SharePoint workflow hooks, etc.. All

  • Getting the 80070005 error during the backup with windows vista home premium then closes backup

    When I use backup in windows I get errors then backup closes. the errors were 0x800700AA and now 0x80070005. I'm not familiar with what they mean but have tried Fixit without success.