Build 25267.1000 is live in Dev, ISO out

Anonymous
2022-12-14T18:05:26+00:00

Build 25267.1000 is live in Dev

Windows Insider program | Program announcements and registration | Communications and announcements

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

63 answers

Sort by: Oldest
  1. Anonymous
    2022-12-26T15:27:18+00:00

    The second Insider PC is still giving me problems. Tried to install about six times already. Using WU and ISO, all stopped at the same point. No results using scans and Dism.

    Goes to 30% after the initial reboot, the restarts. The screen goes blank for a few minutes at 48%. Eventually goes to 64%, where it stays. Have left it for a couple of hours, before eventually pressing the reset. It does go back to previous, with a message after log-in:

    MB GIGABYTE Z590 AORUS ELITE AX

    Processor 11th Gen Intel(R) Core(TM) i9-11900 @ 2.50GHz 2.50 GHz

    Installed RAM 128 GB (128 GB usable)

    System type 64-bit operating system, x64-based processor

    GPU GIGABYTE GTX 1060 G1 Gaming Rev 2.0 (GV-N1060G1 GAMING-6GD)

    Samsung SSD 850 PRO 1TB

    Plus a few other SSD's

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-12-26T15:41:22+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-26T16:27:18+00:00

    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>

    	&lt;DriverPackage Inf="oem39.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem56.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem50.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem38.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem37.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem65.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem63.inf" BlockMigration="True" HasSignedBinaries="False"/&gt; 
    
    	&lt;DriverPackage Inf="oem15.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem9.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem5.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem35.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem24.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem2.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    	&lt;DriverPackage Inf="oem46.inf" BlockMigration="False" HasSignedBinaries="True"/&gt; 
    
    &lt;/DriverPackages&gt;
    

    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

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-26T16:36:58+00:00

    Are you OK with uninstalling the printer?

    Then re-attempting the update?

    You can always reinstall after completion.

    Davy.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-12-26T16:46:51+00:00

    Actually not, because I don't know where and which to uninstall, or delete

    Was this answer helpful?

    0 comments No comments