Parity-Ethereum version >= v2.1.1 fails to start on windows.

[fevo1971]

• Parity Ethereum version: 2.1.1
• Operating system: Windows 10 Pro
• Installation: official binary and built from source
• Fully synchronized: -
• Network: -
• Restarted: -

Tested with binary release from
https://github.com/paritytech/parity-ethereum/releases/tag/v2.1.1
as well as fresh build from master on my local machine.

actual
When starting parity.exe (with or without command options)
immediately returns to the command-prompt without any output.

expected behavior
starting parity.exe should start a node / display version when started with --version / --help

steps to reproduce

    Directory: C:\Users\Parity\Downloads


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        10/4/2018  10:42 AM       42538152 parity-2.0.6-stable.exe
-a----        10/4/2018  10:44 AM       44270760 parity-2.1.1-beta.exe


PS C:\Users\parity\Downloads> .\parity-2.0.6-stable.exe --version
Parity
  version Parity-Ethereum/v2.0.6-stable-549e202fc-20180919/x86_64-windows-msvc/rustc1.29.0
Copyright 2015, 2016, 2017, 2018 Parity Technologies (UK) Ltd
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

By Wood/Paronyan/Kotewicz/Drwięga/Volf
   Habermeier/Czaban/Greeff/Gotchac/Redmann

PS C:\Users\parity\Downloads> .\parity-2.1.1-beta.exe --version
PS C:\Users\parity\Downloads>

[niklasad1]

/cc @andresilva can it be related to the segfault in rocksdb?

@fevo1971
If you can give me access to the machine or show me in the office next week I can help investigate this!

[jam10o-new]

any chance this is related to #9624 ?

[ordian]

Can also be related to #9684

[andresilva]

Is it possible to build a binary from latest master on that windows machine? If that binary also fails then we know it's not related to #9684.

[andresilva]

Now that I think of it, issue #9684 should be GCC/LLVM specific and shouldn't affect the Windows build.

[ordian]

On Windows it uses /arch:AVX2 flag in release build of v2.1.1, so if the CPU is older than Haswell (Q2 2013), it will fail with illegal instruction.

[ordian]

if the same applies to 2.1.2-beta, then it was unrelated to #9684

[Tbaut]

That's been fixed right?