Bad PowerShell Command Causes Critial Stop – Hyper-V 2016


I asked this question in the PowerShell forum but was given rather short shrift, so hopefully, someone here can help please . . . 

I just installed Hyper-V 2016 and applied the latest Updates to an HP Server that is certified for 2016.

I started PowerShell and entered an incorrect command in PowerShell - I was trying to get a list of the services status and should have entered "get-service". I made a mistake and entered "services" instead. That is obviously
a mistake, but should it have had critical consequences for the server?

When I entered the command, I got a Critical Stop ("Your PC ran into a problem and needs to restart . . . . " The Stop Code was CRITICAL PROCESS DIED.

(This is repeatable)

Is this expected behaviour when entering a bad command in PowerShell (I hope not!). I am reluctant to go ahead and complete configuration of the server now, including installing the VMs. Do I have a critical problem with the server, or is it all
down to "pilot error"? 

Does the (bad) "services" command have any special meaning, or is PowerShell prone to being able to kill a server like this?

To help try and isolate the issue, can someone also point me to guidance on how I can uninstall the Windows updates that I applied for a Hyper-V server with no GUI?



Read full post . . . .

Best Practises for configuring server 2016

Hi ,

 I bought a Fujitsu server  with Intel Xeon processor , 4 cores,  32Gb RAM ,  2TB Storage (4 disks) and 2 network cards. 

I need to configure  Host server with Windows server 2016 and need to configure HyperV . I need 2 VMs , and RAID configuration for Storage. 

What is the best practice to configure this , to get best performance  . 

How much Processor, RAM and Physical memory can be allocated  for each VM . 

Which type of load balancing is good  (Active-active or active -passive) for network. 


Read full post . . . .

Windows 10 2004 Update Breaks Failover Clustering Tool

Just installed 2004 Feature update to Windows 10.  Now when I try to connect to my failover cluster(running on Server 2016) it gives an error stating it is an unsupported version.  Anyone else seeing this issue?

Read full post . . . .

Virtual Switch and physical NIC in team

Hi all,

as far as I know, NIC associated with external virtual switch are "dedicated" to virtual machine communication , unless they are flagged as "shared".

Now, I have two physical NIC in team. When I try to create an external virtual switch, I have the option to connect NIC1, NIC2 or the virtual teamed NIC.

What happens if I set virtual switch with :

a) only NIC1?

b) only NIC2?

c) only with virtual teamed NIC?

Is it correct to say that with the c) option the Server cannot communicate with external network unless it is flagged as shared?

With option a) or b) i’m confused.

This is what I think could happen with option a) and  "shared" flag not set:

- The traffic to the physical server pass all through NIC 2 with NIC1  dedicated to virtual machines. Am Iright? But if this is true, which benefits I could have from having the physical NIC in team?


Read full post . . . .

Hyper-V Initial replication not starting

Dear Tech Net team, 

I have 2 node cluster Hyper-V where i have 14 VM’s are running. recently i have configured Hyper-V replication on the cluster and replicated VM’s to replica server and most of servers are replicated successfully. 

However, am facing issue with two servers while doing initial replica, the replication is enabled on the VM and replcated copy of VM created on replica server, but replication folder [initial replica via external media ] not creating any VHD files and not creating
any copy of VM in order to import on Replica VM. 

All other VM i did same scenario via External media, and it was successfully but only two servers having this issue. 
Hyper-Replication VM health report shows the error : General access denied error (0x80070005). (Virtual machine ID 5

If anyone face the same issue, or knows the fix for this kindly advise. 

Thank you in advance
The VM HDD Size is 640  GB, 


Read full post . . . .

Can not connect to my Hyper V server

Hi, I am new to this and am trying to set up my R610 with Hyper-v server 2019 Core.  I have followed many steps but am getting hung up on the Set-Item for trustedhost.. below is my error. I am able to ping my server ip of but get the
CredSSP error from my client. I do not have a domain so I am using a "WorkGroup".. Help?


PS C:Windowssystem32> Set-Item WSMan:localhostClientTrustedHosts "R610VIRT"

Start WinRM Service
WinRM service is not started currently. Running this command will start the WinRM service.

Do you want to continue?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

WinRM Security Configuration.
This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
authenticated. The client might send credential information to these computers. Are you sure that you want to modify
this list?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

Set-Item : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
At line:1 char:1
+ Set-Item WSMan:localhostClientTrustedHosts "R610VIRT"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-Item], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.SetItemCommand


This is what I have on my Server


Status   Name               DisplayName
——   —-               ———-
Running  winrm              Windows Remote Management (WS-Manag…


Read full post . . . .

Hyper-V Failover Cluster Issue – Copy of VM being left on source server after Drain

Summary - When draining a Server 2016 Hyper-V Cluster node, randomly certain VMs will be left on the source node, even though they get properly moved to the destination node and this is reflected in the Failover Manager.

Long version:

Greetings!  We have run into a rather unique (it appears) situation with our Hyper-V 2016 Failover Cluster. 
Whenever we do maintenance, we follow the standard process of Draining the node, which moves all of the Storage and VM resources over to the other functional nodes. 
While the Drain process appears to complete as far as the Cluster is concerned (no errors or warning generated), we noticed that randomly certain VMs were being left on the drained node, but they also existed at the destination node where the cluster
now says they should be located.   It only affects VMs that are in an Offline state.  
This issue is particularly bad on our Replica/Testing Cluster, where MOST of the VMs are not running (because they are replicas), but it has also occurred on our Primary cluster as well with the few VMs that are not running on there. 
The biggest issue this situation causes is that because the VMs exist on both nodes at the same time, they can both attempt to do their replication process and usually end up screwing it up, requiring a Resynch of the entire VM to the replica.

The issue occurs with VMs both with and without replication enabled. When our clusters nodes were still running Server 2012 R2, this issue never occurred. 
We migrated to 2016 late last year and this issue started occurring periodically during maintenance windows.

At this point, I am just curious if anyone else has ever ran across this or has any thoughts.  
Other than this issue, the nodes and VMs run fine.

Thanks for your time!

Read full post . . . .

vmconnect.config use 2 monitors instead of all 3 like

Hi all,

I’ve been searching all night and haven’t found anything yet. So I’ll post my question here.

I work with a VM which has my company VPN Client installed from where go log in into my Office Computer.

Since the VPN Client has no split tunneling enabled (company Policy) I can’t use any other network resource except for the company resources.

Since I still need my S4B locally, because Audio is also restricted, I need to start my S4B Client locally, so far so good everything works. But what annoys me so much is that I need to minimize my vmconnect session all the time i need to use the local S4b

That’s when I tried to configure the vm connect client to use only 2 Monitors instead of all 3.
This would be possible if the connection is an RDP Connection.
MSTSC Config for that:

use multimon:i:1

I can’t find any reference for the vmconnect.config files that are stored in C:UsersuserAppDataRoamingMicrosoftWindowsHyper-VClient1.0

Can you help me if that?

Or even better do you know the config option for multimonitor for vmconnect?

Mycurrent vmconnect rdp file:











Or can I create a connection to the hyper-v console with mstsc?

If you can help me with that you would be my hero 🙂


Read full post . . . .

Can’t remove Hyper-v server role.


I can’t remove the hyper-v server 2012 role that show error" The request to add or remove feature on the specified server failed. Teomovel of one or more role, role services, or features failed Access is denied. Error: 0x080070005."

Please see the problem as capture screen.

Could you please advice how to fix issue?

Thank you


Read full post . . . .

Install error Kali 2020.2 in Hyper-V, Couldn’t Mount File

Trying to install Kali 2020.0, using Hyper-V in Windows 10 Pro, Error from Kali was Installation Error, Installation Step Failed. Hyper-V options are enabled and turned on in Windows features, I ran an elevated cmd ‘systeminfo’ and error listed with "Hyper-V
requirements" was "A hypervisor has been detected. Features required for Hyper-V will not be displayed." Any thoughts or ideas are greatly appreciated.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1996