VMware workstation, crashes when I try to create a new virtual machine

Hello

I never had this problem before, but I didn't create a new virtual machine in a very long time. Last time I created one was making Workstation 9 I think. Some time after the upgrade to Workstation 10 or 8.1 of Windows Update 1 it has started.

In 10 Workstation running on Windows 8.1, I select the file > new Virtual Machine dialog coming upwards and in a few seconds crashes of VMware workstation and closes.

So I checked the Windows event logs and find

Warning "VMware Workstation to function properly, must be reinstalled after the upgrade to Windows."

So, I upgraded from 10.0.2 to 10.0.3 and it uninstalled and reinstalled but I still get this warning.

Followed by an error

***

Journal name:Application
Source:Application error
Date:15/08/2014 23:33:53
Event ID:1000

Task category: (100)

Level:Error
Keywords:Classic
User:N/A
Computer:P7Win8MC

Description:

Name of the failing application: vmware.exe, version: 10.0.3.48389, time stamp: 0x539a4fb0

Name of the failed module: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

Exception code: 0xc0000005

Offset: 0x0003bece

ID of the process failed: 0 x 1788

Start time of application vulnerabilities: 0x01cfb902de541c11

The failing application path: C:\Program Files (x 86) \VMware\VMware Workstation\vmware.exe

Path of the failing module: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

Report ID: 24d5effb-24f6-11e4-bedd-20cf30780548

***

So I need help to track down what I am not sure what VMware paper to look to maybe see what is happening.

Thank you

Rainey

Well, I found the problem.

I looked in the UNK file and found a few ISO files wrongs tracks.

I had mounted some ISO in the past and they have made the entry in this file of preferences such as "isoLocationMRUx".

I'd change the leter this ISO file player so they could not be found as input, once I corrected the paths I can now create a new virtual machine.

He is responsible for ion BONE the new virtual machine now.

Tags: VMware

Similar Questions

  • . ISO is grayed out when you try to make the new Virtual Machine

    I recently downloaded fusion VM 5 and I am trying to make a virtual machine for windows 7 without using a disc. I use an .iso file that is saved on my mac. When I'm in the new virtual machine Wizard and go click win7.iso I can't because the text and thumbnail are grayed out and won't do anything. Help, please.

    The page you are showing has noting to do with the installation of an ISO Image, it takes to with the virtual hard disk.  The ISO Image is assigned to the CD/DVD in the settings of the Virtual Machine if you don't select it in the wizard at the beginning.

    Documentation (integrated help file).

    1 Select file > new.

    2 the new Virtual Machine Assistant starts.

    3 click on continue without disc to go to the installation media Panel.

    4 in the installation media Panel, click on the image or use operating system installation disc.

    5. use the drop-down menu to locate the file .iso for the operating system.

    6 click Open to identify the file and click on continue to go to control panel of the operating system.

  • I can't create a new virtual machine, for the error "invalid state" of vmware

    Hi, I have an esx server with some production virtual machines vmware;

    Yestarday I made a new VM, suse linux, froma cdrom; but the file system broke down, it has been altered, I don't know why,

    and I had to cancel the machine using the "remove disc";

    After that I could read "a system general error occurred" and when I click on create a new virtual machine (ctrl + n), I can't because the answer is "invalid state".

    When I click on each virtual machine in 'events', I do not see the logs, I see this error "system general error occurred.

    can someone help me? , should I restart the service mgmt-vmware?  (init.d) on the host server?

    Thanks in advance, best regards

    Toscano Max

    If you use Virtual Center, rebbot VC server and try again. If this does not work, you may have to restart the ESX host.

  • When I try to create a (new folder) the Briefcase icon appears instead

    When I try to create a (new folder) the Briefcase icon appears instead. What is going on? When I try to create a (new folder) in some files, it tells me that the choice is 'empty' what can I do to get the files works again?

    * original title - cannot create a "new folder."

    Hello

    ·         Did you make any changes before the show?

    I suggest that you create a new user account and check if the problem persists since the new user account:

    http://Windows.Microsoft.com/en-us/Windows-Vista/create-a-user-account

    If the problem does not persist and then follow the link below to fix the corrupted account:

    http://Windows.Microsoft.com/en-us/Windows-Vista/fix-a-corrupted-user-profile

  • When I try to create a new folder of file I get the error Code 0 x 80070570

    When I try to create a new folder of file I get the error Code 0 x 80070570

    Hello Denny,


    Thanks for the reply with the State of the question, sorry for the caused incontinence.
    I suggest you follow the suggestion of Babu V replied on 16 may 2013

    CHKDSK WARNING: Running chkdsk on the drive if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data can be lost.

    Please respond with the State of the question of assistance in
    Windows.
  • I don't have a blank page option when you try to create a new page

    I don't have a blank page option when you try to create a new page, what should I do?

    When questions about the user interface, it helps if you say that you are using which version of Dreamweaver. It sounds as if you are using the latest version of Dreamweaver CC, but try to follow instructions written for an older version. This is the new Document dialog box in Dreamweaver CC 2015:

    New Document has replaced the White Page in older versions. To get a blank page, select New Document in the left column, HTML as a Type of Document and there is no tab for framework.

  • Illustrator crash when I try to open a new file or an existing file. What should I do?

    Illustrator crash when I try to open a new file or an existing file. What should I do?

    Our creative cloud has had some problems in the updates and I've installed illustrator again with the new version of the cc for 2014, but the rest of the problem.

    I found the solution! I begged the rep and the supervisor to help me, even if they are not (like a policy) support Surface Pro 3 because "it's a tablet" (LOL!-c' is still a laptop with a detachable keyboard). It's a necessary printer updated driver. That's all. Unfortunate as a broken printer driver my paperless work stream, but happy, it is fixed.

  • Crash when the instant withdrawal: State of the virtual machine is 'unknown (invalid) '.

    Hi all

    Currently, I'm in the middle of a nightmare: a few moments I tried to delete a snapshot that has been there for a while on one of my virtual machines. Of course, it can take a loy of time for this kind of operation to achieve, so I waited patiently so that it reaches its end.

    But in the middle of it my host had a kernel panic (I'll have to diagnose this one).

    When I got to new host, the virtual machine was not the webui, try saving it shows the machine as being "unknow (invalid)"...

    I scoured Suur intrenet for a while, but everything I have read until knowledge is quiet frightneging.

    Currently, the directory that stores all the files of the virtual machine is looking as follows:

    drwxrwxrwx 2 root root 4096 12 October 2008 564d583c-363e-0c7a-96e0-cd07d5b1a8e1.vmem.lck

    -rw - 1 root root 2147221504 2 May 20:31 colossus2_2new - f001.vmdk

    -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_2new - f002.vmdk

    -rw - 1 root root 1074266112 Jan 11 22:27 colossus2_2new - f003.vmdk

    -rw - 1 root root 528 2 May 20:31 colossus2_2new.vmdk

    -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f001.vmdk

    -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f002.vmdk

    -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f003.vmdk

    -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_3new - f004.vmdk

    -rw - 1 root root 2147221504 Jan 11 22:35 colossus2_3new - f005.vmdk

    -rw - 1 root root 1310720 Jan 11 22:35 colossus2_3new - f006.vmdk

    -rw - 1 root root 661 2 May 20:32 colossus2_3new.vmdk

    -rw - 1 root root 2147221504 2 May 20:32 colossus2_4new - f001.vmdk

    -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f002.vmdk

    -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f003.vmdk

    -rw - 1 root root 2147221504 2 May 20:34 colossus2_4new - f004.vmdk

    -rw - 1 root root 2147221504 2 May 20:35 colossus2_4new - f005.vmdk

    -rw - 1 root root 1310720 Jan 11 22:42 colossus2_4new - f006.vmdk

    -rw - 1 root root 661 2 May 20:35 colossus2_4new.vmdk

    -rw - 1 root root 1868365824 2 May 22:13 colossus2_5new-000001 - s001.vmdk

    -rw - 1 root root 1637482496 2 May 22:13 colossus2_5new-000001 - s002.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s003.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s004.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s005.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s006.vmdk

    -rw - 1 root root 2096824320 2 May 22:13 colossus2_5new-000001 - s007.vmdk

    -rw - 1 root root 554369024 2 May 22:13 colossus2_5new-000001 - s008.vmdk

    -rw - 1 root root 1728839680 2 May 22:13 colossus2_5new-000001 - s009.vmdk

    -rw - 1 root root 2114191360 2 May 22:13 colossus2_5new-000001 - s010.vmdk

    -rw - 1 root root 1659371520 2 May 22:13 colossus2_5new-000001 - s011.vmdk

    -rw - 1 root root 1527775232 2 May 22:13 colossus2_5new-000001 - s012.vmdk

    -rw - 1 root root 1578958848 2 May 22:13 colossus2_5new-000001 - s013.vmdk

    -rw - 1 root root 1611792384 2 May 22:13 colossus2_5new-000001 - s014.vmdk

    -rw - 1 root root 1602945024 2 May 22:13 colossus2_5new-000001 - s015.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s016.vmdk

    -rw - 1 root root 2085617664 2 May 22:13 colossus2_5new-000001 - s017.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s018.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s019.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s020.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s021.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s022.vmdk

    -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s023.vmdk

    -rw - 1 root root 132055040 2 May 22:13 colossus2_5new-000001 - s024.vmdk

    -rw - 1 root root 327680 2 May 22:13 colossus2_5new-000001 - s025.vmdk

    -rw - 1 root root 65536 2 May 22:13 colossus2_5new-000001 - s026.vmdk

    -rw - 1 root root 1582 Mar 8 17:53 colossus2_5new - 000001.vmdk

    drwxrwxrwx 3 root root 4096 2 May 22:14 colossus2_5new - 000001.vmdk.lck

    -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f001.vmdk

    -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f002.vmdk

    -rw - 1 root root 2147221504 2 May 20:37 colossus2_5new - f003.vmdk

    -rw - 1 root root 2147221504 2 May 20:38 colossus2_5new - f004.vmdk

    -rw - 1 root root 2147221504 2 May 20:39 colossus2_5new - f005.vmdk

    -rw - 1 root root 2147221504 2 May 20:41 colossus2_5new - f006.vmdk

    -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f007.vmdk

    -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f008.vmdk

    -rw - 1 root root 2147221504 2 May 20:43 colossus2_5new - f009.vmdk

    -rw - 1 root root 2147221504 2 May 20:45 colossus2_5new - f010.vmdk

    -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f011.vmdk

    -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f012.vmdk

    -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f013.vmdk

    -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f014.vmdk

    -rw - 1 root root 2147221504 2 May 20:48 colossus2_5new - f015.vmdk

    -rw - 1 root root 2147221504 Feb 11 13:19 colossus2_5new - f016.vmdk

    -rw - 1 root root 2147221504 8 Mar 17:17 colossus2_5new - f017.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:02 colossus2_5new - f018.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f019.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f020.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f021.vmdk

    -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_5new - f022.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:04 colossus2_5new - f023.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f024.vmdk

    -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f025.vmdk

    -rw - 1 root root by 6553600 Jan 11 23:05 colossus2_5new - f026.vmdk

    -rw - 1 root root 1562 2 May 20:35 colossus2_5new.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f001.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f002.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f003.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f004.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f005.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f006.vmdk

    -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f007.vmdk

    -rw - 1 root root 1075576832 2 May 20:31 colossus2 - f008.vmdk

    -rw - 1 root root 8684 2 May 20:19 colossus2.nvram

    -rw - 1 root root 714 2 May 20:31 colossus2.vmdk

    -rw - 1 root root 821 2 May 20:31 colossus2.vmsd

    drwxrwxrwx 2 root root 4096 2 May 22:13 colossus2.vmsd.lck

    -rwxr-xr-x 1 root root 2680 may 2 21:35 colossus2.vmx

    -rw - 1 root root 264 Jan 11 22:25 colossus2.vmxf

    -rw - rr 1 root root 98347008 1 October 2008 gparted-live - 0.3.9 - 4.ISO

    -rw - rr 1 root root 1581428 Jan 13 11:53 0.log - vmware

    -rw - rr 1 root root 771239 19 Dec 12:59 vmware - 1.log

    -rw - rr 1 root root 76388 Jan 11 23:21 vmware - 2.log

    -rw - rr 1 root root 10161063 2 May 20:18 vmware.log

    The vmx file contains the following:

    #! / usr/bin/vmware

    . Encoding = 'UTF-8 '.

    config.version = '8 '.

    virtualHW.version = "7".

    floppy0. Present = "FALSE".

    MKS. Enable3D = 'TRUE '.

    pciBridge0.present = 'TRUE '.

    pciBridge4.present = 'TRUE '.

    pciBridge4.virtualDev = "pcieRootPort"

    pciBridge4.functions = '8 '.

    pciBridge5.present = 'TRUE '.

    pciBridge5.virtualDev = "pcieRootPort"

    pciBridge5.functions = '8 '.

    pciBridge6.present = 'TRUE '.

    pciBridge6.virtualDev = "pcieRootPort"

    pciBridge6.functions = '8 '.

    pciBridge7.present = 'TRUE '.

    pciBridge7.virtualDev = "pcieRootPort"

    pciBridge7.functions = '8 '.

    vmci0. Present = 'TRUE '.

    NVRAM = "colossus2.nvram."

    virtualHW.productCompatibility = "hosted".

    FT.secondary0.enabled = 'TRUE '.

    Tools.Upgrade.Policy = "useGlobal".

    powerType.powerOff = 'soft '.

    powerType.powerOn = "hard."

    powerType.suspend = "hard."

    powerType.reset = 'soft '.

    displayName = "colossus2."

    extendedConfigFile = "colossus2.vmxf".

    scsi0. Present = 'TRUE '.

    scsi0.sharedBus = 'none '.

    scsi0.virtualDev = "free".

    memsize = "4096".

    scsi0:0. Present = 'TRUE '.

    scsi0:0. FileName = "colossus2.vmdk".

    IDE1:0. Present = "FALSE".

    IDE1:0. FileName = ' / vmachines/colossus2/gparted-live-0.3.9-4.iso '.

    IDE1:0. DeviceType = "cdrom-image".

    IDE1:0.allowGuestConnectionControl = "FALSE".

    ethernet0. Present = 'TRUE '.

    ethernet0.allowGuestConnectionControl = "FALSE".

    ethernet0. Features = "1".

    ethernet0.wakeOnPcktRcv = "FALSE".

    ethernet0.networkName = "Bridged".

    ethernet0. AddressType = 'generated '.

    guestOS = "rhel3.

    UUID. Location = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

    UUID. BIOS = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

    VC. UUID = "52 88 6f 19 b2 66 ae 20-28 5 c 6 b 8 b 96 a1 15 6 d.

    scsi0:1.present = 'TRUE '.

    scsi0:1.filename = "colossus2_2new.vmdk".

    scsi0:1.writeThrough = 'TRUE '.

    scsi0:2.present = 'TRUE '.

    scsi0:2.filename = "colossus2_3new.vmdk".

    scsi0:2.writeThrough = 'TRUE '.

    scsi0:3.present = 'TRUE '.

    scsi0:3.filename = "colossus2_4new.vmdk".

    scsi0:3.writeThrough = 'TRUE '.

    scsi0:4.present = 'TRUE '.

    scsi0:4.filename = "colossus2_5new - 000001.vmdk".

    scsi0:4.writeThrough = 'TRUE '.

    IDE1:0.startConnected = 'TRUE '.

    IDE1:0.clientDevice = "FALSE".

    ethernet0.generatedAddress = "00: 0C: 29:b1:a8:e1.

    tools.syncTime = "TRUE".

    scsi0:0. Redo = «»

    scsi0:1.redo = «»

    scsi0:2.redo = «»

    scsi0:3.redo = «»

    scsi0:4.redo = «»

    vmotion.checkpointFBSize = "16777216.

    pciBridge0.pciSlotNumber = "17".

    pciBridge4.pciSlotNumber = "21".

    pciBridge5.pciSlotNumber = "22".

    pciBridge6.pciSlotNumber = "23".

    pciBridge7.pciSlotNumber = "24".

    scsi0.pciSlotNumber = "16".

    ethernet0.pciSlotNumber = "32".

    vmci0.pciSlotNumber = "33".

    ethernet0.generatedAddressOffset = '0 '.

    vmci0.ID = "-709777183".

    sched.mem.pshare.Enable = "FALSE".

    mainMem.useNamedFile = "FALSE".

    MemTrimRate = '0 '.

    MemAllowAutoScaleDown = "FALSE".

    Could someone point me to a solution if there is? I have Saturday night here and I would not spend my Sunday to rebuild the server from scratch and have to explain Monday morning I lost 2 months of work for users little by relying on this virtual machine.

    Thank you very much in advance!

    bugjargal,

    In the past if I had a VM that is displayed as invalid when you try to add it to the inventory, I usually just created a new virtual machine based on the original settings & attached the existing VMDK.  Not sure how that will work with a virtual machine that has snapshots, but can be worth (nothing to lose)?

    Doug.

  • HDD USB not recognized as "physical1" when creating the new virtual machine

    Hi all

    I wanted to create a new virtual machine, and I wanted to use my USB as a physical drive.

    But Workstation shows me "physical0" which is of course my drive internal.

    I tried USB pen drives. They are not recognized either.

    This somehow is no longer supported? I would have that it would be possible to use USB external HDD as the physical drive to a new virtual machine.

    you have installed VirtualBox?

    If so, you can try to use the virtuaklbox command line tool to create a descriptor of rawdisk for this disc.

    say diskpart on this drive? -It is "online"?

    _________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

    You find me also in the PhD Virtual Backup support team

  • How to specify the file of virtual hard disk when you create a new virtual machine using virtual hard disk on the data store?

    I'm new to PowerCLI and find quite simple, but in the documentation I read, I don't see how to use a virtual hard drive, existing on a data store when you create a new virtual machine.

    Is this simple registration on the virtual hard disk, or did I miss something?

    My current create VM is the following statement:

    New-VM

    -Name $TargetHostName -host $TargetVMCenterHost -data store $TargetVMCenterDatastore DiskMB - 20000 -MemoryMB $TargetHostMemoryMB -NumCPU $TargetHostCPUs -ID $TargetHostOS -CD -Description $TargetHostName

    Didn't notice this before, but I think that vSphere will use a backslash instead of a slash in the paths.

  • Upgrade to ESXi 5.0 to 5.1 - No Hardware 9 option available when creating a new virtual machine

    Greetings,

    I improved my esxi U1 5.0 to 5.1 and attempted to create a new virtual machine in hopes of using the new version of material 9.

    Using the standard and Custom options I been unable to create a Version 9 hardware VM by default.

    The only option I had was manually upgrade to version 9 once the virtual machine was created.

    Any thought or is - this as planned? I need to reinstall from scratch, my host?

    dhayashi

    To create virtual machines with HW version 9, you can use the Web Client, rather than the windows based Client vSphere.

    André

  • Error during communication with the remote host when you create the new virtual machine

    I'm under 7 ESX servers on IBM Blade H22 there is a mistake to invite while I create a new virtual machine

    on the vcenter Server

    At the end of 30-35 minutes, it gives an error

    "Error during communication with the remote host"

    The existing machines are working well... I tried to create virtual machines to other ESX servers as well

    but the same question. I also tried to make the clone of existing machines, but without success

    Can anyone help?

    You rescan the LUNS once?

    You've restarted the management agent?

    You've restarted the vpxa?

    If this isn't the case, please perform the step above and check out them.

  • create the new virtual machine, access to a physical disk

    I just created a new virtual machine. Then, I deleted the preconfigured disk and added a physical disk. This drive is connected to my computer with an S - ATA to USB docking station. The wizard displays all of the data, were leaving and so on correctly. But when I try to turn on the virtual machine, it tells me that it cannot access the drive.

    What I am doing wrong?

    I use Windows 7 64-bit with VMware Player 3.

    http://communities.VMware.com/docs/doc-10455

    ___________________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

  • create a new virtual machine with the default settings?

    I was wondering if there was a way to create a new virtual machine with the default settings.

    For example, let's say I want all new Lion VM to have 2 CPU cores. Is there a way to set this automatically? There are other parameters I want a new machine to inherit automatically, I was wondering if there is an automatic way to do this, or is it a feature request...

    Thanks in advance

    lerker wrote:

    Just for my clarification, when you say a vm model, basically I would execute a finder copy then drag back to the VM library, right?

    Yes.

    On the orders of spcirpting, it would be unix commands or are there specific vmware controls that make your job easier (in Applications/VMware\ Fusion/content or elsewhere)...

    IIRC, VMware Fusion 3 and later versions has an AppleScript dictionary, but it is not yet officially supported and may not be able to do what you want so, basically, only Unix Shell scripts, that's what I was referring to.  For an example, see my script attached to the following response: Re: vmware - script of the creation of the vm and the operating system installation process

  • You can create a new virtual machine snapshot from another machine?

    Hi all!  I was wondering - is it possible to create a new virtual machine with an existing snapshot of a running virtual machine?  Or should I essentially clone the machine to a new virtual machine and then go back to the snapshot I want?

    I use ESX Server 3.5 with a Lefthand SAN - and was curious to know if there may be either a separate utility, I can run or if the VI Client contains all the tools I would need?

    Thank you all for your time!

    Good question, I know you can do this with VMware Workstation:

    1 VM > overview > Snapshot Manager

    2. Select the snapshot > Clone

    However, for VMware ESX, I think you should use vmkfstools to the service console.

    Basically, you have already created a snapshot and just need to copy the vmdk files, create a new virtual machine and attach an existing drive. I think that's what you're looking for: cloning a Virtual Machine running using the Console Service

Maybe you are looking for