knmdk's Posts

Quick follow-up: For some reason the Quake folder that is present in uploaded faulty VM is corrupt (it reports PAK0.PAK error at startup and byte size is 1 byte off). Please use the Quake ZIP I attached yesterday to investigate the issue (or AutoCAD 2023.1.3, which is easier). I tested the faulty VM that I have uploaded yesterday (created by VMware Workstation Pro 16.1.0, VMware Tools is 12.2.0) in VMware Workstation Pro 17.0.0. The Quake game starts (the one that is attached to this post) and the framerate is not ~10 fps but ~30 fps. Still way lower than ~300 fps when run in VM created in VMware Workstation Pro 17 natively. AutoCAD 2023.1.3 does crash (when manipulating any 3D object, i.e. simplest box) without any error dialog, VMware Workstation Pro continues to run after AutoCAD crashes. VM (guest and host OS is Windows 10, version 21H2, 3D accelerated with 2 GB of VRAM) created from scratch in VMware Workstation 17.0.0 and VMware Tools 12.2.0 performs fine, great framerate in Quake (~300 fps in 2560×1600), great performance and no crashes in AutoCAD 2023.1.3. I have also stumbled upon an ongoing thread regarding ISBRendererComm regression in VMware Workstation Pro 16 that leads to crash similar to the one I experienced with Quake. It appears to me that my initial claim regarding recent AutoCAD version may be connected to this issue in some way despite the absence of error dialog box. I will be upgrading to VMware Workstation Pro 17.0.0 since it appears to be working fine with my computer. It looks like this is the only option for now. Maybe that is in some way related to my laptop's GPU that was released in summer of 2020 and sports RDNA1 architecture. I'm happy I didn't roll out VMware Workstation Pro 16 to the production environment! Please let me know if there's something I can do to help you get this issue sorted.

@shibdas wrote: I filed a bug but so far we have not been able to hit the crash. We are running the AutoCAD 2023 cert suite. Is there a specific model for which this happens? if you run the AutoCAD cer suite do you see the crash? Hey shibdas & mjkrol, thanks for attention to my report. TL;DR After extensive testing it appears there's some problem with  the way VMware Workstation Pro 16.1.0 creates and runs VMs and it's not related to AutoCAD 2022/2023. VMware Workstation Pro 17.0.0 doesn't have this kind of problem if the VM is created in VM Workstation Pro 17.0.0 (and not imported from earlier versions). See, I downloaded a vanilla AutoCAD 2023 and standalone update to 2023.1.3 (as you suggested), installed both to brand new VMware Workstation Pro 17.0.0 VM with 2 GB VRAM created from en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.iso, and applied VMware Tools 12.2.0. And the FATAL CRASH doesn't happen when 3D objects are called/view rotated, etc.! The interesting thing is for some reason this way AutoCAD does initiate DirectX 11 mode by itself, so no Software mode triggered by AutoCAD 2023.1.3 in virtual environment by default. However when I do exactly the same with VMware Workstation Pro 16.1.0 VM the crash happens. But wait, there's more. I have tried free QuakeSpasm-Spiked 0.94 in 2560×1600 in both versions of VMware Workstation Pro 16.1.0 and 17.0.0 with VMware Tools 12.2.0 using newly created VM with the same specs each time (2 GB VRAM, 1 CPU with 8 cores, 4 GB RAM) and same Windows 10, version 21H2 guest ISO. And here's what I found: - VMware Workstation Pro 17.0.0 provides ~300 fps, game starts with game config file imported directly from a real hardware machine (which runs at 600+ fps), no crashes - VMware Workstation Pro 16.1.0 provides ~10 fps, game does not start at all with game config file imported directly from a real hardware machine, however if no config file is preset game can be started and performance is ~10 fps, almost not playable. I then took VM folder created with VMware Workstation Pro 17, edited VMX virtualHW.version from "20" to "18" so VMware Workstation Pro 16 would accept the "downgraded" VM. Uninstalled VMware Workstation Pro 17, reinstalled VMware Workstation Pro 16.1.0 once again. Imported "downgraded" VM with edited VMX. VM started, however the game will crash just as in VM that was created with VMware Workstation Pro 16 from scratch. I then reinstalled VMware Workstation Pro 17, took an unedited VM created with VMware Workstation Pro 16.1.0 and imported it to VMware Workstation Pro 17 (without editing VMX virtualHW.version), game started but the FPS is again at ~10! Unfortunately I forgot to test if "upgrading" virtualHW.version of VM created with VMware Workstation Pro 16 from 18 to 20 actually fixes the VMWP16-created VM to run as expected in VMWP17. I will try to test this too. All this makes me believe there's something wrong with VMware Workstation Pro 16, maybe specifically with my laptop configuration. I'm attaching the game in ZIP too (wit my config files as well, no installation required, just unzip and run EXE), or you can download it yourself from official website for security reasons (and use pak0.pak file from my archive since it's actually maps and models file as I understand it). I believe this crash may be connected to AutoCAD crash so it may be quicker to troubleshoot using lighter process (AutoCAD installation takes ages).  I attach both logs of crash of both VMs (one natively created in VMWP16, other one created in VVMWP17 and manually downgraded to work with VMWP16) when executed in VMware Workstation Pro 16. It may be also worth a look into those logs because the new error window appeared, previously unseen in AutoCAD crash. This window says: VMware Workstation urecoverable error: (mks) ISBRendererComm: Lost connection to mksSandbox A log file is available in: You can request support. To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu. You can also run the vm-support script in the Workstation folder directly. We will respond on the basis of your support entitlement. I actually did use Help menu but it never saved the ZIP file with Support Data. So I just ZIP logs and attach to my message here (date may be off in LOG files). Oh, I know I could use Blender to test everything instead of some Quake game but I actually accidentally tried it and I'm quite exhausted from all that testing.  @mjkrol wrote: I'm trying to reproduce the crash with AutoCAD 2024 but no luck so far. Since I'm not familiar with AutoCAD, I'm probably doing something wrong. Can you provide baby-steps after AutoCAD is launched that reproduce the crash? Hey mjkrol, sure, I attach Baby Steps ZIP file with all the steps I took up to crash, all other settings are default. Here's a link to download entire faulty VM that gets created by VMWP16 — … Please use 7-Zip to unpack (8.7 GB unpacked size). Basically it's the VM what was created for Baby Steps sequence.

Hey shibdas, I've been testing using VMware Workstation Pro 17 trial the whole weekend. The problem persists and the FATAL ERROR crash happens in AutoCAD 2022, 2023, 2024 with VMware Tools 12.2.0 on a real hardware and fresh Windows 10 version 21H2 virtual machines. Please have a look into this or elevate this report to engineers.

Hey shibdas, I tested both AutoCAD 2022 and 2023 on a real hardware of the host system in DirectX 12 and DirectX 11 modes (11 triggered via command in AutoCAD). Everything runs fine. It appears like something's wrong with VMware Workstation Pro 16.1.0 or VMware Tools 12.2.0, or Autodesk implemented some limitation to prohibit running software in virtual environment (can't think of a reason). Both AutoCAD 2022 and 2023 behave (crash) exactly the same in VM.

Hey shibdas, thank you for stopping by! I have deleted old LOG files and run VM to the crash point and soft turn off. I attach these "fresh" LOG files to this message as well as AutoCAD 2022 dump files provided by AutoCAD crash helper. The XML in dump archive contains some data about virtual GPU driver and invoked operation (I invoked model view rotate command in 2D Wireframe view with a basic 3D Box object, crash happened immediately at 09:02:50 AM @ host time), unfortunately I don't have the means to read DMP file. Please allow me some time to install the program onto real hardware and report if DirectX 11 mode works correctly (DirectX 12 mode works fine with my DirectX 12 capable GPU). P.S. Please read some data saying Civil 3D as AutoCAD. Civil 3D is essentially just a profile with additional libraries applied over regular AutoCAD. You can run Civil 3D branded product as regular AutoCAD, it just won't load additional DLLs. What I'm trying to say is the product name is irrelevant in this case.

Darius Davis wrote: Hi knmdk, Sorry for the frustration.  It is an extremely unfortunate set of circumstances that has left us with no proper resolution for this problem at this time.  I assure you that we have not been sitting on our hands with this issue. You should be able to download Fusion 5.0.1 by logging into My VMware, going into Downloads, finding the "Download Fusion 5.0" page (you should end up on this page which will only list Fusion 5.0.2), clicking View Download, and towards the top of the download page you should be able to choose Version 5.0.1 or Version 5.0.0. Hope this helps! -- Darius Thanks, Darius. I've found the correct link. Hope it helps.

royfox wrote: UPDATE: I can confirm by installing the 5.01 over the top of the 5.02 it seems to have sorted my problem for now. Hi all, I'm running OSX 10.8.2 (12C3012) with Windows 8 and have now started to be effected by this issue. Its strange as it's been working fine for about 2 weeks, only really started today but have already lost a lot of work becasue of the three crashes I've had today alone. I did save the full report to my desktop before closing. If these are any good to send to the support.. I do find the support side of VMware to be lacking. It's not easy to create report requests etc. Just to re iterate: Running a mac book pro 2.6ghz i7 core 16gb 1600MHz DDR3 Software 10.8.2 (12C3012) VMWare 5.0.2 (900491) Windows 8 pro I've downloaded the 5.01 install file, could anyone advise if I simply install over the top of 5.02 or do i have to do a fresh install and then move the vmware profile? Joachim_Neudert wrote: Hello Darius, thank you for your confirmation. Meanwhile I have downgraded to 5.01 and can work flawless again. No I'm looking forward to a new version of VMWare. It gave me a hard time yesterday, it happened on my "production system", I am a cardiologist and have many medical demos to show to my patients. I then transcoded the embedded videos to Quicktime and showed the videos under a OSX environment in Keynote. Kind regards Joachim Where do I download 5.0.1 DMG? I only get 5.0.2 in downloads section. Do I have to get it on torrents now? Help me out please!

Darius Davis wrote: Hi RadicalRich, If you are running a mid-2012 MacBook Pro with the latest Apple  updates, you'll likely encounter crashes unless you disable 3D  graphics: With your VM powered off, go into the Virtual Machine > Settings, then choose Display, and turn off the Accelerate 3D Graphics option.  If you only run Windows VMs, you also have the option of  reverting to Fusion 5.0.1. We're busily investigating the issue, which only arose with the release of Apple's MacBook Air and MacBook Pro Update 2.0 late last week.  Sorry for the trouble! -- Darius Are you kidding us? It's been one month since the issue and yesterday I accidentally updated to 5.0.2. So what do you think I get now?! Crash on startup! So you're lying you've been investigating issue. Where do I download 5.0.1 to downgrade? It isn't listed in downloads anymore. VMware Fusion has worst support I've ever seen in my entire life. Thanks.

Just try it. The most terrible thing that can happen is VMware Fusion will quit/freeze. I'm also sure you should provide some more information regrading the software you're running inside guest OS. It may happen you experience performance issues not because of lack of RAM/CPU but because of outdated graphics driver used by VMware Fusion. You can see search for my thread with video on that particular issue (still not resoluted).

Well after further investigation I've figured out fixes for some of the issues mentioned in first post. 1. Magic Mouse gestsures still work in fullscreen Windows 7. So I've setup mouse to show Mission Control with double-tap of two fingers. However still no way to call up Launchpad while in Windows 7 (fullscreen or windowed). 2. Eventually it fixed itself on it's own. Probably it should've taken some time and some restarts (or "hard" shut downs) to get it working right. Today "Ctrl+Primary mouse button" works as it should when selecting multiple items in Explorer. 3. I've found a most recent release of Punto Switcher (1.2.1) has a feature to assign any keyboard shortcut to input language switching in OS X. I've set it to use Ctrl+Shift for switching keyboard layout. So far it works alright with OS X 10.8.1. Just had to tweak menubar icon so it isn't blurry on Retina display. Issues 4, 5, 6 still to be answered.