![]() Vmm.sys is required to run VPC2007 anyway and there's no updated version of it, not even the more modern one from the SDK 7.1 runs (from 2012-2013 or so). If anybody here can help me with this, it would be great.Īctually, it's the vmm.sys driver (in vpc2007 for 圆4) in Win10 圆4 that causes the bsod, vmm.sys for x86 is alright but you can't run it on 圆4 Windows 10. Is there some kind of trick to this? Some kind of unofficial driver fix I could install to make MSVPC2007 run again, even in Windows 10? I really would like to run MSVPC2007 again, but don't want to have to downgrade the OS on my computer or run VPC2007 on an older OS inside Oracle VirtualBox (what's the point of running a virtual machine inside of a virtual machine?). Important stuff that the OS needs to read and write is probably in completely different places now than it was before, so when drivers write to what they think is the correct location, and it's not the correct location, it ends up corrupting the OS in memory, forcing Windows to do a BSoD and then reboot. I'm not sure, but I'm guessing that the issue is that the driver accesses kernel memory (the layout of memory for the OS itself), and the layout is probably much different now than it was when MSVPC2007 was released. I figured it probably was that there was a driver that it installed that was incompatible with the current version of Windows. It gave me a BSoD, something VERY RARE in Windows 10. So after that I was able to install MS Virtual PC 2007. I carefully blanked out that entry with 0x00 bytes (not removing the bytes from the file as that would change the offsets for other entries and corrupt the file, which could cause other issues). I bypassed this by hex editing one of the files Windows uses to determine the compatibility of various software (and blocks installation of known incompatible software). It says it's not compatible with the current version of Windows. Unfortunately it won't even install in Windows 10. I have Virtual PC 2007, the last version made by Microsoft. If you have any applications that use or create VMs or system images, you might need to update or uninstall them to remove this safeguard hold.Here's my situation. Important If you do not have VirtualBox installed but are receiving this safeguard hold, you might have an application that is based on VirtualBox, or which has bundled VirtualBox within their installation. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 21H2 is offered. ![]() To remove the safeguard hold on your device, you will need to update to VirtualBox 6.1.28 or a later version. Oracle has resolved this issue in VirtualBox 6.1.28 and later versions. If you no longer use VirtualBox, uninstalling it should also mitigate the safeguard. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. You can check Oracle's progress by monitoring their ticket #20536. ![]() To mitigate the safeguard, you have to remove Hyper-V or Windows Hypervisor temporarily until this issue is fixed with an update Oracle plans to release in October 2021. To safeguard your upgrade experience, we have applied a compatibility hold on these devices from installing or being offered Windows 11. When Hyper-V or Windows Hypervisor is installed, you might be unable to start virtual machines (VMs) and you might receive the message. Microsoft and Oracle have found a compatibility issue between VirtualBox and Windows 11. Click Learn More for information on how to update this app. Your PC requires the latest version of this app. When you try to upgrade to Windows 11, you might encounter an upgrade compatibility hold and receive the following message: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |