mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #2045] [Bug] Build Error: Access is Denied. (os error 5) in cargo install --force cargo-make #818
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#818
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @JRS296 on GitHub (Mar 20, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2045
Bug Description
I am getting the following error on trying to build out the development environment on my local machine.
I have followed the Build guide as specified in this doc: https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/environment-setup/building-on-windows
The bottleneck arrives on attempting command:
cargo install --force cargo-makeHow to Reproduce
Follow Build steps from doc https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/environment-setup/building-on-windows
Expected Behavior
Completed Compilation for the given development environment.
Operating System
Windows
AppFlowy Version(s)
AppFlowy-IO#2009
Screenshots
Additional Context
(Another small concern) Been receiving malware calls from Kaspersky during build process. Is this something to be concerned over?
Screenshot for the same:

@appflowy commented on GitHub (Mar 21, 2023):
What's your Rust version? You can try
rustup show.@JRS296 commented on GitHub (Mar 21, 2023):
Cargo is at 1.68.0
@JRS296 commented on GitHub (Mar 21, 2023):
UPDATE: downgraded to rust version 1.65, still getting the same error.. Anything that can be done for the same?
@squidrye commented on GitHub (Mar 21, 2023):
Hi @JRS296, I believe your terminal does not has adminstrator privileges to execute files in your C drive, did you try launching your terminal as an administrator ?
@JRS296 commented on GitHub (Mar 21, 2023):
Tried it with Admin priveleges, same result:
@JRS296 commented on GitHub (Mar 26, 2023):
Successfully Built out the dev environment today, AntiVirus was interfering with the build
@vhanla commented on GitHub (Sep 27, 2023):
Kaspersky is blocking it. Could you please update build-script-build executable core and test it against virustotal so it won't be marked as false positive by most reknown antimalware software?

It is crazy of different build-script-build.exe files generated, and all of them marked as malware. I have to disable malware protection, and on reenable, it forces me to restart in order to "disinfect". 😅
@tao-a-man commented on GitHub (Feb 5, 2024):
hii @JRS296 I have same problem, Plss help me tell how you can fix it?
@JRS296 commented on GitHub (Feb 5, 2024):
Hello @tao-a-man, just disable your antivirus (or add cargo to the list of exclusions), and enable firewall permissions for cargo. This should help.