<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Exception 0xc0000005 (access violation) has occurred when starting VM in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2874077#M171967</link>
    <description>&lt;P&gt;I'm having a similar issue but don't think its the video driver. I have Workstation 15.5 with Windows 11 on a Surface Pro 8. I have disabled Hyper-V but no luck.&amp;nbsp; I have attached my log file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sun, 24 Oct 2021 14:28:49 GMT</pubDate>
    <dc:creator>smccrary</dc:creator>
    <dc:date>2021-10-24T14:28:49Z</dc:date>
    <item>
      <title>Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266480#M71647</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a WIndows 2003 R2 image using VMware Workstation 6.5.5 build 328052.&amp;nbsp;&amp;nbsp; The host is Windows 7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was working fine, but now I am seeing Exception 0xc0000005 a while after I start the image.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am attaching the dmp and log that VMware Workstation produced hoping someone can tell what might have gone wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: melahn: added vmx file also&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 Mar 2012 18:46:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266480#M71647</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-18T18:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266481#M71648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;I have did followings task for solved this problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. uninstall vmware tools from control panel;&lt;/P&gt;&lt;P&gt;2. stop all vmware services, exit VMWare tools;&lt;/P&gt;&lt;P&gt;3. delete install directory, eg. c:\Program Files\Vmware;&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; open c:\windows\system32, delete all files of vmware, eg: vm*.dll, can&amp;nbsp; identify by description of file; some files maybe can't be delete; go to&amp;nbsp; 5&lt;/P&gt;&lt;P&gt;5. reboot system;&lt;/P&gt;&lt;P&gt;6. do 4 again;&lt;/P&gt;&lt;P&gt;7. install new&amp;nbsp; vmware tools. or copy all files from vmware tools' install cd to&amp;nbsp; c:\windows\temp, click setup.exe(setup64 for x64) to install. I select&amp;nbsp; the last method.&lt;/P&gt;&lt;P&gt;8. reboot. the problem has been solved.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Milton &lt;IMG src="http://emoicons.us.to/laugh.gif" /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 11:14:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266481#M71648</guid>
      <dc:creator>orthohin</dc:creator>
      <dc:date>2012-03-19T11:14:24Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266482#M71649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@ Orthonin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;did you look at the vmware.log ? - obviously not ...&lt;BR /&gt;Uninstalling vmware-tools is a rather strange tip here and in no way justified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;@ OP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;somehowe the location where you stored your VM is no longer writeable to VMware Workstation.&lt;BR /&gt;Do you have an explanation for that ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"C:\impact2012\Candidate_F\Impact2012.Lab2812_CandidateF.7z\Impact2012.Lab2812.vmdk" : Access is denied.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 11:48:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266482#M71649</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2012-03-19T11:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266483#M71650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@&lt;A _jive_internal="true" class="jiveTT-hover-user jive-username-link" href="https://communities.vmware.com/people/continuum" id="jive-278142,210,159,680,526,608"&gt;continuum&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tx for looking at the problem.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see the access issue but I can't account for why the location is not accessible.&amp;nbsp;&amp;nbsp; I shutdown the virus scanner on the host thinking maybe it is contending for the file but no change.&amp;nbsp;&amp;nbsp; The error is very predictable now.&amp;nbsp;&amp;nbsp; If I start the VM, about ten minutes or so, it always reports this error.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas what I can look for?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 12:46:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266483#M71650</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-19T12:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266484#M71651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@Orthohin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tx for the suggestion.&amp;nbsp;&amp;nbsp; Before I take this step, do have an idea why VMware tools could be the source of the access issue?&amp;nbsp;&amp;nbsp; Have you seen it cause this kind of problem before because of VMware?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 12:51:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266484#M71651</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-19T12:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266485#M71652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;do you have configured exceptions for your Antivirus tools ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when did you last run a checkdisk against the C: drive ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;does the same problem occur if you run the VM as administrator ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 13:05:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266485#M71652</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2012-03-19T13:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266486#M71653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tx Ulli for your time,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had my virus scanner turned off but I now have added an exception for the directory where the vmdk gives.&amp;nbsp; Good idea to do that anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I admit I have not run chkdsk on C: at all.&amp;nbsp;&amp;nbsp; It is a fairly new machine and I thought I was safe (famous last words).&amp;nbsp;&amp;nbsp; Perhaps there is a bad spot on the disk so I will run chkdsk. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One simple test that I did just try was to copy the vmdk on which I am seeing this error to a external USB and run it from there.&amp;nbsp; It is running ok from the USB.&amp;nbsp; That is consistent with a problem on the host disk, though other explanations are possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will try to run as admin as my next test.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will post what I find.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;tx Greg &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 14:35:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266486#M71653</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-19T14:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266487#M71654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ulli,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An update on what I have tried so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added the location of the vmdk to the exception list for virus scanning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran VMware as Administrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran CHKDSK /F on both the host and guest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I still see the same issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Open to any ideas.&amp;nbsp;&amp;nbsp; tx!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 22:09:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266487#M71654</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-19T22:09:54Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266488#M71655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; Insufficient permissions to access the file (115).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please right click the file and check its properties - maybe the folder it is stored in uses some strange permissions ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Mar 2012 22:49:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266488#M71655</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2012-03-19T22:49:25Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266489#M71656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just checked the file and parent folder permissions and did not see anything diffent from other files and folders.&amp;nbsp; While I was there I also tried to disable indexing but still see the same error.&amp;nbsp; Puzzling.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2012 01:42:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266489#M71656</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-20T01:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266490#M71657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The thing that is very strange about this problem is that I can xcopy the vmdk and other files for the image into another location on the host disk or to a attached USB disk, and start the image from there and it works fine.&amp;nbsp;&amp;nbsp; Even though the result of the xcopy is a working image for me, I would really like to know what the underlying problem is with the original image.&amp;nbsp; It smells like an issue with the spot on the host disk that the first vmdk landed on,&amp;nbsp; but, after six hours of running, CHKDSK says the whole disk is OK.&amp;nbsp;&amp;nbsp; Any other ideas of things to look at are appreciated.&amp;nbsp; Tx!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 20:36:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266490#M71657</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-21T20:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266491#M71658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an interesting observation to make.&amp;nbsp;&amp;nbsp; Given the problem was related to a specific instance of the vmdk on disk, and chkdsk showed no errors, I thought I would look at the fragmentation state of the host disk.&amp;nbsp;&amp;nbsp; Indeed the host disk was fragmented.&amp;nbsp;&amp;nbsp; So, first I again validated the problem existed with one particular instance of the vmdk on disk.&amp;nbsp;&amp;nbsp; With that instance the exception occured 100% of the time on many attempts (&amp;gt; 50).&amp;nbsp;&amp;nbsp; The vmdk itself is 22 GB in size.&amp;nbsp; The failure occurrs at different specific times around ten minutes into the startup sequence of nine Windows services in the guest.&amp;nbsp;&amp;nbsp; Then I defragged the host disk overnight.&amp;nbsp;&amp;nbsp; Then I started the VM with that same vmdk and the problem does not occur at all any more (so far more than &amp;gt;10 attempts but now I am getting tired of running it). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible there is a problem in VMware 6.5 related to a large vmdk stored on a fragmented disk? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other explanations are possible (like a timing related bug in one of the Windows services I am starting that happens to be affected by the defrag).&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I would be interested in hearing if anyone else has encountered issues related to fragmentation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Mar 2012 21:27:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266491#M71658</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-23T21:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266492#M71659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for posting that.&lt;BR /&gt;Does not Windows 7 has a autodefrag-tool that can run in the background ? Maybe that is responsible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WS 6.5 itself does not care wether a VMDK is very fragmented - the perforance of that VM will go down but it will run on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Mar 2012 15:07:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266492#M71659</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2012-03-24T15:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266493#M71660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I was also starting to think that maybe the defrag tool was running when the error first appeared, but I looked at the scheduler and it says that defrag happens on Wednesdays at 01:00 AM, and this error first appeared on Sunday morning, and then never went away.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having altered the timing (because of improved disk performance) maybe I had exposed a bug in one of the Windows services in the Windows guest.&amp;nbsp;&amp;nbsp; The app logs I looked at showed failures at different points though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that VMware Workstation 6.5 shouldn't be sensitive to the fragmentation state of the vmdk, but I suppose it may also be possible it exposed a bug in VMware? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Mar 2012 18:10:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266493#M71660</guid>
      <dc:creator>melahn</dc:creator>
      <dc:date>2012-03-24T18:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266494#M71661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2012572" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2012572"&gt;VMware KB: VMware Tools on a Windows virtual machine fails with the error: Exception 0xc0000005 (access violation) …&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jan 2014 04:39:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266494#M71661</guid>
      <dc:creator>vinessen</dc:creator>
      <dc:date>2014-01-14T04:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266495#M71662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@orthonin, you're a life-saver!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I followed the exact same steps as you indicated, with two minor changes, to resolve Exception 0xc0000005 (access violation) in a Windows 10 VM guest running on a VMware Fusion 11.5.1 host on a MacOS Catalina machine in January of 2020:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I found no VMware services running in your step 2, as nothing from earlier VMware tools installations was running in my guest VM, so I replaced your step 2 with a reboot&lt;/LI&gt;&lt;LI&gt;Again, as no VMware services were running in my guest VM, I was able to delete all files in step 4, so I did not need to repeat that step after a reboot&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps I followed:&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;1. uninstall vmware tools from control panel;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;2. reboot&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;3. delete install directory, eg. c:\Program Files\Vmware;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;4. open c:\windows\system32, delete all files of vmware, (every vm* that showed "VMware" as the publisher on mouse-over).&amp;nbsp; All file deletion attempts succeeded in my case, making your step #6 unnecessary for me.&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;5. reboot system;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;6. copy all files from vmware tools' install cd to&amp;nbsp; c:\temp, click setup.exe(setup64 for x64) to install.&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;7. reboot. the problem has been solved.&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;SPAN style="color: #303030;"&gt;Upon final reboot, I found my friendly VM icon in the system tray and knew I'd overcome the "access violation."&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 2px;"&gt;&lt;SPAN style="color: #303030; font-family: proxima-nova, Arial, sans-serif;"&gt;Thank you so &lt;SPAN style="caret-color: #303030;"&gt;much&lt;/SPAN&gt;, Milton, for taking the time to share what worked for you!&amp;nbsp; I'd spent hours across several days, chasing VMware.log files I couldn't find, running vm-support.vbs scripts that seemingly ran forever and never reported the directory where they dropped their output and trying to decipher tips in other threads that lead to blind alleys.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jan 2020 23:39:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/1266495#M71662</guid>
      <dc:creator>IlDavo</dc:creator>
      <dc:date>2020-01-19T23:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2809763#M167191</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/474750"&gt;@IlDavo&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1237172"&gt;@orthohin&lt;/a&gt;,&amp;nbsp;thanks very much for this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was having similar problems with a Windows 10 VM guest on VMware Fusion 12.0.0 on MacOS Catalina 10.15.7. It seems that it was a video driver DLL hanging around from previous VMware Tools installations. Following&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/474750"&gt;@IlDavo&lt;/a&gt;'s procedure sorted it out and now everything is working properly.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2020 17:34:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2809763#M167191</guid>
      <dc:creator>chris_ivys</dc:creator>
      <dc:date>2020-11-16T17:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2874077#M171967</link>
      <description>&lt;P&gt;I'm having a similar issue but don't think its the video driver. I have Workstation 15.5 with Windows 11 on a Surface Pro 8. I have disabled Hyper-V but no luck.&amp;nbsp; I have attached my log file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 24 Oct 2021 14:28:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2874077#M171967</guid>
      <dc:creator>smccrary</dc:creator>
      <dc:date>2021-10-24T14:28:49Z</dc:date>
    </item>
    <item>
      <title>Re: Exception 0xc0000005 (access violation) has occurred when starting VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2885530#M173236</link>
      <description>&lt;P&gt;&lt;A href="https://community.spiceworks.com/topic/2343447-vmware-workstation-16-cannot-launch-server-2016-vm" target="_blank"&gt;VMware Workstation 16 - Cannot launch Server 2016 VM - Spiceworks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Same here. Could it be it thinks the ISO is in use??&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 15:14:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Exception-0xc0000005-access-violation-has-occurred-when-starting/m-p/2885530#M173236</guid>
      <dc:creator>Simple-IT</dc:creator>
      <dc:date>2021-12-28T15:14:09Z</dc:date>
    </item>
  </channel>
</rss>

