Question Locked

Can't boot - it's complicated

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I was having some issues with my computer and after trying everything else that I knew about, I decided to try Windows 11's Fix problems using Windows Update. It downloaded and installed 25H2 ( I THINK - could it possibly have been 25H1?) (repair). (The word "reapir" in parentheses followed 25H2.)
It didn't solve my problems.
I may have misunderstood, but I thought that using that option would replace Windows files if necessary. Since it only installed an update, I tried again. Good old Microsoft. It downloaded and installed the same update again! I wanted to stop it, but by the time I realized what had happened, it was already downloaded and I couldn't find a way to prevent it from installing.
After that, I was unable to boot. No Windows boot menu. When starting, it would take a little over a minute to get to the m/b logo and a few seconds later, my screen displayed "No signal." It would then go back to restarting. In other words, an endless loop.
One of the issues I was having was with my USB ports. Two of them suddenly stopped working. Another one works but isn't recognized until Windows loads. Not sure about the 4th. Bottom line: I can't boot off a flash drive.
I have a Windows 11 installation DVD and tried to have it repair the damage, but it was unable to.
I do a daily backup, using different programs each night. I did a restore, but no luck.
I had Lazesoft fix all problems with no success.

18 replies

by Wizard57M-TR edited

The "No Signal" is usually a sign that a hardware component, such as video, USB ports, drive controller, etc. is failing.
What are your computers specifications? Make/model, CPU, RAM, age?

by doniel edited

Thank you for your reply.
I don't believe it's a hardware issue. It was working until Microsoft installed the same update over the same update.
As I've done for decades, I put the computer together myself. While the components aren't the latest generation, I only installed them a few months ago.
An MSI m/b, a Core i7, 64GB RAM.

by kees_b

If you can't boot from a Linux install drive or stick (easy to make on another PC), nor from a Windows install stick or disk (make it on another PC via the media creation tool as mentioned in https://www.microsoft.com/en-us/software-download/windows11 if needed) there's a BIOS or hardware issue. If you can't fix that yourself, find a repair shop.

With that issue fixed, you might have other problems, but the problem in your subject line is solved: you can boot.

Then boot into your Windows 11 installation disc or stick and do a normal install, like you would on a new hard disk. You could even consider to install it on a totally empty new hard disk and keep your current one as backup of all your current data, but that's up to you.
Then reinstall all programs and apps and get your data back from the backup you make each night.

Nothing complicated at all.

by doniel

I wrote that in my original post. That's how I was able to try to have Windows repair the harm it caused.
I'm trying to desperately to avoid a new install because I have a number of giveaway programs installed. Even if I had the license numbers, which I don't, they wouldn't work anymore if I reinstalled. Those license numbers are usually good for between 2-6 days.
By the way, I forgot to mention that I also tried creating a BCD with Lazesoft. Struck out there, too.
It's good to hear from you again, kees_b.

by kees_b

Then try a "repair install". That leaves a lot of stuff as it is. That's done by booting into Windows and running setup.exe from the installation disk of stick. Google it if necessary.

Or in a working Windows or the run sfc /scannow from an elevated command prompt. Might fix it. Same for: DISM.exe /Online /Cleanup-image /Restorehealth. They work also in the recovery console after booting from the Windows install medium. Google that if necessary.

The installation data usually is stored in the subfolder in Programs or Programs (x86) or in your Appdata folder or in the registry (where it can be exported from while everything still works). Then with those data copied or imported from your backup it might work again.

By the way, what's the use of a backup if you can't use it, because it doesn't include license keys? Make an image backup and restore it to get the exact system back as it was. It seems you use another backup method,

by doniel edited

I'm pretty sure you're suggesting I do something that I wrote I already tried. I booted from a Windows installation DVD and tried Repair. The message was that Windows couldn't repair things.
I was under the impression that sfc and DISM worked with Windows files. Since I'm not getting a Windows boot menu, my problem begins before Windows files come into play. Or am I mistaken?
I'm doing System backups. Those backups include my programs and their licenses.
I don't see installation data in any of the places you mentioned. So they're probably in the registry, where I can't get at it.
Heel hartelijk bedankt!
(For those who don't know Dutch, that's: Thank you very much.)

by kees_b

If Windows says it can't repair things, it's getting hopeless.

There is no "boot menu" in normal Windows. The "boot menu" is something in the BIOS. But in the recovery console you can open a command prompt to run sfc and dism and chkdsk. Those might work if the "repair" doesn't work. Or maybe not. Only Microsoft knows the differences.

If repair isn't possible, a new installation of Windows certainly works, if there are no hardware issues.

It's unclear what a "System backup" is. Apparenly something else as a "full image" . As Copilot says: "For effective image backup, consider using software like Acronis True Image, EaseUS Todo Backup, or R-Drive Image, which offer robust features for creating and managing disk images."
Or use a program like "Clonezilla" to copy each and every sector of your hard disk to another hard disk, ready to boot from like the original. You won't lose much if you do that every month and copy new and changed data files to another disk or USB-stick each evening with xcopy /m or so.

by doniel edited

Trying a number of things got me to the point where I have my old Windows boot menu back!
First, a little background. Windows 11 was installed on my hard drive years ago. When I installed the new hardware components a few months ago, an SSD was among them, and I installed Windows 11 there.
However, when I tried to boot to it just now, it gave me an error 0xc000000e: A Required Device Isn't Connected or Can't Be Accessed.
I WAS able to boot into the hard drive Windows 11.
The SSD is connected. I've been copying files from it while all this has been going on and in fact, I just used File Explorer to look at its contents.
I ran msconfig, but it wasn't helpful. It shows the hard drive Windows as being on drive C: and the SSD Windows (the default) as simply Windows, with no drive specified.
I don't know what else to do.

by birdmantd

What version of MS Windows are you using? I haven't needed/used an installation DVD/CD in over a decade and I didn't think they were readily available.

by doniel edited

I replied a day or 2 ago, but for some reason, the reply went all the way to the end of this thread.
Windows 11 Pro.

by rproffitt edited

Yes, when you are booting from a drive, doesn't matter which and you install another drive and then do what you gotta do to boot from the NEW drive it appears to be a ticking time bomb that can result in a failed boot later.

No. I have yet to find a way to fix this except to remove all but the boot drive and try repairs. There are no guarantees here but Windows, updates and more seem to get confused with boot data on multiple drives.

So that's all I can offer. One drive during the work to recover. Get that working and only add drives after repairs or reinstall. Be sure you secured your BITLOCKER CODES as soon as you can.

by doniel edited

As I've said in the past, it's always good to hear from you, Bob.
Due to some more fiddling, I got a drop further and received a new error message when trying to boot into SSD Windows. 0xc000000f - winload.efi is missing. You can't imagine how far my jaw dropped when I checked to see if it was in system32 and found only folders there - no files whatsoever! (Although there are way too many folders to check, a cursory check revealed that they're empty.) Microsoft really did a job on my Windows with that double update.
So here's my latest problem in this sorry saga. I tried to run sfc as follows: sfc /scannow /offbootdir=D:\ offwindir=D:\windows
All I got was a listing of the parameters that can be specified with sfc and the command prompt.
How do I get sfc - and actually, first, dism - to run? I'm going to try to either get into the WinRE environment or to boot from my installation DVD, but as it's really, really late, I'm going to bed now.
Can dism and sfc replace ALL those missing files?

by rproffitt edited

The fix varies with situation and owner. But first I define fix as "it boots and runs Windows" and not "it works like before and all files recovered."

The problem I encountered and observed too many times on more than one drive systems where for what ever reason the BOOT DRIVE was changed from old to new drive is the boot information is now SPREAD over the two drives.

To get the new drive booting Windows I have to unplug any non-boot drives and I want to be clear here the PC shall have one and only one drive. Highlander rules. Then I can examine the drive and almost always the PARTITIONs are not what you see on a good booting drive.

When that happens and this is over 3 decades of such work there has yet to be a tool to "fix that" and get it booting without a drive wipe and OS install.

When I see this it's FULL STOP to talk to the owner about sending the drives to DATA RECOVERY companies to get the files out. And mind you that's to get the files out and nothing more. In over 3 decades not once over thousands of data recovery send ups have I seen that drive get recovered and booting without a wipe and reinstall.

Hope your files and such are safe.

Sadly, the story has been heard many times.

by doniel edited

I received email notification that you posted a reply to this thread, but I don't see it anywhere.
At any rate, the problem has been solved.
Thank you.

by doniel edited

First, I have to retract what I wrote about the double Windows updates wiping out my system32 files. The cause turned out to be benign and was taken care of by changing a program's parameters and doing a restore of my SSD Windows installation.
Having said that, I can only attribute 2 steps forward in this process of recovery to miracles.
As I wrote, one of my first attempts to fix things was with Lazesoft's Windows Recovery. At some point, before my Windows boot menu reappeared, I decided to try Lazesoft's BCD Doctor to get a working BCD. (I couldn't use EasyBCD because I couldn't get into anything on my computer at that point.) It only showed me one entry, whereas my boot menu had a number of entries, so it appeared that it was working with a different BCD than the one I normally used. When I rebooted after that, my Windows boot menu with all its entries magically reappeared.
At the very end, I still couldn't boot into my SSD Windows because, Windows informed me, a file was missing from the EFI partition. I dutifully followed its suggestion to try Startup Repair, but it was unable to effect any repairs. Given that nothing had changed, there was no reason to try to boot into my SSD Windows again when I rebooted, but I tried, and against all logic, it booted into my SSD Windows!
Bob, your recommendation to disconnect all drives but the one in question is a good one, and I believe you suggested it once before, possibly as far back as the cnet days. Too bad I'd forgotten it.
But all's well that ends well.
Thank you, guys, for taking the time to offer your thoughts and help.

by doniel edited

See my message to aleerazarid1122, which is directly above this one.

by rproffitt

I see spam or such posts so nothing @doniel did here is the reason.

This is why we can't have nice things.

This discussion is closed to new replies.