Unable to boot into windows 10 \ VOGONS

Unable to boot into windows 10

Topic actions

Post a reply

First post, by Nemo1985

Posted on 2024-03-29, 04:40

Nemo1985 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1189
Joined: 2018-05-15, 21:45

Hello good people, I know we are mainly focused on older hardware but today I face a problem with my daily computer.

Back in 2020 I installed windows 10 in my amd am4 platform.
The original hard drives configuration was as following:
1 ssd (sabrent) 1tb as boot drive
2 raid 1 hard drives created from raid bios (so not software).

During the installation only the ssd was visible (and sometimes it wasn't). So I decided to add the raid drivers to installation to have both drives visible (ssd and raid 1).

This in time lead to some random boot issues, from time to time I was unable to boot since the ssd became invisible to windows (I wonder how is it possible that the recovery console is visible (which lies in the same hard drive) while windows partition isn't.
Then with some reboots, some random changes in the bios, everything was good again (until the next time).

Today I decided to upgrade the ssd to a 2tb pciex 4.0.

During installation (Windows 10 ltsc) only the ssd was visible and the raid 1 was undetected until I installed the chipset drivers.

Then I went back to the old ssd since I wanted to transfer some files and data to the new installation. All good so far, then I decided to update the audio driver from the old installation and this lead to the issues (the audio drivers aren't the issue since I'm using them in my new ssd).

When I rebooted I was unable to get into old windows installation. I was able to access the recovery console, which using diskpart showed me that the only driver visible is the raid 1, noone of the ssd are visible (therefore unable to boot on old installation).

Now i'm able to access the new windows installation where all the drives are visible and unable to boot to the old windows installation.

It's like if the drivers I gave during install back on 2020 makes the raid 1 visible but not the other drives (nvme), while if I try to install ltsc right now the visible drives are the ssd (but not the raid 1).

I tried several guides (sfc, dism, stupid youtubes video which shows noob things), without being unable to solve the issue.

Some pictures:
Old installation diskpart from recovery:
https://imgur.com/QCx86QU

Windows old installation version:
https://imgur.com/mXokMdP

Error trying to boot from old ssd:
https://imgur.com/o64iejU

New installation diskpart (which shows old and new ssd):
https://imgur.com/h5FXchk

My educated guess is that I should use the working installation and pnputils to export the drivers and then import them to the old installation from recovery, unlucky I lack the proper knowledge to do so, therefore any help would be appreciated.

As attachment also the log files (unlucky they are in italian mostly).

Attachments

Filename

Srt.7z

File size

24.05 KiB

Downloads

6 downloads

File license

CC-BY-4.0

Reply 1 of 7, by myne

Posted on 2024-03-29, 06:43

myne Offline

Rank Member

Rank: Member
Posts: 221
Joined: 2022-07-26, 03:47

Have you checked the bios boot options?
Sounds like it's set to one drive, and that drive doesn't have the other drive in the EFI boot settings.
It might be as simple as "boot from 1tb" instead of "boot from 2tb"

Things I built:
Mechwarrior 2 installer for Windows 10/11 Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11 auto-install iso template (for vmware)

Reply 2 of 7, by Nemo1985

Posted on 2024-03-29, 07:19

Nemo1985 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1189
Joined: 2018-05-15, 21:45

myne wrote on 2024-03-29, 06:43:

Have you checked the bios boot options?
Sounds like it's set to one drive, and that drive doesn't have the other drive in the EFI boot settings.
It might be as simple as "boot from 1tb" instead of "boot from 2tb"

Obviously, the two ssd have been installed while the other was disconnected.
When I decide which os to boot I select the right device on uefi (sabrent or the other one).
The problem is that the older installation seems unable to detect the ssds anymore (despite it's installed on that) and lock during the bootup.

Reply 3 of 7, by myne

Posted on 2024-03-29, 09:09

myne Offline

Rank Member

Rank: Member
Posts: 221
Joined: 2022-07-26, 03:47

Nothing's obvious when it comes to troubleshooting.
Just to be clear, the new drive can read the old one when it's in windows, yes?
What do you want the old OS for? Just the drivers?

If yes to both, then it's simple, boot from the new one, do the add driver thing, and point it at the other drive.
Ie, if the working install is C: and the non-working is D: point it at D:\Windows\System32\DriverStore\FileRepository

Reply 4 of 7, by Nemo1985

Posted on 2024-03-29, 10:35

Nemo1985 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1189
Joined: 2018-05-15, 21:45

myne wrote on 2024-03-29, 09:09:
Nothing's obvious when it comes to troubleshooting. Just to be clear, the new drive can read the old one when it's in windows, y […]
Show full quote

Nothing's obvious when it comes to troubleshooting.
Just to be clear, the new drive can read the old one when it's in windows, yes?
What do you want the old OS for? Just the drivers?

If yes to both, then it's simple, boot from the new one, do the add driver thing, and point it at the other drive.
Ie, if the working install is C: and the non-working is D: point it at D:\Windows\System32\DriverStore\FileRepository

Yes the new os can see everything without issues, here is a picture:
https://imgur.com/2habeox
New ssd (2tb), old ssd (1tb) and the raid 1 storage drives

I'd need to copy some settings from the old os to the new one, comestic settings and stuff.

Thank you for the advice, I will try that later after a backup.

It's interesting because I noticed that there are some directories which are available on the new installation but they aren't on the old:
amdfendr.inf_amd64_a1ac06c173945048 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:14:22
amdgpio2.inf_amd64_c72fc3523c1372d0 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:20:46
amdgpio3.inf_amd64_bb3599d0d57c5b6a Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:13:04
amdpcidev.inf_amd64_07eabc68f3f8029e Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:13:02
amdpsp.inf_amd64_db1b2556e686c32f Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:15:18
cthda.inf_amd64_1d59c5f7015c71a9 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 29/03/2024 03:06:04
cthda.inf_amd64_7d5b6f49f229bbe4 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:15:06
prnms001.inf_amd64_8bc1bda6cf47380c Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:11:34
rcbottom.inf_amd64_86be10757f47e582 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:19:28
rccfg.inf_amd64_2a80f50f071c2754 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:19:29
rcraid.inf_amd64_dcc1910b7fb4ec16 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:19:28
rt640x64.inf_amd64_b4d7d422f80229e7 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:20:45
smbusamd.inf_amd64_e470528883cc6bc5 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:15:24
u0390451.inf_amd64_39377efdd62734d1 Solo sinistra: C:\Windows\System32\DriverStore\FileRepository * 28/03/2024 10:14:22

I messed around with the permissions and copied the missing directories.

Just paste the directory didn't work. I think they need to be "loaded" somehow with pnputil

Last edited by Nemo1985 on 2024-03-29, 12:06. Edited 1 time in total.

Reply 5 of 7, by myne

Posted on 2024-03-29, 11:48

myne Offline

Rank Member

Rank: Member
Posts: 221
Joined: 2022-07-26, 03:47

It's pretty straightforward.
https://www.windowscentral.com/how-take-owner … ders-windows-10

But, if you do want to try booting it, one possibility is to convert it into a virtual machine.
Once it's imaged, it might start booting normally within the hyperv.
If not, at least it's easier to fix from there without affecting the actual drive.
https://learn.microsoft.com/en-us/sysinternal … nloads/disk2vhd

Reply 6 of 7, by Nemo1985

Posted on 2024-03-30, 06:29

Nemo1985 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1189
Joined: 2018-05-15, 21:45

So a small update, because despite I asked on different communities I received pratically 0 answers.

I messed with the old ssd a bit without making any step forward other than once I have been able to boot just to have a DPC Watchdog Violation, without being able to create any minidump.

What I did next was to remove the newer ssd (which I also did on other tryings) and put on the first m1 slot the old ssd, this made it boot straight away, but just once.

Reply 7 of 7, by Nemo1985

Posted on 2024-03-31, 09:55

Nemo1985 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1189
Joined: 2018-05-15, 21:45

Problem solved (thanks to troubleshooting on tenforums). The issue was that on windows partition there was a efi directory, which belongs to another partition (of the same hard drive), this didn't allow the system to boot for unknown reason when something was triggered.

Everything now works like a charme.

Go to top of page Go to top of page

Back to Milliways

Main menu

Common searches