To be clear, the recommendation is to add "-d", not "d". "d" displays output (the default); "-d" suppresses output. If that is indeed the bug you're running into, it is fixed in newer wheels.
This is another case in which you're going to be happier using one of the newer wheels that comes with 2023.1.2. You're likely getting some kind of error on the server that the old 1.0.0 wheel cannot report back to you cleanly.
One thing you might try, if for some reason you're stuck on 1.0.0, is to add "-d" to the qspec argument. There's a really old bug/limitation, and I don't remember whether it was fixed on the client or server side, having to do with unexpected writes by a class method. "-d" would suppress that.
@Murray Oldfield posted "Decoding Intel processor models reported by Windows" a while back. Perhaps the wmic command is along the lines of what you're looking for. The properties that look of interest include name, description, caption, and processorid:
I don't know if any of these alone is enough to determine whether the processor supports AVX and/or BMI, but it should be enough to find specifications for the processor.