instituteoreo.blogg.se - Windows virtual pc windows 7 says it needs to be repaired

#Windows virtual pc windows 7 says it needs to be repaired install#
#Windows virtual pc windows 7 says it needs to be repaired drivers#
#Windows virtual pc windows 7 says it needs to be repaired driver#
#Windows virtual pc windows 7 says it needs to be repaired Patch#

#Windows virtual pc windows 7 says it needs to be repaired Patch#

It is quite unlikely somebody will patch the Virtual PC hypervisor in order to work with Windows 10 圆4, because nobody has really used Virtual PC for years by now, therefore it's hardly worth the effort.

Switch to a host operating system able to run Virtual PC 2007.

Switch to a different VM solution such as VirtualBox or 86Box.

Perhaps if you give some insight as to why you actually need to use Virtual PC 2007, somebody might give a better solution, but right now, there are only two realistic outcomes to this situation: I hate to break it to you, but here is the deal: Virtual PC 2007 is ancient. Any patching would require knowledge of what the calling code in VMM.SYS is doing and if it can even be patched. The situation is as follows: 32-bit Virtual PC 2007 still works on 32-bit Windows 10, but 64-bit Virtual PC 2007 no longer works on 64-bit Windows 10, because, for reasons still unknown, a Windows Kernel API function called by VMM.SYS has swapped the meaning of two registers. And I'm sure somebody by now has decompiled those VPC2007 drivers, so they know how they work.

#Windows virtual pc windows 7 says it needs to be repaired drivers#

Or maybe some 3rd party has made 64bit replacement drivers for VPC2007 that exactly duplicate the behavior of the 32bit drivers that come with VPC2007, so as to enable VPC2007 to run even on 64bit Windows 10? I mean 32bit software can use 64bit drivers, the fact that any 32bit software that runs on Windows 10 proves. 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).

#Windows virtual pc windows 7 says it needs to be repaired driver#

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.

#Windows virtual pc windows 7 says it needs to be repaired install#

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.