Windows 11下通过命令行启动Android模拟器失败的问题求助

大家好，我在Windows 11上遇到了Android模拟器的启动问题，想请教下各位：

我目前的环境情况：

• 操作系统：Windows 11
• Android模拟器版本：35.6.11.0（build_id 13610412）
• 已经通过Android Studio设备管理器安装了Pixel 9 Pro API 36的系统镜像，在AS内置模拟器中启动这个设备完全正常，没有任何问题。

但我想跳过Android Studio，直接用命令行启动模拟器，尝试后却遇到了故障。我对模拟器底层工作原理几乎一无所知，实在摸不清头绪，所以来求助大家。

我执行的命令步骤如下：
首先列出已有的AVD设备：

PS> C:\Users\User\AppData\Local\Android\Sdk\emulator\emulator.exe -list-avds
Pixel_9_Pro_API_36

然后尝试启动指定的AVD：

PS> C:\Users\User\AppData\Local\Android\Sdk\emulator\emulator.exe -avd Pixel_9_Pro_API_36

执行启动命令后输出了大量日志，其中有一行我觉得是关键问题：

WARNING | adb command 'C:\Users\User\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 shell am start-foreground-service -e meter on com.android.emulator.radio.config/.MeterService ' failed: 'adb.exe: device offline'

另外还有一条显眼的警告：WARNING | Please update the emulator to one that supports the feature(s): VulkanVirtualQueue

完整日志输出如下：

INFO | Android emulator version 35.6.11.0 (build_id 13610412) (CL:N/A)
INFO | Graphics backend: gfxstream
INFO | Found systemPath C:\Users\User\AppData\Local\Android\Sdk\system-images\android-36\google_apis_playstore\x86_64\
WARNING | Please update the emulator to one that supports the feature(s): VulkanVirtualQueue
INFO | Increasing RAM size to 3072MB
INFO | IPv4 server found: 8.8.8.8
INFO | Ignore IPv6 address: 801d:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 801d:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 801d:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: b023:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: b023:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: b023:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: e02b:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: e02b:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: e02b:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: f831:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: f831:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: f831:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 483f:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 483f:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 483f:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 3045:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 3045:7a62:8e01:0:801d:7a62:8e01:0
INFO | Ignore IPv6 address: 3045:7a62:8e01:0:801d:7a62:8e01:0
INFO | Guest GLES Driver: Auto (ext controls) library_mode host gpu mode host
INFO | emuglConfig_get_vulkan_hardware_gpu_support_info: Found physical GPU 'Intel(R) Iris(R) Xe Graphics', type: VK_PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU, apiVersion: 1.3.280, driverVersion: 0.405.1446
INFO | GPU device local memory = 10061MB
INFO | Checking system compatibility:
INFO | Checking: hasCompatibleHypervisor
INFO | Ok: Hypervisor compatibility to run avd: `Pixel_9_Pro_API_36` is met
INFO | Checking: hasSufficientSystem
INFO | Ok: System requirements to run avd: `Pixel_9_Pro_API_36` are met
INFO | Checking: hasSufficientHwGpu
INFO | Ok: Hardware GPU requirements to run avd: `Pixel_9_Pro_API_36` are passed
INFO | Checking: hasSufficientDiskSpace
INFO | Ok: Disk space requirements to run avd: `Pixel_9_Pro_API_36` are met
INFO | Critical: Failed to load opengl32sw (The specified module could not be found.) (:0, )
INFO | Warning: Software OpenGL failed. Falling back to the system OpenGL. (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_btn_xr_environment_living_room_day_clicked() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_btn_xr_environment_living_room_night_clicked() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_new_posture_requested(int) (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_posture_selection_dialog() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_new_resizable_requested(PresetEmulatorSizeType) (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_resizable_dialog() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_xr_environment_mode_changed(int) (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_xr_environment_mode_dialog() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_xr_input_mode_changed(int) (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_xr_input_mode_dialog() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_sleep_timer_done() (:0, )
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_unfold_timer_done() (:0, )
INFO | Critical: Failed to load opengl32sw (The specified module could not be found.) (:0, )
INFO | Warning: Software OpenGL failed. Falling back to the system OpenGL. (:0, )
WARNING | adb command 'C:\Users\User\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 shell am start-foreground-service -e meter on com.android.emulator.radio.config/.MeterService ' failed: 'adb.exe: device offline'

我的几个核心疑问：

1. 为什么在Android Studio里能正常启动的模拟器，命令行启动就会报adb.exe: device offline的错误？
2. 日志里的VulkanVirtualQueue版本警告，会不会是导致启动失败的原因？
3. 加载opengl32sw模块失败的错误，和当前故障有没有关联？

希望各位能帮忙分析问题所在，给我一些解决思路，谢谢大家！

内容来源于stack exchange