[Bug]: Windows LM Studio installation remains at 75% and is not detected after successful llmster install
維護者通常 5 天內回覆
@ckelseynv 已經在處理了。
開始於 2026年9月11日。
評估
這個 Issue 還沒有評估資料。
描述
PAIR version or commit
PAIR desktop application 0.91.7
Affected component
Engine or model management
Environment
- OS: Microsoft Windows 11 Pro 10.0.26200, build 26200
- Architecture: x64
- GPU: NVIDIA RTX PRO 6000 Blackwell Workstation Edition
- GPU driver: 32.0.15.8216
- LM Studio CLI: 1.3.3, commit
07b7252 - llmster: 0.0.23-1
- Cluster size: 2
Steps to reproduce
- Have LM Studio installed on Windows with its server running on port 1234.
- Install and open PAIR 0.91.7.
- Select the LM Studio Download/install action.
- Observe progress reach 75% at the
installingstage. - Wait approximately 108 seconds.
- Stop the existing server with
lms server stop, then fully stop the daemon withlms daemon down. - Run the same official
https://lmstudio.ai/install.ps1script manually. - Confirm that it successfully installs llmster 0.0.23-1.
- Restart PAIR and retry the LM Studio installation.
This was reproduced three times, including after confirming that lms.exe was present on PATH and executable by the same Windows user.
Expected behavior
PAIR should detect or adopt the existing LM Studio installation, configure its managed backend on port 1235, and complete registration. If an existing daemon must be stopped first, PAIR should report that requirement instead of remaining at 75%.
Actual behavior
PAIR reaches 75% and later reports:
engine "lmstudio" was not detected after install
PAIR's proxy takes port 1234 and repeatedly checks its expected backend at 127.0.0.1:1235, but that backend is not registered or kept running. engine-state.json continues to contain only Ollama.
Running the official LM Studio installer manually succeeds:
Install completed at %USERPROFILE%\.cache\lm-studio\llmster\0.0.23-1.
Installation finished successfully! llmster is ready to launch.
Closing PAIR and restoring the original LM Studio service returns port 1234 and the existing models to normal operation.
Sanitized logs
engine:install-progress
engine=lmstudio percent=75 stage=installing
[nvpair-engine-manager] WARN engine error reported
id=engine-manager:install-failed:lmstudio
message="engine \"lmstudio\" was not detected after install"
engine:install-progress
engine=lmstudio
error="engine \"lmstudio\" was not detected after install"
percent=-1
stage=failed
[lmstudio-proxy] INFO local backend updated
engine=lmstudio host=127.0.0.1 port=1235 healthy=false
Confirmations
- I searched existing issues for duplicates.
- This is not a security vulnerability.
- I agree to follow the Code of Conduct.
- 主要語言
- Go
- 星號
- 1.6k
- 分支
- 266
- 平均合併
- 3 天 6 小時
- 30 天內合併 PR
- 22
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NVIDIA/Personal-AI-Router 的其他 Issue
-
難度 5/5 一週以上 新手友好度 20/100
NVIDIA/Personal-AI-Router#165 ·
維護者通常 5 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 46/100
NVIDIA/Personal-AI-Router#164 ·
維護者通常 5 天內回覆
-
enhancement
難度 4/5 一週以上 新手友好度 12/100
NVIDIA/Personal-AI-Router#162 ·
維護者通常 5 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 25/100
NVIDIA/Personal-AI-Router#154 · 1 則留言 ·
維護者通常 5 天內回覆
-
[Feature]: [Ollama] Alert the user about model pull failures可能已有人在做 @ckelseynv 於 4 天前認領。 未關閉enhancement
難度 3/5 1-2 天 新手友好度 56/100
NVIDIA/Personal-AI-Router#152 · 1 則留言 · 已指派 1 人 ·
維護者通常 5 天內回覆
查看 NVIDIA/Personal-AI-Router 的全部 Issue
相似的 Issue
-
component/gpu-kubelet-plugin component/helm needs-triage
難度 2/5 1-3 小時 新手友好度 62/100
kubernetes-sigs/dra-driver-nvidia-gpu#1559 ·
維護者通常 1 天內回覆
-
TOTP enrollment returns 500 for phone-only users (empty TOTP account name)可能已有人在做 @emiliosandoval4 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 60/100
維護者通常 1 天內回覆
-
8.9 to 8.10 Helm upgrade guide still says deprecated keys are removed in chart v16 (Camunda 8.11)未關閉
難度 1/5 1 小時以內 新手友好度 78/100
camunda/camunda-platform-helm#7559 ·
維護者通常 1 天內回覆
-
docs: namespaceRegexes example teaches prefix matching, but regexes are matched as a substring可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉triage/pending-triage
難度 2/5 1-3 小時 新手友好度 74/100
external-secrets/external-secrets#7117 ·
維護者通常 2 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
ENTERPILOT/GoModel#1183 · 1 則留言 ·
維護者通常 1 天內回覆