SOLVED
Home

18362 Upgrade failed due to 17763 Microsoft XPS and PDF drivers?

%3CLINGO-SUB%20id%3D%22lingo-sub-451506%22%20slang%3D%22en-US%22%3E18362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-451506%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20Release%20Preview%20Ring%201809%20(17763.404)%20computer%20can't%20upgrade%20using%20Windows%20Update%20directly%2C%20every%20time%20it%20run%20100%25%20and%20told%20me%20restart%20to%20install%2019H1%2C%20never%20jumped%20into%20install%20screen%2C%20and%20the%2010GB%20migration%20%5C%24WINDOWS.~BT%5C%20just%20disappeared%2C%20then%20the%26nbsp%3BWindows%20Update%20just%20start%20over%20again%2C%20to%20break%20the%20loop%20I%20tried%20to%20install%20it%20on%20uupdump%20ISO.%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20checking%20comparability%20(%22Make%20sure%20you%20are%20ready%20to%20install%22)%20it%20says%3A%3C%2FP%3E%3CP%3EThis%20PC%20can't%20be%20upgraded%20to%20Windows%2010.%3CBR%20%2F%3EYour%20PC%20has%20hardware%20that%20isn't%20ready%20for%20this%20version%20of%20Windows%2010.%20No%20action%20is%20needed.%20Windows%20Update%20will%20offer%20this%20version%20of%20Windows%2010%20automatically%20once%20the%20issue%20has%20been%20resolved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%26nbsp%3B%24WINDOWS.~BT%5CSources%5CPanther%5CCompatData.xml%20it%20says%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CDRIVERPACKAGES%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem20.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem59.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem71.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem87.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem44.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem42.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem16.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem124.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem24.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem70.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem116.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem19.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem77.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem102.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem64.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem106.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem34.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem6.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BFalse%26quot%3B%22%20blockmigration%3D%22%26quot%3BTrue%26quot%3B%22%20inf%3D%22%26quot%3Boem93.inf%26quot%3B%2F%22%3E%3C%2FDRIVERPACKAGE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BFalse%26quot%3B%22%20blockmigration%3D%22%26quot%3BTrue%26quot%3B%22%20inf%3D%22%26quot%3Boem92.inf%26quot%3B%2F%22%3E%3C%2FDRIVERPACKAGE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem39.inf%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDRIVERPACKAGE%20hassignedbinaries%3D%22%26quot%3BTrue%26quot%3B%22%20blockmigration%3D%22%26quot%3BFalse%26quot%3B%22%20inf%3D%22%26quot%3Boem2.inf%26quot%3B%2F%22%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGE%3E%3C%2FDRIVERPACKAGES%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20the%20drivers%20blocking%20Upgrade%20are%20C%3A%5CWindows%5CINF%5Coem92.inf%20and%26nbsp%3Boem93.inf%3C%2FP%3E%3CP%3E%3CSTRONG%3EMicrosoft%20Print%20To%20PDF%3C%2FSTRONG%3E%3CBR%20%2F%3EC%3A%5CWindows%5CSystem32%5CDriverStore%5CFileRepository%5Cprnms009.inf_amd64_80184dcbef6775bc%20(ver.20180915)%3CBR%20%2F%3E%3CSTRONG%3EMicrosoft%20XPS%20Document%20Writer%3C%2FSTRONG%3E%3CBR%20%2F%3EC%3A%5CWindows%5CSystem32%5CDriverStore%5CFileRepository%5Cprnms001.inf_amd64_f340cb58fcd23202%20(ver.20180915)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can't%20update%20those%20printer%20drivers%20which%26nbsp%3BWindows%20Update%20already%20got%20those%2018362%20new%20drivers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EC%3A%5CWindows%5CSoftwareDistribution%5CDownload%5C3847f82412c0d2e352b774ced8c14c9b%5Camd64_Microsoft-Windows-Client-Desktop-Required-Package~~amd64~~10.0.18362.1%5Camd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.18362.1_none_f5360ee5e03eb891%3C%2FP%3E%3CP%3E(ver.20190301)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EC%3A%5CWindows%5CSoftwareDistribution%5CDownload%5C3847f82412c0d2e352b774ced8c14c9b%5Camd64_Microsoft-Windows-Client-Desktop-Required-Package~~amd64~~10.0.18362.1%5Camd64_microsoft-windows-printing-printtopdf_31bf3856ad364e35_10.0.18362.1_none_548d6537c3c46736%3C%2FP%3E%3CP%3E(ver.20190301)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20delete%20those%20printers%20but%20still%20can't%20pass%26nbsp%3Bcomparability%20check%2C%20since%20those%20drivers%20are%20still%20in%20C%3A%5CWindows%5C%20after%20uninstall%26nbsp%3Bprinters.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-457494%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-457494%22%20slang%3D%22en-US%22%3E%3CP%3EI%20continue%20to%20receive%20this%20error%20even%20after%20removing%20those%20two%20virtual%20print%20drivers%20with%20pnputil.%3CBR%20%2F%3EThere%20are%20no%20blockers%20but%20it%20still%20blocks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%3A%20Apparently%20if%20you%20use%20pnputil%20to%20remove%20those%20virtual%20print%20drivers%2C%20then%20delete%20compatscancache.dat%20in%20the%20Panther%20folder%2C%20then%20hit%20back%20and%20rescan%2C%20it'll%20then%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-458349%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458349%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F67014%22%20target%3D%22_blank%22%3E%40Inari%20Okami%3C%2FA%3E%26nbsp%3BDid%20you%20successfully%20installed%2018362%20after%20deleted%20compatscancache.dat%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20removed%20those%20printer%20drivers%20using%20Control%20Panel%20%26gt%3B%20Turn%20Windows%20features%20on%20or%20off.%20The%20log%20don't%20have%20anymore%20driver%20block%20the%20migration%2C%20but%20still%20get%20%22Your%20PC%20has%20hardware%20that%20isn't%20ready%20for%20this%20version%20of%20Windows%2010%20%22.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBefore%20I%20tried%2018362%20uupdump%20converted%20iso%2C%20I%20tried%20the%20official%20insider%20ISO%20aka.ms%2FWIPISO%20build%2018343%2C%20and%20my%20PC%20passed%20the%26nbsp%3Bcompatibility%20check%20in%2018343%2C%20installation%20run%20to%2087%25%20then%20failed.%20setuperr.log%20was%20pretty%20mess.%20I%20believe%20is%20said%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20481px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109016i276A49BCFBF4D9D4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22somethinghappened.gif%22%20title%3D%22somethinghappened.gif%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EError%20CONX%200xd0000034%20Failed%20to%20add%20user%20mode%20driver%20%5B%25SystemRoot%25%5Csystem32%5CDRIVERS%5CUMDF%5Cuicciso.dll%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-458443%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458443%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F320979%22%20target%3D%22_blank%22%3E%40visa1901%3C%2FA%3EIt%20did%20successfully%20install%2C%20yes.%20For%20some%20reason%20it%20was%20still%20detecting%20it%20because%20of%20the%20stale%20cache%20file.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-458445%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458445%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F320979%22%20target%3D%22_blank%22%3E%40visa1901%3C%2FA%3EIt%20did%20successfully%20install%2C%20yes.%20For%20some%20reason%20it%20was%20still%20detecting%20it%20because%20of%20the%20stale%20cache%20file.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20also%20using%20a%20uupdump%20based%20ISO.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-477439%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-477439%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F320979%22%20target%3D%22_blank%22%3E%40visa1901%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20did%20you%20find%20what%20driver%20oem92.inf%26nbsp%3B%20points%20to%3F%20I'm%20having%20a%20similar%20issue%20but%20my%20ScanResult%2FCompatData%20says%20oem123.inf%20and%20oem122.inf%20are%20blocking%20the%20upgrade.%20What%20are%20these%20drivers%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E----%3C%2FP%3E%3CP%3EOk%2C%20I%20found%20the%20driver%20names%20with%20this%20command%3A%3C%2FP%3E%3CPRE%3Epnputil%20%2Fenum-drivers%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20they%20are%20printer%20drivers%20from%20Microsoft%20as%20old%20as%20from%202006...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-477463%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-477463%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324383%22%20target%3D%22_blank%22%3E%40tmxkn1%3C%2FA%3E%26nbsp%3BIf%20it's%20the%20same%20virtual%20print%20drivers%2C%20they%20can%20be%20temporarily%20removed%20from%20Control%20Panel%20-%26gt%3B%20Programs%20and%20Features%20-%26gt%3B%20Turn%20Windows%20Features%20on%20or%20off%20-%26gt%3B%20mid-way%20down%2C%20Microsoft%20Print%20to%20PDF%20and%20Microsoft%20XPS%20Document%20Writer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESimply%20opening%20each%20INF%20listed%20as%20a%20blocker%20in%20C%3A%5CWindows%5CINF%20will%20also%20tell%20you%20exactly%20what%20they%20are%20at%20the%20top%20of%20the%20file.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2006%20is%20the%20listed%20driver%20date%20of%20most%20official%20inbox%20Windows%20drivers%2C%20as%20the%20date%20allows%20OEM%20drivers%20to%20automatically%20override%20them%20if%20they're%20newer.%20It%20doesn't%20mean%20they're%20actually%20that%20old.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-477469%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-477469%22%20slang%3D%22en-US%22%3EYes%20they%20are%20the%20same%20print%20to%20x%20drivers.%20After%20disabling%20them%20in%20%22Turn%20Windows%20Features%20on%20or%20off%22%2C%20I%20have%20to%20manually%20delete%20the%20%22compatscancache.dat%22%20too%20as%20you%20mentioned%20in%20the%20accepted%20answer.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-485609%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-485609%22%20slang%3D%22en-US%22%3EPerfect%20measure%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-837490%22%20slang%3D%22en-US%22%3ERe%3A%2018362%20Upgrade%20failed%20due%20to%2017763%20Microsoft%20XPS%20and%20PDF%20drivers%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-837490%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324383%22%20target%3D%22_blank%22%3E%40tmxkn1%3C%2FA%3E%26nbsp%3BYou%20can%20also%20open%20the%20file%20from%20C%3A%5CWindows%5CInf%5CoemXX.inf%20and%20it%20will%20say%20what%20device%20the%20driver%20is%20for.%3C%2FP%3E%3C%2FLINGO-BODY%3E
visa1901
New Contributor

My Release Preview Ring 1809 (17763.404) computer can't upgrade using Windows Update directly, every time it run 100% and told me restart to install 19H1, never jumped into install screen, and the 10GB migration \$WINDOWS.~BT\ just disappeared, then the Windows Update just start over again, to break the loop I tried to install it on uupdump ISO.

After checking comparability ("Make sure you are ready to install") it says:

This PC can't be upgraded to Windows 10.
Your PC has hardware that isn't ready for this version of Windows 10. No action is needed. Windows Update will offer this version of Windows 10 automatically once the issue has been resolved.

 

In $WINDOWS.~BT\Sources\Panther\CompatData.xml it says:

 

<DriverPackages>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem20.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem59.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem71.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem87.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem44.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem42.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem16.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem124.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem24.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem70.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem116.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem19.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem77.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem102.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem64.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem106.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem34.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem6.inf"/>
<DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem93.inf"/>
<DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem92.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem39.inf"/>
<DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem2.inf"/>

 

 

So the drivers blocking Upgrade are C:\Windows\INF\oem92.inf and oem93.inf

Microsoft Print To PDF
C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_80184dcbef6775bc (ver.20180915)
Microsoft XPS Document Writer
C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_f340cb58fcd23202 (ver.20180915)

 

I can't update those printer drivers which Windows Update already got those 18362 new drivers

 

C:\Windows\SoftwareDistribution\Download\3847f82412c0d2e352b774ced8c14c9b\amd64_Microsoft-Windows-Client-Desktop-Required-Package~~amd64~~10.0.18362.1\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.18362.1_none_f5360ee5e03eb891

(ver.20190301)

 

C:\Windows\SoftwareDistribution\Download\3847f82412c0d2e352b774ced8c14c9b\amd64_Microsoft-Windows-Client-Desktop-Required-Package~~amd64~~10.0.18362.1\amd64_microsoft-windows-printing-printtopdf_31bf3856ad364e35_10.0.18362.1_none_548d6537c3c46736

(ver.20190301)

 

I've tried delete those printers but still can't pass comparability check, since those drivers are still in C:\Windows\ after uninstall printers.

9 Replies
Solution

I continue to receive this error even after removing those two virtual print drivers with pnputil.
There are no blockers but it still blocks.

 

UPDATE: Apparently if you use pnputil to remove those virtual print drivers, then delete compatscancache.dat in the Panther folder, then hit back and rescan, it'll then work.

@Inari Okami Did you successfully installed 18362 after deleted compatscancache.dat?

 

I removed those printer drivers using Control Panel > Turn Windows features on or off. The log don't have anymore driver block the migration, but still get "Your PC has hardware that isn't ready for this version of Windows 10 ". 

 

Before I tried 18362 uupdump converted iso, I tried the official insider ISO aka.ms/WIPISO build 18343, and my PC passed the compatibility check in 18343, installation run to 87% then failed. setuperr.log was pretty mess. I believe is said

somethinghappened.gif

Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

 

@visa1901It did successfully install, yes. For some reason it was still detecting it because of the stale cache file.

@visa1901It did successfully install, yes. For some reason it was still detecting it because of the stale cache file.

 

I'm also using a uupdump based ISO.

@visa1901 

 

How did you find what driver oem92.inf  points to? I'm having a similar issue but my ScanResult/CompatData says oem123.inf and oem122.inf are blocking the upgrade. What are these drivers?

 

----

Ok, I found the driver names with this command:

pnputil /enum-drivers

 

and they are printer drivers from Microsoft as old as from 2006...

@tmxkn1 If it's the same virtual print drivers, they can be temporarily removed from Control Panel -> Programs and Features -> Turn Windows Features on or off -> mid-way down, Microsoft Print to PDF and Microsoft XPS Document Writer.

 

Simply opening each INF listed as a blocker in C:\Windows\INF will also tell you exactly what they are at the top of the file.

 

2006 is the listed driver date of most official inbox Windows drivers, as the date allows OEM drivers to automatically override them if they're newer. It doesn't mean they're actually that old.

Yes they are the same print to x drivers. After disabling them in "Turn Windows Features on or off", I have to manually delete the "compatscancache.dat" too as you mentioned in the accepted answer.

@tmxkn1 You can also open the file from C:\Windows\Inf\oemXX.inf and it will say what device the driver is for.

Related Conversations
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies