Bitcoin Core 0.16 intentionally makes it more difficult to generate legacy addresses because we want to move towards segwit by default (particularly bech32). Thus there isn't really an easy way to make legacy addresses from within the GUI.

However you can use the debug console (or RPC interface, i.e. bitcoin-cli) to generate legacy addresses when -addresstype is not set to legacy. getnewaddress has a new address type parameter that lets you specify what type of address to generate.

Except the large number of services that currently don't support bech32 addresses #devilsAdvocate

Seriously tho, it is indeed a catch-22 situation... services won't start using bech32 until there is widespread adoption among users, users won't start using bech32 until there is widespread adoption among services

Personally, I commend the Bitcoin Core team for forging ahead and "encouraging" the migration to SegWit and bech32.

Segwit nested into P2SH was thought as a way of transition from legacy to segwit (bech32).
While nested segwit does reduce the transaction weight, it is still not as efficient as bech32.

Changing user habits is a tedious process. Moving from legacy to nested segwit is definetely a step in the right direction.
But the goal should be to get widespread bech32 adoption. It doesn't just improve the user experience, but also contributes to the overall network health.


@OP:
Is there a particular reason you want to use an legacy addresse?
General rejection towards segwit?