Android SDK Error: Android emulator stderr

Post Views: 5

Error:

[ERR] The Android emulator exited with code -1073741819 after startup
[ERR] Android emulator stderr:
[ERR] [12084:15220:20240427,175914.017:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachmentsb010e1-a697-4f34-afe4-516a9cadb76a: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.018:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments\a4840e14-a6ff-4298-afdb-948b2a5d1392: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.018:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments1787f5-0862-4140-96b3-10c17a8b6772: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.019:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachmentsa11058a-52ea-4b69-99b2-c71646e20742: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.019:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments\e79ba356-d95c-4d18-a560-c74ef96beb38: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.020:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments\e09873b3-1dd7-4d53-9c65-f33ed080983c: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.020:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments95dbe1-7182-4a6b-8b2a-9e15e3059a0d: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.020:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachmentsc3c6c69-8b4a-402d-a92e-ea2fd0d4968c: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.021:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments97a8d0-92b5-4880-aeda-42212d65c2ae: The system cannot find the file specified. (2)
[ERR] [12084:15220:20240427,175914.021:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments\cade5c67-0924-425c-8275-27ec37754aaa: The system cannot find the file specified. (2)
[ERR] [8180:14204:20240427,175914.156:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachmentsb010e1-a697-4f34-afe4-516a9cadb76a: The system cannot find the file specified. (2)
[ERR] [8180:14204:20240427,175914.157:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments\a4840e14-a6ff-4298-afdb-948b2a5d1392: The system cannot find the file specified. (2)
[ERR] [8180:14204:20240427,175914.158:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachments1787f5-0862-4140-96b3-10c17a8b6772: The system cannot find the file specified. (2)
[ERR] [8180:14204:20240427,175914.158:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\soura\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db\attachmentsa11058a-52ea-4b69-99b2-c71646e20742: The system cannot find the file specified. (2)

Solution

It looks like you’re encountering several issues with your Android Emulator on a Windows system. Here’s a breakdown of the problems and some potential solutions:

File System Errors: The logs show repeated errors indicating that certain files cannot be found (The system cannot find the file specified). This could be caused by missing files necessary for the emulator to run or issues with file permissions.
- Solution: Ensure that all necessary files are in place and that your user account has appropriate permissions to access these files. Sometimes, running the emulator as an administrator can help resolve these access issues.
Vulkan Support Errors: There are warnings and errors related to Vulkan, such as VK_VERSION_1_0 check failed and Vulkan 1.0 APIs missing from instance. This suggests that your emulator configuration is attempting to use Vulkan, but either it isn’t supported by your hardware or the necessary drivers aren’t installed.
- Solution: Update your graphics drivers to the latest version available from your hardware manufacturer. If Vulkan is not supported, you may need to switch to an alternative graphics rendering API in your emulator settings, such as OpenGL.
Emulator Configuration and Update Recommendation: The log includes messages about the need to update the emulator and issues with processing configuration files (e.g., .ini files).
- Solution: Make sure that your Android Emulator is up to date. Check for updates in your Android SDK Manager. Also, verify that the configuration files like quickbootChoice.ini are correctly formatted and accessible.
Potential Corruption or Misconfiguration: Given the number of files that cannot be located and repeated failures, there might be a corruption or misconfiguration in your emulator setup or temporary files.
- Solution: Consider clearing out the emulator’s temporary files located typically under C:\Users\[YourUsername]\AppData\Local\Temp\. Additionally, you may need to recreate the AVD (Android Virtual Device) or reinstall the Android Emulator entirely.

Author
Recent Posts

rajeshkumar