update_where.js test performs updates with multi=true, which are sent without shard versions outside of a transaction when they cannot target a single shard. This can lead to several known anomalies (see SERVER-20361), so until the behavior of multi writes against sharded collections is improved, this test should be blacklisted from the sharded with balancer concurrency suites. Notably multi writes do use shard versions in transactions, so this test does not need to be blacklisted in concurrency_sharded_multi_stmt_txn_with_balancer.