If I boot a VMware VM to the rescue media (Windows Boot Menu), the mouse it pretty much useless.  I just moves all over the screen.  I tried adding the VMware mouse drivers to the "C:\Boot\macrium\WinREDrivers\64Bit\Mouse\VMware" folder and it sees new drivers and asks me to rebuild the rescue media.  However, when I boot again, its the same results.

Does anyone know how to successfully add VMware mouse drivers to the rescue media?  Without a working mouse, the rescue media is pretty much useless in a VMware environment (6.7).
Thanks
NK

What version is your WinRE environment running? Have you experimented to see if this occurs on other environments, like WinPE 10 1709, which is used when you select PE 10? Given that WinRE on your system may use a different kernel and that WinRE environments on PCs are customized per PC, this could be an issue with a specific kernel version and/or something caused by something specific to the WinRE environment on your system. WinPE 10 does not get modified before Reflect touches it, so it may be worth trying.

+x

 

jphughan - 22 May 2021 12:31 PM

What version is your WinRE environment running? Have you experimented to see if this occurs on other environments, like WinPE 10 1709, which is used when you select PE 10? Given that WinRE on your system may use a different kernel and that WinRE environments on PCs are customized per PC, this could be an issue with a specific kernel version and/or something caused by something specific to the WinRE environment on your system. WinPE 10 does not get modified before Reflect touches it, so it may be worth trying.

Yeah, using Windows RE 10 1809 (from Windows Server 2019).  I will give WinPE a try instead to see if that works better.  Thanks for the suggestion.

NK

Same issue.  I tried both just the default drivers and then adding the VMware mouse drivers - both failed.  When the PE environment loads, I can see in the splash screen it loading the drivers and can see mouse drivers being loaded.  But for whatever reason, those drivers have no affect on fixing the problem.  I think this used to work with the old Windows vSphere client - and it seems like now that we upgraded to vCenter 6.7 and we have to use the web client, it is now broken.  But I could be wrong.

NK

Ah ok, I somehow missed that you were using VMware ESX and therefore connecting through a web-based console.  I thought you were using VMware Workstation.  I think it was ESX 5.5 that marked the "fat" client as deprecated and said all new features would be implemented exclusively in the HTML5 client, but maybe a newer release removed the former entirely?  But if you're using the Web client, have you experimented with different browsers, specifically having tried both a Gecko-based browser (Firefox) and a Chromium-based browser (Google Chrome, the new Edge Chromium, etc.)?

+x

 

jphughan - 23 May 2021 3:17 AM

Ah ok, I somehow missed that you were using VMware ESX and therefore connecting through a web-based console.  I thought you were using VMware Workstation.  I think it was ESX 5.5 that marked the "fat" client as deprecated and said all new features would be implemented exclusively in the HTML5 client, but maybe a newer release removed the former entirely?  But if you're using the Web client, have you experimented with different browsers, specifically having tried both a Gecko-based browser (Firefox) and a Chromium-based browser (Google Chrome, the new Edge Chromium, etc.)?

I am using Chrome.  I will do some experimentation with other browsers.  Thanks.

NK