Windows 10: Windows 10 in Asus laptop firmware update or hyper-v causes automatic repair loop everytime

I have an Asus FX705DX laptop (Ryzen 3550H) and i've been having the same issue since i bought it several months ago.
Everytime a new Firmware (BIOS) update from Asus is installed automatically by Windows Update my system runs into an Automatic Repair Loop and nothing i do (startup repair, system restore, uninstall updates) but reinstalling Windows solves the problem.
I also get to this situation with a new windows install and enabling Hyper-V.
This last time i made a clean new installations of Windows 10 1903 Education, installed all updates and then, when i enabled Hyper-V i got into reboot loop again. I ran automatic startup repair and SrtTrail.txt said:

**Root cause found:
---------------------------
A recently serviced boot binary is corrupt.

Repair action: Uninstall latest LCU
Result: Failed. Error code = 0x3713**

So i entered command prompt from rescue environment and did a:

**DISM /Image:\ /ScratchDir:\Scratch /Cleanup-Image /RevertPendingActions**

which completed successfully and i could restart and, to my surprise, Hyper-V is enabled.

The problem is i tried to enable Hypervisor Platform and shows error "Changes cannot be completed".
I went again to recovery command line and tried to install if from there with:

**dism /image:c:\ /scratchdir:c:\scratch /enable-feature /featurename:hypervisorplatform**

which gave me error:


Then i did a dism checkhealth and i have:


Also, installing VisualStudio i got a warning saying:

**Package 'Microsoft.VisualStudio.AspNet45.Feature,version=16.0.28315.86' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.AspNet45.Feature;PackageAction=Install;ReturnCode=-2146498512
Details
Command executed: "C:\Windows\system32\dism.exe" /online /quiet /norestart /Enable-Feature /FeatureName:"netfx4extended-aspnet45" /All /logPath:"C:\Users\mike\AppData\Local\Temp\dd_setup_20190811143007_359_Microsoft.VisualStudio.AspNet45.Feature.log"
Return code: -2146498512
Return code details: Unknown error (0x800f0830)**

So i can work with the system but it seems a bit corrupted.
Some apps like Boxcryptor are failing to install now.


Thanks in advance. Any help would be much appreciated.

I attach links to dism logfiles.
https://drive.google.com/file/d/1MGO9qt5lbVAqu5p6LI7jOAMTDLn2RG69/view?usp=sharing
https://drive.google.com/file/d/1wEnwJhk5v3Xgc5cv-9FjDzpudjBp_RWz/view?usp=sharing

:)

 

Hyper-V causing boot loop in Windows 10 Pro x64

It appears that insider build 10547 has corrected the hyper-v boot loop issue in windows 10 x64. Running systeminfo.exe inside an admin command prompt shows that (you can find statement next to "Hyper-V Requirements:" shown at the bottom of the list) "A
hypervisor has been detected. Features required for Hyper-V will not be displayed." (Which means Hyper-V is now working). Downloading emulators now for windows phone for Visual Studio 2015 to see if they work. Will update later today...

 

Hyper-V causing boot loop in Windows 10 Pro x64

After upgrading to Windows 10 x64 Pro from Windows 10 Home to x64 Professional and activating Hyper-V in Windows 10 x64 Pro my computer reboots. After a couple of tries it goes in automatic repair and attempts to repair the startup. This cycle just repeats
itself. I tried many combinations of things in the bios, shutting down, nothing has worked.

The only way I found to bring out of the loop is re-install windows

So I re installed Windows 10 Pro and activated Hyper-V and same reboot loop occurs.

So re-installed a second time then I found the cure.

The cure is to enable Hyper V from Power Shell , once I did this the pc restarted a couple of times, and everything back to normal hyper v working .

CLI command to enable

CLI command to disable

 

Hyper-V Feature Causes Repair Loop After Fall Creators Update

I use Windows 10 Education Edition. I had trouble installing the Fall Creator's update a few days ago and ultimately, I backed up my files and reset my PC. During this process, the Fall Creator’s update was installed.

I use Hyper-V for study and this feature was removed during the reset and update process. I turned Hyper-V back on and after the resulting reboot, my computer went into a repair loop. It would never completely restart or repair itself. I was unable to use
a restore point so I reset the computer a second time. I tried to turn on Hyper-V a second time and got into the same repair loop. This time, I went into UEFI and turned off virtualization. After exiting, the computer started normally. After experimenting
a little with this, the bottom line is that I can have virtualization in UEFI turned on only if Hyper-V is turned off. If Hyper-V is turned on virtualization must be turned off in UEFI and renders Hyper-V useless. I decided to do a clean install but got the
same results. Occasionally, I would get a blue screen that read,

If you call a support person, give them this info: STOP CODE: IRQL NOT LESS OR EQUAL

Any ideas?