Total Boot Failure After Removing Second SSD - Win 10

Anonymous
2022-07-14T20:03:36+00:00

Windows 10: I have a primary disc for the OS and a secondary disc for just data (or maybe not???). I took out the secondary disc (in order to a bigger one in) and rebooted. I got a boot failure and Windows automatically tried to repair the issue, but it failed. I then replaced the secondary disc (so system is back as it was), but this did not solve the problem. During the "automatic repair process" it must have broken something.

The only thing that comes to mind is I may have split the pagefile to both discs, so when I took the data disc out it may have gotten confused.

So far, I have seemingly tried all of the "safe mode" options, other than than an option to restore a new Win 10 OS (last resort). I'd like to be able to at least somehow get into the OS so I can can deactivate licenses and put them on a new computer. At least some way to transition stuff to a new computer.

I guess in prior Windows versions (I'm still old school dating to 3.11), but this thing would not have happened. It all started with an automatic repair process that changed things such that putting the drives back "as is" didn't resolve it.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

50 answers

Sort by: Oldest
  1. Anonymous
    2022-08-03T01:48:14+00:00

    It sounds like your BIOS is set right. I wish I had another thought &/or a 50% better brain. I can't say I have any greater faith in MSFT than you have expressed. They've got geniuses but do they put them at the other end of the phone? Try to get a commitment for a fix that isn't a clean install before you part with money. Good luck & keep us informed.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-09-22T13:16:25+00:00

    Been a while, but here is an update. I contacted MS and they elevated it twice (I talked to 3 people in total). I pointed to this thread as well. He said there was nothing I could do and I think he did "reasonable" diligence, but didn't put a lot of effort into either. I am keeping the computer as is still and maybe there is a local person I could still take it to mess around with it. Its definitely still highly desirable to get it up and running, but maybe I am out of options.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-09-23T02:23:27+00:00

    Thanks for the update. It's disappointing even Microsoft has no answer. What kills me is that SFC & DISM wouldn't run no matter how many switches we used. Did they have a reason for that? But those two often won't be a fix even when they do run, anyhow. Still, SFC just sits on a blinking cursor with no progress bar, & DISM says...

    "

    Error: 4448

    An error occurred accessing the temporary folder E:\Windows\Temp\C7D2F3DE-C3DA-4CF3-9018-C82B21BB9D6

    Ensure the path to the temporary folder exists and that you have Read/Writer permissions on the folder.

    "

    It doesn't make sense that DISM was able to create that subfolder then complain it can't access it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-03T16:07:00+00:00

    Unfortunately, I don't think we got into specifics. He read the thread so presumably he was aware of this, but its also possible he was like "well this is out of my league now". I suspect there may still be a way to fix it, but you need a super guru, ha. Or maybe its toast!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-10-03T18:47:21+00:00

    OK. Well, one last long shot. At the BIOS Security screen, check that no password has been activated, on the HDD especially. I doubt it because I'm sure you'd have been asked for a password if so, but it's all I've got left. Good luck & keep us informed.

    Was this answer helpful?

    0 comments No comments