Windows 10: BSOD upon reboot following upgrade from WIN 10 V 1903 to V 1909

In a previous post I was having installation failures with WIN 10 V 1903 for Cumulative Updates 2019-07, 2019-09 and 2019-10. Each failed with error code 0x800f0845. Time Lady had be try numerous things, all failed. In addition, I was getting repeated BSOD after reboot. She suggested waiting until V1909 was released as it would include all updates that failed to install. Successfully to V1909 without problem except now I am getting BSOD after each reboot. Eventually get to login okay, but the first update KB4522742 also failed to install. Same error code. The following is my PC reliability history following the upgrade to 1909. I also read, that all 1909 does is turn on updates previously installed as Quality Updates under V 1903. Since those failed to install, could that be the problem? Any help would be appreciated.





:)

 

V.1809 to V.1909?

Has anyone gone from v.1809 to v.1909 yet? The WU FU to 1903 failed (twice) on my system and I rolled back to 1809. WU says v.1903 is successfully installed along with a first failed v.1903 and it also shows (correctly) that v.1809 is installed. WINVR also shows v.1809 to be installed. WU is now showing the "Download and install now" link after this week's v.1809 CU update, but I'm wondering if the FU will be successful from v.1809?

 

Windows 10 v 1903

I can't upgrade to Windows 10 v 1903. I can download it and it will try to install it. When I get the message that my computer needs to shut down and does so, I get the following message:

"Boot Manager recovered from an error.

Boot Manager has restored Boot Priority from default configuration.

Press Esc to continue or F1 to enter Setup."

When I press Esc, I then enter my password and everything looks fine. When I check to see if I an running the v 1903 version, it shows 1803.

How can I upgrade to v 1903?

 

Windows 10, ver 1903 with Hyper-V: BSOD Synthetic_Watchdog_Timeout

Greetings,

Since updating to Win 10 version 1903 in the past several weeks, two machines with Hyper-V enabled are BSOD with a Synthetic_Watchdog_Timeout error, noting hal.dll and ntoskrnl.exe in the dmp files on both systems.

One machine was updated to 1903 that has a constant VM running on it, that subsequently crashed at least once per day. After fully updating all known drivers in the host system, and the system's BIOS, Hyper-V was uninstalled, and reinstalled where the machine
seemed to be OK for 4 days, but has since crashed again, at least once per day for the last 3 days.

The other machine, recently updated to version 1903 with Hyper-V installed, also shows the same symptoms (BSOD) if a VM is live and running. The system does not crash if a VM is not running.

Are there any known issues or resolutions to this problem?

Dropbox to the dmp file:

Dropbox - Link not found