Tuesday, January 24, 2017

Windows Movie Maker 2012 fails to launch on VMware Horizon View Windows 7 virtual desktop

Problem

You’ve downloaded Windows Essential 2012 and installed Windows Movie Maker 2012 on a Windows 7 desktop fails to launch and displays the following error message:

Sorry, Movie Maker can’t start. Make sure your computer meetings the minimum system requirements before trying to start Movie Maker again, and then try to update the driver for your video card if Movie Maker still doesn’t start.

clip_image002[13]

Searching through the internet leads you to the following Microsoft KB:

You cannot start Windows Movie Maker 2012 when a graphics card that only supports DirectX 9 is installed on a Windows 7 or Windows Server 2008 R2-based computer
https://support.microsoft.com/en-us/help/2741355/you-cannot-start-windows-movie-maker-2012-when-a-graphics-card-that-only-supports-directx-9-is-installed-on-a-windows-7-or-windows-server-2008-r2-based-computer

… but attempting to install the update displays the following message:

The update is not applicable to your computer.

clip_image002[11]

Downloading other video editing applications such as Shotcut also fails to launch indicating the video card does not support OpenGL.

You attempt to try and install Windows Live Essentials 2011 that supports DirectX 9 but receive the following error message during the install:

Couldn’t set up the installer

Check to be sure you are connected to the Internet

You cannot download Windows Live programs unless you’re connected to the Internet.

Error: 0x8104000d

Source: WaitForCatalog

image

Solution

In order to get the Windows 7 virtual desktop to successfully launch Windows Movie Maker, 3D support needs to enabled as shown in the following virtual machine properties:

Video card

3D graphics

Enable 3D support

image

It is important to note that VMware Horizon View desktops cannot be simply powered off and have the Video Card settings configured because if the pool properties are not configured to enable 3D then the settings of the virtual desktop would eventually be reverted back.

Proceed by logging onto the View administration console, open the desktop pool properties, navigate to the Remote Display Protocol tab and review the following settings:

Default display protocol: PCoIP

Allow users to choose protocol: Yes

3D Renderer: Disabled

If the Allow users to choose protocol setting is configured as Yes then 3D support would be disabled:

image

In order to enable 3D support, we’ll need to ensure that the following settings are configured:

Remote Display Protocol

Default display protocol: PCoIP

Allow users to choose protocol: No

With the Allow users to choose protocol configured as No, we will now be change to change the 3D Renderer setting:

image

Proceed and change the settings to the following:

Remote Display Protocol

Default display protocol: PCoIP

Allow users to choose protocol: No

3D Renderer: Automatic

image

The VRAM size can be adjusted from the default if required:

VRAM Size: 96MB

image

The last important step is to completely shut off the desktop so that View would send the commands to vCenter to reconfigure the VM.  A simple restart or reset of the virtual desktop will not change the configuration so make sure you initiate a full guest shutdown.  Once 3D support is enabled, both Windows Movie Maker (DirectX 11) and Shotcut (OpenGL) would now launch:

clip_image002[4]

clip_image002[6]

clip_image002

No comments: