# Render() causes a non responding Visualization Toolkit - Win32OpenGL on Windows

**URL:** https://discourse.paraview.org/t/render-causes-a-non-responding-visualization-toolkit-win32opengl-on-windows/538
**Category:** ParaView Support
**Tags:** python
**Created:** [September 6, 2018, 10:28pm UTC](https://discourse.paraview.org/t/render-causes-a-non-responding-visualization-toolkit-win32opengl-on-windows/538 "2018-09-06T22:28:46Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 7, 2018, 2:04am UTC](https://discourse.paraview.org/t/render-causes-a-non-responding-visualization-toolkit-win32opengl-on-windows/538/3 "2018-09-07T02:04:31Z")

</div>

The render window is not expected to be interactive when using ParaView’s Python scripting. One important exception is if you are executing Python scripts in `paraview.exe` - in that case the RenderView is interactive.

ParaView and all supporting libraries are 64-bit. It will work only with the 64-bit Python installation. There is no need for 32-bit anything. But as I mentioned [here](https://discourse.paraview.org/t/not-able-to-import-paraview-simple-module-on-windows/537/10?u=cory.quammen), `pvpython.exe` may be your best bet.

---

_[View the full topic](https://discourse.paraview.org/t/render-causes-a-non-responding-visualization-toolkit-win32opengl-on-windows/538)._