intel / intel/AI-Playground

AI Playground doesn't install properly on Intel(R) Core(TM) Ultra 9 285K no Discrete GPU. Works great on my ASUS Zenbook S14 UX5406SA_UX5406SA

Open
#148 4 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
979
Forks
132
Avg merge
9h 23m
Merged PRs (30d)
8

Description

## Describe the bug

Downloaded the latest beta of AI Playground AI.Playground-v2.0.0-alpha-prev.exe
Installed the latest Intel® Graphics Driver 32.0.101.6458/32.0.101.6257
Installed the latest NPU driver: npudriver-32.0.100.3104
When I go to Windows 11 Device Manager, under Display Adapters is only shows Intel(R) Graphics, no GPU.
When I start AI Playground it shows the three resources I need to install:
Component Type Information Enable * Status Action
1. AI Playground Required Failed Repair
2. ComfyUI Optional Failed Repair
3. Llama.cpp - GGUF Optional Failed Repair
All three fail.

## To Reproduce

Steps to reproduce the behavior:
1. Download and execute AI.Playground-v2.0.0-alpha-prev.exe
2. Select the three options, and Click on Install/Repair all selected
3. View three FAILED.

## Expected behavior

A clear and concise description of what you expected to happen.
Success not failed.
## Screenshots

If applicable, add screenshots to help explain your problem.

## Environment (please complete the following information):
Device name xxxxx
Processor Intel(R) Core(TM) Ultra 9 285K 3.70 GHz
Installed RAM 64.0 GB (63.5 GB usable)
Device ID DB4DE9B2-E34F-4A9D-B1DB-E0207D150F5D
Product ID 00330-53476-45869-AAOEM
System type 64-bit operating system, x64-based processor
Software:
Edition Windows 11 Pro
Version 24H2
Installed on ‎1/‎18/‎2025
OS build 26100.2894
Experience Windows Feature Experience Pack 1000.26100.36.0

No discrete GPU.
The log C:\Users\prent\Downloads\aip-2025-01-08.log
Here are some interesting log entries:
The script llm-convert.exe is installed in 'D:\Program Files\AI Playground\resources\ai-backend-env_tmp\Scripts' which is not on PATH.
Many more items identified as not being in the path.

I would post the log but I don't know where to find it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.