Knowledge Base NComputing vSpace Server vSpace Pro 10 & 11

            Windows 10 update (1809 or May 2019 Update Release) affecting vSpace Pro Notification


            Both vSpace Pro 11 and vSpace Pro Enterprise Edition support Windows 10 OS up to version 1809 (up to build 17763.1). However, within version 1809, there are many different OS build #s which could potentially create issues. This article will guide you through the Windows 10 upgrade process.

             

            If you plan to upgrade your Windows 10 OS to version 1809 (higher build than 17763.1) or the latest May 2019 Update Release, please download and install vSpace Pro 11.3.1 interim release. This special release provides compatibility with the latest Windows 10 OS versions. You an skip the rest of the KB article.

             

            https://ncomputing.box.com/shared/static/cvwfydyzkuwjx5kz2rg1uplat1f9f404.pdf

             

            If you do not wish to update your vSpace Pro software to this vSpace Pro 11.3.1 interim version, you will need to follow below instructions to rollback Windows 10 updates. Please read through the rest of the KB article.




            If you wish to have more control over the Windows 10 update process you can disable the Windows Update service. There are two methods we recommended:
            1. Use third party utility such as ‘Windows Update Blocker’ from Sordum.org to provide an easy way to disable Windows 10 update: https://www.sordum.org/9470/windows-update-blocker-v1-2/
            2. Manually disable Windows update service. Example of video instructions can be found here:  https://www.youtube.com/watch?v=fHF7vLCMWWI 

            Case #1: If you upgraded your Windows 10 OS to an OS build # that is equal or smaller (i.e. older) than the specified above, then your vSpace Pro deployment will work properly

            However, if you encountered an error message “Insufficient system resource exist to complete the requested service” and the vSpace system is unusable after your OS upgrade, then most likely during the Windows 10 update, the OS removed several important registry keys required for vSpace Pro. Simply follow the below procedure to restore the relevant vSpace Pro registry keys to resolve the issue and your vSpace Pro deployment will work properly again: 

            To resolve this issue, please follow the below procedures to ‘repair’ your vSpace Pro installation on this system:

            1. From the host machine, open ‘Control Panel’, select ‘Programs’-> ‘Programs and Features’ 
            2. Choose the installed ‘NComputing vSpace Pro’ application and click on ‘Repair’. Please refer to the screenshot below for reference. This procedure will restore the missing registry keys required for vSpace Pro. The ‘repair’ process will be completed with an automatic system reboot and vSpace connection should be fine afterwards.

             


             

             

            Case #2: If you upgraded your Windows 10 OS to an OS build # that is larger (i.e. later) than the specified above, then your vSpace Pro deployment will NOT work properly. You must rollback back your Windows 10 OS build # to the supported version. 

                  

            A.   To rollback Windows 10 Pro OS Edition (version 1809) to the supported OS build #, please follow the below procedures:



            1.    From Explorer, go to Control Panel.



             


            2.    Search for “Installed Updates” and Open “View Installed updates” from the Control Panel.







             


            3.    Find KB4493509, press right mouse key and press Uninstall.






              



            4.    After KB4493509 is uninstalled, reboot host. After reboot the vSpace Pro issue will be resolved.






             


             

            B.    To rollback Windows 10 Enterprise OS Edition (version 1809) to the supported OS build #, please follow similar procedures as described above to uninstall KB4493509, KB4489899 and KB4487044 sequentially.  Unconfirmed reports mention also that KB4494441 and KB4497934 may also be necessary.  




            REV 05/2019
            Helpful?  
            Help us to make this article better
            6 19