error 0xc0000225 -winload.exe missing after resized m2 multiboot disk?

why you delete my thread???

.. so i tried to resize the 3rd partition by taking the space from the last partition, but now i only get this error and only the F9 option on the light blue Recovery screen boots me to the 2nd partition(win7), but why did the resize even fail and how could i get it back working again?
the last os was probably Linux and now it doesnt show the main grub bootloader either, just the light blue F9 error page...

i have already tried these commands:
bootrec /fixmbr,
bootrec /fixboot,
bootrec /scanos,
bootrec /rebuildbcd

but that only finds 1 os, which is probably the same win7 one that boots up, plus i probably cant make any partitions active with other apps, because that would make things only worse?
(it was probably win10 20h2)

plus there is probably the issue also with the diskpart thing - in a multiboot system the drives constantly change their letters, so how should i even know which ones do i have to set in the options etc... or would it actually start working if i set them up manually then...

?^?_??^?_??^?_?

?

so now im basically trying these commands with the usb boot disk:

diskpart
list volume
<then determine the disk labels from there...>
sfc /scannow /offbootdir=f:\ /offwindir=f:\windows /offlogfile=g:\sfc-log1.txt
... as f: is the windows 10 partition that should contain all of the boot information?

or how could i even check where is the actual bootloader located....

Each time the computer is rebooted you can perform these steps to find the applicable drive letter:

1) select any drive letter followed by the dir command
2) bcdedit
3) bcdedit /enum
4) bcdedit /enum all
5) bcdedit | find "osdevice"
6) diskpart > lis dis > lis vol > sel dis 0 > det dis > lis par > sel par 1 > det par > etc. (change the number to the applicable disk or partition)

However, depending upon the error message or code bcdedit commands may fail to run and also generate error messages and codes.

what would that find and det do?
and what could even be the issue with the winload.exe in the first place when i only resized couple of partitions, lol...

jenny5 said:

in a multiboot system the drives constantly change their letters, so how should i even know which ones do i have to set in the options etc... or would it actually start working if i set them up manually then...

jenny5 said:

how could i even check where is the actual bootloader located....

The earlier post was for the above quotes

ok, but would i have to set the boot partition as C: first and then run those rebuild commands or smth?

but now i probably found out with this command via the linux live cd, that win10 bootloader is probably on a separate 500mb partition (partition 2, which it actually lists as C most/all of the times...):
sudo os-prober

but i read from somewhere that if i make the wrong partition as active, then it will just make things even worse? or would it actually be ok, if i know that the bootloader should be on the 2nd partition now?

- - - Updated - - -

or what could be the commands to rebuild the whole Bcd thing when i should know the order of every OS and boot partition now?
the last os is basically Linux and it also should have that Grub thing somewhere as it was also the last OS that was installed on the pc... but is now totally dissapeared somewhere and i only get that light blue F9 error screen... and only the last OS before win10 boots up with the "choose another OS option"...

...
so if i set the 2nd partition as active, then it wont actually see the grub loader/partition anymore and then i wont even get the only os booting anymore? or would i have to set somekind of grub partiton as active then? and how could i determine where is that even located... OR why does it even shows me the windows light blue error screen if i previously only had the black grub loader as my default bootloader before the partition resize thing....

This is a Windows 10 forum.
There are few members that comment on Linux /Ubuntu.
So you may be better off seeking help in a Linux forum.

Were you dual booting Windows 10 and Linux?
or Windows 7 and Linux?
And you can no longer boot without an error message or code?

If you're using Windows 7 did you open a thread in Seven Forums?
Windows 7 Help Forums

What are the status of the important files?
a) backed up images saved to another drive or the cloud
b) backed up files saved to another drive or the cloud
c) no backed up images or files and steps are needed to save them
d) no backed up images or files and steps are not needed to save them

Did you attempt to run startup repair?
Did it create a srttrail.txt?

Did you attempt to run system restore?
Were there restore points?

Find a camera or smartphone camera to take pictures and post images into this thread.

For any problems posting images please use share links: one drive, drop box, or google drive


Post images of these commands with results:

Code:

bcdedit /enum all
bcdedit | find "osdevice"
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel par 6
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel par 6
det par