biowizard's Posts

Thanks to all who are reporting these same issues. Simply, for now, I have reverted to VMWare 16, which is not ideal, and also is a lot slower on Windows 11 than ever it was on Windows 10. Such a s... See more...
Thanks to all who are reporting these same issues. Simply, for now, I have reverted to VMWare 16, which is not ideal, and also is a lot slower on Windows 11 than ever it was on Windows 10. Such a shame - up until now, I have been very impressed with VMWare, both Workstation on the PC and Fusion on the Mac. Now, for the first time, I'm beginning to consider alternative solutions. Please, VMWare, wake up and respond to these issues! Brian
I got 17.0.1 (while I was still on Windows 10 Pro), but reverted to 16.(latest) when the Chess Titans program in my Win 7 VM crashed VMware altogether. Not my most important programme, I know, but th... See more...
I got 17.0.1 (while I was still on Windows 10 Pro), but reverted to 16.(latest) when the Chess Titans program in my Win 7 VM crashed VMware altogether. Not my most important programme, I know, but this told me that WS 17 was not yet ready for prime time. Then I upgraded (just over a week ago) to Windows 11 Pro. After sorting out some initial device driver issues, everything was running smoothly. Everything, that is, apart from my VMs, which not so much ran, but walked. With a limp. Playing around with numerous settings, and scanning the web for solution, the ONE trick that DID appear to work, was disabling the Core Isolation's "Memory Integrity" setting. Switched off, and following a restart, my VMs were very much back up to speed. The obvious question is, am I happy to leave this security feature in Windows 11 Pro disabled, just so my VMs run at full speed? Tricky one, but then again I've survived the past several years running Windows 10 (and before that, WInodws 7), without this particular protection. I just wonder how to stop the warning exclamation mark on the task bar tray if I do decide to turn this feature off permanently ... Brian
Hi Folks, I've also been suffering from a massive slowdown of some of my VMs since upgrading Win 10 Pro to Win 11 Pro. One setting I've found in Windows 11 which DOES seem to restore my former spee... See more...
Hi Folks, I've also been suffering from a massive slowdown of some of my VMs since upgrading Win 10 Pro to Win 11 Pro. One setting I've found in Windows 11 which DOES seem to restore my former speed, is to turn off "Memory Integrity" in the "Core Isolation" page of Windows Security, I am not sure how "safe" this is in terms of Windows 11's own security, but at least it lets Workstation Pro 16 run at full speed once more.
FOUND IT! The "memory integrity" feature of Windows 11 Pro is what is severally knobbling my DOS VM. If I turn this feature off in Win 11 Pro, my VM restores its lightning fast characteristics, mea... See more...
FOUND IT! The "memory integrity" feature of Windows 11 Pro is what is severally knobbling my DOS VM. If I turn this feature off in Win 11 Pro, my VM restores its lightning fast characteristics, meaning I can do substantial systems builds in just a few seconds, rather than minutes. Now obviously I kind of want to keep this safety feature "on" to protect my Windows 11 installation. But is there any way to tweak Workstation Pro 16 so as not to suffer from it?
PS: Just checked, and my Hyper-V subsystem is not currently enabled ...
RDPetruska, Hyper-V sounds intriguing, and I will have to admit to not knowing much about it. Is this something new in Win 11 that was absent from Win 10? Or just a setting that used to be "off", and... See more...
RDPetruska, Hyper-V sounds intriguing, and I will have to admit to not knowing much about it. Is this something new in Win 11 that was absent from Win 10? Or just a setting that used to be "off", and is now "on"? Can it be disabled? And if so, what happens?! Could ask a zillion more silly questions, but let's leave it there for now! Brian
Good thought - but I am only using Microsoft Security Essentials as previously: apart from the OS update to 11 from 10, everything else is exactly as before - apart from the speed of running a couple... See more...
Good thought - but I am only using Microsoft Security Essentials as previously: apart from the OS update to 11 from 10, everything else is exactly as before - apart from the speed of running a couple of my VMs. Nothing else is slower in Win 11 Pro than it was in Win 10 Pro. In fact, many things are faster thanks to the recently recreated (and I guess de-garbaged) registry! Something else is going on, something that VMware is doing in WIn 11, that it was not in Win 10.
Same computer, Same VM, Same everything except that I decided to update my PC from WIndows 10 Pro to WIndows 11 Pro. Everything seemed to work OK after initial teething troubles (device drivers for l... See more...
Same computer, Same VM, Same everything except that I decided to update my PC from WIndows 10 Pro to WIndows 11 Pro. Everything seemed to work OK after initial teething troubles (device drivers for legacy hardware, etc), but one nasty side effect, is that at least one of my formerly blisteringly fast VMs is now crawling. Is there some setting in Windows 11 that I can apply, which will enable Workstation 16 Pro to restore its former performance? Alas, for now, Workstation 17 (even if it fixed this issue) is not an option, as it breaks one of my other VMs (already reported).
Nobody else had any experiences like this in Workstation 17? Just wondering ... Brian
Yesterday I purchased my Workstation Pro 17 / Fusion Pro 13 serial number, and set about installing the former on my WIndows 10 22H2 PC. Installation when smoothly, and after some some jiggery pokery... See more...
Yesterday I purchased my Workstation Pro 17 / Fusion Pro 13 serial number, and set about installing the former on my WIndows 10 22H2 PC. Installation when smoothly, and after some some jiggery pokery with shared folders, I had my most important VMs up and running smoothly. Or so I thought. In testing Windows 7 (32-bit), which I use as part of my workflow for legacy applications, and to pass files to/from my MS-DOS 8 VM, I decided to run my favourite pass-the-time game, Chess Titans. OOPS! Bang, crash, I dialog popped up which I tried to capture with "Print Screen", but could not paste into my Windows 10 environment; the last items on the VMWARE,LOG file before a message about how to contact support, are shown below. While Chess Titans isn't the be-all and end-all of my VM life, the total (and repeatable) collapse of this application left my VM in a bit of a mess (luckily, I had a recent backup), and in short, for now, I have reverted to Workstation Pro 16. Who/which dept at VMware would be the best person to send the entire logfile to? 2023-02-11T00:28:11.543Z Wa(03) mks Win32 object usage: GDI 7, USER 20 2023-02-11T00:28:11.543Z In(05) mks Writing monitor `vmmcores.gz` 2023-02-11T00:28:11.549Z Wa(03) mks Dumping core for vcpu-0 2023-02-11T00:28:11.549Z In(05) mks Beginning monitor coredump 2023-02-11T00:28:11.633Z In(05) mks CoreDump error: Read, page 0xa00 (0x8523ff) Invalid access to memory location 2023-02-11T00:28:11.633Z In(05) mks CoreDump error: Read, page 0xa01 (0x21aefe) Invalid access to memory location 2023-02-11T00:28:11.642Z In(05) mks CoreDump error: Read, page 0xb34 (0) Invalid access to memory location 2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb35 (0) Invalid access to memory location 2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb36 (0) Invalid access to memory location 2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb37 (0) Invalid access to memory location 2023-02-11T00:28:11.857Z In(05) mks End monitor coredump 2023-02-11T00:28:12.857Z In(05) mks Msg_Post: Error 2023-02-11T00:28:12.857Z In(05) mks [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (mks) 2023-02-11T00:28:12.857Z In(05)+ mks ISBRendererComm: Lost connection to mksSandbox (3093)
Thanks @Technogeezer, I'll check that out in due course!
Happy to report that I now have Workstation Pro 17 up and running, with my new Fusion Pro 13 serial number! The only bummer is that Fusion 13 won't run on my 2012 MacBook Pro, so I'm stuck with Fusi... See more...
Happy to report that I now have Workstation Pro 17 up and running, with my new Fusion Pro 13 serial number! The only bummer is that Fusion 13 won't run on my 2012 MacBook Pro, so I'm stuck with Fusion Pro 12 on that. Never mind, I do have a 2021 M1 MacBook Pro, so will install on that instead and then attempt to get the ARM version of Windows 11 up and running! This could be "fun" ... Thanks to all - a happy bunny here!
Happy to report that Workstation Pro 17 is running all of my VMs perfectly. Thanks for the help and advice!
I guess I just came across my method by trial and error, some 8-9 years ago, after getting my first Mac, setting up Fusion, and then wondering how to get files in and out of my DOS VM. One of my firs... See more...
I guess I just came across my method by trial and error, some 8-9 years ago, after getting my first Mac, setting up Fusion, and then wondering how to get files in and out of my DOS VM. One of my first ever posts on this community was to ask for help and advice for how to connect the DOS VM to the outside world!
Thank you so much for the clarification. Based on that, I think I will pony up for the upgrade. It will be good to be able to run Windows 11 in a VM, including (potentially) on my newer M1 MacBook P... See more...
Thank you so much for the clarification. Based on that, I think I will pony up for the upgrade. It will be good to be able to run Windows 11 in a VM, including (potentially) on my newer M1 MacBook Pro - even if the latter machine will most certainly NOT run MS-DOS! Best, Brian
Thank you for that information! I've been trying to ascertain this for several days, searching in vain over the vmware website! Best, Brian
Thank you very much for that response. Yes, I do rely on connecting my DOS VM (actually DOS 8, the non-Windows part of Windows 98SE) to a separate FAT32 formatted virtual disk which is shared with a ... See more...
Thank you very much for that response. Yes, I do rely on connecting my DOS VM (actually DOS 8, the non-Windows part of Windows 98SE) to a separate FAT32 formatted virtual disk which is shared with a Windows 7 VM; it's my long-winded way of getting files in and out of the DOS world! If this will no longer work with Workstation Pro 17, I'd better stop upgrading right here! Brian EDIT: Just re-reading your response, and my message above, maybe I've misunderstood something. I don't every try to mount my VM MS-DOS "C:" drive in another VM, but what I do do, is have a separate FAT32 drive, which appears as "D:" in my MS-DOS VM, and as "E:" in my various Windows VMs. I can't run any two versions of Windows at once, nor Windows and MS-DOS simultaneously, because of the potential for double-updates and other sharing conflicts on this additional virtual drive, but what I can do is copy files to and from it in either DOS or Windows, then shut down, and run the other OS, to retrieve the files. It might be a bit long-winded, but I only typically have to do this once per week or so. So supplementary question: do you know whether this method of exchanging files between MS-DOS and the outside world, might still work?
I am running an essential legacy DOS VM both in Fusion 12 and in Workstation 16; these are critical to one of my long-term workflows. Before I try upgrading to versions 13 and 17 respectively, does ... See more...
I am running an essential legacy DOS VM both in Fusion 12 and in Workstation 16; these are critical to one of my long-term workflows. Before I try upgrading to versions 13 and 17 respectively, does anyone know whether these VMs will still work? Brian
With Fusion Pro 12 and Workstation Pro 16, I was able to install Fusion on my Mac and Workstation on my PC for the purchase of just one, single serial number which they shared. Is the same true of F... See more...
With Fusion Pro 12 and Workstation Pro 16, I was able to install Fusion on my Mac and Workstation on my PC for the purchase of just one, single serial number which they shared. Is the same true of Fusion Pro 13 and Workstation Pro 17? I can't seem to find the licence agreement anywhere on the VMWARE website.
I just tried updating from Mac Fusion 7.1.1 to 7.1.2. The download seemed to work, but when the files we checked for validation, the VM Core file was found to be corrupt, and the update aborte... See more...
I just tried updating from Mac Fusion 7.1.1 to 7.1.2. The download seemed to work, but when the files we checked for validation, the VM Core file was found to be corrupt, and the update aborted. So I decided to try again - only this time, Fusion did not attempt to do any downloading: instead, it simply tried to validate and expand the previously downloaded update files. The VM Core update once again reported as corrupted, and the update aborted. I've tried rewinding to a backup version of Fusion using Time Machine, but even then, the update finds and tries to open the existing download files, including the corrupted VM Core, The BIG question is this: How do I force a fresh download of the corrupted VM Core Update file? I don't even know where to find the file, so I can manually delete it. Help, please, anyone! Thanks in advance, Brian