Windows won't shut down since last update to V1909 build 18363.900

When there is a windows upgrade the data within many of the logs are cleaned.
So if you can, replace the prior V2.
New V2 can be uploaded into the newest post.

Indicate whether windows shutdowns properly post windows upgrade.

Hi those logs on dropbox are new. I did them after the update.

The shutting down and restarts were working before the latest update after I had removed Hyper V from windows features .

So to test it again I just re-installed hyper V and restarted.
When it booted back up I could not get the internet it said the ethernet cable was unplugged . I tried re-plugging it and did the trouble shooter but still couldn't connect.
So I shut down - which worked OK
then re-booted and this time I have a connection so I hope everything is OK now

The computer had had multiple BSOD in April 2020.
The Windows upgrade may or may not have fixed the recent BSOD.

1) Open administrative command prompt and type or copy and paste:
2) wmic recoveros set autoreboot = false
3) wmic recoveros set DebugInfoType = 7
4) wmic recoveros get autoreboot
5) wmic recoveros get DebugInfoType

6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

The above will modify the default Windows settings to optimize the detection of BSOD.

There is a default 10 day rollback period for windows upgrades.
The computer has both a restore point and Macrium.
So you have options in case there are any future problems

The computer can be monitored for additional days or you can mark the thread solved.

If there are any more BSOD you can open a new thread in the BSOD forum:
BSOD - Posting Instructions

The reliability monitor is an additional method to monitor for unexpected shutdowns and restarts:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

OK thanks I'll leave a couple of days to see if it works ok.
The BSODS in April was Me Testing Macrium ViBoot.
It's too long a story to tell but I was getting multiple bsods on testing Macrium Reflect backups in Viboot.
I never got to the bottom of the problem. Even Macrium Techs could not solve it. I eventually gave up testing the backups as it caused so much hassle.
I began testing because I had a serious backup failure where Lots of my backups would not work after I had a bad crash and needed them badly. Causing me to totally re-install from scratch. Macrium techs could not get to the bottom of that either!
Here are the results you requested.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\WINDOWS\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\MAIN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\MAIN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros get autoreboot
AutoReboot
FALSE

PS C:\WINDOWS\system32> wmic recoveros get DebugInfoType
DebugInfoType
7

PS C:\WINDOWS\system32>

Automatic reboot is now unchecked.
So this improves the likelihood of identifying BSOD.
BSOD can still be missed.
The new upgrade cleaned the the files reporting the BSOD.
If there are BSOD we typically see dump files or errors reporting the crashes (running V2).

Ok Thanks very much for your Help .
I'll just leave it a day or so and close the thread if there are no more problems.

Thanks again

Mike