VMware Cloud Community
jodykw1982
Enthusiast
Enthusiast

Windows 2008 R2 Slow Mouse After Sysprep

So,

I know installing VMware's WDDM driver in C:\Program Files\Common Files\VMware\Drivers\wddm_video will fix slow mouse problems normally and it does.

I've installed this into a VM and converting this VM to a template, I've deployed other VMs from it.

Every VM that I deploy has the slow mouse problem again.  If I check the Display Adapter in the device manager it is still using the VMware WDDM driver but the mouse cursor is slow again.

I heard uninstalling VMware tools and reinstalling and reinstall WDDM driver will fix the problem.  I don't want to have to do this though.  How can I fix this so when I deploy VMs from my template, the mouse cursor stays quick.

Thanks.

Reply
0 Kudos
35 Replies
MauroBonder
VMware Employee
VMware Employee

check if:

vmware tools is ok ?

hardware acceleration set full ?

set the Video RAM to 32MB ok ?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101170...

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

VMware Tools is OK.  I've tried giving it 32MB for video also.

there is no hardware acceleration that I know of in 2008 R2.... do you know of it?

Reply
0 Kudos
a_p_
Leadership
Leadership

Did you also replace the display driver as mentioned in the KB article Mauro provided (or this one http://kb.vmware.com/kb/1016770)?

André

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

Umm... yeah... as I explained in my original problem.

Reply
0 Kudos
a_p_
Leadership
Leadership

Oops, sorry, I somehow missed this Smiley Wink

André

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

...and what driver are you using for the mouse "VMware Pointing Device"?

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

Hmm, I checked it and it seems to have reverted to "PS/2 Compatible Mouse".  Where is the VMware driver located for pointing device?

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

change it to VMware Pointing Device and I would bet that resolves the problem.  Driver is located at c:\Program Files\VMware\VMware Tools\Drivers\mouse

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

Yeah I just found it and changed it.  It did fix the problem... so now I need to figure out why it reverts back to the default pointing device driver after a sysprep.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

make sure your template is using the VMware Pointing Device as well.  Sysprep should not change these drviers assuming you are deploying off a template with the VMware Tools installed and current.

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

The VMware Pointing Device driver definitely fixes the issue.  I'm using VMware Pointing Device driver before sysprep.  Somewhere in there it is deciding to go back to the standard pointing device which is causing the issue.  I'm investigating it now.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

one thing you may look at on your template is to ensure all "greyed" out hardware is removed.  There may be a hidden mouse driver causing problems.

  1. Click Start, click Run, type cmd.exe, and then press ENTER.
  2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
  3. Type Start DEVMGMT.MSC, and then press ENTER.
  4. Click View, and then click Show Hidden Devices.
  5. Right-click the dimmed device, and then click Uninstall.
Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

This issue is definitely caused by sysprep.  Before I sysprep I am using the VMware Pointing Device driver, after I sysprep, it reverts back to PS/2 Compatible Mouse.

What can be causing this?

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

we have about 100 W2K8 R2 guests in our inventory and have not seen this behavior. We sysprep all of them.  Have you confirmed through device manager there are no hidden drivers for the mouse?  Remember getting to device manager and viewing the hidden devices properly, you must run all the commands listed above from a command prompt.

With that said, we are running 4.1.  What version of ESX(i) are you running?

Reply
0 Kudos
DSTAVERT
Immortal
Immortal

A quick fix could be to export the registry entry and install it during first boot.

-- David -- VMware Communities Moderator
Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

ESXi 4.1 Update 1 & vCenter 4.1.

I didn't see any hidden drivers.

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

Hmm, how would I go about exporting the registry entry and installing on first boot?

Reply
0 Kudos
jasonistre
Contributor
Contributor

I can confirm.   I have the same problem after sysprep of Windows 2008 R2.  ESX Build 381591 if that matters.

sysprep.exe /generalize /unattend:unattend.xml /oobe /reboot

XML is:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:d:\install.wim#Windows Server 2008 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I've just been running a VMtools repair after deployment, but that's annoying.

Reply
0 Kudos
jodykw1982
Enthusiast
Enthusiast

I rebuilt my templates from scratch and the issue has gone away.  The only real difference that I could think of is before I installed any windows patches, I installed SP1 for Server 2K8R2, then I proceeded to install any other patches.

I proceeded to shut the VM down, then converted VM to template.  I've deployed VMs from it and issue is gone.

Reply
0 Kudos