Lexia no longer recognized by the laptop

[cit-rotti]

For WIN 7 64 Pro, according to my information, VMware Workstation 15 should be used instead of VMware Workstation 16 Player.

Version 16 is used from WIN 10 64 Bit Pro. I cannot judge whether this may be the problem or whether it is due to incorrect installation steps.

[Cristache39]

For WIN 7 64 Pro, according to my information, VMware Workstation 15 should be used instead of VMware Workstation 16 Player.

Version 16 is used from WIN 10 64 Bit Pro. I cannot judge whether this may be the problem or whether it is due to incorrect installation steps.

I tried again with VMware 15, same issue, interface still not visible. I have tried to install VMware Tools but the launcher is not starting, APPCRASH error. Something happened after I deleted from disk the DiagBox and reinstall it, maybe the virtual machine is corrupted or I don't know. It gives me headaches.

[Cristache39]

So, i made some digging on why the VCI is not recognized by laptop.

To confirm it’s not a driver or OS issue, I:
Used USBDeview to check if the VCI is connecting at the USB level—it’s not detected at all.
Tried on another laptop, and got the same result.

This particular clone VCI uses the MB90F546GS microcontroller, which has mask ROM—meaning the firmware cannot be reflashed or updated safely.

Apparently, DiagBox version 9.91 attempts automatic firmware updates after some time, even without an internet connection. If this update process is interrupted or fails (as likely happens with this MCU), it bricks the device.

Can anyone confirm that DiagBox 9.91 tries to push a firmware update that bricks clone VCIs with MB90F546GS?

I discovered that the seller has recently changed the product description. It used to say the interface supports DiagBox 9.91, but now it only lists compatibility up to 9.168, which might indicate they’re aware of this issue.

[Cristache39]

Also, I have installed today the native version of DiagBox 9.186 which also installed the interface's driver, Actia, but still not recognizable. The led remains on, how I said.

So i guess that the only cause should be the "brick" part?