Windows 10: Attempting to run MSERT or MSRT on a VM Hyper-V Manager crashes the host system both host...

I have a VM running Windows 10 x64 1809 OS build 17763.4737 which has been operating okay with no problems at all for more than two years now.The host system where the Hyper-V Manager runs is also Windows 10 x64 1809 OS build 17763.4737, and this operates okay as well.Moreover, in both host and VM, full scans by the integrated Windows Defender AV have been performed with no findings at all.There is no other antivirus installed on either system, i.e. other than Windows Defender. Both systems are fully updated and patched.I've downloaded both MSERT and MSRT KB890830 in their most current v

:)

 

Strange Problem: PhotoApp crashes host system but runs fine in hyper-v

I have Photoshop Elements running fine in a Hyper-v image, but the application crashes (reboots) Win 10 1809 in graphic intensive conditions when running in the HOST system. It's most likely related to GPU since it is not enabled in hyper-v. There is much less allocated memory in hyper-v, but the app runs fine.

I have turned off the graphics processor in both Nvidia and within the application, but the crashes in the HOST persists. The event viewer logs the system restart, but nothing is logged prior to the crash. It's not a video driver issue since in hyper-v the app works perfectly. One difference with the host: the hyper-v system has no internet switches installed.

What could be causing this very weird behavior?

- - - Updated - - -

Forgot to add: The hyper-v system is identical to the host system -- it was created using Macrium.

 

Hyper-V host cannot RDP into local clients running in an internal network

I have installed Hyper-V on my Windows 10 machine and are running a few different test machines on it. My test machines have two Nics -- One is disabled and primarily used when I need them to connect with the internet for various downloads etc. The other
Nic is connected to an internal switch on the host with hardcoded IP's allowing the VMs to always communicate with each other.

My problem is when I attempt to RDP into the VMs from the host machine I am not able to reach them. IF I log into the machines first through the Hyper-V console and toggle a Nic (i.e. disable/enable one of the nics) I am able to RDP into the VM until it
is rebooted again (My host is a laptop so they are being shutdown nightly).

I did mess around with the network settings on a previous setup and had it working -- but I am unable to reproduce the same settings. Currently the host is all "auto" setup by the system with three switches:

• External linked to my Wireless Nic
• External Linked to my Physical Nic
• Internal switch used for the VM's communicate amongst each other

Any ideas on what network settings I am missing that will allow me to connect to the VM's instantly through an RDP connection? (I can console connect but prefer using RDCMan).

Thanks,

HP

 

Account failed logon 4625 on VM guest when clicking the entry of VM guest on failover cluster Manager on VM Host

Issue:

We found a multiple failed logon events on VM guest (evert ID 4625) with account (the account you logon on VM host) when we clicking the entry of VM guest on failover cluster manager console on VM host with Integration servers (Data Exchange) is enabled.



How to reproduce:

1. Check the “Data Exchange” is enabled on a VM guest (Enabled by default, right?)
2. Open Failover Cluster Manager Console on VM host.
3. Click the VM guest entry
4. Then you may found multiple failed logon events on that VM guest.

Reference:

https://docs.microsoft.com/en-us/vi...on-services#hyper-v-data-exchange-service-kvp



Question:

1. Does the multiple failed logons are normal or necessary?
2. If the failed logons are normal and necessary to be happened and the “Data exchange” function is good to be enabled to gather data from VM guest, any recommendation for us to correct or avoid these failed logon?

Please advise.



Constrain:

We have no chance to use same account and password on VM hosts and VM guests (because all account are managed by password management) and the Audit Policy of Audit Credential Validation must be enabled.