# Could not run sketch. Target VM failed to initialize

**URL:** <https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166>\
**Category:** Processing\
**Created:** [September 24, 2019, 9:35am UTC](https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166 "2019-09-24T09:35:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![VPadu](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@VPadu](https://discourse.processing.org/u/VPadu)\
**Post date:** [September 24, 2019, 9:35am UTC](https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166/1 "2019-09-24T09:35:42Z")

</div>

So since the release of the new windows 10 update and the release of the new nvidia drivers I could not use processing anymore because of the error in the title with EVERY kind of sketch (even empty ones).  
I noticed that this error was common in 2017 as well when nvidia released a new driver and the solution there was to go back to previous graphic card drivers. I tried this option as well but it seems that the old drivers were not compatible with the new windows 10 update anymore so I was (and technically still am) kind of stuck.  
I found a workaround, but I would like to know if someone has a solution for this problem.

My solution was to download the 32-bit Processing version even if my computer runs at 64.  
So I just wanted to post this in case anyone has this problem and I would like to know if anyone has an actual solution for the 64 bit problem

---

<div class="post-metadata">

**Author:** ![kll](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/kll/32/964_2.png) [@kll](https://discourse.processing.org/u/kll)\
**Post date:** [September 24, 2019, 9:54am UTC](https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166/2 "2019-09-24T09:54:55Z")

</div>

thanks for this info ?warning not to update nvidia driver ?  
can you add more details?

 ![nvidia_driver_rollback](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/2X/c/c8070b451a94339ffa0d12c33baf5a04a075e803.png)  
by any chance you could use the  
[Roll Back Driver] ? option ?

---

<div class="post-metadata">

**Author:** ![VPadu](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@VPadu](https://discourse.processing.org/u/VPadu)\
**Post date:** [September 24, 2019, 11:15am UTC](https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166/4 "2019-09-24T11:15:52Z")

</div>

I tried, but that option was greyed out for me. My guess is it was like that because of the windows new drivers system. Intel is going to update as well as you can read here [https://www.intel.com/content/www/us/en/support/articles/000031572/programs/intel-corporation.html](https://www.intel.com/content/www/us/en/support/articles/000031572/programs/intel-corporation.html)

---

<div class="post-metadata">

**Author:** ![VPadu](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@VPadu](https://discourse.processing.org/u/VPadu)\
**Post date:** [October 4, 2019, 12:00pm UTC](https://discourse.processing.org/t/could-not-run-sketch-target-vm-failed-to-initialize/14166/5 "2019-10-04T12:00:05Z")

</div>

Windows update 1903 fixed the error