if follow the instruction , the problem can solve . But i will get the same problem again when creat a new site. I already check to see my antivirus doing any “quarantining” or not and also remove local from the “quarantining” list already , but the problem still continue.
System Details
Which version of Local is being used?
latest version
What Operating System (OS) and OS version is being used?
Windows 10 home
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Hey @ttctst – Welcome to the Local Community Forums!
Looking at the Antivirus’ quarantine list is a good idea, and what I recommend for those EBUSY errors.
One other thing to consider is – do you have some sort of syncing or backup process in place? Something like a tool to automatically upload file to Dropbox or GDrive?
Are you able to use Window’s resource monitor to see what exactly is holding onto the file when Local gives that error? Something similar to what’s described in this StackOverflow question:
I wonder if it’s that SearchApp.exe process? When I was investigating some performance issues in this other thread, I came across issues when the computer was indexing all of the files that Local was creating:
I was able to improve performance by adding exclusions for the various Local files so that they wouldn’t be indexed.
I don’t think you want to stop that process – it will keep re-spawning. Instead, you’ll want to configure it so that it isn’t watching the WordPress site folders are creating.
Again, I don’t know for sure if this will work, but this seems something that would cause that EBUSY error.