Server 2016 to Server 2019 adprep error "Failed to verify file signature: error 0x800b0109."

%3CLINGO-SUB%20id%3D%22lingo-sub-188840%22%20slang%3D%22en-US%22%3EServer%202016%20to%20Server%202019%20adprep%20error%20%22Failed%20to%20verify%20file%20signature%3A%20error%200x800b0109.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188840%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20ADPrep%20in%20order%20to%20begin%20the%20process%20of%20upgrading%202016%20to%202019%20I%20get%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%22Verifying%20file%20signature%3CBR%20%2F%3EFailed%20to%20verify%20file%20signature%3A%20error%200x800b0109.%3CBR%20%2F%3EERROR%3A%20Import%20from%20file%20D%3A%5C2019%5Csupport%5Cadprep%5Csch88.ldf%20failed.%20Error%20file%20is%20saved%20in%20C%3A%5CWindows%5Cdebug%5Cadprep%5Clogs%5C20180501005227%5Cldif.err.88.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%26nbsp%3Busing%20server%202019%20LTSB%2C%20the%202016%20datacenter%20server%20is%20fully%20updated.%3C%2FP%3E%3CP%3EIs%20there%20an%20.iso%26nbsp%3Bthat%20has%20the%20sch88.ldf%20file%20with%20the%20correct%20signature%3F%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20other%20ideas%20on%20how%20to%20resolve%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-188840%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EServer%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EServer%20Error%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266569%22%20slang%3D%22en-US%22%3ERe%3A%20Server%202016%20to%20Server%202019%20adprep%20error%20%22Failed%20to%20verify%20file%20signature%3A%20error%200x800b0109.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266569%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20have%20to%20do%20adprep%20%2Fdomainprep%20as%20well%3A%20it%20works%20after%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-196606%22%20slang%3D%22en-US%22%3ERe%3A%20Server%202016%20to%20Server%202019%20adprep%20error%20%22Failed%20to%20verify%20file%20signature%3A%20error%200x800b0109.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196606%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20problem%20with%20the%20schupgrade.cat%20certificate%20not%20being%20trusted%2C%20see%20my%20reply%20here%20on%20how%20to%20fix%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Server-Insiders%2FProblem-with-adprep-before-in-place-upgrade-of-domain-controller%2Fm-p%2F196604%2Fhighlight%2Ftrue%23M445%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Server-Insiders%2FProblem-with-adprep-before-in-place-upgrade-of-domain-controller%2Fm-p%2F196604%2Fhighlight%2Ftrue%23M445%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189866%22%20slang%3D%22en-US%22%3ERe%3A%20Server%202016%20to%20Server%202019%20adprep%20error%20%22Failed%20to%20verify%20file%20signature%3A%20error%200x800b0109.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189866%22%20slang%3D%22en-US%22%3E%3CP%3EI%20too%20ran%20into%20this%20issue.%20Looking%20forward%20to%20getting%20it%20licked!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hello,

 

Running ADPrep in order to begin the process of upgrading 2016 to 2019 I get the following error:

"Verifying file signature
Failed to verify file signature: error 0x800b0109.
ERROR: Import from file D:\2019\support\adprep\sch88.ldf failed. Error file is saved in C:\Windows\debug\adprep\logs\20180501005227\ldif.err.88."

 

I'm using server 2019 LTSB, the 2016 datacenter server is fully updated.

Is there an .iso that has the sch88.ldf file with the correct signature? 

Any other ideas on how to resolve this issue?

 

 

Thank you

3 Replies
Highlighted

I too ran into this issue. Looking forward to getting it licked! :)

Highlighted
Highlighted

You have to do adprep /domainprep as well: it works after that.