Software: Windows Live Movie Maker
Current releases of vSpace Server include a set of features that can be enabled through the registry that resolve most compatibility issues a user may potentially experience when using Windows Live Movie Maker within a vSpace environment. Below are steps for enabling these features.
NOTE: The following steps involve editing the system's registry. This task should only be undertaken by authorized computer administrators as a mistake during this process could have adverse affects on the system in question.
- From the host computer, as an admin, open the registry editor. This can be accomplished in most versions of Windows by clicking the Windows Start button, then typing "regedit" (without the quotes) in the Run field.
- Navigate to HKEY Local Machine > System > CurrentControlSet > Control > Multiuser
- Create a new DWORD entry called Force32BitColor and set its Value = 1
If there are connected sessions using display resolutions of 1366 x 768 or higher, the following key must also be added:
- Return to HKEY Local Machine > System > CurrentControlSet > Control > Multiuser
- Create a new DWORD entry called Big32BitFB and set its Value = 1
Close the registry editor to complete the process.
Additional Notes
- Older versions of vSpace Server 6 do not include this feature. Be sure that you are running vSpace Server 6.6.7.4 or newer before attempting to enable this feature.
- Windows Live Movie Maker requires a DirectX compatible graphics card or GPU (whether it is a discrete card or an integrated chip on the motherboard). For this reason, Windows Live Movie Maker may not function in VM environments.
- Note that while this solution was specifically engineered for Windows Live Movie Maker, it may resolve compatibility issues with other similar applications, or applications that can only operate in 32bit color mode.
Article ID: 424
Related Articles
Windows 10 High CPU issue Addressed continued (2 of 4)
roduct Line: VERDE Method 1 – Group Policy Editor Method 2 – Registry Editor There's a service that continuously runs that you should consider disabling. Windows Telemetry. To do so: Method 1 – Group Policy Editor 1) On your keyboard, press ...
What are the Windows OS and software requirements for using the UXP Turbo protocol in a vSpace virtualization session?
The ‘UXP Turbo’ protocol enhances desktop delivery for multimedia-intensive tasks, such as smooth browser scrolling, video playback, and improved performance in multimedia applications. It is supported on vSpace Pro Enterprise running the following ...
Windows: How to enable specific software access for user accounts
If you may want to protect files and folders or limit access to some programs by users permanently or for a time period, you may be able to achieve this using Group Policies and Domain Policies. there is are Solutions: One example of a third ...
Installing vSpace from the Windows Command Line
These older versions of vSpace are no longer available, nor supported. However, if you are trying to do this process with modern versions of vSpace Pro, please use this article instead: ...
***WARNING*** Do Not Use Windows 10 Build 1809 ***WARNING***
Product Line: VERDE At this writing, with VERDE 8.2.x, DO NOT use Windows 10 build 1809. There are huge bugs. Everything from profiles to installing software other than Microsoft products. It's better to stay with 1709 or 1803.