Windows Install problem - error code 0x8007025D

[Abandoned_Trolley]

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

[Jeff Gaines]

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.

[Jaimie Vandenbergh]

On 31 Jul 2023 at 17:35:21 BST, "Abandoned_Trolley"

<fr...@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.

[GB]

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?

[Abandoned_Trolley]

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 ...

[Adrian Caspersz]

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

[Abandoned_Trolley]

>
> 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

[Jeff Gaines]

On 01/08/2023 in message <uaavra$3lnl1$1...@dont-email.me> Abandoned_Trolley
wrote:

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)

[Abandoned_Trolley]

>
> 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

[Jeff Gaines]

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.

[Abandoned_Trolley]

> 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.

[Abandoned_Trolley]

On 01/08/2023 15:26, Jeff Gaines wrote:
> 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!
>

so ... I bit the bullet and did a BIOS update - which was of course a
lot less trouble than I imagined

and now I have a new problem - with error code ox80070570


This apparently relates to some corrupted media

So I have downloaded (again) the latest Media Creation Tool, and used it
to create a bootable USB stick (a brand new Kingston stick)

and will have another try later ..

hey ho

[Jeff Gaines]

On 03/08/2023 in message <uag10o$nq29$1...@dont-email.me> Abandoned_Trolley
wrote:

Good luck, there is some good technical support in here if you have issues.

If you want an MBR install (I still use MBR) then ensure the disk your are
installing to is set up as MBR and set up the partition you want to
install to - sometimes it's easier to do that by hanging it off another
machine via a connector/USB and use something like Mini Tool Partition
Wizard with its neat GUI.

--
Jeff Gaines Dorset UK

If Björn & Benny had been called Syd and Dave then ABBA would have been
called ASDA.

[Abandoned_Trolley]

well ... you might be amused to learn that the problem was caused by a
faulty memory stick :-\

I would have tried some diagnostics before but none of those "universal"
bootable CD things would even boot up on the system.

I eventually found an iso which agreed to boot up and then started
memtest86 which revealed the problem

And now ? The current system seems happy to boot up Win 10 / Win 11 and
Ubuntu - and appears not to care a jot about any GPT / MBR / EUFI /
Secure BIOS variables

[Jeff Gaines]

On 15/08/2023 in message <ubfbjf$2o9ep$1...@dont-email.me> Abandoned_Trolley
wrote:

>well ... you might be amused to learn that the problem was caused by a
>faulty memory stick :-\
>
>I would have tried some diagnostics before but none of those "universal"
>bootable CD things would even boot up on the system.
>
>I eventually found an iso which agreed to boot up and then started
>memtest86 which revealed the problem
>
>And now ? The current system seems happy to boot up Win 10 / Win 11 and
>Ubuntu - and appears not to care a jot about any GPT / MBR / EUFI / Secure
>BIOS variables

Tedious but satisfying to find the issue :-)

--
Jeff Gaines Dorset UK

Those are my principles – and if you don’t like them, well, I have
others.
(Groucho Marx)