The update didn't seem to have any significant impact on the benchmark duration: https://chromeperf.appspot.com/report?sid=9f57d3809dd1da99644338e9a0587df4d08028dcf53ec1591e065ed4d8e43041

Clearing myself as the owner, as rolling the version of Windows that we use in the lab didn't turn out to be a blocker for more stable power benchmarks.

Shouldn't you mark these Windows Comparision bugs as Won't Fix then?

I asked benhenry@ what he wanted me to do with these bugs in https://bugs.chromium.org/p/chromium/issues/detail?id=723745#c24