# Pro Tools 11 Windows & QU16 not working

**URL:** <https://forums.allen-heath.com/t/pro-tools-11-windows-qu16-not-working/2730>\
**Category:** Qu Troubleshooting\
**Created:** [26 April 2014 09:02 UTC](https://forums.allen-heath.com/t/pro-tools-11-windows-qu16-not-working/2730 "2014-04-26T09:02:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deleted.User](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/deleted.user/32/4433_2.png) [@Deleted.User](https://forums.allen-heath.com/u/Deleted.User)\
**Post date:** [26 April 2014 09:02 UTC](https://forums.allen-heath.com/t/pro-tools-11-windows-qu16-not-working/2730/1 "2014-04-26T09:02:48Z")

</div>

Hi all…  
I have a problem streaming via USB B to Pro Tools 11 on Windows 7 64. When i connect the QU16 everything works fine, I can stream my Windows audio to the QU and record via the QU in Audacity.  
I’m normaly running Pro Tools 11 with my MBox 2, and it works flawlessly.  
When I try to open Pro Tools 11 with the QU connected instead it takes ages to start PT. In the Setup screen of PT I can see the QU Asio, also in the I/O screen.  
When I try to start a new session it takes ages to load. I created 1 new mono channel trying to record Channel 1 from QU. When I record enable the channel, there’s no moving in the level meter. When I start recording, there’s an error that there wouldn’t be enough CPU-Power.  
As I stated above, with MBox 2 it works without problems, so I think there’s something wrong with the windows driver of QU.  
Has anyone had the same problems?

---

<div class="post-metadata">

**Author:** ![Deleted.User](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/deleted.user/32/4433_2.png) [@Deleted.User](https://forums.allen-heath.com/u/Deleted.User)\
**Post date:** [26 April 2014 16:23 UTC](https://forums.allen-heath.com/t/pro-tools-11-windows-qu16-not-working/2730/2 "2014-04-26T16:23:17Z")

</div>

I downloaded Cubase 7 Elements trial and it works totaly fine, both streaming to and from QU. So it’s definetly a Pro Tools problem.

Any idea from the A&H people?
