# Intel UHD 620 + VTK + Qt bug with new drivers on windows

**URL:** https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694
**Category:** Support
**Created:** [September 4, 2019, 1:55pm UTC](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694 "2019-09-04T13:55:36Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![estan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/estan/32/460_2.png) [@estan](https://discourse.vtk.org/u/estan)
#### Post date: [September 5, 2019, 10:01am UTC](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694/5 "2019-09-05T10:01:42Z")

</div>

We ran into some problems with the new non-native widget, and in the end decided to revert to using `QVTKOpenGLNativeWidget` everywhere (see the thread at [How to decide between QVTKOpenGL{Native}Widget?](https://discourse.vtk.org/t/how-to-decide-between-qvtkopengl-native-widget/1070/4)). The common wisdom right now seems to be to use `QVTKOpenGLNativeWidget` unless you need stereo rendering.

I can have a go with your test case + latest drivers on my test Windows laptop after lunch. It has an older Intel GPU though. Do you know if you only saw this with UDH 620/630, not with older GPUs? I have a laptop with UHD620 as well, but I recently switched it to Linux 😕

---

_[View the full topic](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694)._