“# Your device is not supported”
after 3.15 (that was an v.environment problem) and 3.18 and now 3.23 it still doesn’t work.
I have just installed the Nvidia 566.14 driver but got the same result.
Why can i just not get over this step and see and decide if it works for myself? Does it have to be this way? I am just at the merge to call this as an early Alpha release and move away for a while until it works(hopefully later).
I have windows 11 and a Nvidia RTX 3060
Having great difficulty reproducing this on our side. We definitely agree - the next version is going to do exactly as you’ve described - display a warning, and just let users move on. It didn’t make it into 0.3.23, sorry!
If you don’t want to wait, some tests:
The command below should spit out a bunch of information. No need to upload it - just want to know if it spits out something similar to the below, and that the something is not an error.
powershell.exe -c "`$n = '*NVIDIA*'; Get-CimInstance win32_videocontroller | ? { `$_.Name -like `$n -or `$_.VideoProcessor -like `$n -or `$_.AdapterCompatibility -like `$n }"
[Edit: This is just reading CIM data (what WMI reads), then filtering for NVIDIA. It is a new check added in 0.3.23 - I’m trying to determine if I’ve missed something, or my PS is just rusty.]
Example output
Caption : NVIDIA GeForce etc etc
Description : NVIDIA GeForce etc etc
InstallDate :
Name : NVIDIA GeForce etc etc
Status : OK
[ ... many more lines ]
Not sure how to use the command. Tried with cmd first and then with wmic and got this.
And with powershell this.
Thank you.
With any kind of hardware-software configuration around i can certainly understand the difficulty. So please don’t think that i am not grateful. But when the real thing you want is to make something, trying to deal with all those new things (even a webpage like github was strange and scary 3 weeks ago) like safetensors, vae, lora, and all the strange error windows that reads more like a formula then anything understandable for ordinary users and a workflow that worked 1 week ago doesn’t work etc…it feels frustrating after a while.
This is what people like you have to deal and make easier for people like me i suppose. I wish you good luck 
All good! I get the frustration. Beta can sometimes be … challenging! Trying to fix an issue for some time that you may have to abandon is just not rewarding.
Those screen shots, though - your computer can’t find PowerShell - which is a problem. It works when you run it from the start menu / task bar because the full path is hard-coded into Windows. Which makes sense for Windows, but not for apps.
In PowerShell, if you run this:
$env:PATH.split(';')
You should get output similar to:
PS C:\> $env:PATH.split(';')
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
[ ... many more ]
If you’re missing any of these, it seems something has gone and mucked around with your environment variables. They should be in the System environment variable named Path.
It is possible that an anti-virus or anti-malware app removed PowerShell from the path to try and prevent very basic bad things from running. But the list of possibilities is very long.
When i first tried only “Wbem” path was there. I brute forced my way by making some false things but got the paths you showed above into the env. in the end. Now they show up and when i tried the earlier command you gave me about the GPU it showed the desired result in Powershell. It looks ok… “Status: OK”, “Caption: NVIDIA GeForce RTX 3060” and etc. shows up.
After i changed the env.paths to be like you showed above i tried to install Comfyui 3.23 ones more.
IT WORKED!
There might be other problems around but at least i can finally see the latest version.
Thank you very much