Q&A widget does not open for host

It sounds like a frustrating issue, especially as the host. Since attendees and co-hosts could use the Q&A normally, it might be related to a temporary connection issue between the client and Zoom’s servers. You could try signing out of the Zoom app and signing back in, checking firewall or network restrictions, or testing from the web client or another device. If the problem continues, it may be best to contact Zoom support with the webinar logs so they can investigate further.

hi ​@Paulette E ,

that does not sound like normal practice. You should be able to click on the q&a button and see the outstanding questions. 
For me the widget pops up but at the top, the words connecting and disconnected keep alternating.
this sounds like the app is having problems drawing its screens, How powerful is your machine, did you have screen sharing or other apps in progress?

I would try running a webinar without an audiece - let me know how it goes.

I am also having this issue and several other people in our company. Have any resolutions been found? I have the most current zoom update, deleted and redownloaded the app and internet connection is good. The issue occurs both as a host and as an attendee.

Problem is still unresolved.  And others in my company have the same issue.  Zoom worked as expected when run from the browser but not the app.  VPN on or off makes no difference.  Freeing up RA no difference.  Put in a ticket with Zoom.  Still no resolution.

After trying a lot of different things, I discovered the Zoom Desktop App does not have a friendly working relationship with the cybersecurity software that our company has running in the background for those working remotely.  An update of the cybersecurity app gave me access to launching my webinar from the browser again which resolved my issues with both Q&A and seeing the participant list.  

It did take some experimentation to rule out potential issues.  Kudos to the Zoom support folks who offered suggestions of what might have been causing the issues so I could test and narrow down the potential sources of the issue.