Updating From 1909 To 2004 Eror

I tried updating and received error 0xC1900101 - 0x20017 The installation
failed in the SAFE_OS phase with an error during BOOT operation.

It appears this can be many things. I am looking for guidance if there is
something I should look for in the XML files under Panther and what file(s)
I should look in. I did find in one file oem1.inf and oem0.inf had a
BlockMigration="True". I do not know if this means it is blocking the
update.

Bill

Bill Bradshaw wrote:

I tried updating and received error 0xC1900101 - 0x20017 The
installation failed in the SAFE_OS phase with an error during BOOT
operation.

It appears this can be many things. I am looking for guidance if
there is something I should look for in the XML files under Panther
and what file(s) I should look in. I did find in one file oem1.inf
and oem0.inf had a BlockMigration="True". I do not know if this
means it is blocking the update.

What I'd try first and simplist: Boot into Windows's safe mode (there
are lots of online articles on how to do this with Windows 10), and then
reboot into normal normal mode. Although pending file replaces should
occur on shutdown and restart (when they are not in use), I've seen
where a safe mode was required to get the setup to work, so a following
normal mode also works. Sometimes safe mode then normal mode works,
sometimes not. Safe mode eliminates interference by startup programs
and non-critical OS and non-OS services. If you are using an anti-virus
program other than Defender, safe mode should prevent it from loading.

Another cause is a peripheral. Disconnect all periphals (e.g.,
disconnect USB printer, external USB driver, etc) other than the
keyboard and mouse (if those use USB instead of PS/2). Then try booting
into Windows. Also disconnect from your network during the boot. If
using wired LAN (Ethernet), unplug the Cat5 cable. If using wi-fi, and
if you can manage to get into Windows, disable it, and reboot. If you
cannot get into Windows at all, use safe mode but NOT with networking.

I also did an online search on "safe_os phase", and one of hits was:

https://www.auslogics.com/en/article...with-an-error/
https://windowsreport.com/installati...safe_os-phase/

Were you overclocking the motherboard or video? Is the BIOS configured
to optimal speed settings, or did they get tweaked? If tweaked, you
should try resetting to optimal values. As for overclocking the video
card (not onboard video), you'll have to check with the maker of yours
to see if they provide a reset rather than relying on using software ran
under Windows to tweak the video card's firmware. If you have both
onboard video, like you have a CPU with it or the southbridge has video,
make sure the BIOS is configured to NOT use onboard video. Eliminate it
having to decide when both are present as to which should get used. You
could also switch to onboard video and remove the video card to reboot
using the onboard video.

The 2004 feature upgrade includes CPU overrides (software trying to fix
defects in the CPU regarding vulnerabilities). You may have to update
the BIOS/UEFI firmware. Usually this has you create bootable media
which you use to write into the EEPROM(s) for the BIOS. If available, I
first save the old BIOS firmware, so I can revert to it if the new code
has problems. My desktop PC is attached to a UPS. You don't want to
lose power during a firmware update. If the update gets interrupted,
and because you're modifying the brains of the mobo, you could end up
with an unusable mobo requiring a new EEPROM chip. If the code gets
corrupted due to a power outage, the code may impacted sufficiently to
prevent bringing up the mobo and OS.

VanguardLH wrote:
Bill Bradshaw wrote:

I tried updating and received error 0xC1900101 - 0x20017 The
installation failed in the SAFE_OS phase with an error during BOOT
operation.

It appears this can be many things. I am looking for guidance if
there is something I should look for in the XML files under Panther
and what file(s) I should look in. I did find in one file oem1.inf
and oem0.inf had a BlockMigration="True". I do not know if this
means it is blocking the update.

What I'd try first and simplist: Boot into Windows's safe mode (there
are lots of online articles on how to do this with Windows 10), and
then reboot into normal normal mode. Although pending file replaces
should occur on shutdown and restart (when they are not in use), I've
seen where a safe mode was required to get the setup to work, so a
following normal mode also works. Sometimes safe mode then normal
mode works, sometimes not. Safe mode eliminates interference by
startup programs and non-critical OS and non-OS services. If you are
using an anti-virus program other than Defender, safe mode should
prevent it from loading.

Another cause is a peripheral. Disconnect all periphals (e.g.,
disconnect USB printer, external USB driver, etc) other than the
keyboard and mouse (if those use USB instead of PS/2). Then try
booting into Windows. Also disconnect from your network during the
boot. If using wired LAN (Ethernet), unplug the Cat5 cable. If
using wi-fi, and if you can manage to get into Windows, disable it,
and reboot. If you cannot get into Windows at all, use safe mode but
NOT with networking.

I also did an online search on "safe_os phase", and one of hits was:

https://www.auslogics.com/en/article...with-an-error/
https://windowsreport.com/installati...safe_os-phase/

Were you overclocking the motherboard or video? Is the BIOS
configured to optimal speed settings, or did they get tweaked? If
tweaked, you should try resetting to optimal values. As for
overclocking the video card (not onboard video), you'll have to check
with the maker of yours to see if they provide a reset rather than
relying on using software ran under Windows to tweak the video card's
firmware. If you have both onboard video, like you have a CPU with
it or the southbridge has video, make sure the BIOS is configured to
NOT use onboard video. Eliminate it having to decide when both are
present as to which should get used. You could also switch to
onboard video and remove the video card to reboot using the onboard
video.

The 2004 feature upgrade includes CPU overrides (software trying to
fix defects in the CPU regarding vulnerabilities). You may have to
update the BIOS/UEFI firmware. Usually this has you create bootable
media which you use to write into the EEPROM(s) for the BIOS. If
available, I first save the old BIOS firmware, so I can revert to it
if the new code has problems. My desktop PC is attached to a UPS.
You don't want to lose power during a firmware update. If the update
gets interrupted, and because you're modifying the brains of the
mobo, you could end up with an unusable mobo requiring a new EEPROM
chip. If the code gets corrupted due to a power outage, the code may
impacted sufficiently to prevent bringing up the mobo and OS.

I did notice the genuine Intel dll was accessed so I might try overriding
that. This is an older computer so items like BIOS, etc. are at the last
versions. Thanks for the input. The problem is I have to use the computer
for other work and thus can only try to update it when I have gaps and also
have backed it up which takes time before I start trying to update. I
always cross my fingers in hopes of a simpliar solution.

Bill

On 07/06/2020 20:26, Bill Bradshaw wrote:
I did find in one file oem1.inf and oem0.inf had a
BlockMigration="True". I do not know if this means it is blocking the
update.


Has anybody told you to try doing a "clean" default install?Â* I say
default because some idiots here will tell you to start meddling all
sorts of settings when installing and this could be the problem in the
hands of plebs.

I bet nobody has told you this and you are not likely to do it because
of your low intelligence who is prepared to waste weeks trying to fix
this.Â*Â* In your case it is nearly a month as far as I can see.Â* Time
doesn't seem to be very important these days because of the lockdown.Â* I
suspect this won't last long because most countries have started opening
again and the white slaves are being recruited to do the manual work
because blacks are in command and their previously white masters are
kneeling to their demands.Â* See this picture of the day!

[ Nancy Pelosi & Jack Schummer surrendering to Negros ]
https://s.abcnews.com/images/US/pelosi3-gty-ml-200608_hpEmbed_3x2_992.jpg





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