Command Examples list is empty & ListAllAVDs not working about rootavd

[oom-]

Seems to have worked by passing the ramdisk.img (not existing) to the command line : rootAVD.bat D:\AndroidSDK\system-images\android-30\google_apis\x86_64\ramdisk.img

[newbit1]

Did you install any AVD images yet?

[oom-]

Yes I have. 28/29/30. All this part of the path is actually existing: D:\AndroidSDK\system-images\android-30\google_apis\x86_64\. Could be because they are on another disk ?

[newbit1]

Yes, i am just looking in the standard dir. Is this other location some how populated?
Is this other location changed in the SDK Manager?
You can check in CMD by just typing set if there is any Android related variable set.
According to Environment variables from AOSP.
ANDROID_HOME would be the right variable to set. Even tho it mentions as well, that ANDROID_SDK_ROOT
is deprecated, if you check the emulator help, it still refers to ANDROID_SDK_ROOT.

emulator -help-environment

  The Android emulator looks at various environment variables when it starts:

  If ANDROID_LOG_TAGS is defined, it will be used as in '-logcat <tags>'.

  If 'http_proxy' is defined, it will be used as in '-http-proxy <proxy>'.

  If ANDROID_VERBOSE is defined, it can contain a comma-separated list of
  verbose items. for example:

      ANDROID_VERBOSE=socket,radio

  is equivalent to using the '-verbose -verbose-socket -verbose-radio'
  options together. unsupported items will be ignored.

  If ANDROID_LOG_TAGS is defined, it will be used as in '-logcat <tags>'.

  If ANDROID_EMULATOR_HOME is defined, it replaces the path of the '$HOME/.android'
  directory which contains the emulator config data (key stores, etc.).

  If ANDROID_SDK_ROOT is defined, it indicates the path of the SDK
  installation directory.

To cover your use case, If you make sure, either one of the variables ANDROID_HOME or ANDROID_SDK_ROOT is set, I can include both in my search routine.