Win3x.Org

About registry editions: did you really follow ALL the instructions I provided, except the KB2908279 installation of course (already installed on your system, by the KB2903939 rollup)?

I mean these steps :

Big Monstro a écrit : *

11 sept. 2015 16:50

2) By default, that patch takes effect only on some popular games but Microsoft explains how to add another program on the list. You guess that's the procedure to resolve the annoying bug on Microsoft Virtual PC 2007. Firstly, run Registry Editor (regedit.exe). Ignore the UAC if warning.

3) Go to the following key

Code : Tout sélectionner HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags

and display the content of « Layers ». If the key doesn't exist, create it.

4) Inside the « Layers » key, create a new string value. For its name, specify the complete address of Microsoft Virtual PC 2007 executable file. For example, if the host operating system is Windows 8 64-bit and it's installed on C: drive, the value name should look like this:

C:\Program Files (x86)\Microsoft Virtual PC\Virtual PC.exe

The exact address depends on the configuration of your computer! You must take into account the actual name of executable file.

5) In addition to name, you have to modify the data of that string value. Enter NoDTToDITMouseBatch

6) It isn't over! Open a command prompt with administrators permissions and run the following command:

Code : Tout sélectionner Rundll32 apphelp.dll,ShimFlushCache

7) Reboot the computer. Now, the mouse cursor normally behaves inside all virtual machines

Posted: 05 Aug 2017 12:54

Yes, I did follow the instructions carefully.

In the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers registry key, I put C:\VPC\VPC.EXE in the value name where I installed Virtual PC and added NoDTToDITMouseBatch string value.

The reason why I renamed the executable, "Virtual PC.exe" to "VPC.EXE" is due to compatibility issues with Windows 8.1.

I did apply the KB2903939 patch, but it still didn't solve the mouse stuttering issue when capturing the mouse cursor inside the windowed VM on the secondary monitor.

----
Posted: 15 Aug 2017 05:46

Okay, this does not seem to be a issue with the second monitor, but more of a text and item resizing issue.

If I set the screen resolution on my second monitor to either 1280 x 1024 or 1600 x 900, the mouse inside the virtual machine's guest operating system does not stutter.

However, if I set the screen resolution to either 1600 x 1024 or 1600 x 1200, the mouse stutters!

But I found another way and I solved the problem! How I did it?

1. Go to Control Panel, select Appearance and Personalization and go to Display.

2. Click on where it says, "Make text and other items larger or smaller".

3. You will see the section that says, "Change the size of all items", click on Smaller - 100% (default) and check mark "Let me choose one scaling level for all my displays". When you're done, click on Apply.

You will need to sign-out of your local account or Microsoft account in order for the changes to take effect.

I hope that this solves the mouse stuttering problem!

I am glad to find this forum. I used Virtual PC 2007 (sp1 with hotfix) on Windows 7 (as a host) about a year ago with Windows 98SE and Windows XP (as gests). During the time I made many instals and uninstals on Windows 7. Now I want to try some things in the Virtual Windows Xp. For my surprise the Virtual PC 2007 do not see my physical network card. It offers only "Not Connected", "Local" and "NAT". What can I do to see the card? I tried to uninstall and reinstall Virtual PC 2007 but it does not help.

Hello sorbit4 and welcome to Win3x.Org.

It sounds like you have the problem normally associated to Windows 8.1, after applying the rollup for Virtual PC 2007 SP1. It seems Windows 7 could be affected by the same issue (probably due to some recent system updates)

If you uninstall Virtual PC and reinstalling it without the rollup, do you still encounter the same bug? If you want to enjoy the improvements offered by the rollup (faster NAT and higher resolutions), you can follow the guidelines intended for Windows 8.1.

Best regards,
Big Monstro

Thank you for the answer. Your advice did not help me. But I found a solution by trying many things. The solution was that first I removed the Virtual Machine Network Services form the card connection properties in the host (Windows 7). Then in the Device Manager appeared a Virtual Machine Network Services driver with a sign that it is not correctly installed. I removed it with complet delete. After that I add the Virtual Machine Network Services to the card connection properties from the Program Files\Microsoft Virtual PC\Utilities\VMNetSrv directory. It installed and after these steps the card appeared again in the Virtual PC settings. And it works.
Between every steps I rebooted the PC.

I successfully installed Virtual PC 2007 in a windows 10 x64bit but an error once I run the application "Virtual PC could not open the Virtual Network Services driver". I also tried to check the Virtual Machine Network in my LAN and it is not available so I tried to install it manually but it fails without any error. Any advise???

What's the version of vmm.sys that you used ?

I have tried the same procedure for Windows 10, 64-bit, but it's not launching even after replacing the old vmm.sys file with a new one. Does anyone know what might be the issue ?

To my knowledge, nobody has ever reported to run successfully Microsoft Virtual PC on Windows 10 64-bit. Apart from downgrading the host to Windows 10 32-bit (or to a previous version of Windows, 32-bit or 64-bit), your only option would be to install another program such as VMware or VirtualBox, then install an older Windows (from 2000 to 8.1) as guest and, finally, install Microsoft Virtual PC (2004/2007) inside the virtual machine.

That might just work but I'm trying to compare the performance of the type-II hypervisors for a project, and there seems to be only 5, out of which Microsoft Server is no where to be found, I've got the numbers from Virtualbox and workstation 15, and I'll be done with KVM too, but Virtual PC is holding me back and doing what you told me would most possibly defeat the purpose, like it needs the same hardware resources for an accurate report.
Anyways thank you for the advice !