$WinREAgent Error with VMware Workstation 17 Pro

I will start off with this…

 ╭─fenris@fenris in ~ took 22ms
 ╰─λ garuda-inxi
  Kernel: 6.6.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=8adfdab2-f46f-4dc9-bec4-6c286c843cff rw rootflags=subvol=@
    quiet resume=UUID=a72d297c-8ad5-4e2f-9483-375f636e64b4 loglevel=3 ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
  Type: Desktop System: AZW product: MINI S v: N/A
    serial: <superuser required>
  Mobo: AZW model: MINI S v: 10 serial: <superuser required> UEFI: American
    Megatrends LLC. v: ADLNV104 date: 02/06/2023
  Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 90%
    rechargeable: yes status: discharging
  Info: model: Intel N100 bits: 64 type: MCP arch: Alder Lake level: v3
    note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6
    model-id: 0xBE (190) stepping: 0 microcode: 0x12
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
    desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 850 high: 1219 min/max: 700/3400 scaling:
    driver: intel_pstate governor: powersave cores: 1: 700 2: 1219 3: 702 4: 782
    bogomips: 6451
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel
    arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports:
    active: HDMI-A-1,HDMI-A-2 empty: none bus-ID: 00:02.0 chip-ID: 8086:46d1
    class-ID: 0300
  Device-2: Creative Live! Cam Sync 1080p V2 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3.4:9
    chip-ID: 041e:40a0 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.10 compositor: xfwm v: 4.18.0 driver:
    X: loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3280x1080 s-dpi: 96 s-size: 867x285mm (34.13x11.22")
    s-diag: 913mm (35.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: bottom-l model: HKC TV
    serial: <filter> built: 2015 res: 1360x768 hz: 60 dpi: 45 gamma: 1.2
    size: 760x450mm (29.92x17.72") diag: 806mm (31.7") ratio: 16:9, 15:9
    modes: max: 1360x768 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: primary,top-right model: HP LA2206
    serial: <filter> built: 2011 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2
    size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: Vulkan v: 1.3.274 layers: 5 device: 0 type: integrated-gpu
    name: Intel Graphics (ADL-N) driver: mesa intel v: 23.3.3-arch1.1
    device-ID: 8086:46d1 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.3.3-arch1.1 (LLVM
    16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Device-1: Intel driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:54c8
    class-ID: 0403
  Device-2: C-Media CM106 Like Sound Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-3.2:4 chip-ID: 0d8c:0102 class-ID: 0300
  Device-3: JMTek LLC. LCS USB Audio
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-3.3:7 chip-ID: 0c76:2018 class-ID: 0300
    serial: <filter>
  Device-4: Creative Live! Cam Sync 1080p V2 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3.4:9
    chip-ID: 041e:40a0 class-ID: 0102 serial: <filter>
  API: ALSA v: k6.6.10-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.0.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
  Device-1: Intel CNVi: Wi-Fi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
    bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: ASIX AX88179 Gigabit Ethernet driver: ax88179_178a type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-3.1:5
    chip-ID: 0b95:1790 class-ID: ff00 serial: <filter>
  IF: enp0s20f0u3u1 state: down mac: <filter>
  IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:5 chip-ID: 8087:0026
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
    status: discoverable: no pairing: no
  Local Storage: total: 2.29 TiB used: 507.35 GiB (21.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: PCIe SSD size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
    tech: SSD serial: <filter> fw-rev: EHFM90.1 temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000LM015-2E8174
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-1: / raw-size: 500 GiB size: 500 GiB (100.00%) used: 12.45 GiB (2.5%)
    fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 584 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 1.06 TiB size: 1.06 TiB (100.00%)
    used: 53.65 GiB (5.0%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-4: /var/log raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 12.45 GiB (2.5%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-5: /var/tmp raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 12.45 GiB (2.5%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.4 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 24 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 maj-min: 8:2
  System Temperatures: cpu: 51.0 C mobo: N/A
  Fan Speeds (rpm): N/A
  Processes: 261 Uptime: 18m wakeups: 0 Memory: total: 16 GiB note: est.
  available: 15.4 GiB used: 11.3 GiB (73.4%) Init: systemd v: 255
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1414 libs: 414 tools: pamac,paru,yay Shell: Bash v: 5.2.21
  running-in: xfce4-terminal inxi: 3.3.31
Garuda (2.6.22-1):
  System install date:     2024-01-12
  Last full system update: 2024-01-13
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            vmware-workstation-server.service vmware.service 

 ╭─fenris@fenris in ~ took 4s

So here is the scoop, I have this NVMe stick in this Beelink computer that can load into Windows 11, so I store a virtual machine of Windows 11 Pro in the drive so I can access it through Garuda. Now something happened where it glitched out and I had to build it again in Garuda then I file transferred it over to the drive.

So I did this figuring that perhaps its a partition issue…

 ╭─fenris@fenris in ~ took 10ms
 ╰─λ sudo mount -t ntfs-3g /dev/nvme0n1p3 /mnt/beelinknvme
[sudo] password for fenris:         

 ╭─fenris@fenris in ~ as 🧙 took 2s
 ╰─λ sudo umount /dev/nvme0n1p3

 ╭─fenris@fenris in ~ as 🧙 took 135ms
 ╰─λ sudo ntfsfix /dev/nvme0n1p3
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/nvme0n1p3 was processed successfully.

 ╭─fenris@fenris in ~ as 🧙 took 227ms
 ╰─λ sudo mount -t ntfs-3g /dev/nvme0n1p3 /mnt/beelinknvme

 ╭─fenris@fenris in ~ as 🧙 took 176ms

However this didn’t fix my issue.

You can see that I can access the files just fine, and the virtual machine is located in “vmware”

Now when you load up VMware Workstation and try to access it, you find that the engine won’t let you. You get this…

If I go into the folder and try to load it up by double clicking it, Garuda forcefully loads up VMware Player 17 and tries to make you use that.

I haven’t found anything online that mentions this kind of an issue before

VMWare is the problem, Google-fu says.

Terrific :face_with_raised_eyebrow:

Have you tried using ntfs3 instead of ntfs-3g to see if that makes any difference?

Is there a reason you are using ntfs on that drive? Do you share it with a physical Windows device? ntfs on Linux is generally a pain sometimes.

Here is the results:

 ╭─fenris@fenris in ~ as 🧙 took 5s
 ╰─λ sudo mount -t ntfs3 /dev/nvme0n1p3 /mnt/beelinknvme
mount: /mnt/beelinknvme: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

 ╭─fenris@fenris in ~ as 🧙 took 129ms
[🔴] × 

This NVMe drive is what came with the Beelink Mini S PC. It has Windows 11 install files on it that’s keyed to the driver settings on this PC. However, this has been deactivated and I installed a 2 TB plattered drive with Garuda on it instead. I wish to preserve the drive in it’s original format encase I need to boot to windows for what ever reason. At that point I could launch the VM and continue on my day as need be. This has to remain in NTFS format to make that possible.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.