If you do not run the development client as administrator and try to run an object, the windows client will crash.
I've spottet the error on a platform upgraded test server, but recreated it on a fresh installed NAV 2016 CU7 Azure test server.
The workaround is to run the development client as administrator - then it works as expected.
I'm already exchanging e-mails with some MS development employees which are looking into it - so it will probably be fixed in a future CU.
I've also blogged about it here (only in Danish unfortunately :-) ): http://blog.systemconnect.dk/?p=943