Win10 1803 update frreezing at 43%, yep another one.....

I thought all but two items were checked, but the last three aren't here.

No crashes yet.....

Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x002defbb

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[X] 0x00002000 Invariant MDL checking for stack.
[X] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[X] 0x00010000 Port/miniport interface checking.
[X] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[X] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.additional
ndis: rules.default

Verified Drivers:

amdpsp.sys
asupio.sys
asio.sys
rt640x64.sys
atikmpag.sys
atikmdag.sys
amdpcidev.sys
amdgpio2.sys
amdgpio3.sys
busenum.sys
atihdwt6.sys
rtkvhd64.sys
lhidfilt.sys
lmoufilt.sys
dump_diskdump.sys
dump_stornvme.sys
dump_dumpfve.sys
ndis.sys
wdiwifi.sys

C:\WINDOWS\system32>

Please use the snipping tool and post an image of the windows driver verifier driver boxes for the available drivers for testing.

Will it allow you to check the additional flags:
Select everything. For Win 8 and win 10 dont checkDDI compliance checking and randomized low resource simulation, then click "Next"

Were these not able to be checked?
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Yep, silly me. I didn't scroll down enough to see those last three tests. Since included them and that caused a series of BSOD on restarts. Have now finally got some crash dumps!

DJR-POOTA (2018-08-14 18 57).zip
Now hopefully we've got something useful!

OK, this problem is going to have to wait until I get this system hang on 'scan for hardware changes' issue sorted first.
This happens if I do it in Device Manager as well as the setup process.

Thanks so much for all your time and effort helping me here. Cheers.

Follow up.

Since the last post I have returned the mobo because of its BIOS issue with W10 scan for hardware changes problem. Definitely a problem there. And BIOS wasn't listing the M2 drive although it works perfectly.

I purchased a replacement mobo (the superseding ASUS Prime B450-Plus) which despite the upgraded chipset seems to function the same as the B350. It came with BIOS 0318 which didn't hang doing a hardware scan, but I still couldn't upgrade W10 with it. Checked for any updates available for it, sure enough a new BIOS was. So installed that and.......... now it hangs doing the hardware scan. Most definitely a BIOS issue that is on both mobo's. I've let ASUS know so hopefully they can resolve the issue in the next BIOS update.

Since then I tried seeing what would happen if I removed a OCI-e to SATA add-on card. I had installed it to regain the 5th and 6th SATA port which is disabled on the mobo when an M2 SSD is installed. Everything works and I've been able to upgrade W10 to 1803. Had to re-activate because of the new mobo which turned out to be unnecessary. Oh well, when the first mobo comes back it will be the basis of upgrading my sons poota, my hand-me-down.

Thank you to all those that have helped me here. You're an invaluable support community. Cheers.

That's great that you have a new motherboard and have been able to upgrade to windows 1803.
Consider making a backup image using Macrium so that you have some protection for unexpected problems:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect | Windows 10 Tutorials

Got the NAS box fired up now backing everything up too.

I have to admit, to Microsoft's credit, Windows has reliably always recovered from these multiple failed attempts to upgrade. Given the complexity and shear volume of data that the process deals with, it never faltered. Kinda impressive.

Thanks zbook, you're a champ.

Your welcome.......anytime