Processing windows updates using powershell on Hyper-V machine running on 2012 r2

Can you perhaps explain a bit differently? What do you mean by "the 2012 R2 side."  What is and isn't updating? The host? One of the guests? Your terminology leaves it all a bit ambiguous.

I have a HP G8 server running a 2012r2 Domain Controller on the physical side and one VM running SQL 2014. The DC side updates just fine but the VM says it checking but never stops checking, like it's in a loop. Once before in 2015 I had a tech come in and he used a power shell command to manually download and process the updates.

Here is a bit of the windowsupdate log.
2018-02-03      18:19:25:732       844      24d8      AU      OOBE is in progress, so cannot perform Accelerated Install
2018-02-03      18:19:25:732       844      24d8      AU      Currently AUX is enabled - so not show any WU Upgrade notifications.
2018-02-03      18:19:25:732       844      24d8      AU      WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2018-02-03      18:19:25:732       844      24d8      AU      WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2018-02-03      18:49:25:747       844      24d8      AU      Windows OOBE is still in progress. AU deferring detection
2018-02-03      18:49:25:747       844      24d8      AU      WARNING: BeginDetection failed, hr:0x8024a008
2018-02-03      18:49:25:747       844      24d8      AU      All AU searches complete.
2018-02-03      18:49:25:747       844      24d8      AU        # WARNING: Failed to find updates with error code 8024a008
2018-02-03      18:49:25:747       844      24d8      AU      Need to show Unable to Detect notification
2018-02-03      18:49:25:747       844      24d8      AU      AU setting next detection timeout to 2018-02-04 01:19:25
2018-02-03      18:49:25:747       844      24d8      AU      Adding timer:
2018-02-03      18:49:25:747       844      24d8      AU          Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2018-02-04 01:19:25, not idle-only, not network-only
2018-02-03      18:49:25:747       844      24d8      AU      OOBE is in progress, so cannot perform Accelerated Install
2018-02-03      18:49:25:747       844      24d8      AU      Currently AUX is enabled - so not show any WU Upgrade notifications.
2018-02-03      18:49:25:747       844      24d8      AU      WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2018-02-03      18:49:25:747       844      24d8      AU      WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

Hi,

I hope this setup is in a lab and not in a business environment. Either way you need to split the roles: DC x1 with NOTHING else installed (no IIS, no WSUS) - then a second machine as your Hyper- V host. OR just one server with a guest DC and other VMs doing whatever else you want.

Mike

I have a RDP server and the DC / Hyperv server. We run a small accounting database with about 11GB of data. We don't use the DC as a file or print server. I setup a linux server to handle login, printing, IM, email, files and etc. I've never had an issue except processing the updates on the VM. The update process worked fine last time using the powershell command but I was looking over the shoulder of another tech and didn't see the whole process. So I was asking to see if someone could guide me to the right article or process.

I got the updates loaded last night and all is good. I had to use the WSUS offline method.

I just bought a third server, HP G10, I'm installing VMWare to run three small VMs. I'll take your recommendation and move the VM off the DC.

Thanks everyone.