Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4701] [BUG]: Fail to create workspace on both 1.90 r 1or 1.8.5 r2 #2978

New Issue
Closed
opened 2026-02-22 18:32:07 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:32:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @fengyqy on GitHub (Dec 1, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4701

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). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4701 ### 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.
yindo added the possible buginvestigating labels 2026-02-22 18:32:07 -05:00
yindo closed this issue 2026-02-22 18:32:07 -05:00
yindo commented 2026-02-22 18:32:07 -05:00
Author
Owner
Copy Link
Copy Source

@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
yindo commented 2026-02-22 18:32:07 -05:00
Author
Owner
Copy Link
Copy Source

@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" />
yindo commented 2026-02-22 18:32:07 -05:00
Author
Owner
Copy Link
Copy Source

@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
yindo changed title from [BUG]: Fail to create workspace on both 1.90 r 1or 1.8.5 r2 to [GH-ISSUE #4701] [BUG]: Fail to create workspace on both 1.90 r 1or 1.8.5 r2 2026-06-05 14:49:37 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label investigating possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2978
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?