New
#140
Well, if MS release a security update and someone pokes holes in it, they need to fix those holes.....so maybe previewing security updates before general release would actually be a GOOD idea.
I have problems with my VMs running on Hyper-V Windows 10 after installing latest august update.
I have Windows 10 (1903) all updates running Hyper-V and few Windows 10 VMs.
When I connect to any of my Windows 10 VMs on running on Hyper-V via RDP from other Windows 10 PC it crashes the VM. Any one lese can confirm or deny this? Is this problem only with my setup?
If I roll back update everything works fine and all VMs (5) display same behavior after august update they crash when I try to make RDP connection.
Physical PCs are OK when connecting via RDP, only my Windows 10 VMs running on Windows 10 Hyper-v crashes.
Exactly this! Does not matter what update MS release, it should be previewed first, just in case it breaks something or if the update is a security fix that can be easily breakable.
MS is pushing too much Windows update crap out all the time, and they don't always even tell us what they really fixed.
I could not agree more with what @Pejole2165 wrote.
Furthermore and only before my eyes (I am but a mere home user), this situations glaringly exposes two issues at Microsoft re: Windows 10 updates:
* Band B CU team (security only) does not seem to communicate well with Band D CU team (non-security improvements) - a.k.a: left had does not know what right hand is doing
* More importantly (and scaringly as well): Band B CUs do not seem to be tested at all by Microsoft prior to their releases