cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

san-san
Journeyman III

Unnable to install Ryzen AI Software to Copilot+ PC(AMD Ryzen AI 7 PRO 360)

Greetings, I need your help.

 

I have ThinkPad T14s Gen6(AMD Ryzen AI 7 PRO 360).

 

Many time I tried to install Ryzen AI Software with this instruction(https://ryzenai.docs.amd.com/en/latest/inst.html), but installer lost response every time.

 

----------------------------------------------------------------------------------------------

Installed Item

Visual Studio 2022 Community Edition with C++ Desktop

cmake(cmake-3.31.2-windows-x86_64.msi)

Miniconda(Install path -> C:\Miniconda)

----------------------------------------------------------------------------------------------

 

I made directory for Ryzen AI Software -> C:\RyzenAI

 

Every time installer stops here.

 

sansan_0-1734165058725.png

 

I have Temp folder on C:\Temp and there is ryzenai_error_log.txt.

It says every time like this, but onnxruntime.dll exists in dest directory.

2024-12-14 16:03:18,196 - INFO - copying onnxruntime\bin\onnxruntime.dll to C:\Miniconda\envs\ryzen-ai-1.3.0\lib\site-packages\onnxruntime\capi

 

Here, AMD Ryzen AI 7 PRO 360 is not listed. If this trouble is caused it, how can I use NPU on my computer?

---------------------------------------------------------------------

Supported Configurations#
The Ryzen AI Software supports the following processors running Windows 11 (Win 11 build>=22621.3527 is required for Ryzen AI Software 1.3.)

Phoenix (PHX): AMD Ryzen™ 7940HS, 7840HS, 7640HS, 7840U, 7640U.

Hawk (HPT): AMD Ryzen™ 8640U, 8640HS, 8645H, 8840U, 8840HS, 8845H, 8945H.

Strix (STX): AMD Ryzen™ Ryzen AI 9 HX375, Ryzen AI 9 HX370, Ryzen AI 9 365

---------------------------------------------------------------------

 

regards,

0 Likes
1 Reply
san-san
Journeyman III

Thanks to your help, the issue has been resolved. I was using a PC signed in with an M365 account, but when I tried signing in with a Microsoft account, it worked. I'm not sure if the cause was the M365 policy or the inclusion of multibyte characters in the user directory name, but if anyone else is facing the same issue, please give this a try.

0 Likes