Folks!! If you are wondering what the 123 vulnerabilities that were patched today are all about, please have a look at this write up over on Bleeping Computer. Its massive and covers a boat load of Windows products. Patch up!! Don't wait.
Cheers
No!! There are no VM's running of this laptop. Not enabled in BIOS as well. I just wanted to reflect that, although the vulnerability is targeted toward the enterprise community the registry key will be set to disable it on Windows 10 machines as well for the everyday user. Beginning with version 1809 the registry entries were set to "Depreciate", July 2020 it was set as the screenshot posted, on Windows 10. Disabled.
I still have two machines on 1909 build 18363.900 that haven't yet applied the patches from this month. I will post feedback about those later today when I have the opportunity to update them both. Good question on your part, I am in the wait and see mode before patching those machines due to the content on them and DO have images on external drives for both.
Cheers
SoulAsylum:One of the serious issues corrected is mentioned here by Microsoft. Some of the other security sites are saying if you are should you be concerned, their answers are NO!! Well it was in fact scheduled per the linked article some time ago. My screenshot serves that is was indeed serious enough to be disabled on a Windows Pro x64 machine via WU. Its now a running process at boot time....
Hi SoulAsylum:
Do you have a VM running on your Win 10 Pro machine? That support article Update to Disable and Remove the RemoteFX vGPU Component in Windows seems to suggest that the RemoteFX vGPU vulnerabilities are only a concern on machines with VMs that share a physical GPU.
I'm still on Win 10 Pro v1909 Build 18363.900 (KB4560960 for the June 2020 Patch Tuesday) and I'm curious if all Win 10 Pro v1909 Build 18363.959 users will see this RemoteFXvGPUDisablement.exe process launch at boot-up after they apply the July 2020 Patch Tuesday update (i.e., even if their machine does not run a VM) just by virtue of having Hyper-V Manager built into their Win 10 Pro OS.
-------------
64-bit Win 10 Pro v1909 build 18363.900 * Firefox ESR v68.10.0 * Windows Defender v4.18.2006.10
One of the serious issues corrected is mentioned here by Microsoft. Some of the other security sites are saying if you are should you be concerned, their answers are NO!! Well it was in fact scheduled per the linked article some time ago. My screenshot serves that is was indeed serious enough to be disabled on a Windows Pro x64 machine via WU. Its now a running process at boot time.
Cheers