Disk cloned incorrectly to the OS...
Disk cloned incorrectly to the OS...
Good that you have got it going. I have spent weeks in spare time trying to manually repair corrupt or unbootable Windows 10 installations (to save days of work) without any success. It's frustrating to lack the knowledge to manually repair some of these what seems should be simple to re-create the boot data and point to an OS installation. I've tried to fix MBR and UEFI installations that were not bootable after some NON virus and Non malware event rendered them unbootable. All files seemed to be intact but various versions of blue screens on bootup or advanced boot menu not available etc. There is so much useless mis-information on the web and in youtube videos on this matter. Anyhow I have a ways to go and a lot to learn about Windows startup and how it actually works. Almost the entire world takes the easy approach to reinstall Windows to fix just about everything rather than fix the actual problem. Windows 10 is going to be around for awhile and I think it's worth my investment of time and effort to get an actual handle on this. It seems that virtually nobody out there actually already does and if they do they are keeping it close and not sharing the information.
Several people are discussing this topic. I discovered my approach in a video: the challenge isn't just lack of sharing, but two main points. First, to solve a problem you must grasp it and ask the right questions. Initially I only knew about the bios message saying no boot drive was found and an error code, which still leaves many possibilities and solutions. This often needs testing and adjusting. I moved from the error code to Windows USB repair, then tried the command prompt (noticing /fixboot didn’t help), searched for fixboot fixes, and finally looked up ways to work around it. Second, this issue seems very particular—likely affecting only a small number of users worldwide. If your group is tiny, finding a fix becomes harder. My method might not fit everyone. These are extremely niche problems, so keep trying. Always check if you're asking the right question and making sure your understanding is accurate. I personally didn’t like Windows 10 a few years back; one update in May 2018 completely broke a Windows install (the famous update), but Microsoft has since improved that. Now it’s one of the best systems available, and being able to switch OS drives easily is a big upgrade.
The issue really lies in the sharing or availability of the right details, whether it comes from Microsoft or not. Where can I find the necessary information? The video above is acceptable, and I’ve definitely seen similar content over the past couple of years. It’s another example of trying a specific step-by-step guide, but it hasn’t solved any real problems I’ve encountered. It doesn’t explain what’s happening or how things function, nor does it clarify what happens if it fails. Clearly, this is exactly what I’m facing—understanding Windows startup and troubleshooting issues in Windows 10. These types of videos haven’t helped me with the specific challenges I’ve run into. I’m still trying to piece together how everything connects and how to properly diagnose and fix boot problems in Windows 10. Thanks for the reply! Windows 10 usually works fine, but finding the right information to repair it when it doesn’t is quite challenging. There are many factors involved that this video overlooks. And in practice, I’ve run into a lot more than it covers. For instance, when I have a Windows 10 version that’s outdated or different—like between 1709 and 1903—I’m unsure if using a specific boot media can fix older versions. Or what happens if the system crashes mid-update? There’s a lot more to it than what’s shown. I could start with a simple question as an example: With all the different Windows 10 versions available now, does the recovery version I boot into have to exactly match the OS I’m installing? Or can I use a different version’s media to repair others? When someone gives me a non-functioning laptop, how do I quickly identify the installed Windows 10 version? And what if it fails during an update from one version to another? Where can anyone reliably find this kind of definitive guidance? This is just one of many questions I’m dealing with while trying to master boot repairs.
From the video I can reconstruct what's happening based on my knowledge. He's reorganizing the FAT32 partition and then creating boot files from the OS drive. It seems straightforward but didn't succeed for me. The files on the OS drive weren't working either, another issue not shown in the video. I've tried similar approaches on MBR systems too—they didn't work well either. There are other videos for those situations, but they didn't help in my case. This topic is really complex. I spent a few weeks working on it and still feel like I'm not very skilled at it. I've gained some insights but remain quite limited or ineffective.
I didn't pay particular interest to this. However, since I made the usb recovery stick at that moment, I assume it encompassed the latest build. Another assumption would that my mate kept his OS updated (not a far stretch really as microsoft does not allow you to turn them off by normal means). So I think they matched at the time. I honestly don't think this is going to matter if the version on the recovery drive is newer, as that will likely end up with the OS being repaired and updated. Absoiutely not booting is a bit vaguely described . I had a lot of cases across that spectrum, and that goes from a failing drive, to messed up boot records to a botched windows update: -A failing hard drive is rather simple: I don't even begin on an attempt to repair or salvage data, because I lack both knowledge and instruments for that. Me trying to do anything about that will likely result in permanent loss of data. So I usually give them the option of a 1000 euro repair job by an external firm who have airsealed rooms and spare parts to crack up a hard drive and replace broken components. Of course, I can remove the hard drive myself, build in a new one, set up the OS and their programs. That's basically Lego for adults. -Missing master boot records we already covered, though note I have only seen this once (and that is what this topic is about). -A botched windows upgrade that damages the OS beyond ability to boot, is pretty much solvable with the a recovery usb drive. It will even keep programs, registry files, and all your data. Though from experience I do know some settings do get lost. Of upmost importance however, is that your system can still detect the boot drive. The outcome will wildly vary. I think if it fails, windows will try to roll back to the version before updating. But, if critical OS files are damaged it will not boot to windows. At that point you will need to use the recovery drive. And this is again a case where you can't judge such a thing before it happens: it really depends where in the middle it crashes, which file it was replacing at that time. There's no pinpointing to that. There's no library in the world that will 100% guaranteed give the answer you seek immediately. Usually small mundane questions, you will be able to find the answer immediately by googling it. These kind of questions, it gets tricky, and will end up with just sifting through google search results until you find the answer that matches your question. Do you really believe that? Ok, you have not found the solution (yet), but in the whole process you have learned how to tackle similar problems, you have learned how to better diagnose the problem. Your problem-searching and solving skills have improved. You have learned potential solutions. Even though all that you have learned is not applicable in this particular case, it was not useless. It can always be applicable for a future case. Can you send me a picture of the error codes and other relevant things? taken with a smartphone or something like that. I'll not guarantee I will be able to solve it, but it can't hurt to try.
Hey thanks for the help offer! I had to give up and re-install the OS after two weeks of poking at it. The customer was understanding and I gave them a loaner with all their data from a backup so I could have the two weeks to poke at it. I come across these occasionally so the next time I have to (or get to) deal with this and it's not a simple fix I will post here or start a new thread and track you down and invite you to see Interested? This last one was related to a Windows 10 update and/or EASEUS (paid version) backup software that in my opinion failed miserably. This is another topic entirely. And a doozy of one at that. Thanks again! I look forward to learning more.
I appreciate the interest! I’ve worked with various operating systems over time and enjoy exploring Windows 10 in depth. My usual focus is on network infrastructure for medium-sized businesses, which keeps me engaged and challenged. I also enjoy troubleshooting and learning about how systems launch and function. While my day-to-day is more centered around networks and servers, I’m always up for diving into OS-related topics when the opportunity arises.