Just saw this as I'm looking at encrypting a production SQL Server DB.
On my desktop PC, Win 10, I created a new test DB and went thru the Encrypt Columns wizard to apply Always Encrypted. In SSMS I could query the data but, as expected, it returns long strings of gobbledy-gook. I was dismayed to learn that SSMS can't apply the master key and do updates or inserts, etc on encrypted columns. Before I encrypt the production SQL DB, I need to make sure all client apps that connect to it can decrypt the data and manipulate it, and that includes QlikView.
I created an ODBC DSN for SQL using ODBC Driver 13 for SQL Server with all the standard settings and used this in a little QV desktop doc to connect to my new test DB. It populated a table box and some of the columns showed gobbledy-gook.
I went back to the ODBC administrator and reconfigured the same DSN. Hit Next twice and at the bottom is a tick box 'Column Encryption'. Tick that, Next and Finish. Back in QV, reload and there's my decrypted data. Simple as that.