Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming

Subaru SSM4 FlashWrite VM - Subaru Diagnostic Software Tool 26.6

Sign in to download for free
Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming
Subaru SSM4 FlashWrite VM - Subaru Diagnostic Software Tool 26.6
Sign in to download for free
Overview History Discussion
Bin

Bin

Thread Owner
Administrator
Joined
03.05.2025
Messages
1,863
Reaction score
47,092
New release thread for Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming: discuss, share feedback, and get help.

Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming Bin

Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming

v26.6 — ready-to-run VM, dealer-style diagnostics, FlashWrite programming workflow

Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming​#

v26.6 — ready-to-run VM, dealer-style diagnostics, FlashWrite programming workflow

This virtual machine package bundles Subaru SSM4 with FlashWrite 2 for workshop diagnostics and control unit programming tasks. It is intended for service environments that need a consistent, preconfigured runtime with the correct application stack kept together inside a VM. Typical use includes reading and clearing DTCs, viewing live data and readiness information, running guided functions, and performing supported ECU or module programming operations through approved interfaces.

Use it as...
Click to expand...

Frequently Asked Questions​#

Which Windows version is recommended?
For maximum stability during ECU flashing and diagnostics, a clean installation of Windows 10 (64-bit) is recommended.
Is it compatible with J2534 PassThru?
Most modern software versions support standard J2534 interfaces like Scanmatik 2 Pro, OpenPort 2.0, and specific VCI adapters.

What's inside:
  • Overview & screenshots
  • Version history and compatibility
  • Download link and setup notes

👉 View full details and download — Subaru SSM4 and FlashWrite VM for Diagnostics and ECU Programming
 
Ratings and Reviews
Total ratings: 0
hi thanks for the download im just having abit of difficultygetting it running on my pc, any help would be aprecciated than ks again
 
mattyp said:
hi thanks for the download im just having abit of difficultygetting it running on my pc, any help wo...
Click to expand...

No worries — happy to help. To point you in the right direction, can you share a bit more detail:

  1. What hypervisor are you using — VMware Workstation, VMware Player, VirtualBox, or something else?
  2. Which VM image did you import — the W10 32-bit or the XP 32-bit?
  3. What exactly happens when you try to run it — does the VM fail to boot, throw an error, or does SSM4 itself not launch inside the guest?
  4. Is hardware virtualization (VT-x / AMD-V) enabled in your BIOS/UEFI?
  5. What are your host PC specs — OS, RAM, CPU?

Most common issues with this type of VM package:

  • VM won't start at all — usually VT-x/AMD-V is disabled in BIOS. Enter BIOS setup and enable it under CPU or Security settings.
  • VM boots but SSM4 won't launch or errors out — check that the VM has enough allocated RAM (at least 2–4 GB for the guest) and that no files got corrupted during extraction.
  • USB interface not seen inside the VM — you need to pass the J2534 adapter USB device through to the guest via the VM's USB settings.

Post back with the details and any error messages and we'll get it sorted.
 
v
Gemini said:
No worries — happy to help. To point you in the right direction, can you share a bit more detail:

  1. What hypervisor are you using — VMware Workstation, VMware Player, VirtualBox, or something else?
  2. Which VM image did you import — the W10 32-bit or the XP 32-bit?
  3. What exactly happens when you try to run it — does the VM fail to boot, throw an error, or does SSM4 itself not launch inside the guest?
  4. Is hardware virtualization (VT-x / AMD-V) enabled in your BIOS/UEFI?
  5. What are your host PC specs — OS, RAM, CPU?

Most common issues with this type of VM package:

  • VM won't start at all — usually VT-x/AMD-V is disabled in BIOS. Enter BIOS setup and enable it under CPU or Security settings.
  • VM boots but SSM4 won't launch or errors out — check that the VM has enough allocated RAM (at least 2–4 GB for the guest) and that no files got corrupted during extraction.
  • USB interface not seen inside the VM — you need to pass the J2534 adapter USB device through to the guest via the VM's USB settings.

Post back with the details and any error messages and we'll get it sorted.
Click to expand...
vm workstation i have on pc already, can you give me instrucyions from when i open vm workstation, how do i open it on the program ?
 
mattyp said:
it says the file isngt a vmx file
Click to expand...

That error means you're trying to open the wrong file type. Here's the step-by-step:

How to import the VM into VMware Workstation:

  1. Open VMware Workstation
  2. Go to File → Open
  3. Browse to the folder where you extracted the download
  4. Look for a file with the .ova or .ovf extension — that's the one you need to open (not a .vmdk or random file)
  5. Select it and click Open
  6. VMware will ask you to name the VM and choose a storage location — just accept the defaults and click Import
  7. Wait for the import to finish, then power on the VM

If you only see a .vmdk file and no .ova/.ovf:

Instead of "Open", you need to create a new VM manually:

  1. File → New Virtual Machine → Custom
  2. Choose the appropriate guest OS (Windows 10 x32 or Windows XP x32 depending on which image you downloaded)
  3. When it asks about the disk, choose "Use an existing virtual disk" and point it to the .vmdk file
  4. Finish the wizard, then power on

Can you check the extracted folder and tell me exactly which file extensions you see in there? That way I can give you the exact steps for your situation.
 
Gemini said:
That error means you're trying to open the wrong file type. Here's the step-by-step:

How to import the VM into VMware Workstation:

  1. Open VMware Workstation
  2. Go to File → Open
  3. Browse to the folder where you extracted the download
  4. Look for a file with the .ova or .ovf extension — that's the one you need to open (not a .vmdk or random file)
  5. Select it and click Open
  6. VMware will ask you to name the VM and choose a storage location — just accept the defaults and click Import
  7. Wait for the import to finish, then power on the VM

If you only see a .vmdk file and no .ova/.ovf:

Instead of "Open", you need to create a new VM manually:

  1. File → New Virtual Machine → Custom
  2. Choose the appropriate guest OS (Windows 10 x32 or Windows XP x32 depending on which image you downloaded)
  3. When it asks about the disk, choose "Use an existing virtual disk" and point it to the .vmdk file
  4. Finish the wizard, then power on

Can you check the extracted folder and tell me exactly which file extensions you see in there? That way I can give you the exact steps for your situation.
Click to expand...
i can see a file called subaru select monitor 26.6 - smpro
says its a vmware virtual disc file
it says in vm worksttion that its incompatible ith workstation 8.0
 
mattyp said:
i can see a file called subaru select monitor 26.6 - smpro
says its a vmware virtual disc file
it s...
Click to expand...

Got it. You're seeing the virtual disk file (.vmdk), but VMware Workstation needs a configuration file (.vmx) or an appliance file (.ova/.ovf) to import or open a pre-built VM.

The error "incompatible with workstation 8.0" suggests that either:

1. The VM was created with a much newer version of VMware and is trying to use features not supported by version 8.0.
2. Or, you're trying to open the .vmdk directly, which is not how you import a full VM.

Here's how to proceed:

Option 1: If you can find an .ova or .ovf file:

This is the easiest. If the download package contains a .ova or .ovf file (often alongside the .vmdk), use that:

1. Open VMware Workstation.
2. Go to File > Open a Virtual Machine.
3. Navigate to the folder where you extracted the download.
4. Select the .ova or .ovf file and click Open.
5. Follow the prompts to import the VM.

Option 2: If you only have the .vmdk and need to create a new VM (most likely scenario based on your description):

Since you have an older version of Workstation (8.0), you'll need to create a new VM and attach the existing disk.

1. Open VMware Workstation.
2. Go to File > New Virtual Machine....
3. Select Custom (advanced) and click Next.
4. Choose I will install the operating system later. and click Next.
5. Select the OS type and version that matches the VM you downloaded. If it's Windows 10 32-bit, select Microsoft Windows and then Windows 10 (even if it's 32-bit, Workstation 8.0 might not list it specifically, so choose the closest option). If it's XP, select Microsoft Windows and Windows XP Professional. Click Next.
6. Give your virtual machine a name (e.g., "Subaru SSM4") and choose a location to store it. Click Next.
7. Specify the processor and memory. For a 32-bit OS, 2GB RAM is usually sufficient, but check the VM's requirements if you have them. For CPU, 1 or 2 cores is typically fine. Click Next.
8. For Network Type, you can choose NAT or Bridged depending on your needs. NAT is usually fine for diagnostics. Click Next.
9. On the "Recommended" screen, click Next.
10. On the "Select a Disk" screen, choose Use an existing virtual disk. Click Next.
11. Browse to the location of your subaru select monitor 26.6 - smpro.vmdk file and select it. Click Open, then Next.
12. On the "Choose Disk Type" screen, select VMware Compatible and click Next.
13. On the "Choose a File for the Virtual Disk" screen, you can usually just click Next to use the existing file name, or choose a new location if you prefer.
14. On the "Ready to Create Virtual Machine" screen, click Finish.

After creating the VM:

1. The new VM will appear in your VMware Workstation library.
2. Before powering it on, right-click the VM and select Settings.
3. Check that the RAM and CPU settings are appropriate for the guest OS.
4. Crucially, ensure that USB support is enabled. Go to USB Controller and make sure Enable virtual USB 2.0 (or 3.0) is checked.
5. Power on the VM.

If you still encounter issues, please provide the exact version of VMware Workstation you are running. Workstation 8.0 is quite old, and compatibility can be an issue with newer VM formats.
 
Gemini said:
Got it. You're seeing the virtual disk file (.vmdk), but VMware Workstation needs a configuration file (.vmx) or an appliance file (.ova/.ovf) to import or open a pre-built VM.

The error "incompatible with workstation 8.0" suggests that either:

1. The VM was created with a much newer version of VMware and is trying to use features not supported by version 8.0.
2. Or, you're trying to open the .vmdk directly, which is not how you import a full VM.

Here's how to proceed:

Option 1: If you can find an .ova or .ovf file:

This is the easiest. If the download package contains a .ova or .ovf file (often alongside the .vmdk), use that:

1. Open VMware Workstation.
2. Go to File > Open a Virtual Machine.
3. Navigate to the folder where you extracted the download.
4. Select the .ova or .ovf file and click Open.
5. Follow the prompts to import the VM.

Option 2: If you only have the .vmdk and need to create a new VM (most likely scenario based on your description):

Since you have an older version of Workstation (8.0), you'll need to create a new VM and attach the existing disk.

1. Open VMware Workstation.
2. Go to File > New Virtual Machine....
3. Select Custom (advanced) and click Next.
4. Choose I will install the operating system later. and click Next.
5. Select the OS type and version that matches the VM you downloaded. If it's Windows 10 32-bit, select Microsoft Windows and then Windows 10 (even if it's 32-bit, Workstation 8.0 might not list it specifically, so choose the closest option). If it's XP, select Microsoft Windows and Windows XP Professional. Click Next.
6. Give your virtual machine a name (e.g., "Subaru SSM4") and choose a location to store it. Click Next.
7. Specify the processor and memory. For a 32-bit OS, 2GB RAM is usually sufficient, but check the VM's requirements if you have them. For CPU, 1 or 2 cores is typically fine. Click Next.
8. For Network Type, you can choose NAT or Bridged depending on your needs. NAT is usually fine for diagnostics. Click Next.
9. On the "Recommended" screen, click Next.
10. On the "Select a Disk" screen, choose Use an existing virtual disk. Click Next.
11. Browse to the location of your subaru select monitor 26.6 - smpro.vmdk file and select it. Click Open, then Next.
12. On the "Choose Disk Type" screen, select VMware Compatible and click Next.
13. On the "Choose a File for the Virtual Disk" screen, you can usually just click Next to use the existing file name, or choose a new location if you prefer.
14. On the "Ready to Create Virtual Machine" screen, click Finish.

After creating the VM:

1. The new VM will appear in your VMware Workstation library.
2. Before powering it on, right-click the VM and select Settings.
3. Check that the RAM and CPU settings are appropriate for the guest OS.
4. Crucially, ensure that USB support is enabled. Go to USB Controller and make sure Enable virtual USB 2.0 (or 3.0) is checked.
5. Power on the VM.

If you still encounter issues, please provide the exact version of VMware Workstation you are running. Workstation 8.0 is quite old, and compatibility can be an issue with newer VM formats.
Click to expand...
and its asking which hardware to use 8.0 or lower?
 
mattyp said:
and its asking which hardware to use 8.0 or lower?
Click to expand...

When you are creating a new virtual machine in VMware Workstation and it asks for the hardware compatibility level, you should generally choose the option that matches your VMware Workstation version or is the closest compatible option.

For VMware Workstation 8.0, you should select:

  • "Workstation 8.0" or "Workstation 7.x and later"

Choosing a lower compatibility level (like "Workstation 6.x") might limit the features available to the VM, but it can sometimes resolve compatibility issues if the VM was created with very old settings. However, since you are trying to import or create a VM that is likely based on a more recent guest OS (like Windows 10), using the highest compatible level for your Workstation version (8.0) is usually best.

If you are creating a new VM and attaching the existing .vmdk, the "Custom (advanced)" path is the correct one. The hardware compatibility setting is one of the steps in that wizard.

Try selecting "Workstation 8.0". If that doesn't work, you might try the next lower option if available, but it's less likely to be the cause of the .vmdk incompatibility itself. The main issue is that the .vmdk might have been created with features not understood by Workstation 8.0, or it's not part of a complete VM configuration.
 
Gemini said:
When you are creating a new virtual machine in VMware Workstation and it asks for the hardware compatibility level, you should generally choose the option that matches your VMware Workstation version or is the closest compatible option.

For VMware Workstation 8.0, you should select:

  • "Workstation 8.0" or "Workstation 7.x and later"

Choosing a lower compatibility level (like "Workstation 6.x") might limit the features available to the VM, but it can sometimes resolve compatibility issues if the VM was created with very old settings. However, since you are trying to import or create a VM that is likely based on a more recent guest OS (like Windows 10), using the highest compatible level for your Workstation version (8.0) is usually best.

If you are creating a new VM and attaching the existing .vmdk, the "Custom (advanced)" path is the correct one. The hardware compatibility setting is one of the steps in that wizard.

Try selecting "Workstation 8.0". If that doesn't work, you might try the next lower option if available, but it's less likely to be the cause of the .vmdk incompatibility itself. The main issue is that the .vmdk might have been created with features not understood by Workstation 8.0, or it's not part of a complete VM configuration.
Click to expand...
The selected virtual disk is incompatible with this Workstation 5.x virtual machine. Adding this disk would make this virtual machine incompatible with older VMware products.
 
mattyp said:
The selected virtual disk is incompatible with this Workstation 5.x virtual machine. Adding this dis...
Click to expand...

This error message tells us two key things:

1. The virtual disk file (.vmdk) you have was created using features or a format that is incompatible with the "Workstation 5.x" compatibility setting.
2. VMware Workstation 8.0 is trying to create a VM with a default hardware compatibility level that is too low (likely set to 5.x by default in the wizard, or you selected it).

Here's how to fix this:

When creating the new VM, ensure you select the highest possible hardware compatibility level that your VMware Workstation 8.0 supports.

Follow these steps precisely:

1. Open VMware Workstation.
2. Go to File > New Virtual Machine....
3. Select Custom (advanced) and click Next.
4. Choose I will install the operating system later. and click Next.
5. Select the correct Guest OS type and version (e.g., Microsoft Windows > Windows 10 (32-bit) or Windows XP Professional). Click Next.
6. Name the VM and choose a location. Click Next.
7. Configure Processor and Memory. Click Next.
8. Configure Network Type. Click Next.
9. On the "Recommended" screen, click Next.
10. On the "Select a Disk" screen, choose Use an existing virtual disk. Click Next.
11. Browse and select your subaru select monitor 26.6 - smpro.vmdk file. Click Open, then Next.
12. THIS IS THE CRITICAL STEP: You will now be on a screen that asks you to "Choose Disk Type" or "Select a Disk Type". Directly after that, or on the next screen, you will see a dropdown or option for Virtual machine hardware compatibility.
* Make sure this is set to Workstation 8.0 (or the highest option available that includes 8.0). Do NOT select 5.x or lower.
13. Click Next.
14. On the "Choose a File for the Virtual Disk" screen, click Next.
15. On the "Ready to Create Virtual Machine" screen, click Finish.

If you are still being forced to select 5.x, it might be an issue with how the wizard is presenting options in your specific Workstation 8.0 build.

Alternative approach if the above doesn't work:

If Workstation 8.0 is genuinely struggling with that .vmdk, you might need to:
  • Upgrade VMware Workstation to a newer version (even Workstation 16.x is free for personal use).
  • Find a different source for the VM image that is compatible with older VMware versions.

Could you please confirm exactly what options are presented for "Virtual machine hardware compatibility" when you get to that step in the wizard?
 
Gemini said:
This error message tells us two key things:

1. The virtual disk file (.vmdk) you have was created using features or a format that is incompatible with the "Workstation 5.x" compatibility setting.
2. VMware Workstation 8.0 is trying to create a VM with a default hardware compatibility level that is too low (likely set to 5.x by default in the wizard, or you selected it).

Here's how to fix this:

When creating the new VM, ensure you select the highest possible hardware compatibility level that your VMware Workstation 8.0 supports.

Follow these steps precisely:

1. Open VMware Workstation.
2. Go to File > New Virtual Machine....
3. Select Custom (advanced) and click Next.
4. Choose I will install the operating system later. and click Next.
5. Select the correct Guest OS type and version (e.g., Microsoft Windows > Windows 10 (32-bit) or Windows XP Professional). Click Next.
6. Name the VM and choose a location. Click Next.
7. Configure Processor and Memory. Click Next.
8. Configure Network Type. Click Next.
9. On the "Recommended" screen, click Next.
10. On the "Select a Disk" screen, choose Use an existing virtual disk. Click Next.
11. Browse and select your subaru select monitor 26.6 - smpro.vmdk file. Click Open, then Next.
12. THIS IS THE CRITICAL STEP: You will now be on a screen that asks you to "Choose Disk Type" or "Select a Disk Type". Directly after that, or on the next screen, you will see a dropdown or option for Virtual machine hardware compatibility.
* Make sure this is set to Workstation 8.0 (or the highest option available that includes 8.0). Do NOT select 5.x or lower.
13. Click Next.
14. On the "Choose a File for the Virtual Disk" screen, click Next.
15. On the "Ready to Create Virtual Machine" screen, click Finish.

If you are still being forced to select 5.x, it might be an issue with how the wizard is presenting options in your specific Workstation 8.0 build.

Alternative approach if the above doesn't work:

If Workstation 8.0 is genuinely struggling with that .vmdk, you might need to:
  • Upgrade VMware Workstation to a newer version (even Workstation 16.x is free for personal use).
  • Find a different source for the VM image that is compatible with older VMware versions.

Could you please confirm exactly what options are presented for "Virtual machine hardware compatibility" when you get to that step in the wizard?
Click to expand...
The selected virtual disk is incompatible with this Workstation 8.0 virtual machine. Adding this disk would make this virtual machine incompatible with older VMware products.
 
mattyp said:
The selected virtual disk is incompatible with this Workstation 8.0 virtual machine. Adding this dis...
Click to expand...

This error is slightly different, but the root cause is the same: the .vmdk file you have was created with newer features or a different disk format that Workstation 8.0 cannot fully accommodate while maintaining compatibility with older VMware products.

Essentially, VMware Workstation 8.0 is telling you: "If I use this disk, I won't be able to run it on a really old VMware player or product that might only support up to Workstation 5.x or 7.x hardware versions. Are you sure you want to proceed?"

Since you are using Workstation 8.0, you want to use Workstation 8.0 compatibility. The message is just a warning.

Here's what you need to do:

1. Proceed with the warning. When you see that message: "The selected virtual disk is incompatible with this Workstation 8.0 virtual machine. Adding this disk would make this virtual machine incompatible with older VMware products."
* There should be an option to continue or accept the disk despite the warning. Look for a button like "Continue", "OK", or "Yes".
* You are using Workstation 8.0, so you want the VM to be compatible with Workstation 8.0 hardware. The fact that it might not be compatible with older products (like 5.x) is irrelevant to you if you only use Workstation 8.0.

2. Ensure the hardware compatibility is set to Workstation 8.0. Double-check this setting in the wizard. When you get to the step where you select the disk, after choosing "Use an existing virtual disk" and selecting your .vmdk, the wizard should then ask you about the hardware compatibility level for the VM itself. Make sure it's set to Workstation 8.0 (or the highest available option for your installed version).

If you click "Continue" or "OK" past that warning and successfully create the VM with Workstation 8.0 compatibility, it should then allow you to power it on.

Could you confirm if there was a "Continue" or "OK" button after that specific error message?
 
mattyp said:
The selected virtual disk is incompatible with this Workstation 8.0 virtual machine. Adding this disk would make this virtual machine incompatible with older VMware products.
Click to expand...

Gemini said:
This error is slightly different, but the root cause is the same: the .vmdk file you have was created with newer features or a different disk format that Workstation 8.0 cannot fully accommodate while maintaining compatibility with older VMware products.

Essentially, VMware Workstation 8.0 is telling you: "If I use this disk, I won't be able to run it on a really old VMware player or product that might only support up to Workstation 5.x or 7.x hardware versions. Are you sure you want to proceed?"

Since you are using Workstation 8.0, you want to use Workstation 8.0 compatibility. The message is just a warning.

Here's what you need to do:

1. Proceed with the warning. When you see that message: "The selected virtual disk is incompatible with this Workstation 8.0 virtual machine. Adding this disk would make this virtual machine incompatible with older VMware products."
* There should be an option to continue or accept the disk despite the warning. Look for a button like "Continue", "OK", or "Yes".
* You are using Workstation 8.0, so you want the VM to be compatible with Workstation 8.0 hardware. The fact that it might not be compatible with older products (like 5.x) is irrelevant to you if you only use Workstation 8.0.

2. Ensure the hardware compatibility is set to Workstation 8.0. Double-check this setting in the wizard. When you get to the step where you select the disk, after choosing "Use an existing virtual disk" and selecting your .vmdk, the wizard should then ask you about the hardware compatibility level for the VM itself. Make sure it's set to Workstation 8.0 (or the highest available option for your installed version).

If you click "Continue" or "OK" past that warning and successfully create the VM with Workstation 8.0 compatibility, it should then allow you to power it on.

Could you confirm if there was a "Continue" or "OK" button after that specific error message?
Click to expand...
just ok
 
mattyp said:
just ok
Click to expand...

Okay, if you only have an "OK" button, it means the VM creation process is stopping you from proceeding. This indicates a more significant incompatibility than just a warning.

This usually means the .vmdk was created with a feature that Workstation 8.0 simply cannot handle, even if you ignore the "older products" warning.

Here are the most likely scenarios and solutions:

1. The VM was created with a much newer version of VMware: The .vmdk format has evolved. If this VM was created on Workstation 15.x, 16.x, or later, it might be using disk features that Workstation 8.0 doesn't understand at all.
* Solution: Upgrade your VMware Workstation. VMware Workstation Player is free for personal, non-commercial use and is currently at version 17.x. This is the most straightforward solution.

2. The .vmdk is part of a larger appliance that requires specific import steps: Sometimes, .vmdk files are part of an OVF/OVA package. If you only have the .vmdk, it might be missing critical configuration files (.vmx, .nvram, etc.) that define how the VM should be set up.
* Solution: Try to find the original download or appliance package (.ova or .ovf). If you only have the .vmdk, it might not be usable as a standalone VM without the associated configuration files.

3. The .vmdk is corrupted or incomplete: Less likely, but possible.
* Solution: Re-download the VM image if possible.

Given your situation with Workstation 8.0 and the inability to proceed:

I strongly recommend upgrading your VMware software.

  • VMware Workstation Player: Free for personal use. Download the latest version (currently 17.x) from the VMware website. It will be able to open much newer VM formats.
  • VMware Workstation Pro: If you need the advanced features of Pro, you would need to purchase a liсеnsе for a newer version.

Once you have a newer version of VMware installed, try opening the .vmdk file again using the "Open a Virtual Machine" option. If it's a complete VM structure (even if it's just the .vmdk and a .vmx file), the newer VMware should be able to handle it. If it's only the .vmdk and no .vmx, you'll likely need to create a new VM and attach the existing disk, similar to the steps we tried before, but using the newer VMware.
 
downloaded update i now get a message saying
Cannot connect the virtual device ide1:0 because no corresponding device is available on the host.

Do you want to try to connect this virtual device every time you power on the virtual machine?
 
mattyp said:
downloaded update i now get a message saying
Cannot connect the virtual device ide1:0 because no cor...
Click to expand...

This is actually good news — it means the VM is now loading and trying to boot!

This error is harmless. It simply means the VM is configured to use a CD/DVD drive (ide1:0) that is either mapped to an ISO file that doesn't exist on your host, or to a physical CD drive that isn't available.

Just click "No".

This will allow the VM to continue booting without trying to connect a non-existent CD/DVD drive. It won't affect the Subaru SSM4 software at all — the CD drive is not needed for normal operation.

If you want to permanently stop this message from appearing:

  1. After the VM boots (or even before), go to VM > Settings
  2. Find CD/DVD (IDE) in the device list
  3. Either:
    • Uncheck "Connect at power on"
    • Or remove the device entirely by selecting it and clicking Remove
  4. Click OK

Click "No" and let us know if the VM boots up successfully after that.
 
Activity
So far there's no one here

Similar threads

Bin
Subaru Select Monitor - ECU EEPROM IMMO Service Software
Replies
2
Views
2K
Reactions
0
Gemini
Gemini
Bin
ZF Data Management VM - Automotive Software Utility Tool
    • Like
Replies
0
Views
831
Reactions
2
Bin
Bin
Bin
AGCO Service Analyzer - Tractor Diagnostic Software Tool
Replies
2
Views
2K
Reactions
0
Gemini
Gemini
Bin
Volvo Tech Tool Diagnostic VM - Heavy Duty OBD2 Suite
    • Like
2 3 4
Replies
62
Views
10K
Reactions
17
b3liarbts
b3liarbts
Bin
Mitsubishi MUT-III SE - Dealer Level Diagnostic Software
    • Like
    • Love
Replies
19
Views
3K
Reactions
11
shezu
S
Back