Windows won't start due to MSConfig RAM.
brucine Posted messages 24411 Registration date Status Membre Last intervention -
I bought RAM to boost my Tuf Fx516P. But I realized that this RAM was not usable. It showed 24 GB but only 16 were usable.
So I searched on Google and came across a tutorial explaining to go to:
MSCONFIG, Startup, Advanced Options, then check maximum memory. I went from a greyed out 0 to 256 (I think). After that, there was a mandatory restart.
But since then I'm stuck, Windows won't start anymore...
I'm in Troubleshoot and I don't know what to do
Thank you for guiding me :)
1 réponse
Hello,
MSCONFIG is the best way to crash a PC, proof of that.
It’s the BCD boot sector that is damaged.
If we still have access to the command line, it’s relatively simple, see here for BCD repair according to MBR or UEFI in the recovery options paragraph:
https://www.malekal.com/resoudre-erreur-bcd-winload-demarrage-windows-10-11/
Otherwise, we're in deep trouble if we don't have a USB reinstallation media (now is the time to create one after repair).
Thank you very much for the feedback!
We still have access to the command line, all is not lost :)
- I entered /rebuildbcd
"Windows installations were scanned. Number of Windows installations identified 0.
The operation was successful"
- the command bootrec.exe /fixmbr
"The specified path was not found"
- The command bootsect.exe /nt60 all /force
"The target volumes will be updated with a boot code compatible with boot mgr
The boot code was updated on all targeted volumes"
- The command: bootrec /fixboot
The specified path was not found
- And the command: bcdboot c:\windows /l fr-fr
Failed to copy boot files
Any idea what the issue might be?
These commands are accessible not from the simple command prompt but from the WinRE environment, which can be accessed, without installation media, in different ways, see here "Entry Points in WinRE".
https://learn.microsoft.com/fr-fr/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11
Furthermore, it is likely that the disk is not in MBR but in UEFI, in which case it is necessary to use, as indicated in the link in <1>, not bootrec and the like but Diskpart.