I have had similar errors with builds. Mostly they point to drivers.
Have you tried running SetupDiag
https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
To see if it identifies the particular driver.
Davy.
Thank you very much Davy.
hadn't run it, which I did immediately. Picked up a driver, which appears to be Microsoft printer driver
<DriverPackages>
<DriverPackage Inf="oem39.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem56.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem50.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem38.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem37.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem65.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem63.inf" BlockMigration="True" HasSignedBinaries="False"/>
<DriverPackage Inf="oem15.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem9.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem5.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem35.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem24.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem2.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem46.inf" BlockMigration="False" HasSignedBinaries="True"/>
</DriverPackages>
Published Name: oem63.inf
Original Name: prnms009.inf
Provider Name: Microsoft
Class Name: Printer
Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}
Class Version: 4.0
Driver Version: 06/21/2006 10.0.25252.1000
Signer Name: Microsoft Windows
Wonder if this is it. Have heard about this driver a while ago (I think). Don't really know as to what to do next