Upgrading 1809 to 1909 - mysterious problem.

Sorry, wasn't clear enough. I can boot now, as i have manually configured BCD with "bcdboot c:\windows"
 
Good.

It seems to me that your other drive with the Windows installation is doing something!
I suppose you didn't do the installation on the other drive with all the other drives disconnected?

Please connect also the other drive with the clean 1909 and post a screenshot of the disk manager expanded to show both drives.
 
Hmm, what we are trying to see here ? The initial issue of being unable to upgrade existed long before I've created clean install of 1909.
 
I'm thinking that the drives order may affect where Windows is writing the boot record or something!

If I'm not mistaken Windows tries to write the boot information on drive 0 and sometimes the BIOS depending on the settings and/or sata ports can change the order of the drives.

When possible I try to ensure that my main drive is drive 0 in BIOS and Windows to avoid strange problems that sometimes happen...
 
So the Disk1 on the image is where your problematic Windows 10 is right?

I'm confuse because on post #50 you post this after MBR2GPT:
Code: 
DISKPART> list partition

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 1861 GB 1024 KB
Partition 2 System 100 MB 1861 GB
Partition 3 Recovery 990 MB 1862 GB

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C x64 NTFS Partition 1861 GB Healthy Boot
Volume 1 FAT32 Partition 100 MB Healthy System

Now on Disk1 there is no Recovery partition! I only see one on the Disk0.
 
Yeah. So after running MBR2GPT Windows stopped recognized recovery partition at all, it was marked as unknown. Which probably makes sense, it was leftover from Win 7 and I never used it. Tried different options, and ended up deleting that partition, as utility to create recovery drive isn't working.
 
Hi,

Just to be safe I would try to put the boot drive as disk 0 by changing the drives order on the UEFI if available or by switching the sata cables.

I did a recheck in your logs and remember to ask if you did run a memory check?
 
Run a memory check

Code: 
The Windows Memory Diagnostic tested the computer's memory and detected no errors

Any other ideas what to do ? Windows have problems with fixboot even when the drive is only one connected, so I don't think changing cables will do anything.
 
Orkhis said:
Run a memory check

Code: 
The Windows Memory Diagnostic tested the computer's memory and detected no errors
Click to expand...

Good.
Any other ideas what to do ? Windows have problems with fixboot even when the drive is only one connected, so I don't think changing cables will do anything.
Click to expand...

Switching the cables will put the main drive as drive 0 if you can't do it only on the BIOS.

We can start from the beginning by running Dism /Online /Cleanup-Image /RestoreHealth and collecting the CBS.log immediately after dism fail.

When I re-checked your setupact.log logs it seems that the logs got cut, we probably don't have the full picture about what is going one!

It seems like the system shutdown or restarted in the middle of applying the wim file!
 
Fresh CBS.log

It seems like the system shutdown or restarted in the middle of applying the wim file!
Click to expand...

Exactly. This is what I have said in the very first message :)
 

Attachments

Hi,

I think it would be interesting to see what happens if you apply the image manually to a test folder...

Code: 
dism /Apply-Image /ImageFile:D:\Sources\install.wim /index:6 /ApplyDir:C:\IMGTEST\
 
Why I am not surprised ?

Code: 
Applying image
[==========================100.0%==========================]
The operation completed successfully.
 
I'm surprised!

Then why this fails?
Code: 
Applying WIM file: C:\$WINDOWS.~BT\Sources\Install.wim, index 6(create EAs), to C:\$WINDOWS.~BT\NewOS. Work dir: C:\$WINDOWS.~BT\Work
 
Well, for start - it is a different execution environment (Safe OS vs Full OS). Second - are you sure that this step is also executed by DISM and not by some other mechanism ?
 
Orkhis said:
Well, for start - it is a different execution environment (Safe OS vs Full OS). Second - are you sure that this step is also executed by DISM and not by some other mechanism ?
Click to expand...

The Safe OS should be better because no system files are in use, etc. The last command listed on the setupact.log is the dism command that didn't complete but there isn't any error after! I suspect the system didn't have time to write the log.

Do you have the Windows 10 DVD with v1809? to try a Repair Install.
 
Another thing the machine have/had any Language Packs installed?
 
I'm once again away on a trip. This time i have remote access via TeamViewer, but i don't think i can do repair install this way. Unless there is some obscure shell command ? I have Russian as additional keyboard language, but UI is in English, so i assume no language packs. Although Win 10 seems to very sneaky about silently installing those, so maybe I had Russian pack in the past.
 
I see, doing a Repair install or try to do an Upgrade doesn't seems good idea via TeamViewer!

Just wondering if removing all the extra languages will result on a clean check with Dism...
Dism /Online /Cleanup-Image /RestoreHealth
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top