Error code: 0X8007025D - Win 10 install on old desktop with a new SSD

Page 1 of 4 123 ... LastLast

  1. Posts : 15
    win 10
       #1

    Error code: 0X8007025D - Win 10 install on old desktop with a new SSD


    Windows Version: 22h2 (OS build 19045.3570) - Windows 10 Pro

    I have a pretty old desktop pc and my hard drive kind of died to I got a new SSD.
    So to install win 10 64b there, I first created a bootable USB with the media tool.

    So it boots, I click shift+f10, opens cmd, I enter:
    diskpart
    list disk
    select disk 2
    clean
    convert mbr
    exit
    exit

    and then select the disk with unallocated space and try to install win 10.
    and in 2% I get a popup:

    Installation cancelled.
    Windows cannot install the required files. Make sure all files required for installation are available, and restart the installation.
    Error code: 0X8007025D

    So far I tried (with no luck):
    - switching cables
    - removing a ram

    The SSD is a Verbatim 500gb.
    My desktop pc is old and doesn't have uefi/gpt so apparently the way to go is mbr.


    When I look at the drive after the failed install I see this in Panther/setuperr.log:

    2023-10-26 16:41:08, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490]
    2023-10-26 16:42:29, Error [0x0600af] IBS ApplyWIMCallback: Error applying E:\Windows\WinSxS\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.19041.1741_none_2bdbeed55a474ed6\ImagingProvider.dll. GLE [605][gle=0x0000025d]
    2023-10-26 16:42:29, Error [0x0606cc] IBS WIMApplyImage failed; hr = 0x8007025D[gle=0x0000025d]
    2023-10-26 16:42:29, Error [0x0600a1] IBS DeployImage:Image application failed; hr = 0x8007025D[gle=0x00000057]
    2023-10-26 16:42:29, Error [0x060082] IBS Callback_ImageTransfer:Failed to lay down the OS image; hr = 0x8007025d[gle=0x00000057]


    Can someone please help?
      My Computer


  2. Posts : 43,014
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, you mention 'Disk 2'.

    I'm wondering how many disks you have in your PC when trying to install Win 10.

    Best to keep it simple. Have just your target disk in place, and ensure there are no partitions on it (deleting partitions is an option in the installation sequence).

    Clean Install Windows 10
      My Computers


  3. Posts : 15
    win 10
    Thread Starter
       #3

    Thanks dalchina.
    Will try it and report back.

    - - - Updated - - -

    dalchina said:
    Hi, you mention 'Disk 2'.

    I'm wondering how many disks you have in your PC when trying to install Win 10.

    Best to keep it simple. Have just your target disk in place, and ensure there are no partitions on it (deleting partitions is an option in the installation sequence).

    Clean Install Windows 10
    So I've unplugged the other 2 discs, and left only the SSD, without partitions (unallocated).
    Still getting the same error.

    Any more ideas?
      My Computer


  4. Posts : 18,432
    Windows 11 Pro
       #4

    You have a corrupt installation media (USB flash drive or DVD). Create a new one with the Microsoft Media Creation Tool.
      My Computer


  5. Posts : 15
    win 10
    Thread Starter
       #5

    Thanks NavyLCDR.
    I've created and tested the USB 2 times but from the same file/method (windows media creation tool), and none of the times worked.
    But I'm reading the info here:
    Create Bootable USB Flash Drive to Install Windows 10

    and will test other method/s / ISO and report back.
      My Computer


  6. Posts : 43,014
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #6

    I'm wondering where the reference to drive E: comes from:
    Error applying E:\Windows\WinSxS\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.19041.1741_none_2bdbeed55a474ed6\ImagingProvider.dll.
    - do you have any other external drives plugged in?
      My Computers


  7. Posts : 6,347
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #7

    I suggest you build the USB Win 10 22h2 installation drive using MCT so it can boot as Legacy or UEFI.

    Windows can be installed in two ways: Legacy-MBR or UEFI-GPT
    To install as Legacy-MBR you must boot the installation drive as Legacy
    To install as UEFI-GPT you must boot the installation drive as UEFI.

    If you have a UEFI BIOS, you should install as UEFI-GPT
    Detach any other drives (SATA or Power cable) from the MB.

    During POST, press F12(?) to launch the boot menu. You will see two options for the USB drive. USB UEFI (Name) and USB (Name). Select USB UEFI (Name) if you want to install as UEFI-GPT or select USB (name) if you want to install as Legacy-MBR.
    Go to install and delete ALL partitions on the main drive till you have one and only one unallocated space and then proceed.
    If you don't want to use MS account, don't enable updates or connect to the internet during installation.
      My Computers


  8. Posts : 15
    win 10
    Thread Starter
       #8

    Thanks both.

    The desktop in question is quite old (15 years? maybe) and the BIOS doesn't have UEFI.
    The USB created with the MCT aren't working. Tested 2 times. Same error.

    New test:
    I downloaded the following ISO from Microsoft using the Apple ipad trick (from the link above)
    Win10_22H2_English_x64v1.iso

    and used the Create_a_bootable_Windows_USB_device.bat to create a brand new bootable USB.
    Then I unplugged the other hard drives, booted from the USB,
    shift+f10
    diskpart
    list disk
    select disk 0
    clean (this removes all partitions)
    convert mbr
    exit
    exit

    went to install with the drive with 100% unallocated space and.. still the same error.

    When I look at the files installed tho I see more files (not completed obviously, as it stopped at 1%).
    See pic.
    Error code: 0X8007025D - Win 10 install on old desktop with a new SSD-usb-install-truncated.png


    And the log in windowsbt/sources/panther/setuperr.log

    2023-10-27 15:08:09, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490]
    2023-10-27 15:08:55, Error [0x0600af] IBS ApplyWIMCallback: Error applying E:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-setup_31bf3856ad364e35_10.0.19041.1266_none_22b99d078bbc3016\setup_wm.exe. GLE [1392][gle=0x00000570]
    2023-10-27 15:08:55, Error [0x0606cc] IBS WIMApplyImage failed; hr = 0x80070570[gle=0x00000570]
    2023-10-27 15:08:55, Error [0x0600a1] IBS DeployImage:Image application failed; hr = 0x80070570[gle=0x00000057]
    2023-10-27 15:08:55, Error [0x060082] IBS Callback_ImageTransfer:Failed to lay down the OS image; hr = 0x80070570[gle=0x00000057]


    The e: drive is the SSD apparently. No other external drives, apart from the USB.

    Any ideas?
      My Computer


  9. Posts : 6,347
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #9

    I would say that the main drive has a problem. Do you have another drive (SSD or HDD) to use on that computer?
    Can you install the SSD drive into another computer to test it?

    Try Bob.Omb’s Modified Win10PEx64 v4.985. It's a Win PE with many tools so you can test the computer and the drive.
    Bob.Omb's Modified Win10PEx64 v4.985 - FC Portables: Download Portable Software and ISO!

    To make Bob.Omb’s Modified Win10PEx64 boot able drive:

    Open a CMD window as administrator and type:

    diskpart
    list disk (it will list all drives. Identify the USB drive number)
    select disk n (replace n by the USB drive number obtained with list disk)
    clean
    convert mbr
    create part primary
    select part 1
    format fs=fat32 quick
    assign
    active
    exit (to exit diskpart)

    On Win 10, mount the iso file and copy all files and folders to the USB drive.
      My Computers


  10. Posts : 15
    win 10
    Thread Starter
       #10

    The desktop has 2 HD. The main one went corrupt, and am currently using the backup one (a super old HD).

    The SSD is a brand new Verbatim 500, never used (not refurbished). Is highly unlikely that that's the problem.
    I changed the cables just to be sure, but still got the same error.
    Unfortunately I don't have another pc to test it.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:40.
Find Us




Windows 10 Forums