Cannot upgrade Windows 10 from 1803 (Build 17134.1130) to 1909  

zbook said:

Code:

0x8007023E - 0x60016

Code:

MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE

What are the drive encryption software in use?

What is the status of bitlocker?

I don't use encryption software, and I'm on W10 Home - so no BitLocker, which makes the SetupDiag results very confusing..

After completing the steps in post #26:

(perform an in place upgrade repair with the same windows version followed by an in place upgrade repair to windows 1909)

Download and install: voidtools

Launch the application and search for these folders/files > post share links
(only include files within one day)

Code:

\$Windows.~bt\sources\panther
\$Windows.~bt\Sources\Rollback
\Windows\Panther
\Windows\Panther\NewOS

Setupmem.dmp may be found in either (depending on when the bucheck occurs)
%SystemDrive%$Windows.~bt\Sources\Rollback
%WinDir%\Panther\NewOS\Rollback

setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup
Setupapi.offline.log

Please excuse the simple questions, but what is lost by doing an in-place upgrade repair to the same version? i.e. programs/personal files etc.?

Also, how can I get the MCT for 1803? Downloading the MCT from the MS site gets me 1909..

See post #26.
It has 3 links for iso downloads.

There should be no impact on applications or personal files when performing in place upgrade repairs.

Hi,
Secure boot maybe needs to be disabled ?

ThrashZone said:

Hi,
Secure boot maybe needs to be disabled ?

I've disabled Secure Boot in the BIOS and do you know what, 1909 is taking a lot longer than it usually does.. Here's hoping..!

- - - Updated - - -

No joy, still. It appears to be doing more, but still failing at the last hurdle.

bcdedit /enum all reveals a lot of Windows Setup entries, which I've removed and am reattempting update after clearing folders.

In the case that it's failing to make the Windows Setup boot entry active - is there a way I can boot into it manually?

- - - Updated - - -

Looking for the WinRE.wim file the Windows Setup entries refer to proves fruitless - why are these files disappearing before the PC has even had a chance to update? This is attempting to update via Windows Update btw.

Please update the progress with each step in post #26.

Hi,
Have you also tried to disconnect from the internet doing all this ?

dalchina said:

Please run a disk check before making changes and report result.
HDTune (free) Health and Error Scan tabs.
Slide 1 - Gallery - HD Tune



I have come across references that suggest some partition repair might be needed, given the errors reported. This may relate to the encryption problem related- i.e. something can't be accessed in the normal way.

Have you created a disk image of Windows? This itself would be instructive, as that requires all used sectors be read and problems are flagged. It also requires all partitions comprising Windows (not just C: ) are readable.



You can use
Heidoc iso downloader
-just search for it.


See:
Repair Install Windows 10 with an In-place Upgrade

There is a note in bold which I recently suggested to Brink should be added as so many ask this, when they don't consider it's the same procedure as upgrading, when they would never ask this question.

See hdtune-health.png and hdtune-errorscan.png.

---

So, it's been an eventful few days - I'm still no closer.

I had disabled Secure Boot, however was not able to disable CSM as POST was reporting that my GPU was incompatible. I searched to find an updated BIOS and was lucky enough to find one, I flashed it, and am now running with no CSM/Secure Boot.

When running any of these installs, it creates the BCD entries for the reboot procedure - but then, when OK-ing the 'installation has failed' dialog, cleans up the BT folder located at C: root where the referenced .wim is located, causing a double reboot and back into Windows.

I found that once this error appeared - if I made a copy of the BT folder, then OK'd the dialog so it cleaned up the original (manually deleting the almost-empty folder myself), and removed the ' - Copy' from the duplicate folder, the following happens upon reboot:

- Windows boot logo appears;
- The low-res screen with an updating percentage (i.e. the screen you would normally see upon reboot) appears for a split-second;
- Instantly reboot back to POST, then to Windows as normal;

When this process is done from a MCT/ISO in-place repair install (note that all versions have done this - from 1803 up to 1909 (yes, it has been a long few evenings..!) I get the following error:

"0x8007000D - 0x2000A
The installation failed in the SAFE_OS phase with an error during PREPARE_FIRST_BOOT operation"

..which I guess is a step forward..? I'm so confused right now