For Polish have too? Problem on Virtualbox are some updates October/November from server 2008. On VMware - forget after install that kb sha 2 what need sha wuc to vista 6003 (bsods). Legacy Update make easy to download MSE, sha wuc make patching what you suggest put that proxy. But finally are destroyed VMs to me. Never mind if core isolation turned off or on. XP - forget too. Legacy Update can't update him to end + MSE don't work. I tested all. I don't know how skip that problems.
Hmmm... After put rollup October on Virtualbox have black screen after reboot and don't go to open Vista. VMware put bsods after use that kb for sha 2 (4474419 if i remember good). And can't go more. With and without core insolations turned in Windows. Interesting when windows 7 want start put in mode server 2008 R2 and come after install newest, go in bsods on VMware, but on vbox work. The same versions use + windows 10 22h2 and windows 11 23/24 h2 on real PC tested for install VMware with vbox. Of course 6 gb ram, nat, dysk sata ssd (vbox) / that logic Scsi (VMware) and 200 gb. Vbox turned off acceleration 3D (bc problems) and VMware with acceleration 3D. I haven't idea.
I got this problem a lot with VirtualBox v7 I had to downgrade to v6 eventually. On v7 64bit host and guest I had to shutdown and then start again instead of restarting the VM. It is not the updates causing it but rather that VBox v7 is kinda incompatible with Vista. 32bit guest flat out refuse to finish installing on v7 as well.
Then understand. What about VMWARE? To me after kb4474419 put bsods and can't skip that. To some people works normally.
8gb ram, 80gb sata drive, 4 cores allocated to vm, 3d acceleration enabled and uefi enabled, with workstation 15.x compatibility mode and vmware tools 11.0.6
Ja też spróbowałem tym 15x but uefi didn't gave, because Vista normally don't support I think (clean original iso used sp2). And that bsods after that kb4474419. About Windows 7, BSODs start after install new updates esu server 2008 R2. So i haven't conceptions on VMware. On Virtualbox only windows 7 still work. So I don't know. Maybe you have nodded iso about something more, what after install make to don't come that things?
I used an original SP2 ISO (en_windows_vista_sp2_x64_dvd_342267), it booted normally in UEFI I didn't have to modify any files or install under BIOS and switch to UEFI. Weird it doesnt work for you. For me, Windows 7 works perfectly fine with the new ESU update. I'm starting to think that your main hardware might be problematic with Windows Vista/7.
Or that turned mitigation hyperv in VMware. I turned disable that and finally machine started work. But on i5 13600kf, 32 gb ram, dysk nvme m2 ssd, rtx4060ti z790 plus d4 shouldn't be problems with vmware. Interesting me xp too how make in vmware. Windows 7 like vista in 15 x configuration?
So I don't know. But VMware workstation pro don't let's me on sata for Vista or 7. Some SCSI let's. Next VMware don't like with kb447419 on vista or with new Esus for windows 7. VMs end with bsods then. When is black screen with options about repair put last good configuration, is something about changed hardware. Like VMware check something in VMs. I understand turned core isolations in Windows 11 or turn off all for use Intel vt-x but still the same. Virtualbox 7x end with only black screen, when on Vista are installed newest patches for server 2008. I tell faster. I checked my hardware. I know i have 13 gen Intel i5 but it is to new for VMware? Or about what is?
Read this: Virtualization applications don't work together with Hyper-V, Device Guard, and Credential Guard: learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Many third-party virtualization applications don't work together with Hyper-V. Affected applications include VMware Workstation and VirtualBox. These applications might not start virtual machines, or they may fall back to a slower, emulated mode. These symptoms are introduced when the Hyper-V Hypervisor is running. Some security solutions are also dependent on the hypervisor, such as: Device Guard; Credential Guard. My two cents.
In VirtualBox, you will see a little turtle in the status bar when HyperV coexistence is engaged. The icon itself is a strong hint to the speed you can expect in this mode.
That I know. But and with totally turned off that things from hyperv like core isolation, etc. I have the same. Me don't know why some anticheats want core isolation on enable. Microsoft should start ban example Vanguard. Because why let's prodecents of games to touch levels protection, where shouldn't have place to be? Or maybe my problems are because windows 11? Something in VMware don't like kb4474419 installed on Vista. Vbox don't like newest Server 2008 patches on Vista. That i mean.
So VMware don't like modifications in systems guests when vbs is active on host Windows 10/11. Next problems, I can't put last update ie from server 2008. And modified newest net 4 for vista from GitHub made by one person from your team won't install to me. Suggestions what more install for work that? General update from December for windows server 2008 success. Only ie and net.
So i found skip. Script net 4 esu + script on IE + net 3.5 repack. But ask general. Will be some fix for windows update soon for any problems later again with updates by Windows Update for Windows Vista/Server 2008 ? Or still will be like that to January 2026 ?
Some reg key what unlock update other microsoft products via windows update for vista/7 ? Bc when unlock wu after some updates is default only for system without that option