• Re: Windows Install problem - error code 0x8007025D

    From Jeff Gaines@21:1/5 to All on Mon Jul 31 17:06:38 2023
    On 31/07/2023 in message <ua8nsa$3ao08$1@dont-email.me> Abandoned_Trolley wrote:

    I am a bit reluctant to update the BIOS unless thats the only sensible
    next option, but in the meantime would be interested to hear from anybody >else who has come across this problem before

    I have found with some machines that you have to pull/disconnect all
    storage device except the boot device before installing. Symptoms of not
    doing that are an apparently successful install which on re-booting can't
    find the boot device and Program Files tucked away on the "D" drive or elsewhere.

    On the BIOS front I have been building PCs for 30 years and have always
    updated the BIOS and never had a problem. In the good old days some things didn't work without a BIOS update!

    --
    Jeff Gaines Dorset UK
    Remember, the Flat Earth Society has members all around the globe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Abandoned_Trolley@21:1/5 to All on Mon Jul 31 17:35:21 2023
    I am having some problems with a virgin install of Windows

    (thats Win 10 21H2, Win 10 22H2 and Win 11 23H2) on a system which I
    have recently built from parts.

    It's an ASUS Prime B460 PLUS Motherboard, with an Intel i7 processor and
    32GB of DDR4. Theres a Crucial M.2 1Tb SSD running in PCIe mode
    (although this problem shows up with 2 other SATA SSDs)


    Basically the install crashes out part way through with "error code
    0x8007025D"


    It has been suggested to me that the SSD needs to be "cleaned" and
    converted to MBR and I have used diskpart to do this, but it makes no difference to the result (although subjectively it seemed to get a lot
    further in to the install before crashing)


    I am a bit reluctant to update the BIOS unless thats the only sensible
    next option, but in the meantime would be interested to hear from
    anybody else who has come across this problem before


    AT


    --
    random signature text inserted here

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jaimie Vandenbergh@21:1/5 to fred@fredsmith.co.uk on Mon Jul 31 17:26:23 2023
    On 31 Jul 2023 at 17:35:21 BST, "Abandoned_Trolley"
    <fred@fredsmith.co.uk> wrote:

    I am a bit reluctant to update the BIOS

    Do it now. There should be no reluctance on this, it'll do things like
    make booting from newer NVMe sticks work.

    Cheers - Jaimie
    --
    It's all fun and games until someone loses an eye. Then it's a scavenger hunt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From GB@21:1/5 to All on Mon Jul 31 18:50:43 2023
    On 31/07/2023 17:35, Abandoned_Trolley wrote:

    Basically the install crashes out part way through with "error code 0x8007025D"

    When I google that error code, there are loads of suggestions. I don't
    see what we can add?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Abandoned_Trolley@21:1/5 to All on Mon Jul 31 21:32:34 2023
    On 31/07/2023 18:50, GB wrote:
    On 31/07/2023 17:35, Abandoned_Trolley wrote:

    Basically the install crashes out part way through with "error code
    0x8007025D"

    When I google that error code, there are loads of suggestions. I don't
    see what we can add?





    yeah, I got loads of suggestions as well.

    I raised the subject in here partly in the hope of finding somebody who
    had the same problem AND found a solution ...



    --
    random signature text inserted here

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Caspersz@21:1/5 to All on Tue Aug 1 10:18:56 2023
    On 7/31/23 21:32, Abandoned_Trolley wrote:
    On 31/07/2023 18:50, GB wrote:
    On 31/07/2023 17:35, Abandoned_Trolley wrote:

    Basically the install crashes out part way through with "error code
    0x8007025D"

    When I google that error code, there are loads of suggestions. I don't
    see what we can add?





    yeah, I got loads of suggestions as well.

    I raised the subject in here partly in the hope of finding somebody who
    had the same problem AND found a solution ...


    Dunno.

    In the old days of installing Windows operating systems, with disk
    system that were initially strange to windows (software RAID, AHCI, SCSI
    etc), it was necessary to provide storage related drivers on some media
    device (USB, floppy) before continuing on.

    Is your issue similar to

    Windows 10 11 SSD M.2 PCIe NVMe Not Detected How to Fix VMD Intel RST
    Raid Driver Repair Install
    https://www.youtube.com/watch?v=YtU977t0MQI


    --
    Adrian C

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Abandoned_Trolley@21:1/5 to All on Tue Aug 1 14:03:37 2023

    In the old days of installing Windows operating systems, with disk
    system that were initially strange to windows (software RAID, AHCI, SCSI etc), it was necessary to provide storage related drivers on some media device (USB, floppy) before continuing on.

    Is your issue similar to

    Windows 10 11 SSD M.2 PCIe NVMe Not Detected How to Fix VMD Intel RST
    Raid Driver Repair Install
    https://www.youtube.com/watch?v=YtU977t0MQI




    no - the M.2 drive is detected, and I am offered various partitions and
    free spaces before the install is attempted.

    When it eventually crashes out, theres are a couple of partitions
    created by the install process

    I get exactly the same response / result from 2 other SATA SSDs, and a
    SATA spinning rust drive

    Also, the drives, DVDs and USB sticks are all correctly identified by
    the BIOS



    --
    random signature text inserted here

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Gaines@21:1/5 to All on Tue Aug 1 13:56:17 2023
    On 01/08/2023 in message <uaavra$3lnl1$1@dont-email.me> Abandoned_Trolley wrote:



    In the old days of installing Windows operating systems, with disk system >>that were initially strange to windows (software RAID, AHCI, SCSI etc),
    it was necessary to provide storage related drivers on some media device >>(USB, floppy) before continuing on.

    Is your issue similar to

    Windows 10 11 SSD M.2 PCIe NVMe Not Detected How to Fix VMD Intel RST
    Raid Driver Repair Install
    https://www.youtube.com/watch?v=YtU977t0MQI




    no - the M.2 drive is detected, and I am offered various partitions and
    free spaces before the install is attempted.

    When it eventually crashes out, theres are a couple of partitions created
    by the install process

    I get exactly the same response / result from 2 other SATA SSDs, and a
    SATA spinning rust drive

    Also, the drives, DVDs and USB sticks are all correctly identified by the >BIOS

    Have you tried disconnecting all drives except the install drive before installing?

    --
    Jeff Gaines Dorset UK
    That's an amazing invention but who would ever want to use one of them? (President Hayes speaking to Alexander Graham Bell on the invention of the telephone)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Abandoned_Trolley@21:1/5 to All on Tue Aug 1 15:10:22 2023

    Have you tried disconnecting all drives except the install drive before installing?




    Yes - single SSD on a SATA port, no DVD drive - and boot from USB stick


    --
    random signature text inserted here

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Gaines@21:1/5 to All on Tue Aug 1 14:26:44 2023
    On 01/08/2023 in message <uab3oe$3m5a9$1@dont-email.me> Abandoned_Trolley wrote:



    Have you tried disconnecting all drives except the install drive before >>installing?




    Yes - single SSD on a SATA port, no DVD drive - and boot from USB stick

    OK. The other issue I have come across is confusion between MBR/GPT, BIOS/Legacy/UEFI and secure boot/no secure boot.

    They all need to line up but if I try to explain you will end up
    thoroughly confused so I'll leave it to others - you may not need an explanation of course!

    --
    Jeff Gaines Dorset UK
    Politics is the art of looking for trouble, finding it whether it exists
    or not, diagnosing it incorrectly, and applying the wrong remedies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Abandoned_Trolley@21:1/5 to All on Tue Aug 1 15:33:32 2023
    OK. The other issue I have come across is confusion between MBR/GPT, BIOS/Legacy/UEFI and secure boot/no secure boot.

    They all need to line up but if I try to explain you will end up
    thoroughly confused so I'll leave it to others - you may not need an explanation of course!



    I think that may be the problem too.

    I have tried using diskpart to clean the disc and convert to MBR with no
    luck, so I cleaned it again and converted to GPT with the same result.

    I suspect that as you say they all need to "line up" and in the meantime
    I am a little reluctant to update the BIOS.

    I have also tried loading Windows 7 from an install DVD, in the hope
    that I could update that to W10 in situ, but that didnt get very far either.


    --
    random signature text inserted here

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)