Ascending keys getting bad plans in SQL 2016 (new CE), replacement for TF 4139 et al.?
If all of these are true:


You only need to fix a relatively limited number of queries (dozens to hundreds)
You know exactly what they are, and you can get the T-SQL
They don't change (end users can't dynamically build their own, or add search conditions)
You can guarantee they won't change
You can control which context they execute in (for example, they're not executing in TempDB with fully qualified object names pointing to user databases)
They're in a limited number of databases (as opposed to a software-as-a-service approach where every client is in their own database, and you want to fix all of the queries in all of the databases)


Then plan guides are a good fix. Just know that if you violate any of these rules (like if the queries start changing) then the plan guides won't work.