[BUG]: Fail to create workspace on both 1.90 r 1or 1.8.5 r2 #3006

Closed
opened 2026-02-28 06:26:54 -05:00 by deekerman · 3 comments
Owner

Originally created by @fengyqy on GitHub (Dec 1, 2025).

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I am trying to run anythingLLM desktop on Thinkpad T14s snapdragon X elite powered laptop and see how NPU works with anythingLLM.

However, after installation, the below error pops up when creating workspace.
Error: Invalid prisma.workspaces.create() invocation: The table main.workspaces does not exist in the current database.

I have done some research and saw this issue happened before in multiple thread#1170 or #2771, and I saw some solutions are below

  1. delete storage folder and re-start it :\Users<usr>\AppData\Roaming\anythingllm-desktop\storage
  2. in older version 1.7.1, select one user instead of all user, it resolved the problem, but for 1.9 or 1.8.5, apparently this option is removed.

so what could be the problem then now? I am sure lots of you already started to run anythingllm on Arm64 based windows 11, but somehow I missed some part, thanks for your help .

=Fengy=

Are there known steps to reproduce?

just create new workspace on windows 11 with Snapdragon X Elite, it is 100% reproduceable on my laptop.

Originally created by @fengyqy on GitHub (Dec 1, 2025). ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I am trying to run anythingLLM desktop on Thinkpad T14s snapdragon X elite powered laptop and see how NPU works with anythingLLM. However, after installation, the below error pops up when creating workspace. Error: Invalid `prisma.workspaces.create()` invocation: The table `main.workspaces` does not exist in the current database. I have done some research and saw this issue happened before in multiple thread#1170 or #2771, and I saw some solutions are below 1) delete storage folder and re-start it :\Users\<usr>\AppData\Roaming\anythingllm-desktop\storage 2) in older version 1.7.1, select one user instead of all user, it resolved the problem, but for 1.9 or 1.8.5, apparently this option is removed. so what could be the problem then now? I am sure lots of you already started to run anythingllm on Arm64 based windows 11, but somehow I missed some part, thanks for your help . =Fengy= ### Are there known steps to reproduce? just create new workspace on windows 11 with Snapdragon X Elite, it is 100% reproduceable on my laptop.
deekerman 2026-02-28 06:26:54 -05:00
Author
Owner

@timothycarambat commented on GitHub (Dec 2, 2025):

in older version 1.7.1, select one user instead of all user, it resolved the problem, but for 1.9 or 1.8.5, apparently this option is removed.

This is because we removed the option to install for all on WoA, and it is now always for the user only to remove the possibility of error from being an option.

I have a Windows (clean) Snapdragon X Elite Dell Latitude and cannot reproduce this. With the volume of daily active users on WoA if this problem was not client side or specific to your device/config then we would see this at a higher reporting interval. I can try to repro again on a refreshed machine to see.

Otherwise, Prisma does not support WoA builds, so we actually run an executable from Prisma that is emulated. Since our app is signed and that binary might not be it is possible Windows Defender is halting that process from running silently causing the DB ops to fail since the engine is not running.

Are you able to replicate this with an older (unsigned) build of WoA?
https://docs.anythingllm.com/changelog/v1.8.5#pinned-download-links

@timothycarambat commented on GitHub (Dec 2, 2025): > in older version 1.7.1, select one user instead of all user, it resolved the problem, but for 1.9 or 1.8.5, apparently this option is removed. This is because we removed the option to install for all on WoA, and it is now always for the user only to remove the possibility of error from being an option. I have a Windows (clean) Snapdragon X Elite Dell Latitude and cannot reproduce this. With the volume of daily active users on WoA if this problem was not client side or specific to your device/config then we would see this at a higher reporting interval. I can try to repro again on a refreshed machine to see. Otherwise, Prisma does not support WoA builds, so we actually run an executable from Prisma that is emulated. Since our app is signed and that binary might not be it is possible Windows Defender is halting that process from running silently causing the DB ops to fail since the engine is not running. Are you able to replicate this with an older (unsigned) build of WoA? https://docs.anythingllm.com/changelog/v1.8.5#pinned-download-links
Author
Owner

@fengyqy commented on GitHub (Dec 2, 2025):

Thanks for your response and trying to reproduce it!

I actually tried 1.8.5-r2 and also 1.8.0 today, no luck unfortunately same issue as before. Agreed that it could be my laptop configuration issue if no one reported such problem again.

I will try to use "admin" to install anythingLLM or run it to see if it helps, and will update results later.

thanks
Qiuyu

Image Image
@fengyqy commented on GitHub (Dec 2, 2025): Thanks for your response and trying to reproduce it! I actually tried 1.8.5-r2 and also 1.8.0 today, no luck unfortunately same issue as before. Agreed that it could be my laptop configuration issue if no one reported such problem again. I will try to use "admin" to install anythingLLM or run it to see if it helps, and will update results later. thanks Qiuyu <img width="1863" height="1091" alt="Image" src="https://github.com/user-attachments/assets/4529cb6a-d87b-42b5-b3de-8699a460fe30" /> <img width="1263" height="883" alt="Image" src="https://github.com/user-attachments/assets/d5658aca-02f5-4836-8840-709807eb73d9" />
Author
Owner

@timothycarambat commented on GitHub (Dec 2, 2025):

Do you also happen to know if your device is a corporate device (might have some kind of access/AV stopping prisma from running)? That sometimes can certainly be an issue since a lot of WoA devices are currently used in corporate since they are still new in consumer market

@timothycarambat commented on GitHub (Dec 2, 2025): Do you also happen to know if your device is a corporate device (might have some kind of access/AV stopping prisma from running)? That sometimes can certainly be an issue since a lot of WoA devices are currently used in corporate since they are still new in consumer market
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anything-llm#3006
No description provided.