New
#1
You will need to enclose the whole HardwareID in quotation marks.
Your application is responding to the & in the middle and it thinks you are issuing two separate commands. Using quotation marks makes your app see the whole HardwareID.
I also think:-
1 The command affects all devices with the same HardwareID [so would also affect any replacement of the same type of card] so I am surprised that your app works that way
2 You could simply right-click & disable it in Device mgr instead.
All the best,
Denis
You seem to have stuck " within the HardwareID.
- Put one " before the start of the HardwareID.
- Put another " after the end of the HardwareID.
Like this
SomeCmdOrOther.exe "PCI\VEN_8086&DEV_5916&SUBSYS_07441028&REV_02"
Denis
very thanks. it worked :
devcon64 disable "PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1"
PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&2B8E0B4B&0&18: Disabled
1 device(s) disabled.
devcon64 enable "PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1"
PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&2B8E0B4B&0&18: Enabled
1 device(s) are enabled.
I'm glad the problem is resolved.
You often need to add " to commands.
If the 'argument' you are adding to a command has a space or a special character [such as an ampersand &] then the command can often only read the first part of it.
There is generally no problem adding " to a Windows command's 'argument' unnecessarily.
For example,
Dir C:\Fred works, and
Dir "C:\Fred" works, and
Dir "C:\Fred and Mabel " works, and
Dir "C:\Fred & Mabel " works,
but
Dir C:\Fred and Mabel does not, and
Dir C:\Fred & Mabel is even worse - Windows thinks you are issuing two commands Dir C:\Fred and then Mabel and it has no idea what the command Mabel is at all.
All the best,
Denis
Hello.
I've reinstalled Windows 11 and I have passed again my graphic card inside the VM and I've got the same error as before,but this time I don't see any syntax error. Can you help me again to find what's the right ID of my graphic card ? (it should be the same of the previous time,but it does not seem). Please give a look at the picture attached...thanks
The HardwareID of the device will not have changed.
I notice that your command has changed
from
devcon64 disable "PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1"
to
devcon disable "PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1"
I do not know if using a VM or Windows 11 make any difference to devcon.
All the best,
Denis
Ive got it here :
windows - Quick Method to install DevCon.exe? - Super User
where you read :
Download 787bee96dbd26371076b37b13c405890.cab, extract the file filbad6e2cce5ebc45a401e19c613d0a28f and rename it to devcon.exe (download size: 6.12 MB).
- - - Updated - - -
Ive got another version of devcon,here
https://download.microsoft.com/downl...k/wdksetup.exe
it is inside the WDK 8.1 https://download.microsoft.com/downl...k/wdksetup.exe.
unfortunately I get the same error as before. can u tell me where to get the working file