Comparing my hashes with fanquake's here: #20619#pullrequestreview-566151791
--- fanquake-hashes 2021-01-12 15:23:32.811688091 -0500
+++ my-hashes 2021-01-12 15:24:30.269835400 -0500
@@ -4,9 +4,9 @@
de152cdbe0d9fde9f427ae49fd34adc57b7c4578e15579d206138a175a2d7c37 output/bitcoin-570e43fe72e1-arm-linux-gnueabihf.tar.gz
e8aa890632dca2486bb61a0a50136d18b3d60c70c69799dfe4f449c17f3f9ac1 output/bitcoin-570e43fe72e1-riscv64-linux-gnu-debug.tar.gz
77aaf75aae626b960192aa4de20dbfb625f893dd1caf94fc44f9978e7d7186e7 output/bitcoin-570e43fe72e1-riscv64-linux-gnu.tar.gz
-de9c212405f227f80a3aa882ee994202bbc834137f94a73779d99e9410b86246 output/bitcoin-570e43fe72e1-win-unsigned.tar.gz
+6ef2fefed13aeeefa40c7c93dacb09d6b12f36385f71a3e90fb2d4b28f3fdaa9 output/bitcoin-570e43fe72e1-win-unsigned.tar.gz
98c1e14e46aaa83201befdd54f3aac4229f0a5f246ed464b4fcd6e31550f7eea output/bitcoin-570e43fe72e1-win64-debug.zip
-cf45a21423bad9357526b92305530e7199de8a574d4c02641423cca4404273c0 output/bitcoin-570e43fe72e1-win64-setup-unsigned.exe
+5ab6c1c4b0c90331b364e056bcc9cad90b3ad0ceaa4205bb49ff3ee1c39dd46d output/bitcoin-570e43fe72e1-win64-setup-unsigned.exe
08c7a10b51ef24db6d8dd5e10bdfad7ad2dad2cc1b8d8a70f89ed80b8faeb18b output/bitcoin-570e43fe72e1-win64.zip
5f1fd6c1b9bcb1d7522411e859a7865337bfbfe19388444f36f4d871c76079a6 output/bitcoin-570e43fe72e1-x86_64-linux-gnu-debug.tar.gz
0e3968c071aeeac5bbd0b193a9aac52e536bd756ba86705da773d2c9654efa66 output/bitcoin-570e43fe72e1-x86_64-linux-gnu.tar.gz
This is clearly an NSIS problem as output/bitcoin-570e43fe72e1-win64.zip is reproducible but the -setup.exes are not.
