Windows installation no longer detected after last update

Hey guys,

A week ago or so my PC was updated to the latest build of Windows 10 (i think its 1903?).

My PC is running pretty much 24/7. Now...i just rebooted and it turns out windows.can no longer find the boot device or windows installation.

After this happens the PC reboots and windows recovery mode is triggered. This doesnt help.

1. I tried going to advanced options and do a startup recovery. Windows is saying it can not recover from this situation.
2. I followed a guide to rebuild the bcd via command prompt manually. Again windows is saying it.can no longer find any windows installation.
3. If i try to go back to a previous system restore point or uninstall an update, Windows states it can not find anything to recover or rollback.
4. When i use the command prompt in the recovery environment, disk part will list all the disks and volumes just fine.
One thing i do seem to notice is that my data harddrive now seems to be recognised as drive C: and my (Intel 750 series nvme) SSD partitions have shifted to D: (Windows) and E: (Games).
I doubt if this is problematic for a bootbcd rebuild though? (But im not sure on that).

My complaint seems to resemble the same one mentioned here:
Reboot and select proper boot device after updating to Windows 1903.

Could it be that Windows 10 updated even though a certain Intel RST driver was no longer supported? (Ive read about that somewhere).

Please help! :)

dalchina said:

Hi, your first problem to solve is having the disk recognised.
In a recent thread, it eventually turned out the user had to 'reseat' the drive.

Have you moved any cables or made any hardware changes recently?

Please check all, and check the disk is 'seen' when booted to BIOS.


If indeed you have recently upgraded to 1903, then all restore points for the previous build will, by design, have been deleted as they are irrelevant to 1903.

Hi,

The drive is recognised fine. :) I just reseated it to double check. Diskpart shows all the volumes as expected!

dalchina said:

Good- try booting from a live boot disk and see if you can see the content of the disk.

Has it simply lost its drive letter?

Yeah i can also see the contents of all the partitions. For some odd reason windows recovery environment will repeatedly appoint drive letter D to my windows drive while it used to be C though.
C is now appointed to my data drive/volume.

Screenshots:

NB. Volume 7 is the USB recovery flashdrive.



PS.

I also added my SrtTrail.txt

It states:

Code:

Main cause found:
---------------------------
The system may not start due to a recent installation or upgrade of a driver.


Recovery operation: Check and restore integrity of system files
Result: Failed. Error code = 0x57
Duration = 1328 ms

I have not willingly updated a driver. Could this have been done by Windows update?
(Or would this confirm a driver compatibility issue ever since installing the last update).

dalchina said:

Yours is a UEFI installation:

Clearly the Boot attribute is missing.

You might see what Macrium Reflect's Fix Boot utility on its bootable medium makes of this, also available on Kyhi's live boot disk:
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru

However, you might be best to start by checking the disk:
HD Tune, Health and Error Scan tabs
- on Kyhi's disk

Ive never actually used that. Do you expect the macrium reflect boot fix will automatically fix it, or do i need to run some command?

dalchina said:

I don't know- it's more complete than Startup Repair.

You just run it from the GUI.

But first run a check on your disk as per previous post.

You could then try reassigning drive letters using Minitool Partition Wizard, e.g. - on Kyhi's disk.

Alright, i will try and see if the startup repair fixes it.
On a sidenote...bootrec did actually find the windows installation but now i cant add it..GAH



- - - Updated - - -

Okay, this is me reporting back:
While my USB Flashdrive with KYHI WinPE was being made i got impatient and wanted to try one more thing.
I tried booting into Safe Mode. And whatta ya know... it worked!
So i figured i was only going to try and see if i could update my Intel INF and Intel RST driver. Downloaded on my second PC, put it on a flashdrive and tried to execute it. Error: "The Windows Installer service is not running".
A quick Google fixed that for me.
So i ran the installers again. Rebooted and Voila! I'm back in Windows! No issues at all with my EFI Bootsector or whatever!

Now i only have one more question just as a checkup:
When i was looking in diskpart i found some of my volumes to be a tad bit confusing. Its as if i had a double recovery partition or something?
Does this look alright or is there some clutter in there perhaps?

https://tweakers.net/ext/f/IHplD6ejb...16rRo/full.jpg
(For some reason this picture isn't embedded when you do an Edit)