# How to run ParaView (including the binary release) using Mesa on Windows

**URL:** https://discourse.paraview.org/t/how-to-run-paraview-including-the-binary-release-using-mesa-on-windows/4321
**Category:** Tips and Tricks
**Created:** [May 13, 2020, 4:42am UTC](https://discourse.paraview.org/t/how-to-run-paraview-including-the-binary-release-using-mesa-on-windows/4321 "2020-05-13T04:42:44Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [May 17, 2021, 9:20pm UTC](https://discourse.paraview.org/t/how-to-run-paraview-including-the-binary-release-using-mesa-on-windows/4321/7 "2021-05-17T21:20:24Z")

</div>

If someone is unlucky and found themselves struggling to debug or develop ParaView with VS2019 on a Windows 10 Azure VM/Remote Desktop like me, you’d probably come here. So, here’s an update for you (Relax, it just got better. Windows doesn’t have to be a pain always…)

The original repo link by @mwestphal is much convenient and better now. It provides scripts for per-app or system-wide deployment. I prefer system-wide deployment so that it’s centralized.

 ![image](https://discourse.paraview.org/uploads/default/original/2X/f/ffb2c49ed2849942e409aafc858d4e2f834851af.png)

Select option 1 or 2 or 4 in the cmdlet and deploy. By default, it installs mesa 21.1.0. This supports up to a 4.6 context should you want that.  
 ![image](https://discourse.paraview.org/uploads/default/original/2X/e/e4f7d3f3b4c9701d4ba8960b7682b82734c494d8.png)

The 5.9 release binary for ParaView seems to pick up a 3.1 compat context.  
 ![image](https://discourse.paraview.org/uploads/default/original/2X/d/dab63ed96300d011c6e226b0f9b892b42b9682fa.png)

---

_[View the full topic](https://discourse.paraview.org/t/how-to-run-paraview-including-the-binary-release-using-mesa-on-windows/4321)._
