vllm [Installation]: Error occured while installing vllm

Your current environment

`My current environment is window

pip install vllm

### How you are installing vllm


 creating build\bdist.win-amd64\wheel\vllm\model_executor\layers
      copying build\lib\vllm\model_executor\layers\activation.py -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers
      creating build\bdist.win-amd64\wheel\vllm\model_executor\layers\fused_moe
      creating build\bdist.win-amd64\wheel\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=14336,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=14336,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=1792,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=1792,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=3072,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=3072,device_name=NVIDIA_H100_80GB_HBM3,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=3072,device_name=NVIDIA_H100_80GB_HBM3.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=3584,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=3584,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=7168,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=1,N=7168,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=1344,device_name=NVIDIA_A100-SXM4-40GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=1344,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=1344,device_name=NVIDIA_H100_80GB_HBM3.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=14336,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=14336,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=1792,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=1792,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=2688,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=2688,device_name=NVIDIA_H100_80GB_HBM3.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=3072,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=3072,device_name=NVIDIA_H100_80GB_HBM3,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=3200,device_name=NVIDIA_H100_80GB_HBM3,dtype=fp8_w8a8.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=3584,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=3584,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=6400,device_name=NVIDIA_H100_80GB_HBM3,dtype=fp8_w8a8.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=7168,device_name=NVIDIA_A100-SXM4-80GB,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=7168,device_name=NVIDIA_A100-SXM4-80GB.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=7168,device_name=NVIDIA_H100_80GB_HBM3,dtype=int8_w8a16.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=16,N=800,device_name=NVIDIA_H100_80GB_HBM3,dtype=fp8_w8a8.json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      copying build\lib\vllm\model_executor\layers\fused_moe\configs\E=256,N=128,device_name=NVIDIA_H100_80GB_HBM3,dtype=fp8_w8a8,block_shape=[128,128].json -> build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs
      error: could not create 'build\bdist.win-amd64\wheel\.\vllm\model_executor\layers\fused_moe\configs\E=256,N=128,device_name=NVIDIA_H100_80GB_HBM3,dtype=fp8_w8a8,block_shape=[128,128].json': No such file or directory
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for vllm
Failed to build vllm
ERROR: Failed to build installable wheels for some pyproject.toml based projects (vllm)

### Before submitting a new issue...

- [x] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the [documentation page](https://docs.vllm.ai/en/latest/), which can answer lots of frequently asked questions.

Mar 03 '25 08:03 Bakht-Ullah

This looks to be the problem with flash_attn. I would suggest the following:

!pip install --upgrade vllm
!pip uninstall flash_attn or (!pip install --upgrade flash_attn)

The error mainly talks about incompatibility of package versions.

Mar 03 '25 09:03 manitadayon

I also ran into this issue on Windows. For me, the root cause was that I did not have Windows Long Path support enabled. I was able to fix this by running this command in Windows PowerShell with admin privileges:

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force

I got this command from here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later

After that, I was able to install vllm with pip install vllm.

Mar 10 '25 16:03 adulai

Resolved:

In win+r, type regedit and set:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem The variable LongPathsEnabled in the path, set it to 1.

解决：在win+r，输入 regedit，然后设置： \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem路径下的变量 LongPathsEnabled, 将其置为 1即可.

Mar 11 '25 08:03 AdamPlatin123

I also ran into this issue on Windows. For me, the root cause was that I did not have Windows Long Path support enabled. I was able to fix this by running this command in Windows PowerShell with admin privileges:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
I got this command from here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later

After that, I was able to install vllm with pip install vllm.

Thanks a lot!

Mar 25 '25 14:03 pspdada

I also ran into this issue on Windows. For me, the root cause was that I did not have Windows Long Path support enabled. I was able to fix this by running this command in Windows PowerShell with admin privileges:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
I got this command from here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later After that, I was able to install vllm with pip install vllm.
Thanks a lot!

This works for me. Thank you

Apr 01 '25 15:04 Onkowe

I also ran into this issue on Windows. For me, the root cause was that I did not have Windows Long Path support enabled. I was able to fix this by running this command in Windows PowerShell with admin privileges:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
I got this command from here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later

After that, I was able to install vllm with pip install vllm.

That's help a lot. Thank you!

May 01 '25 11:05 thlui

This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you!

Jul 31 '25 02:07 github-actions[bot]

I also ran into this issue on Windows. For me, the root cause was that I did not have Windows Long Path support enabled. I was able to fix this by running this command in Windows PowerShell with admin privileges:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
I got this command from here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later

After that, I was able to install vllm with pip install vllm.

works for me, thanks.

Aug 21 '25 07:08 ZhuShaoQiang

This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you!

Nov 21 '25 02:11 github-actions[bot]

This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant. Thank you!

Dec 21 '25 02:12 github-actions[bot]