Can't update to 2004. Can BIOS update help?

Windows 10 version 2004 has now hit Norway. Unfortunately it will not
install on my DIY PC. The installation goes to around 90%, and then
the screen returns to my normal Windows 10 1909. The message in
Windows update is simply that it can't update, and a code, something
like 000000x0.
I got in contact with a person from Microsoft Norway. She logged in to
my PC and did some cheks that corrected some errors, and then started
a download of Windows 10 to my PC, and asked me to start the
installation with marking for keep apps and user files, when the
download had finished.
The motherboard in my PC is ASUS F2A85-M LE from around 2012,
processor is AMD A10-5800. She suggested that it could be an issue
with the somerwhat old hardware that stopped the 2004 update, and that
I could try updating the BIOS and drivers for the motherboard if 2004
still would'nt install.
So when the download of Win10 had finished I started the install, and
it also stopped at around 90%. Tried 2 times with the same result.
So what to do now? I have downloaded a newer version of the BIOS, but
I am reluctant to install it, fearing that it will go wrong and brick
the PC. Any suggestions?

Best regards
--
Jesper Kaas -

On 2020-07-28 00:36, Jesper Kaas wrote:
Windows 10 version 2004 has now hit Norway. Unfortunately it will not
install on my DIY PC. The installation goes to around 90%, and then
the screen returns to my normal Windows 10 1909. The message in
Windows update is simply that it can't update, and a code, something
like 000000x0.
I got in contact with a person from Microsoft Norway. She logged in to
my PC and did some cheks that corrected some errors, and then started
a download of Windows 10 to my PC, and asked me to start the
installation with marking for keep apps and user files, when the
download had finished.
The motherboard in my PC is ASUS F2A85-M LE from around 2012,
processor is AMD A10-5800. She suggested that it could be an issue
with the somerwhat old hardware that stopped the 2004 update, and that
I could try updating the BIOS and drivers for the motherboard if 2004
still would'nt install.
So when the download of Win10 had finished I started the install, and
it also stopped at around 90%. Tried 2 times with the same result.
So what to do now? I have downloaded a newer version of the BIOS, but
I am reluctant to install it, fearing that it will go wrong and brick
the PC. Any suggestions?

Best regards


Hi Jasper,

I hate upgrading BIOS'es as I have had them brick
on me.

The only thing I can suggest, and I do not think it
will help, would be to create a Flash drive of
the installer, then boot off it and do an in place
upgrade. Who knows, you might get lucky

-T

Jesper Kaas wrote:
Windows 10 version 2004 has now hit Norway. Unfortunately it will not
install on my DIY PC. The installation goes to around 90%, and then
the screen returns to my normal Windows 10 1909. The message in
Windows update is simply that it can't update, and a code, something
like 000000x0.
I got in contact with a person from Microsoft Norway. She logged in to
my PC and did some cheks that corrected some errors, and then started
a download of Windows 10 to my PC, and asked me to start the
installation with marking for keep apps and user files, when the
download had finished.
The motherboard in my PC is ASUS F2A85-M LE from around 2012,
processor is AMD A10-5800. She suggested that it could be an issue
with the somerwhat old hardware that stopped the 2004 update, and that
I could try updating the BIOS and drivers for the motherboard if 2004
still would'nt install.
So when the download of Win10 had finished I started the install, and
it also stopped at around 90%. Tried 2 times with the same result.
So what to do now? I have downloaded a newer version of the BIOS, but
I am reluctant to install it, fearing that it will go wrong and brick
the PC. Any suggestions?

Best regards

It's an 8 year old processor and quite nice. 4C 4T. AMD64.

http://www.cpu-world.com/CPUs/Bulldo...A10-5800K.html

It is an APU and has built-in GPU for graphics. 384 shaders.

Driver updates from AMD, likely stopped some time ago, as they did
for my AMD video card.

*******

There is a tool to summarize what happened.

You can test it for us. (The last poster who I offered this to,
would not test if for me. Needs a failed install for best test result.)

https://docs.microsoft.com/en-us/win...rade/setupdiag

https://go.microsoft.com/fwlink/?linkid=870142 === immediate download link

SetupDiag.exe 585,136 bytes

What that does, is just read a couple .log files and extract
key lines from them. SetupDiag likely isn't an "IT bod in a can".
It's not going to know what the root cause is, but we'll see
when you test it.

*******

My preferred method would be:

1) Go to Microsoft download page on the web.

https://www.microsoft.com/en-gb/soft...load/windows10

2) Using "MediaCreationTool" which is delivered in step (1)
to "create media for another PC". This can be in the form
of an ISO file if you want, saved to the hard drive.

Windows10-x64-2004.iso 4,144,168,960 bytes

That is the 7 OS version of the 64-bit disc.

3) Right click "Windows10-x64-2004.iso". Select "Mount"

This prepares the ISO in its own virtual DVD drive, so
no media need be burned to do this step. At the end of phase1
of the install, the image will automatically be dismounted and
ignored for the rebooting phases.

4) Double-click on "Setup.exe" at the top level of the virtual DVD
drive, which will start the install.

This method of installing does not pre-stage drivers.

The Windows Update method, seeks to pre-stage drivers and
then it does the upgrade.

This is not much of an improvement, but it's another way to
attempt to finish the job. It can force an Upgrade into a
machine with an FX5200 video card, for example.

*******

Summary: SetupDiag might be able to explain the problem.

Failure at the 90% point, could well be a localization
issue. Some users install separate MUI packages, and normally
the instructions page for such materials, tells you the MUI
must be uninstalled before upgrades. That's the only
"excuse" I can offer for this failure. Installing multiple
languages on Windows computers is past my pay scale.

Paul

On Tue, 28 Jul 2020 05:19:10 -0400, Paul
wrote:



It's an 8 year old processor and quite nice. 4C 4T. AMD64.

http://www.cpu-world.com/CPUs/Bulldo...A10-5800K.html

It is an APU and has built-in GPU for graphics. 384 shaders.

Driver updates from AMD, likely stopped some time ago, as they did
for my AMD video card.

Yes it is a nice PC, doing what I need it to do, so it is a shame to
waste it just because of updates not coming in.
*******

There is a tool to summarize what happened.

You can test it for us. (The last poster who I offered this to,
would not test if for me. Needs a failed install for best test result.)

https://docs.microsoft.com/en-us/win...rade/setupdiag

https://go.microsoft.com/fwlink/?linkid=870142 === immediate download link

SetupDiag.exe 585,136 bytes
I ran the SetupDiag tool, and it created some files here on my C-disc:
Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date
24.07.2020 16:43:29 to be the correct setup log.
Found C:\$WINDOWS.~BT\Sources\Rollback\setupact.log with update date
24.07.2020 21:56:43 to be the correct rollback log.
....and here are hopefully links to the four files, 2 from Setup and 2
from Rollback:
https://www.dropbox.com/s/s9s3c1e2ke...upact.log?dl=0
https://www.dropbox.com/s/v3hvecce8e...uperr.log?dl=0
https://www.dropbox.com/s/2v4ud5zkx9...upact.log?dl=0
https://www.dropbox.com/s/hhj6s4clpz...uperr.log?dl=0



What that does, is just read a couple .log files and extract
key lines from them. SetupDiag likely isn't an "IT bod in a can".
It's not going to know what the root cause is, but we'll see
when you test it.

*******

My preferred method would be:

1) Go to Microsoft download page on the web.

https://www.microsoft.com/en-gb/soft...load/windows10

2) Using "MediaCreationTool" which is delivered in step (1)
to "create media for another PC". This can be in the form
of an ISO file if you want, saved to the hard drive.

Windows10-x64-2004.iso 4,144,168,960 bytes

That is the 7 OS version of the 64-bit disc.

3) Right click "Windows10-x64-2004.iso". Select "Mount"

This prepares the ISO in its own virtual DVD drive, so
no media need be burned to do this step. At the end of phase1
of the install, the image will automatically be dismounted and
ignored for the rebooting phases.

4) Double-click on "Setup.exe" at the top level of the virtual DVD
drive, which will start the install.

This method of installing does not pre-stage drivers.

The Windows Update method, seeks to pre-stage drivers and
then it does the upgrade.

I think what you describe here is what Filipina from Microsoft did.
She left a link called MediaCreationTool on the desktop, and clicking
that starts the process of downloading and installing the full Win10
2004. But unfortunately it stops.

This is not much of an improvement, but it's another way to
attempt to finish the job. It can force an Upgrade into a
machine with an FX5200 video card, for example.

*******

Summary: SetupDiag might be able to explain the problem.

Failure at the 90% point, could well be a localization
issue. Some users install separate MUI packages, and normally
the instructions page for such materials, tells you the MUI
must be uninstalled before upgrades. That's the only
"excuse" I can offer for this failure. Installing multiple
languages on Windows computers is past my pay scale.

Paul
I made the installation of Windows 10 without making any change to
what Microsoft wanted done and where to put things. Made it on a cheap
spinner and later cloned it to a 1 TB SSD. Maybe I did a blunder by
not removing the USB stick when the installer asked for a restart.
Perhaps therefore there is aWindows PE isted in the BIOS' boot
options.
--
Jesper Kaas -

To read posts in this newsgroup, you need Mozilla Thunderbird and HTML enabled. You won't see this if you are using the correct modern application.

If you can't use Thunderbird then please kill-file my posts as they will only frustrate you and make you angry unnecessarily.

--

With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Jesper Kaas wrote:

I ran the SetupDiag tool, and it created some files here on my C-disc:
Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date
24.07.2020 16:43:29 to be the correct setup log.
Found C:\$WINDOWS.~BT\Sources\Rollback\setupact.log with update date
24.07.2020 21:56:43 to be the correct rollback log.
...and here are hopefully links to the four files, 2 from Setup and 2
from Rollback:
https://www.dropbox.com/s/s9s3c1e2ke...upact.log?dl=0
https://www.dropbox.com/s/v3hvecce8e...uperr.log?dl=0
https://www.dropbox.com/s/2v4ud5zkx9...upact.log?dl=0
https://www.dropbox.com/s/hhj6s4clpz...uperr.log?dl=0

I think what you describe here is what Filipina from Microsoft did.
She left a link called MediaCreationTool on the desktop, and clicking
that starts the process of downloading and installing the full Win10
2004. But unfortunately it stops.

I made the installation of Windows 10 without making any change to
Made it on a cheap spinner and later cloned it to a 1 TB SSD.
^^^^^^
||||||

Cloned it with what exactly ?

I suspect something is wrong with one of these disk identifiers.
Maybe it is actually looking for the old spinner ?

2020-07-24 16:43:27, Info SP BFSVC: BfsInitializeBcdStore flags(0x00001008) RetainElementData:n DelExistinObject:n

2020-07-24 16:43:27, Info SP BFSVC: VolumePathName for C:\$WINDOWS.~BT\NewOS\WINDOWS is C:\
2020-07-24 16:43:27, Info SP BFSVC: Opening template from \Device\HarddiskVolume3\$WINDOWS.~BT\NewOS\WINDOWS \System32\config\BCD-Template.
2020-07-24 16:43:27, Info SP BFSVC: Reopening system store.

2020-07-24 16:43:27, FatalError SP Exception handler called! Details:
2020-07-24 16:43:27, FatalError SP Exception record: 0
2020-07-24 16:43:27, FatalError SP Exception code: 0xc0000005
2020-07-24 16:43:27, FatalError SP Exception flags: 0x0
2020-07-24 16:43:27, FatalError SP Exception address: 00007FFCDEB8D25D
2020-07-24 16:43:27, FatalError SP Exception parameter 0: 0000000000000000
2020-07-24 16:43:27, FatalError SP Exception parameter 1: 0000000000000000
2020-07-24 16:43:27, Info SP SEH: Attempting to log exception
2020-07-24 16:43:27, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFCDEB8D25D in C:\$WINDOWS.~BT\Sources\SetupPlatform.dll (+00000000003ED25D). Minidump attached (144370 bytes) to diagerr.xml and C:\$WINDOWS.~BT\Sources\Panther\mnd79F7.diagerr.md mp.

Rollback setupact - the EFI partition (ESP) shouldn't have a drive letter.
- that seems a bit strange.

2020-07-24 21:56:39, Info [0x064165] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: "H:\EFI\Microsoft\Boot" exists, obliterating.
2020-07-24 21:56:42, Info [0x064166] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: DeletePath(H:\EFI\Microsoft\Boot) failed, will try to overwrite.[gle=0x00000020]
2020-07-24 21:56:42, Info [0x064169] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: Copying from "C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Bo ot" to "H:\EFI\Microsoft\Boot".

*******

Now that the OS is back to normal, it probably needs boot repair.

What you should know about that, is boot repairs are not very
"ambitious". They are not allowed to create or delete partitions,
resize partitions, change partition types. They can write a
new BCD file. As a consequence of this, not all distortions of
boot materials can be repaired. If a user deletes a key partition,
it's not going to create a new one and populate it.

The reason for being so weak, is the theory that such weakness
avoids damaging customer configurations. Fewer lawsuits.

And naturally we know, if you do a Repair Install right now, it
will fail exactly the same way. So you can't necessarily get out
of this the "easy way".

What you *could* do, is put the spinner back in the box, boot
from the SSD, install Windows 10 2004 as intended. Some of the
boot setup will be written to the spinner. There will be some
confusion about identifiers. Whether this is the case or not,
depends on the cloning method. If you do a sector-by-sector copy
of the drive (something cloning utilities do not normally do), then
all the disk identifiers are duplicated, and this is a bad thing.

The installation might complete.

But, now you have both spinner and SSD in the computer. If
you unplug the spinner, now it will fail to boot.

Then what do we do ??? Hmmm.

You really have to fix it, using wit and cunning. No cheating :-)

*******

Macrium Reflect Free has a Boot Repair on their Rescue CD.

"Home User", on the left, 50% of the way down the page.

https://www.macrium.com/reflectfree

With *only* the SSD hooked up in the computer, you would
attempt to repair the boot materials, ticking as many
boxes as you could manage (there are four items with tick
boxes that it can repair). It will assign new GUID values,
regenerate a new BCD, and it should hook up the System Reserved
and so on. I don't know how skillful it is at fixing GPT disks
and the EFI (ESP) partition contents. If you deleted a key partition,
it can't fix that.

The article here, shows some pictures of the questions
you would be asked while using the Rescue CD boot repair.

https://kb.macrium.com/KnowledgebaseArticle50168.aspx

*******

Summary:

Something is wrong with boot materials. Either something
in System Reserved, or something is wrong with the ESP on
the GPT-partitioned SSD drive. The ESP is a FAT32 partition
with an EFI folder in it. The partition type (as seen by
gdisk in Linux) is EF01. That partition is not normally
visible and it's a bit weird if it got a drive letter.

It did all that work on the first phase of
installation, but it was unable to do something to the
boot materials near the end. Just a guess.

Now, if this was the case, how did the OS survive
for this long ? Some of the Windows Updates make
adjustments to boot, and how did all of those
not run into a similar kind of problem ?

Paul

On Tue, 28 Jul 2020 13:37:21 -0400, Paul
wrote:

Jesper Kaas wrote:

I ran the SetupDiag tool, and it created some files here on my C-disc:
Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date
24.07.2020 16:43:29 to be the correct setup log.
Found C:\$WINDOWS.~BT\Sources\Rollback\setupact.log with update date
24.07.2020 21:56:43 to be the correct rollback log.
...and here are hopefully links to the four files, 2 from Setup and 2
from Rollback:
https://www.dropbox.com/s/s9s3c1e2ke...upact.log?dl=0
https://www.dropbox.com/s/v3hvecce8e...uperr.log?dl=0
https://www.dropbox.com/s/2v4ud5zkx9...upact.log?dl=0
https://www.dropbox.com/s/hhj6s4clpz...uperr.log?dl=0

I think what you describe here is what Filipina from Microsoft did.
She left a link called MediaCreationTool on the desktop, and clicking
that starts the process of downloading and installing the full Win10
2004. But unfortunately it stops.

I made the installation of Windows 10 without making any change to
Made it on a cheap spinner and later cloned it to a 1 TB SSD.
^^^^^^
||||||

Cloned it with what exactly ?
Macrium Reflect Home

I suspect something is wrong with one of these disk identifiers.
Maybe it is actually looking for the old spinner ?
Yes. Please se below.

2020-07-24 16:43:27, Info SP BFSVC: BfsInitializeBcdStore flags(0x00001008) RetainElementData:n DelExistinObject:n

2020-07-24 16:43:27, Info SP BFSVC: VolumePathName for C:\$WINDOWS.~BT\NewOS\WINDOWS is C:\
2020-07-24 16:43:27, Info SP BFSVC: Opening template from \Device\HarddiskVolume3\$WINDOWS.~BT\NewOS\WINDOWS \System32\config\BCD-Template.
2020-07-24 16:43:27, Info SP BFSVC: Reopening system store.

2020-07-24 16:43:27, FatalError SP Exception handler called! Details:
2020-07-24 16:43:27, FatalError SP Exception record: 0
2020-07-24 16:43:27, FatalError SP Exception code: 0xc0000005
2020-07-24 16:43:27, FatalError SP Exception flags: 0x0
2020-07-24 16:43:27, FatalError SP Exception address: 00007FFCDEB8D25D
2020-07-24 16:43:27, FatalError SP Exception parameter 0: 0000000000000000
2020-07-24 16:43:27, FatalError SP Exception parameter 1: 0000000000000000
2020-07-24 16:43:27, Info SP SEH: Attempting to log exception
2020-07-24 16:43:27, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFCDEB8D25D in C:\$WINDOWS.~BT\Sources\SetupPlatform.dll (+00000000003ED25D). Minidump attached (144370 bytes) to diagerr.xml and C:\$WINDOWS.~BT\Sources\Panther\mnd79F7.diagerr.md mp.

Rollback setupact - the EFI partition (ESP) shouldn't have a drive letter.
- that seems a bit strange.
The "H:\" is actually the old spinner. It has been reformated since it
had the Win10 installation, and is now used just for temporary
storing. Right now it is not connected, but it was when the attempts
to upgrade to 2004 were done. The PC boots OK without old spinner
connected.

2020-07-24 21:56:39, Info [0x064165] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: "H:\EFI\Microsoft\Boot" exists, obliterating.
2020-07-24 21:56:42, Info [0x064166] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: DeletePath(H:\EFI\Microsoft\Boot) failed, will try to overwrite.[gle=0x00000020]
2020-07-24 21:56:42, Info [0x064169] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: Copying from "C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Bo ot" to "H:\EFI\Microsoft\Boot".

*******

Now that the OS is back to normal, it probably needs boot repair.
In fact I had a boot problem after cloning the spinner with Win 10 to
SSD, and used Macrium Reflect to fix the boot, and then it booted OK.
Both with and without the old spinner connected.
I think we have nailed the causes:
1: Not removing the the installation media (USB) at right time when
rebooting during the installation of Win10 to spinner.
2: Maybe my deleting a partition that looked to be obsolete damaged
something.

What you should know about that, is boot repairs are not very
"ambitious". They are not allowed to create or delete partitions,
resize partitions, change partition types. They can write a
new BCD file. As a consequence of this, not all distortions of
boot materials can be repaired. If a user deletes a key partition,
it's not going to create a new one and populate it.

The reason for being so weak, is the theory that such weakness
avoids damaging customer configurations. Fewer lawsuits.

And naturally we know, if you do a Repair Install right now, it
will fail exactly the same way. So you can't necessarily get out
of this the "easy way".

What you *could* do, is put the spinner back in the box, boot
from the SSD, install Windows 10 2004 as intended. Some of the
boot setup will be written to the spinner. There will be some
confusion about identifiers. Whether this is the case or not,
depends on the cloning method. If you do a sector-by-sector copy
of the drive (something cloning utilities do not normally do), then
all the disk identifiers are duplicated, and this is a bad thing.

The installation might complete.

But, now you have both spinner and SSD in the computer. If
you unplug the spinner, now it will fail to boot.

Then what do we do ??? Hmmm.

You really have to fix it, using wit and cunning. No cheating :-)

*******

Macrium Reflect Free has a Boot Repair on their Rescue CD.

"Home User", on the left, 50% of the way down the page.

https://www.macrium.com/reflectfree

With *only* the SSD hooked up in the computer, you would
attempt to repair the boot materials, ticking as many
boxes as you could manage (there are four items with tick
boxes that it can repair). It will assign new GUID values,
regenerate a new BCD, and it should hook up the System Reserved
and so on. I don't know how skillful it is at fixing GPT disks
and the EFI (ESP) partition contents. If you deleted a key partition,
it can't fix that.

The article here, shows some pictures of the questions
you would be asked while using the Rescue CD boot repair.

https://kb.macrium.com/KnowledgebaseArticle50168.aspx

*******

Summary:

Something is wrong with boot materials. Either something
in System Reserved, or something is wrong with the ESP on
the GPT-partitioned SSD drive. The ESP is a FAT32 partition
with an EFI folder in it. The partition type (as seen by
gdisk in Linux) is EF01. That partition is not normally
visible and it's a bit weird if it got a drive letter.
Macrium shows 3 partitions on the SSD. Number 1 is NO NAME (none)
FAT32(LBA) Primary, 26.3 MB, 99 MB total, number 2 is labelled 2 -
(None) Unformatted primary, 16 MB used 16 MB total, number 3 is
labelled 3 - Win10(C) NTFS Primary, 139 GB used, 930 GB total. There
is 530 MB unallocated in the beginning of the disc from a partition I
deleted
Windows diskhandling shows the following: First 530 MB unallocated,
second 99 MB OK (EFI-systempartition), third WIN10 (C OK (Boot,
pagefile, crashdump?, primary partition)

It did all that work on the first phase of
installation, but it was unable to do something to the
boot materials near the end. Just a guess.

Now, if this was the case, how did the OS survive
for this long ? Some of the Windows Updates make
adjustments to boot, and how did all of those
not run into a similar kind of problem ?

Paul

Thanks to Paul and Good Guy for excellent research and advice. By now
I think the SSD is so messed up that, like Good Guy writes, it can
take weeks to maybe repair it if at all possible.
So I will reformat the SSD, do a clean install of Win10 and all
programs. But first upgrade the BIOS.
--
Jesper Kaas -

On Tue, 28 Jul 2020 17:00:00 +0100, ? Good Guy wrote:

Hi Good Guy and thanks for your reply and advice that I will follow.
That is wiping the SSD and do a clean install of Win10 and all
programs.
Please also see my reply to Pouls latest post.
--
Jesper Kaas -

Jesper Kaas wrote:
On Tue, 28 Jul 2020 13:37:21 -0400, Paul
wrote:

Jesper Kaas wrote:

I ran the SetupDiag tool, and it created some files here on my C-disc:
Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date
24.07.2020 16:43:29 to be the correct setup log.
Found C:\$WINDOWS.~BT\Sources\Rollback\setupact.log with update date
24.07.2020 21:56:43 to be the correct rollback log.
...and here are hopefully links to the four files, 2 from Setup and 2
from Rollback:
https://www.dropbox.com/s/s9s3c1e2ke...upact.log?dl=0
https://www.dropbox.com/s/v3hvecce8e...uperr.log?dl=0
https://www.dropbox.com/s/2v4ud5zkx9...upact.log?dl=0
https://www.dropbox.com/s/hhj6s4clpz...uperr.log?dl=0

I think what you describe here is what Filipina from Microsoft did.
She left a link called MediaCreationTool on the desktop, and clicking
that starts the process of downloading and installing the full Win10
2004. But unfortunately it stops.
I made the installation of Windows 10 without making any change to
Made it on a cheap spinner and later cloned it to a 1 TB SSD.
^^^^^^
||||||

Cloned it with what exactly ?
Macrium Reflect Home
I suspect something is wrong with one of these disk identifiers.
Maybe it is actually looking for the old spinner ?
Yes. Please se below.
2020-07-24 16:43:27, Info SP BFSVC: BfsInitializeBcdStore flags(0x00001008) RetainElementData:n DelExistinObject:n

2020-07-24 16:43:27, Info SP BFSVC: VolumePathName for C:\$WINDOWS.~BT\NewOS\WINDOWS is C:\
2020-07-24 16:43:27, Info SP BFSVC: Opening template from \Device\HarddiskVolume3\$WINDOWS.~BT\NewOS\WINDOWS \System32\config\BCD-Template.
2020-07-24 16:43:27, Info SP BFSVC: Reopening system store.

2020-07-24 16:43:27, FatalError SP Exception handler called! Details:
2020-07-24 16:43:27, FatalError SP Exception record: 0
2020-07-24 16:43:27, FatalError SP Exception code: 0xc0000005
2020-07-24 16:43:27, FatalError SP Exception flags: 0x0
2020-07-24 16:43:27, FatalError SP Exception address: 00007FFCDEB8D25D
2020-07-24 16:43:27, FatalError SP Exception parameter 0: 0000000000000000
2020-07-24 16:43:27, FatalError SP Exception parameter 1: 0000000000000000
2020-07-24 16:43:27, Info SP SEH: Attempting to log exception
2020-07-24 16:43:27, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFCDEB8D25D in C:\$WINDOWS.~BT\Sources\SetupPlatform.dll (+00000000003ED25D). Minidump attached (144370 bytes) to diagerr.xml and C:\$WINDOWS.~BT\Sources\Panther\mnd79F7.diagerr.md mp.

Rollback setupact - the EFI partition (ESP) shouldn't have a drive letter.
- that seems a bit strange.
The "H:\" is actually the old spinner. It has been reformated since it
had the Win10 installation, and is now used just for temporary
storing. Right now it is not connected, but it was when the attempts
to upgrade to 2004 were done. The PC boots OK without old spinner
connected.
2020-07-24 21:56:39, Info [0x064165] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: "H:\EFI\Microsoft\Boot" exists, obliterating.
2020-07-24 21:56:42, Info [0x064166] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: DeletePath(H:\EFI\Microsoft\Boot) failed, will try to overwrite.[gle=0x00000020]
2020-07-24 21:56:42, Info [0x064169] IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Ro llback: Copying from "C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Bo ot" to "H:\EFI\Microsoft\Boot".

*******

Now that the OS is back to normal, it probably needs boot repair.
In fact I had a boot problem after cloning the spinner with Win 10 to
SSD, and used Macrium Reflect to fix the boot, and then it booted OK.
Both with and without the old spinner connected.
I think we have nailed the causes:
1: Not removing the the installation media (USB) at right time when
rebooting during the installation of Win10 to spinner.
2: Maybe my deleting a partition that looked to be obsolete damaged
something.
What you should know about that, is boot repairs are not very
"ambitious". They are not allowed to create or delete partitions,
resize partitions, change partition types. They can write a
new BCD file. As a consequence of this, not all distortions of
boot materials can be repaired. If a user deletes a key partition,
it's not going to create a new one and populate it.

The reason for being so weak, is the theory that such weakness
avoids damaging customer configurations. Fewer lawsuits.

And naturally we know, if you do a Repair Install right now, it
will fail exactly the same way. So you can't necessarily get out
of this the "easy way".

What you *could* do, is put the spinner back in the box, boot
from the SSD, install Windows 10 2004 as intended. Some of the
boot setup will be written to the spinner. There will be some
confusion about identifiers. Whether this is the case or not,
depends on the cloning method. If you do a sector-by-sector copy
of the drive (something cloning utilities do not normally do), then
all the disk identifiers are duplicated, and this is a bad thing.

The installation might complete.

But, now you have both spinner and SSD in the computer. If
you unplug the spinner, now it will fail to boot.

Then what do we do ??? Hmmm.

You really have to fix it, using wit and cunning. No cheating :-)

*******

Macrium Reflect Free has a Boot Repair on their Rescue CD.

"Home User", on the left, 50% of the way down the page.

https://www.macrium.com/reflectfree

With *only* the SSD hooked up in the computer, you would
attempt to repair the boot materials, ticking as many
boxes as you could manage (there are four items with tick
boxes that it can repair). It will assign new GUID values,
regenerate a new BCD, and it should hook up the System Reserved
and so on. I don't know how skillful it is at fixing GPT disks
and the EFI (ESP) partition contents. If you deleted a key partition,
it can't fix that.

The article here, shows some pictures of the questions
you would be asked while using the Rescue CD boot repair.

https://kb.macrium.com/KnowledgebaseArticle50168.aspx

*******

Summary:

Something is wrong with boot materials. Either something
in System Reserved, or something is wrong with the ESP on
the GPT-partitioned SSD drive. The ESP is a FAT32 partition
with an EFI folder in it. The partition type (as seen by
gdisk in Linux) is EF01. That partition is not normally
visible and it's a bit weird if it got a drive letter.
Macrium shows 3 partitions on the SSD. Number 1 is NO NAME (none)
FAT32(LBA) Primary, 26.3 MB, 99 MB total, number 2 is labelled 2 -
(None) Unformatted primary, 16 MB used 16 MB total, number 3 is
labelled 3 - Win10(C) NTFS Primary, 139 GB used, 930 GB total. There
is 530 MB unallocated in the beginning of the disc from a partition I
deleted
Windows diskhandling shows the following: First 530 MB unallocated,
second 99 MB OK (EFI-systempartition), third WIN10 (C OK (Boot,
pagefile, crashdump?, primary partition)

It's missing the System Reserved partition.

Clone over a System Reserved from spinner to SSD.

Disconnect spinner.

Boot repair using Macrium CD, see if you can get System Reserved
to be used with the C: as the other partition in the pair.

When you install 2004, yet another System Reserved will be made,
this time with the 2004 version of materials in it.

The reason for "fixing it", as opposed to paving over it, is
learning how to fix stuff.

When your 2004 is completed, you'll have two System Reserved, the 2004
being "closer to C" than the other one.

https://i.postimg.cc/rwXqvwDv/partitions.gif

Paul

On Tue, 28 Jul 2020 18:06:21 -0400, Paul
wrote:

What you *could* do, is put the spinner back in the box, boot
from the SSD, install Windows 10 2004 as intended. Some of the
boot setup will be written to the spinner. There will be some
confusion about identifiers. Whether this is the case or not,
depends on the cloning method. If you do a sector-by-sector copy
of the drive (something cloning utilities do not normally do), then
all the disk identifiers are duplicated, and this is a bad thing.
This is getting too deep for me, not sure what you mean? So I connect
the spinner and from the SSD (which is now boot disc C) or an USB
install a new version of Win10 2004 to the spinner. Then what? Copy
the boot partitions from the spinner to SSD?
The spinner is now connected, and has only one partition, because I
wiped everything else to use it for a data disc.
Yes, it would be a fine learning experince to eventually fix the thing
without doing a clean install and install every program from scratch.
But by now I I think that my approach will be to copy all data from
the SSD to a datadisk, upgrade BIOS, wipe the SSD totally, and then
install everything from Win10 2004 to programs on the SSD.

One thing that puzzles me is the reference to disk H you found in the
logging. Does this mean that cloning a boot disk will not work with
2004, since the clone will contain references to the original disk
that maybe crashed or is removed?

Thanks a lot for sharing your knowledge, and spending time solving
problems for others. It is much appreciated :-)
The installation might complete.

But, now you have both spinner and SSD in the computer. If
you unplug the spinner, now it will fail to boot
No it boots fine without the spinner. The PC has only 4 connections
for SATA drives, and I use 3 for disks and the fourth for DVD.
Then what do we do ??? Hmmm.

You really have to fix it, using wit and cunning. No cheating :-)

PS: Here are links to pictures of the partitions with spinner
connected:
https://i.postimg.cc/tgh3NMKR/Partit...om-Macrium.png
https://i.postimg.cc/sXjh9DPK/Partit...om-Windows.png
--
Jesper Kaas -

Jesper Kaas wrote:
On Tue, 28 Jul 2020 18:06:21 -0400, Paul
wrote:

What you *could* do, is put the spinner back in the box, boot
from the SSD, install Windows 10 2004 as intended. Some of the
boot setup will be written to the spinner. There will be some
confusion about identifiers. Whether this is the case or not,
depends on the cloning method. If you do a sector-by-sector copy
of the drive (something cloning utilities do not normally do), then
all the disk identifiers are duplicated, and this is a bad thing.
This is getting too deep for me, not sure what you mean? So I connect
the spinner and from the SSD (which is now boot disc C) or an USB
install a new version of Win10 2004 to the spinner. Then what? Copy
the boot partitions from the spinner to SSD?
The spinner is now connected, and has only one partition, because I
wiped everything else to use it for a data disc.
Yes, it would be a fine learning experince to eventually fix the thing
without doing a clean install and install every program from scratch.
But by now I I think that my approach will be to copy all data from
the SSD to a datadisk, upgrade BIOS, wipe the SSD totally, and then
install everything from Win10 2004 to programs on the SSD.

One thing that puzzles me is the reference to disk H you found in the
logging. Does this mean that cloning a boot disk will not work with
2004, since the clone will contain references to the original disk
that maybe crashed or is removed?

Thanks a lot for sharing your knowledge, and spending time solving
problems for others. It is much appreciated :-)
The installation might complete.

But, now you have both spinner and SSD in the computer. If
you unplug the spinner, now it will fail to boot
No it boots fine without the spinner. The PC has only 4 connections
for SATA drives, and I use 3 for disks and the fourth for DVD.
Then what do we do ??? Hmmm.

You really have to fix it, using wit and cunning. No cheating :-)

PS: Here are links to pictures of the partitions with spinner
connected:
https://i.postimg.cc/tgh3NMKR/Partit...om-Macrium.png
https://i.postimg.cc/sXjh9DPK/Partit...om-Windows.png

OK, so I can see the "hole" where the 530MB partition is supposed to be.

And the spinner has been wiped, so no copy of 530MB partition
is available for cloning.

*******

This makes a passing reference to "reagentc" command.

"How to Remove the Windows "System Reserved" Partition"

https://www.terabyteunlimited.com/kb/article.php?id=409

*******

This is what a properly hooked up WinRE.wim for emergency
boot looks like (when C: is not working properly). I think
your Recovery partition is the one that's missing. The ESP
(on a GPT setup) is likely the equivalent of System Reserved
on an MSDOS legacy partitioned disk.

https://i.postimg.cc/fLhkXhtp/Fresh-...ood-Hookup.gif

Now, the weird part, is WinRE.wim isn't always hooked up,
it isn't always enabled. Yet there never seem to be any
visible symptoms at runtime from this. You can find WinRE.wim
in C:\Windows\System32\Recovery, but not always.

I suppose a bad thing, would be if

Reagentc: Enabled

and yet the path pointing to WinRE.wim no longer existed.
Maybe that causes indigestion.

But if

reagentc: Disabled

then maybe it does not care.

*******

https://www.ubackup.com/windows-10/c...ment-4348.html

Reagentc /setreimage /path C:\Windows\System32\Recovery

if the winre.wim file was C:\Windows\System32\Recovery\Winre.wim

That's an example of how you assign a path, while reagentc /disable

Paul

On Wed, 29 Jul 2020 07:38:30 -0400, Paul
wrote:

https://i.postimg.cc/tgh3NMKR/Partit...om-Macrium.png
https://i.postimg.cc/sXjh9DPK/Partit...om-Windows.png

OK, so I can see the "hole" where the 530MB partition is supposed to be.

And the spinner has been wiped, so no copy of 530MB partition
is available for cloning.
No. I did not understand the function of "Recovery partition". My
knowledge of Recovery partition was from laptops where the
manufacturer has put in a partition with the whole installation as
from factory. This could not be the case here, so I thought it would
be safe to delete it. For testing i cloned the disk to another SSD,
deleted the Recovery partition, and checked that the thing booted
allright. So it did, and I continued to delete the 530 MB Recovery
partition on the actual disk for Win10. Now I know better :-)
*******

This makes a passing reference to "reagentc" command.

"How to Remove the Windows "System Reserved" Partition"

https://www.terabyteunlimited.com/kb/article.php?id=409

*******

This is what a properly hooked up WinRE.wim for emergency
boot looks like (when C: is not working properly). I think
your Recovery partition is the one that's missing. The ESP
(on a GPT setup) is likely the equivalent of System Reserved
on an MSDOS legacy partitioned disk.

https://i.postimg.cc/fLhkXhtp/Fresh-...ood-Hookup.gif

Now, the weird part, is WinRE.wim isn't always hooked up,
it isn't always enabled. Yet there never seem to be any
visible symptoms at runtime from this. You can find WinRE.wim
in C:\Windows\System32\Recovery, but not always.

I suppose a bad thing, would be if

Reagentc: Enabled

and yet the path pointing to WinRE.wim no longer existed.
Maybe that causes indigestion.

But if

reagentc: Disabled

then maybe it does not care.
Reagentc is disabled on my system:
PS C:\Windows\system32 reagentc /info
Windows Recovery Environment (Windows RE) and system reset
configuration
Information:

Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier:
2ccc0ead-bf5a-11e9-8ac4-a0c2201546fc
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
*******

https://www.ubackup.com/windows-10/c...ment-4348.html

Reagentc /setreimage /path C:\Windows\System32\Recovery

if the winre.wim file was C:\Windows\System32\Recovery\Winre.wim

That's an example of how you assign a path, while reagentc /disable

Paul
I found a winre.wim he c:\$WINDOWS.~BT\Sources\SafeOS
That's a directory created by the attempt to install Win10 2004 that
the Microsoft lady initiated friday.
Following the instructions from the link above I ran this command:
C:\reagentc /setreimage /path C:\$WINDOWS.~BT\Sources\SafeOS
Directory set to:
\\?\GLOBALROOT\device\harddisk0\partition3\$WINDOW S.~BT\Sources\SafeOS

REAGENTC.EXE: Operation Successful.
.... and ran
C:\reagentc /enable
REAGENTC.EXE: Operation Successful.
....and this:
C:\reagentc /info
Windows Recovery Environment (Windows RE) and system reset
configuration
Information:

Windows RE status: Enabled
Windows RE location:
\\?\GLOBALROOT\device\harddisk0\partition3\Recover y\WindowsRE
Boot Configuration Data (BCD) identifier:
c84df3b8-d19a-11ea-a5cd-08606e698f9c
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

Do you think it worth a try to install the 2004 update now?

Thank you for your instructions.
--
Jesper Kaas -

Jesper Kaas wrote:


Do you think it worth a try to install the 2004 update now?

Thank you for your instructions.

You might get yours finished, before I get set up here :-)

Paul

On Wed, 29 Jul 2020 09:09:44 -0400, Paul
wrote:

Jesper Kaas wrote:


Do you think it worth a try to install the 2004 update now?

Thank you for your instructions.

You might get yours finished, before I get set up here :-)

Paul
I have started it from Windows Update now. Gues it will have finished
or stopped late this evening.
--
Jesper Kaas -

On Wed, 29 Jul 2020 15:58:01 +0200, Jesper Kaas
wrote:

I have started the 2004 opdate from Windows Update now. Gues it will have finished
or stopped late this evening.

It finished with negative result now. "We cannot install this update,
but you can try again (0xc0000005)." is the message in Windows Update.
The following happened:
1. Download 0-100% OK
2. Install 0-100% OK
3. Automatic reboot to a green screen that counts from 0-57% then
reboot.
4. During the reboot a splashscreen from BIOS is shown 2 times, the
second time with 5 small white balls running in a circle for half a
minute. This is like a normal reboot, but then a third BIOS splah
screen comes up, this time the picture is smaller.
5. Windows10 start screen comes up, enter pincode and normal running
Win10 opening, but still in version 1909.
I took a second reboot, and this time the reboot ran as normal.
So it got a little further, but no success. Next step for me is a
clean install of Win10 and all programs, unless you have some more
magic to share :-)

--
Jesper Kaas -