Flutter default counter app fails to run on Android emulator (Gradle task assembleDebug failed)

EarlKess · January 28, 2026, 8:36pm

Hello everyone, I am new to Flutter and wanted to start by running the default counter app created via Flutter: New Project → Application

When I try to run this app on an emulated Android device (Google Pixel 9), the build always fails with the following error:

Gradle task assembleDebug failed with exit code 1

I have installed Flutter, Android Studio, and the Android Emulator exactly as described in the official documentation.
My operating system is Windows 11.

Things I have already tried:

Disabled real-time protection in Windows Defender
Verified the setup with flutter doctor (no issues reported)
Running the app in Chrome works without any problems

The issue only occurs when running the app on the Android emulator.

Here is the full error message:

FAILURE: Build failed with an exception.

* Where:
Settings file 'C:\dev\Flutter Projekte\my_first_app\android\settings.gradle.kts' line: 20

* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> A problem occurred configuring project ':gradle'.
   > Multiple build operations failed.
         Could not move temporary workspace (C:\Users\marvi\.gradle\caches\8.14\transforms\8b7a8db04f880977c033a49d68f5c7b3-f7b78e79-b6df-487a-ac1a-0001f2d3b289) to immutable location (C:\Users\marvi\.gradle\caches\8.14\transforms\8b7a8db04f880977c033a49d68f5c7b3)
         Could not move temporary workspace (C:\Users\marvi\.gradle\caches\8.14\transforms\0b6f6b7d0f2a1f4c9c7c5ec70c8cf723-0be7af6f-54ae-4263-98af-ae8e20763fa4) to immutable location (C:\Users\marvi\.gradle\caches\8.14\transforms\0b6f6b7d0f2a1f4c9c7c5ec70c8cf723)
      > Could not move temporary workspace (C:\Users\marvi\.gradle\caches\8.14\transforms\8b7a8db04f880977c033a49d68f5c7b3-f7b78e79-b6df-487a-ac1a-0001f2d3b289) to immutable location (C:\Users\marvi\.gradle\caches\8.14\transforms\8b7a8db04f880977c033a49d68f5c7b3)
      > Could not move temporary workspace (C:\Users\marvi\.gradle\caches\8.14\transforms\0b6f6b7d0f2a1f4c9c7c5ec70c8cf723-0be7af6f-54ae-4263-98af-ae8e20763fa4) to immutable location (C:\Users\marvi\.gradle\caches\8.14\transforms\0b6f6b7d0f2a1f4c9c7c5ec70c8cf723)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 28s
Error: Gradle task assembleDebug failed with exit code 1

Has anyone encountered this issue before or knows how to fix it?

mihalycsaba · January 28, 2026, 10:06pm

github.com/gradle/gradle

Could not move temporary workspace ... to immutable location

opened 04:12PM - 27 Nov 24 UTC

closed 06:17AM - 01 Aug 25 UTC

CC007

a:bug in:execution-engine

### Current Behavior Reopening #27844, because it seems to not be fixed and has… been broken since 8.5 When trying to build a freshly created project, I get the following error: ``` FAILURE: Build failed with an exception. * What went wrong: A build operation failed. Could not move temporary workspace (F:\local\applicationData\gradle\caches\8.9\transforms\e7fa29f876e87b2a15c2bc90d0781fdd-9307ed84-c3b0-4017-bce5-8de12a7efb13) to immutable location (F:\local\applicationData\gradle\caches\8.9\transforms\e7fa29f876e87b2a15c2bc90d0781fdd) > Could not move temporary workspace (F:\local\applicationData\gradle\caches\8.9\transforms\e7fa29f876e87b2a15c2bc90d0781fdd-9307ed84-c3b0-4017-bce5-8de12a7efb13) to immutable location (F:\local\applicationData\gradle\caches\8.9\transforms\e7fa29f876e87b2a15c2bc90d0781fdd) ``` This was even after already having moved GRADLE_USER_HOME off of my C drive (which some suggested could fix the issue). The issue only occurs in version 8.6 and newer. Version 8.5 doesn't have this issue. Manually I actually am able to do the move, but only after killing the Gradle daemon process, since it's locking the files. **Workarounds:** 1. Some people mention that uninstalling the virus scanner might help. This however is obviously not a preferred solution, since we don't want Gradle users to be vulnerable to viruses. 2. As mentioned, you can manually move/rename gradle cashes as the error is trying to do (So `e7fa29f876e87b2a15c2bc90d0781fdd-9307ed84-c3b0-4017-bce5-8de12a7efb13` to `e7fa29f876e87b2a15c2bc90d0781fdd`. This works as a workaround, but is tedious (you need to do this at least 5-6 times before it works) and is only a temporary solution. Any Gradle version updates or cache wipes would require you to do this again. 3. Downgrade to version 8.5. This doesn't work for kotlin compose multiplatform projects though, since they rely on features from newer versions. ### Expected Behavior I expect a simple new gradle project to just build without issue. ### Context (optional) This behavior is not tied to a specific project. It was tested with a simple kotlin jvm application and a project generated by the compose multiplatform wizard. ### Self-contained Reproducer Project The problem is not caused by the project itself (considering it happens with any Gradle project). Here is the gradle project that I used in the build scan: https://github.com/CC007/test-gradle ### Gradle version any version between 8.6 and 8.11.1 ### Build scan URL (optional) https://scans.gradle.com/s/n3yylnhnckwuy ### Your Environment (optional) OS: Windows 10 (22H2 build 19045.5131) Virus scanner: Bitdefender

Lot of people mention bitdefender. I had so many non flutter issues with bitdefender in my job. Worst av ever, I have no idea why do so many people use it.

You could delete that gradle folder too. Or use gradle 9, maybe they fixed this. I’ve been using gradle 9 for a while now, no issues. If I remember correctly, it needs a few changes in your configs to be able to use it.

EarlKess · January 29, 2026, 6:59am

Thank you very much for the hint. I realized that McAfee was preinstalled on my notebook. After uninstalling McAfee, everything seems to be working properly.

mihalycsaba · January 29, 2026, 9:20am

Forgot about mcafee, might worse than bitdefender