• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

VM and windows updates

Which hypervisor you use? VirtualBox, Hyper-V, or something else?
Usually, on VB, it takes a bit longer than normal, but, I haven't see that happen on MS's own Hyper-V, at least, not yet.
 
Haven't tried Hyper V yet (I need to sometime). I use VMware and it does ok. A couple observation from my VMWare experience:

1. Let the VM have access to more than one core, because Windows Update will really hog core 0.
2. Give the VM enough RAM. I would recommend 2 GB at the minimum for anything back to 7.
3. Give it it's own IP address. Letting it share the hosts IP address has caused me issues here and there.

In other words, look at system resources and see what is struggling when you let Windows Update run.
 
Windows update is slow, period. 😛 I can update a fresh install of Linux faster on a Raspberry Pi than any windows machine takes to apply updates even on a non fresh install. Oddly enough sometimes it's fast, it seems to be really random. That said, windows is quite a resource heavy OS so on a VM there will be extra overhead. Best bet is to disable updates and then only do it manually once in a while as an overnight thing. The annoying part though is that windows updates seem to have so many steps involved that require multiple reboots/user interaction in between so even letting it overnight will only accomplish the first step.
 
Back
Top