I created a new project from scratch in Unity, but I’m getting a Burst Compile error right away. My Unity version is 6000.0.38f1.
I did some research, and it seems that running Unity in administrator mode has solved this issue for some users. However, I tried that, and it didn’t work for me. Below is the error message I’m encountering.
Do you have any suggestions for solving this problem?
NEVER EVER do that! It’s a major risk because everything inside Unity executes as administrator, even a script that accidentally deletes important operating system files/folders.
Unity actually warns you when you do run it with admin privileges.
Without seeing the actual error messages in full (copy & paste as text, or attach editor.log) I can think of a few possibilities:
Deleting the Library folder with the project closed may also help.
I’ve tried all the suggestions you mentioned, including granting “Everyone” permissions to the folder, but unfortunately, the issue persists. The computer’s security policies are managed by my company, and I’m unable to apply exceptions in Windows Defender.
Interestingly, this problem didn’t occur until about 3-5 days ago, after I installed the Monetization plugin. Even when I create a completely new project from scratch, the error continues to appear.
Yet they allow you to “run as administrator”? Perhaps someone from IT came over and gave you the admin privilege in this particular case, I hope.
Otherwise IT should be made aware because the ability to grant yourself admin privileges would defy the purpose of having a company-wide security policy in the first place. 
That I wouldn’t do, ever. Now literally everyone, including guest accounts, could read or delete your projects for instance.
Would still help to see the full error details ie editor.log.
You could also try to create a new project under “Documents” to absolutely rule out any permission issues.
I created a new project in the Documents folder, but the issue wasn’t resolved. It continues to persist. I uploaded the log file.
Editor.txt (1.4 MB)
You got several of these:
[Script Updater] Failed to resolve ‘None’ expression : Library/PackageCache/com.unity.2d.pixel-perfect@e3ae982b672d/Editor/Converter/U2DToURPPixelPerfectConverter.cs (57,76). This may cause expected updates to not be applied.
[ApiUpdater] Total time: 18081ms, Parse response file: 208ms, Collect updater configs: 9924ms, Update: 7893ms, Save: 56ms Files: 2 modified / 2 visited / 5 total (Library/Bee/artifacts/1900b0aE.dag/Unity.2D.PixelPerfect.Editor.dll).
STDERR:
[Script Updater] Library/PackageCache/com.unity.2d.pixel-perfect@e3ae982b672d/Editor/Converter/U2DToURPPixelPerfectConverter.cs(26,65): error CS0234: The type or namespace name ‘PixelPerfectCamera’ does not exist in the namespace ‘UnityEngine.Experimental.Rendering.Universal’ (are you missing an assembly reference?)
Are these errors resolved when you open the project?
I can also see from the paths that your project is located under OneDrive. Any project that is in a cloud synched folder is prone to defects. Unity is not designed to be constantly backed up while it is running. This may interfere with and cause those issues. In any case it definitely puts your project(s) at risk since cloud sync is prone to straight out destroying projects due to the nature of always overwriting the latest changed files, and it’s uploading tons of files that are merely temporary artifacts.
I realized after sending the previous message that it was created under OneDrive, so I deleted the project and recreated it directly under the Documents folder under Users. The directory doesn’t matter. No matter which directory I create a new project in, these errors still occur.
Hi @canaktepe!
Creating a new project should indeed not be throwing errors. If possible, could you share which type of system (like Windows 10, or 11 or Mac etc.) you’re on? 
From your log (thanks for providing it!) it looks like it may be a permission issue just like @CodeSmile (thanks for sharing things to try too!) and you have already been discussing, or possibly a virus-checker issue or something like it.
Could you try the following to narrow down what’s happening:
C:\Users\c.aktepe\OneDrive\Documents\TestProject\Library\PackageCache\com.unity.burst@7a907cf5a459\.Runtime\burst-lld-18-hostwin.exe from a command prompt? When you do that, what happens?This may give us more info on what specifically is wrong.
Hello, first of all, thank you for your response.
My operating system is Windows 11.
I also thought that it might be blocked by antivirus or group policies, but everything was working perfectly fine a week ago. I even installed an APK file on my physical device. This issue started when I installed the Ads Monetization package. However, even after uninstalling this package or creating a new project, the problem did not go away.
I can’t uninstall the Burst package from my project because it’s listed as a dependency used by other packages. Therefore, the remove button is disabled.
I haven’t tried running the command in the command prompt yet, but I’ll give it a try when I get back to my computer and will update you on the outcome.
There is a file named burst-lld-18-hostwin-arm64.exe in this folder, but the file name mentioned in the error is burst-lld-18-hostwin.exe
- I can’t uninstall the Burst package from my project because it’s listed as a dependency used by other packages. Therefore, the remove button is disabled.
You could try deleting the cached files manually. To do, first close the Editor, and then in File Explorer, delete the Library\PackageCache\com.unity.burst@7a907cf5a459 folder from your project. Then start the Editor.
There is a file named burst-lld-18-hostwin-arm64.exe in this folder, but the file name mentioned in the error is burst-lld-18-hostwin.exe
Yeah, without .Runtime\burst-lld-18-hostwin.exe, Burst isn’t going to work correctly. Hopefully removing Burst from the package cache fixes the issue, but let us know.
@tim_jones
I deleted the Burst package from the directory and opened the editor, but nothing happened.
Do you mean you still saw the same error in the Console as in your original post, and burst-lld-18-hostwin.exe still doesn’t exist in that folder alongside burst-lld-18-hostwin-arm64.exe?
You could try deleting any com.unity.burst folders from these locations (this is the system-wide location for caching downloaded packages):
%LOCALAPPDATA%\Unity\cache\npm\packages.unity.com%LOCALAPPDATA%\Unity\cache\packages\packages.unity.com%LOCALAPPDATA%\Unity\cache\upm\packages\packages.unity.comWhen you do that you’ll want to delete com.unity.burst from your project’s Library/PackageCache again, to force it to re-download when you next open the Editor.
So far, it looks like one of these locations contains a corrupt Burst package. Hopefully the above will fix it. If not, please could you attach your Editor.log.
As you mentioned, I deleted the burst-related packages in the cache folder. However, nothing changed. Also, when I create a new clean project from scratch, I get these errors as soon as I open the editor.
Editor.txt (419.6 KB)
I’ve added the Package-Manager label to this thread because it seems like something is going wrong either when downloading the Burst package, or unzipping it. Hopefully somebody from that team can help out.
The error message seems to have changed.
"Native error= The system cannot find the file specified."
I suspect that it has not been re-imported correctly.
Try deleting the entire Library folder, not just Library\PackageCache\com.unity.burst@7a907cf5a459, and then restart the editor.
Thank you for your response. I tried completely deleting the project and even uninstalling and reinstalling the entire Unity setup, but this issue still persists.
I talked to IT department. The exe file is blocking by the bitdefender
From personal experience I can tell you Bitdefender is the worst of the many antivirus I have used in the past. It’s akin to be a malware in and of itself, constantly “alerting” things that are absolutely harmless.
Uninstall (or convince IT) and just rely on Windows Defender which is absolutely sufficient these days and much less intrusive than any of the paid solutions and more so their free but heavily upselling “lite” versions.
I respect your personal opinion. However, this may vary for everyone. I can’t comment since I haven’t experienced it myself. But since the IT department of a company with 2,000 employees has chosen it, I can’t ask them why they chose it or tell them to change it. 
I think, first and foremost, this exe file should be marked as trusted in the Bitdefender database.